Anonymous

Changes

From Rare Gaming Dump
186 bytes added ,  20:26, 14 February 2021
Added back image
Line 3: Line 3:     
The NDEV features all the ports and functionality found on a retail system, as well as 3 additional USB ports and one additional serial (DB9) 115200-baud port for disc emulation and host communication. 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 emulated by an [[ODEM]] program on the host system.
 
The NDEV features all the ports and functionality found on a retail system, as well as 3 additional USB ports and one additional serial (DB9) 115200-baud port for disc emulation and host communication. 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 emulated by an [[ODEM]] program on the host system.
 
+
[[File:Ndevpreprodback.png|alt=The back of a pre-production NDEV 2.1 (same as final except for stickers)|thumb|The back of a pre-production NDEV 2.1 (same as final 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 ports.
 
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 ports.