DJWillis
Random GP32/GP2X/Wiz & Pandora Moocher
Ninjia^ posted on Oct 21 2005 at 08:19 AM said:The Firmware and Software are totally seperate from one another, to use your PC analogy its like the BIOS and the Operating system. You dont need to flash the BIOS everytime you reinstall windows...
So even If you screw up the Software in some way all you will need to do is replace it with a backup of the original, and as the firmwares untouched theres no way it would brick the unit.
Whilst you are somewhat correct, in the case of the GP2X and most embedded devices, screwing up the Linux disk image or anything on the NAND could be a "very bad thing(tm)".
All the default stuff stored in NAND really should stay un-tampered unless you know what you’re doing as you can brick your unit if you make a mistake.
Of course GPH upgrades (and community ones in time I am sure) are a different matter as they will be self contained upgrades with verification, tested etc. etc.
The way to look at it is…
BIOS Equivalent = U-Boot Boot loader
O/S Kernel = Linux Kernel 2.4.25 (Brings the hardware up etc.)
O/S Environment = Disk Image using various Linux tools, GPH’s launcher, shared libs etc. etc.
If you, for example, stuff up the shared libs or break the GPH launcher trying to skin it you would be left with a unit that to all intents failed to boot as it does not get far enough into the boot to pass control out to the screen, d-pad etc.. (i.e. Bricked).
Now with no way to get into Linux the Linux based firmware loader from GPH becomes sort of useless so you would then have to result to hooking a serial lead up to your GP2X’s EXT port (or maybe USB in later revisions) and logging into the console to try and fix your install (assuming you can get into the shell to run a fix).
If you can’t get into the shell then the best course of action is to rewrite the disk image and/or kernel (via serial and U-Boot) and that can take a while and a bit of knowledge of how the memory is laid out in the GP2X is very essential. If you screw that up you’re getting into jTAG reflashing territory .
In simple terms, most people did not hack about with the old GamePark launcher and reflash there firmware all the time, the combination of Boot loader, Kernel and Disk image warrants the same level of respect .
Some people will mess about with these items (I have extensively and I plan to do a lot more messing about with the kernel and boot loader) but I would not recommend it unless you have the tools to dig yourself out of the hole or your using well tested code and/or methods .
Basic tools are a serial lead to plug into the EXT and maybe a jTag if firmware hacking about is your thing . Just in case .
Last edited by a moderator: