685
edits
Changes
Jump to navigation
Jump to search
m
Moved hardware info to it's own section
Line 16:
Line 16:
Development on the NDEV is done firstly using the Revolution SDK supplied by Nintendo, which creates a file with the .elf extension. This file is then thrown through a sequence of applications which burn the game into a disc image that can be then loaded into the devkit using a command. Such an image can also be loaded onto an RVT disc, a special variant of the Wii Disc that can be read by the Wii and launched on development kits such as the [[RVT-R Reader]]. These development kits did not have the same development functionalities as the NDEV, but allowed for writing errors and launching non-retail games. They served a useful purpose for testers, who didn't need the programming functions offered by the significantly more expensive NDEV. The NDEV can, however, directly read .elf files without needing to burn them into a disc image beforehand through the "ndrun" command in the Revolution SDK to launch the optical disc emulator to create a simulated optical disc image. This runs the associated .elf directly from a filesystem on the host PC.
The '''NDEV''' ('''RVT-001''' on NDEV 2.x units, '''RVD''' on NDEV 1.x units) is a fully-fledged development kit for the [[Wii]]. It does not have a disc drive or internal hard drive, so all software is read from NAND or the host system. The NDEV cannot boot without an attached host system, and can only launch disc titles if they are given to the NDEV through an optical disc emulator on the host system. The NDEV thus, uses a special system menu that is designed for purposes of debugging and development. The NDEV could operate in two distinct modes: one mode which simulates a disc's read speed and another, a turbo mode, that reads data as quickly as possible, shortening the potential wait times during a test. This allows developers to cut down testing times, while also ensuring that their games were optimized enough to cut down on loading times through an actual disc.
The '''NDEV''' ('''RVT-001''' on NDEV 2.x units, '''RVD''' on NDEV 1.x units) is a fully-fledged development kit for the [[Wii]]. It does not have a disc drive or internal hard drive, so all software is read from NAND or the host system. The NDEV cannot boot without an attached host system, and can only launch disc titles if they are given to the NDEV through an optical disc emulator on the host system. The NDEV thus, uses a special system menu that is designed for purposes of debugging and development. The NDEV could operate in two distinct modes: one mode which simulates a disc's read speed and another, a turbo mode, that reads data as quickly as possible, shortening the potential wait times during a test. This allows developers to cut down testing times, while also ensuring that their games were optimized enough to cut down on loading times through an actual disc.
+Development on the NDEV is done firstly using the Revolution SDK supplied by Nintendo, which creates a file with the .elf extension. This file is then thrown through a sequence of applications which burn the game into a disc image that can be then loaded into the devkit using a command. Such an image can also be loaded onto an RVT disc, a special variant of the Wii Disc that can be read by the Wii and launched on development kits such as the [[RVT-R Reader]]. These development kits did not have the same development functionalities as the NDEV, but allowed for writing errors and launching non-retail games. They served a useful purpose for testers, who didn't need the programming functions offered by the significantly more expensive NDEV. The NDEV can, however, directly read .elf files without needing to burn them into a disc image beforehand through the "ndrun" command in the Revolution SDK to launch the optical disc emulator to create a simulated optical disc image. This runs the associated .elf directly from a filesystem on the host PC.
+
+== Hardware ==
Compared to regular hardware, the NDEV features all the ports found on a retail system. The NDEV has a mains power switch on the back, and an actual power switch located on the front of the unit. All GameCube controller ports, SD reader, and GameCube memory card ports have been moved up to the front of the unit. There is also a dipswitch located on the front, which could be used for debugging purposes. For example, toggling processor usage UI. Also on the front lies multi-purpose LED display, activity diodes for the console's components, a power button with a diode, as well as reset, sync and eject buttons. Eject is likely intended to emulate a console ejecting a disc. There is also a button with labelled reserved. This button seemingly never served any type of function. On the back of the NDEV, there are two USB Type A ports as found on a retail systems, however, there is also three USB Type B ports not seen on retail systems. One of these is labeled as a debug port, used for collecting the debug output of games running. One is labeled as COM, used to send commands to the unit. Finally, one is labeled DI. There is also one serial (DB9) 115200-baud port. In order to use the devkit, there needs to be at least three USB cables plugged into the same computer; one as a software link, another as a data link, and also another for debugging. The instruction manual of the NDEV also states that there needs to be a serial cable plugged in, but that's just optional and the system will launch without it.
Compared to regular hardware, the NDEV features all the ports found on a retail system. The NDEV has a mains power switch on the back, and an actual power switch located on the front of the unit. All GameCube controller ports, SD reader, and GameCube memory card ports have been moved up to the front of the unit. There is also a dipswitch located on the front, which could be used for debugging purposes. For example, toggling processor usage UI. Also on the front lies multi-purpose LED display, activity diodes for the console's components, a power button with a diode, as well as reset, sync and eject buttons. Eject is likely intended to emulate a console ejecting a disc. There is also a button with labelled reserved. This button seemingly never served any type of function. On the back of the NDEV, there are two USB Type A ports as found on a retail systems, however, there is also three USB Type B ports not seen on retail systems. One of these is labeled as a debug port, used for collecting the debug output of games running. One is labeled as COM, used to send commands to the unit. Finally, one is labeled DI. There is also one serial (DB9) 115200-baud port. In order to use the devkit, there needs to be at least three USB cables plugged into the same computer; one as a software link, another as a data link, and also another for debugging. The instruction manual of the NDEV also states that there needs to be a serial cable plugged in, but that's just optional and the system will launch without it.
Unlike the Wii, the NDEV has a built-in power supply, whereas retail models have an externally placed power supply. The NDEV's GDDR3 RAM (MEM2) is upgraded from 64MB to 128MB, giving it a total of 192MB of RAM, up from the retail Wii's 88MB total.
Unlike the Wii, the NDEV has a built-in power supply, whereas retail models have an externally placed power supply. The NDEV's GDDR3 RAM (MEM2) is upgraded from 64MB to 128MB, giving it a total of 192MB of RAM, up from the retail Wii's 88MB total.
−== NDEV Menu ==
== NDEV Menu ==