3dbrew - User contributions [en]

2.1.0-3

2021-03-17T07:53:24Z

LinkSoraZelda:

The 2.1.0-3 system version released on June 15, 2011 for the original Nintendo 3DS.
The official patch notes for this firmware notes "Improvement to system stability and convenience."

Beginning in early 2016, 2.1.0-3 was installed onto the system's NAND as a necessary installation step for arm9loaderhax[https://www.3dbrew.org/wiki/3DS_System_Flaws#arm9loader], to retrieve a console-specific OTP dump.
As this firmware naturally didn't release for any console aside from the CTR-001 Nintendo 3DS, installation on newer devices nets known issues such as corrupted screen data, softlocks, and potential to software brick on FTR-001/Nintendo 2DS units upon formatting the console.

2.1.0-3

2021-03-17T07:50:21Z

LinkSoraZelda:

The 2.1.0-3 system version released on June 15, 2011 for the original Nintendo 3DS.
The official patch notes for this firmware notes "Improvement to system stability and convenience."

Beginning in early 2016, 2.1.0-3 was installed onto the system's NAND as a necessary installation step for arm9loaderhax, to retrieve a console-specific OTP dump.
As this firmware naturally didn't release for any console aside from the CTR-001 Nintendo 3DS, installation on newer devices nets known issues such as corrupted screen data, softlocks, and potential to software brick on FTR-001/Nintendo 2DS units upon formatting the console.

Setting up Development Environment

2018-04-12T01:16:32Z

LinkSoraZelda: Fixed dead link to latest DKP perl script

= Setup =
* Install [https://devkitpro.org/ devkitARM]. If it's already installed, update it.
** On Windows, there's a [https://github.com/devkitPro/installer/releases/latest graphical installer].
** On Unix-like platforms such as Linux/macOS, there's a [https://raw.githubusercontent.com/devkitPro/installer/master/perl/devkitARMupdate.pl Perl script]. Make sure you also select libctru and the 3ds examples when installing.
* Depending on the kind of homebrew you want to develop, you may be interested in installing and using additional libraries and tools which don't ship alongside devkitARM/libctru. A list of them can be found in [[Homebrew Libraries and Tools]].

==Windows==
devkitPro provides Win32-native precompiled versions of devkitARM which can be run directly on Windows.
* [https://github.com/devkitPro/installer/releases/latest download the latest version of the graphical installer] from SourceForge and run it, following the instructions as you go.
* An Internet connection is required.
* You will want to make sure devkitARM is selected during the installation process to develop for the 3DS (and also the DS and GBA) - you can also install devkitPPC (for GameCube/Wii development) and devkitPSP (for PlayStation Portable development) if you wish.
* Once the installer has finished, launch MSYS from:
** Windows 7 and earlier: Start -> All Programs -> devkitPro -> MSYS
** Windows 8 and 8.1: Right click on the Start screen and select 'All Apps'. You should find MSYS there.
** Windows 10 (pre-Anniversary Update): Start -> All Apps -> devkitPro -> MSYS
** Windows 10 (post-Anniversary Update): Start -> devkitPro -> MSYS

Alternatively starting with Windows 10 Anniversary Update (Version 1607), the [https://msdn.microsoft.com/en-us/commandline/wsl/install_guide Windows Subsystem for Linux (WSL)] may also be used to run the Linux version of devkitARM. Unless you have some particular need for WSL it's recommended that you stick to a more standard environment.

==Unix-like platforms==
Currently devkitPro provides precompiled versions of devkitARM for the following Unix-like platforms: Linux (x86/x64), macOS (universal binary). Note that Linux x64 binaries are usable under WSL.

* First, you need to install curl so the installer can download the devkitARM packages, and you should also install Git - you'll need it to update libctru or share your code on GitHub, among many other things. If you are running Linux, you'll also need wget; it comes preinstalled on most distributions, but not all.

* Find your way into a shell (eg. by opening a Terminal window), and follow the instructions for your OS:
** Debian/Ubuntu/Linux Mint/Ubuntu on WSL: <code>sudo apt-get install git curl</code>
** Fedora/CentOS/RHEL: <code>sudo yum install git curl</code>
** openSUSE: <code>sudo zypper install git curl</code>
** Arch Linux/ALWSL: <code>sudo pacman -S git curl wget</code>
** macOS: Download Git from [http://git-scm.com/download/mac] and install it. Curl is included with the OS.

* Next, we need to download, make executable and run the devkitARM updater (don't worry, the updater is also the installer.)
<pre>
curl -L https://github.com/devkitPro/installer/releases/download/v2.2.1/devkitARMupdate.pl -o devkitARMupdate.pl
chmod +x ./devkitARMupdate.pl
sudo ./devkitARMupdate.pl /opt/devkitpro
</pre>

* Finally, we need to tell your shell where to find the devkitARM binaries.
<pre>
echo "export DEVKITPRO=/opt/devkitpro" >> ~/.bashrc
echo "export DEVKITARM=/opt/devkitpro/devkitARM" >> ~/.bashrc
source ~/.bashrc
</pre>

= Building the examples =
3DS examples are still being created; however, there are a growing number of examples available from the [https://github.com/devkitPro/3ds-examples devkitPro/3ds-examples GitHub repository].
There are now too many to list here in detail, so go ahead and browse them.

* To download these, if you installed Git (as you will have if you followed the above instructions), simply type <code>git clone https://github.com/devkitPro/3ds-examples.git</code> into your shell in the directory you wish to store the 3ds-examples folder in.

These can be built from the command line.

To start a new homebrew project from the <code>bash</code> shell, simply type the following (replacing <code>'''~/projects/my3dsproject'''</code> with the place you would like your project to be stored, with <code>~</code> meaning your HOME directory):
cp -r $DEVKITPRO/examples/3ds/templates/application '''~/projects/my3dsproject'''
cd '''~/projects/my3dsproject'''

The standard Makefile will use the folder as the name of the 3dsx that will be built. You can keep that behaviour or simply change the <code>TARGET := $(notdir $(CURDIR))</code> line in the Makefile to explicitly name your project.

To compile it, type <code>make</code> in the project directory.

==Running your code==
To run it on your 3DS, start the Homebrew Launcher, press Y to open the network loader, then on your PC type: <code>$DEVKITARM/bin/3dslink '''my3dsproject'''.3dsx</code>, replacing '''my3dsproject''' with the name of the 3dsx file you want to run.)

If all goes well, you'll soon see your application running on your 3DS.

==Building the examples on Linux with Netbeans==
* Go to File->New Project...
* Select C/C++ Project with existing code
* Navigate to the examples directory and select the folder for the project you want to build; eg. /home/vtsingaras/3ds/examples/app_launch
* Leave Configuration Mode to 'Automatic' and click 'Finish'.
* It will fail to build. Now edit Makefile and insert these two lines, adjusting for your devkitpro path, at the top:
<pre>export DEVKITPRO=/opt/devkitpro
export DEVKITARM=/opt/devkitpro/devkitARM</pre>
* Right-click the project and go to Properties->Code Assistance and click C Compiler.
* In include directories enter
<pre>/opt/devkitpro/devkitARM/include;/opt/devkitpro/libctru/include</pre>
adjusting again for your devkitPro path.
* Do the same for 'C++ Compiler'.
* Go to 'Run' and click 'Clean and Build Project'.
* Now right-click on the project and select Code Assistance->Reparse Project.

Now you can use Netbeans' code completion feature and build your project from the Run menu.

= Troubleshooting =
'''I get the "Please set DEVKITARM in your environment." error.'''

Use the following command before installing [http://askubuntu.com/questions/573070/problem-setting-up-environment-for-make-command-execution]:
sudo chown $USER /opt/devkitpro/ -R
echo "export DEVKITPRO=\"/opt/devkitpro/\"" >> ~/.profile
echo "export DEVKITARM=\"\${DEVKITPRO}/devkitARM/\"" >> ~/.profile
source ~/.profile

For WSL users, you need to close the Bash shell, then reopen it for WSL to reload all of the variables from a clean state.

Mysteries

2017-10-18T19:41:41Z

LinkSoraZelda: /* Is there more than one revision of the bootrom? */

The following is a list of mysteries.

== General ==
* What is the CTR abbreviation?
: C may stand for Chiheisen ("horizon" in Japanese, the O3DS's codename being "Project Horizon").
:: Not true, Horizon refers to the OS.

== Hardware ==
=== Why are there two CTRCARD controllers? ===
'''Background:''' Also [http://problemkaputt.de/twl-core.jpg DSi SoC pinout] shows evidence of dual NTRCARD controllers on the final DSi SoC. (This was a [http://i.imgur.com/0kJlbEw.png planned feature] of the DSi before being axed later in development)

=== Why are there two EMMC controllers? ===
'''Theory:''' At some point during 3DS hardware development there was an idea to split up CTR and TWL nand into two different chips.
=== Is there a JTAG? ===
=== Is there more than one revision of the bootrom? ===
'''Background:''' Bootrom visible portion has been dumped on 3DS, 3DSXL, 2DS, New3DS, New 2DS, and even the Tegra-based unit. All matching exactly.

=== What is the EMMC controller @ 0x10100000 doing? ===
'''Background:''' There's dead code in NWM referencing it.
=== Why did they put NTRCARD accessible from ARM11? ===
'''Theory:''' At some point during 3DS hardware development there was a concept where ARM11 ran a menu with DS(i) icons while ARM9 was in TWL mode.

=== Is there a secret message embedded in the 3DS keyscrambler constant? ===
'''Background:''' TWL key scrambler constant was "Nintendo Co., Ltd" in Japanese ("任天堂株式会社"), UTF-16LE encoded, with byte order mark. The 3DS key scrambler constant, by comparison, is random-looking.

=== What is the PDN abbreviation? ===
: Power distribution network

=== How does Nintendo reflash bricked systems? ===
'''Theory:''' Before trying to boot from NAND, the bootrom checks to see if a key combination (Start + Select + X) is being held, and whether the shell is closed. If so, it tries to boot from an inserted NTR (Nintendo DS) cartridge.
This allows to execute a FIRM that is probably used by Nintendo to reflash the system.

== Software ==
=== What was the problem in "initial program loader" that was mentioned in an FCC filing by Nintendo for 2DS? ===
'''Background:''' http://www.neogaf.com/forum/showthread.php?t=814624&page=1
=== What did SVC 0x74 in the ARM11 kernel do before it got stubbed? ===
=== What is the PTM abbreviation? ===
: Power/time management

=== Why is the DTCM not used anywhere except bootrom? ===
'''Background:''' Bootrom is known to use part of DTCM as state, memsetting it to 0 when it's done. After that, it is never used again.
=== How is CTRAging launched during factory setup? ===
'''Background:''' No TestMenu version is capable of launching CTRAging directly: O3DS factory TestMenu can only launch DevMenu installed on NAND, the inserted cartridge and the TWL/AGB test apps; N3DS factory TestMenu can only launch DevMenu installed on NAND, the inserted cartridge and System Settings.

'''Theory:''' NtrBoot another time
=== Why are there 4 stubbed syscalls named SendSyncRequest1-4? ===