Changes

The '''NDEV''' ([[RVL Product Codes|product code]] '''RVT-001''') is the main development system for the Wii, taking the form of a black box including full Wii hardware with 192MB of RAM (the retail system has 88MB; the GDDR3 area on the NDEV is expanded from 64MB to 128MB, as with the [[RVT-H Reader]]) as well as debugger, optical disc emulation, and Host I/O hardware.

The '''NDEV''' ([[RVL Product Codes|product code]] '''RVT-001''') is the main development system for the Wii, taking the form of a black box including full Wii hardware with 192MB of RAM (the retail system has 88MB; the GDDR3 area on the NDEV is expanded from 64MB to 128MB, as with the [[RVT-H Reader]]) as well as debugger, optical disc emulation, and Host I/O hardware.

The NDEV features all the ports and functionality found on a retail system (minus a physical disc drive), as well as 3 additional USB ports and one additional serial (DB9) 115200-baud port. 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 served using [[ODEM]] on the host system.

The NDEV features all the ports and functionality found on a retail system (minus a physical disc drive), as well as 3 additional USB ports and one additional serial (DB9) 115200-baud port. 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 served using [[ODEM]] on the host system.

[[File:Ndevpreprodback.png|alt=The back of a pre-production NDEV 2.1 (same as final except for stickers)|thumb|NDEV back (pre-production 2.1 unit; the back is the same as the production unit except for stickers)]]

[[File:Ndevpreprodback.png|alt=The back of a pre-production NDEV 2.1 (same as final except for stickers)|thumb|NDEV back (pre-production 2.1 unit; the back is the same as the production unit except for stickers)]]

The typical development flow using an NDEV is to use the "ndrun" command in the [[Revolution SDK]] to launch ODEM to create a simulated optical disc image which runs the associated ELF directly from a filesystem on the host PC. Debug output can be gathered over the serial port as well as through the [[CodeWarrior IDE]] using the debug USB port.

The typical development flow using an NDEV is to use the "ndrun" command in the [[Revolution SDK]] to launch ODEM to create a simulated optical disc image which runs the associated ELF directly from a filesystem on the host PC. Debug output can be gathered over the serial port as well as through the [[CodeWarrior IDE]] using the debug USB port.