G16 firmware dump

fe50

3152
IXUS50 & 860, SX10 Star WARs-Star RAWs

Re: G16 firmware dump

« Reply #10 on: 02 / May / 2014, 04:04:03 »

Advertisements

Hello & welcome !

Quote from: kitemonkee on 22 / April / 2014, 11:17:28

here is my Canon PowerShot G16 firmware dump:
https://drive.google.com/file/d/0B9hf-atVx4uwQk9raFBfa3BPS28/edit?usp=sharing
ver.req didn't work, CameraVersion says it is version: 1.00 rev 8.00
i wish i was be able to contribute more...

Your firmware version is 1.00H
There's already a g16 1.00h dump in our repository - anyway: thanks for your dump

Logged

-->FIRMWARE DUMPS<-- * Manual * Lua * me

waterwingz

12140

Re: G16 firmware dump

« Reply #11 on: 04 / February / 2017, 22:23:45 »

Had a chance today to look at the posted firmware dumps for the G16 1.00H and 1.01A.

Right off the bat, it was interesting that they are 2x the size of the dumps for other DIGIC6 cameras like the SX280, G7X, and SX60. And then the capstone based sigfinder2 basically barfed on parsing those PRIMARY.BIN files when I tried to build a CHDK version for the G16. It didn't really find much useful at all.

So I ran the latest version of the Universal Dumper on a G16 that I had "laying around". And I got a much more useable file - something that results in a stubs_entry.S file equivalent to the sx280.

While I expect this is most likely an issue with the memory offset issues that the dumper used when the G16 firmware was dumped, it does suggest that the existing PRIMARY.BIN files for the G16 are not useful in their present form.

Logged

Ported : A1200 SD940 G10 Powershot N G16

srsa_4c

4451

Re: G16 firmware dump

« Reply #12 on: 05 / February / 2017, 09:35:06 »

Quote from: waterwingz on 04 / February / 2017, 22:23:45

While I expect this is most likely an issue with the memory offset issues that the dumper used when the G16 firmware was dumped, it does suggest that the existing PRIMARY.BIN files for the G16 are not useful in their present form.

That's true. Fortunately, all data we need is there, it just needs to be extracted manually.

Quote

a G16 that I had "laying around"

Are you planning to work on it?

Logged

waterwingz

12140

Re: G16 firmware dump

« Reply #13 on: 05 / February / 2017, 10:44:52 »

Quote from: srsa_4c on 05 / February / 2017, 09:35:06

Quote from: waterwingz on 04 / February / 2017, 22:23:45
While I expect this is most likely an issue with the memory offset issues that the dumper used when the G16 firmware was dumped, it does suggest that the existing PRIMARY.BIN files for the G16 are not useful in their present form.
That's true. Fortunately, all data we need is there, it just needs to be extracted manually.

I have what seems to be a "good" dump of one version. I think I can just write a little "one off" C utility to binary strip the other dump so that it looks the same.

Quote

Quote
a G16 that I had "laying around"
Are you planning to work on it?

Logged

Ported : A1200 SD940 G10 Powershot N G16

nafraf

1308

Re: G16 firmware dump

« Reply #14 on: 05 / February / 2017, 12:11:00 »

Quote from: waterwingz on 05 / February / 2017, 10:44:52

I think I can just write a little "one off" C utility to binary strip the other dump so that it looks the same.

You don't need to write C code. You can use dd linux command.

Logged

waterwingz

12140

Re: G16 firmware dump

« Reply #15 on: 05 / February / 2017, 12:32:15 »

Quote from: nafraf on 05 / February / 2017, 12:11:00

Quote from: waterwingz on 05 / February / 2017, 10:44:52
I think I can just write a little "one off" C utility to binary strip the other dump so that it looks the same.
You don't need to write C code. You can use dd linux command.

Or a hex file editor .. although trying to C&P many megs of binary is painful. I'm not in a big hurry either way.

EDIT: the dd solution was easier that I thought (props to nafraf). I've PM'd @fe50 with a download link for the two modified PRIMARY.BIN files. They are now the "right" size and will allow a successful build when C&P'd into the sx280 sub folders. Naturally, the result won't run on a G16 or sx280 but it does mean I now have usable dump files.