But what happens when the .fxe (or .gxb) tries to read/write the EEPROM? I thought that only the FW can do that, and also what if it writes to EEPROM that the current FW is using??
FW (excluding the low 32k BIOS) is actually a normal GXB file.. There is no protection or control against writing to EEPROM.. or Flash. Any program can do it. Currently what is holding back all those *bad jokes* that erase your Flash or mess up the EEPROM.. or generally using EEPROM to save data is the lack of information. Both EEPROM read/write and Flash read/write procedures are not documented anywhere nor public sources are available :unsure: Maybe it's good in a way as those who really want to play with those can most probably also reverse engineer the needed information h34r:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.