DS-Xtreme OpenSource Firmware Project

DS-Xtreme OpenSource Firmware Project The scope of this project is to open up the DS-Xtreme flash cartridge hardware/firmware for homebrewers to modify. I have asked the DSX for the information prior on embarking on this project. No information was forthcomming. Please remember that this wiki is updated and maintained by YOU - Please help out where you can!

Project Plan I propose the following tasks to achieve that goal. 01) Do Under The Hood research on the DS-X hardware for an insight into what the firmware may be. --DONE-- 02) Acquire all the files that make up the firmware. --DONE-- 03) Disassemble the PC application that updates the firmware. --IN PROGRESS-- 04) Create a new, "OpenSource" updater application based on the knowledge gained. 05) Disassemble the core8051 EZ-USB controller firmware. 06) Create a new, "OpenSource" firmware from the knowledge gained. 07) Disassemble the configuration for the FPGA. 08) Create a new, "OpenSource" project from the knowledge gained.. 09) Disassemble the native NDS application (the launcher) 10) Create a new, "OpenSource" launcher from the knowledge gained.. 11) Using the knowledge gained make some schematics of the DS-X cartridge. This order was chosen because the firmware "update.bin" is one large zipped?, binary file. So first we have to decompile the updater application to understand how its zipped and what parts make up the USB, FPGA and NDS launcher....

Firmware Realease V1.1.0 (Shuny Files)

V1.1.0 Launcher skin files
V1.1.0 USB/FPGA/Launcher firmware
V1.1.0 Updater application info file
V1.1.0 PC Updater application

V1.1.2 Updater Files (DSX Current Files)

[[1]] Launcher skin files.
[[2]] USB/FPGA/Launcher firmware.
[[3]] Updater application info file
[[4]] PC Updater application

Recovery Tool

[[5]] Cypress Windows XP Drivers for the USB Controller.
[[6]] The recovery tool (this seems identical to the updater).

Work In Progress Log

5th January 2008:

Initial viewing of the PC Updater tool yields the following information.

1) The updater was coded with Borland Delphi development enviroment in C/C++.
2) The updater contains ZLIB compression librarys (probabily for the firmware).
3) The updater contains Altera Jam FPGA communication librarys (maybe for the JTAG connector on the circuit board).
4) The updater contains Mozilla/3.0 (compatible; Indy Library).
5) The Updater contains Cypress USB communication librarys.

On running the updater, it uses windows sockets api to download update.txt and update.bin from the DSX server. The mozilla api is probabily the wrapper to call the windows sockets api, for platform independancy. Delphi also has wrappers for the application windows. The applications resources can easily be pulled out with XN Resource editor. I've also noticed on some of the disassembly that the updater looks like it can take command line arguments?

ToDo:

I'm currently trying out a few disassemblers on the .exe to see which gives me the best results.
The hardware investigations need putting on the wiki on a seperate page.
The files need moving to a seperate wiki page.

All in all not bad going for a weak lameass like me :)