universal dumper - one more idea - page 7 - Firmware Dumping - CHDK Forum

universal dumper - one more idea

  • 63 Replies
  • 36833 Views
*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: universal dumper - one more idea
« Reply #60 on: 04 / October / 2008, 11:39:55 »
Advertisements
hm, on my s3is using the vxworks method this doesnt seem to work.
i prepare the 16 mb sdcard, lock it, put it into cam, press play, wait a minute, take out batteries, take out card. empty.dum is empty :(

edit: doesnt seem to work with previous (1.38) cardtricks/udumper version
« Last Edit: 04 / October / 2008, 11:51:13 by PhyrePhoX »

*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: universal dumper - one more idea
« Reply #61 on: 04 / October / 2008, 12:27:08 »
@PhyrePhox

Could it be that your empty.bin (16 Mb since introduction udump08) is bigger than the card ?
(empty.bin = 16.777.216 bytes to be exact)
If it is, trim off some bytes in a hexeditor to make it fit the card, or use bigger card

I tested the vxworks udumper on A630 and ixus70 and it worked OK  ???
I'll DL from archive and test again done, worked OK on ixus70 (FF81 0000) and a620 (FFC0 0000)

wim
« Last Edit: 04 / October / 2008, 12:58:14 by whim »

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: universal dumper - one more idea
« Reply #62 on: 04 / October / 2008, 12:56:08 »
jup, that was the reason. now i also saw that the windows cmd window was showing an error (copying empty.dum).
so you should check for cards that are 16 MB in size or smaller - these probably will not work.

also, my 4gb card doesnt work as well, though i think cardtricks does manage it to format it in fat16? dont know why it didnt work. anyhow, managed to get a dump using a 2 gb card. thanks!

*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: universal dumper - one more idea
« Reply #63 on: 04 / October / 2008, 13:13:15 »
@PhyrePhox

It's true that 16 Mb is exaggerated, in CT i assure empty.dum gets written first, offset in udump is 2048 sectors of 512 byte
= 0x100000. Max dump is FFFF FFFF - FF81 0000 = 7F0000 (starting calculator)

max. needed = 9.371.648 / 0x8F0000 hex. So 10.420.224 / 0x9F0000 hex should be plenty.

I will adjust this in CT 1.40 AND add a card size test, thanks for debugging  :D


wim


 

Related Topics