Quote:
|
Originally Posted by ShamrockMan
I dont have the update fully reverse engineered yet, as it still fails. I need a working PMP or emulator so I can figure out what is wrong. If the directory bug, or the invaild image bugs can be exploited, that would be better since people will not need to risk flashing the pmp.
|
Ok. You have not yet get a working PMP on ebay ?
I have worked a bit on the firmware. I don't understand what is sys.img ! Can sby light me about this file ?
Apparently, there are redondancies between the firmware file allimg.hex and the sys.img (which may be included in it and filled with data found in PmpVersion.defs). And there are big similarity between... I don't understand.
My tonight work gave me that :
[code]
0x00000000-0x0000000F : firmware header
->0x00000000-0x00000001 : major firmware version = PmpVersion.defS->USER_MAJOR
->0x00000002-0x00000003 : minor firmware version = PmpVersion.defS->USER_MINOR
->0x00000004-0x00000005 : major rrload version ? = PmpVersion.defS->PMP_RRLOAD_VER
->0x00000006-0x00000007 : minor rrload version ? = PmpVersion.defS->PMP_CODEC_VER
->0x00000008-0x00000009 : firmware checksum = PmpVersion.defS->PMP_KERNEL_VER
->0x0000000A-0x0000000B : region code = PmpVersion.defS->BMPVERSION
->0x0000000C-0x0000000D : region code
[code]
CRC computation :
memory data area from firmware : 0x00000010-00400000
C code found in ./fs/inputserv/checksysimg/crc.c