SX280 HS 101B Dump - I am truly willing to help test if someone develops - page 5 - Firmware Dumping - CHDK Forum

SX280 HS 101B Dump - I am truly willing to help test if someone develops

  • 54 Replies
  • 24525 Views
Re: SX280 HS 101B Dump - I am truly willing to help test if someone develops
« Reply #40 on: 26 / October / 2013, 08:49:30 »
Advertisements

I'm mostly interested in RAW saving - any option to get hold of that without having to go through the whole problematic stage of hacking the entire software?

Re: SX280 HS 101B Dump - I am truly willing to help test if someone develops
« Reply #41 on: 26 / October / 2013, 09:26:24 »
I'm mostly interested in RAW saving - any option to get hold of that without having to go through the whole problematic stage of hacking the entire software?
No.  You have to get almost all of the hard parts done in order to get enough of CHDK running to save RAW.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SX280 HS 101B Dump - I am truly willing to help test if someone develops
« Reply #42 on: 08 / February / 2014, 06:13:54 »
Where are the Profis i wait and wait for canon sx270

Re: SX280 HS 101B Dump - I am truly willing to help test if someone develops
« Reply #43 on: 08 / February / 2014, 10:50:02 »
Where are the Profis i wait and wait for canon sx270
link> CHDK FAQ : My camera isn't ported yet

and this link .
Ported :   A1200    SD940   G10    Powershot N    G16


Re: SX280 HS 101B Dump - I am truly willing to help test if someone develops
« Reply #44 on: 11 / February / 2014, 14:45:14 »
Vry fast answer
How can i help as beginner or other beginner people so that the porting faster
First Tools To begin or....
Sorry for my english

*

Offline reyalp

  • ******
  • 12072
Re: SX280 HS 101B Dump - I am truly willing to help test if someone develops
« Reply #45 on: 11 / February / 2014, 23:26:31 »
Vry fast answer
How can i help as beginner or other beginner people so that the porting faster
First Tools To begin or....
Sorry for my english
I'm afraid there is not much you can do. Porting to Digic 6 will require an experienced developer with access to a Digic 6 camera and a lot of time.
Don't forget what the H stands for.

*

Offline JvdP

  • ***
  • 174
if there is an experienced person on this forum who is interested in doing this but doesn't have a DIGIC6 camera, I could send one over to "borrow". Somebody interested in this?

*

Offline c10ud

  • ***
  • 245
As you can see from the s120 thread I finally managed to dump a firmware and I'd like to experiment a bit.

I am working on the first 16M of the 64M dump and I am a little unsure on the new "best practices"

what is the preferred toolchain? gcc464? (seeing srsa4c new thumb2 disasm script)


edit: my strategy is to copy the s110 code, replace the reset code with the new one and then the first part of the new boot....suggestions? dancing bits? :)
« Last Edit: 11 / March / 2014, 10:40:53 by c10ud »


*

Offline srsa_4c

  • ******
  • 3979
As you can see from the s120 thread I finally managed to dump a firmware and I'd like to experiment a bit.

I am working on the first 16M of the 64M dump and I am a little unsure on the new "best practices"

what is the preferred toolchain? gcc464?
You'll need something that can output ARM and Thumb-2 code for ARMv7. The CPU seems to know both instruction sets, the firmware is mostly Thumb-2, there is some thunk code that has ARM instructions.
The CHDK build makefiles/scripts will have to be altered more or less. Since copied fw code will be thumb-2, probably the whole CHDK should be compiled as thumb-2.
If correct support of this CPU family requires gcc 4.8+, even more parts of the CHDK tools will have to be rewritten due to the no longer available arm-elf ABI (I expect incompatibilities with arm-none-eabi)...
Quote
(seeing srsa4c new thumb2 disasm script)
You only need a recent binutils with ARM support for that.

Quote
edit: my strategy is to copy the s110 code, replace the reset code with the new one and then the first part of the new boot....suggestions? dancing bits? :)
Yeah, you'll likely still need dancing bits. You can use an s110 disassembly to help with locating the needed firmware functions. However, don't expect that you'll be able to get a usable CHDK build right away.

Oh, and you may want to dump a few MB of RAM too, the kernel is IMHO still located in RAM.

If you're serious with continuing, I'd suggest creating an S120 thread, so SX280 owners won't get the false impression.

*

Offline c10ud

  • ***
  • 245
As you can see from the s120 thread I finally managed to dump a firmware and I'd like to experiment a bit.

I am working on the first 16M of the 64M dump and I am a little unsure on the new "best practices"

what is the preferred toolchain? gcc464?
You'll need something that can output ARM and Thumb-2 code for ARMv7. The CPU seems to know both instruction sets, the firmware is mostly Thumb-2, there is some thunk code that has ARM instructions.
The CHDK build makefiles/scripts will have to be altered more or less. Since copied fw code will be thumb-2, probably the whole CHDK should be compiled as thumb-2.
If correct support of this CPU family requires gcc 4.8+, even more parts of the CHDK tools will have to be rewritten due to the no longer available arm-elf ABI (I expect incompatibilities with arm-none-eabi)...
Quote
(seeing srsa4c new thumb2 disasm script)
You only need a recent binutils with ARM support for that.

Quote
edit: my strategy is to copy the s110 code, replace the reset code with the new one and then the first part of the new boot....suggestions? dancing bits? :)
Yeah, you'll likely still need dancing bits. You can use an s110 disassembly to help with locating the needed firmware functions. However, don't expect that you'll be able to get a usable CHDK build right away.

Oh, and you may want to dump a few MB of RAM too, the kernel is IMHO still located in RAM.

If you're serious with continuing, I'd suggest creating an S120 thread, so SX280 owners won't get the false impression.
Ofcourse I don't expect an usable build, but seeing the diskboot starting would be a little success (assuming things are more or less the same other than processor-specific bits)

I am serious on continuing but I don't own the camera and probably I'll have to ask for it once a while in order to test things.. Today I managed to dump the firmware and started looking into this thread for pointers but I see there is little progress

Navigating through all gcc/binutils versions is the biggest pain for me (already experienced with linux on arm)! I think that we could agree on some specific versions and start from that given that the usual automagic tools cannot be used...

I am in IRC now if someone wants to discuss

 

Related Topics