the sx20 porting thread

  • 1279 Replies
  • 180823 Views
*

Offline neszt

  • ***
  • 174
the sx20 porting thread
« on: 10 / October / 2009, 09:40:44 »
Advertisements
Hi All!

I have a new sx20, and i decided to help chdk porting.

First i dumped the firmware using blinker hardware, with help of RaduP (Thanx!)

Now i read many docs to see what kind of work it is. However, i'am a programmer, but i totally new to chdk, and i even not tried it on older camera, so being a new porter seems a dead idea..

I compared the sx10 and sx20 datasheets side by side and i see no differencies except the megapixel, and the hd video capability. Obviously this not means that the chdk porters need to change only few things, but probably means that sx20 porting could be easier taking the code of sx10 port. Am i right?

Anyway, i definitely can't start the porting, but i offer testing with my camera day by day if needed.

*

Offline yakabmarci

  • *
  • 16
  • sx20is
Re: the sx20 porting thread
« Reply #1 on: 12 / October / 2009, 13:19:30 »
same here,

got an sx20is, developer, no chdk experience, happy to test or help out in any ohter way

*

Offline jan

  • *
  • 48
  • PowerShot SX20 IS (100f)
    • cms -db
Re: the sx20 porting thread
« Reply #2 on: 13 / October / 2009, 07:20:25 »
I could help with testing, too, but I don't have skills in Assembler and C, so I can't help with coding.

*

Offline reyalp

  • ******
  • 10069
Re: the sx20 porting thread
« Reply #3 on: 14 / October / 2009, 02:21:33 »
Don't forget what the H stands for.


*

Offline neszt

  • ***
  • 174
Re: the sx20 porting thread
« Reply #4 on: 14 / October / 2009, 06:50:33 »
I set up a mini chdk developement environment just for playing. (chdk-shell under windows)

1. I made a copy form sx10 -> sx20 (new and only PLATFORMSUB: 100f)
2. I updated the Makefiles
3. I was able to compile
4. I replaced the AF led adressess with the new correct one.
5. I copied the new PRIMARY.BIN to the 100f dir
6. I got a lot of success signature found and a lot of "not found" during the make process
7. I inserted the missing signatures to the entry_2.S, with dummy (0xff81000) addresses
8. I got compile errors with unreferenced symols and i don't know why?
9. However i inserted the unrefenrenced symbol names from the sx10, to compile.
10. Now of course the new bootdisk.bin won't boot :)
11. I tried to debug with AF led blinking at the very first enrty point as the guide says, but nothing happens.

Now i'am stuck.

A. I know this is not the correct order of the porting, but it is only "playing". It is just a test for myself, to see my limitations. :)
B. I know the dummy addresses definitely breaks the boot process, but i don't know how to find the correct ones from the disassembled firmware.
C. I know there is more to do before try to boot.
D. However, i missed l ot of things, but, the AF LED should blinks, shouldn't it?

Thanx for RaduP the help for every 3 questions / step. :)

Sorry for lame description, i'll detail any point if not understable clearly.

*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: the sx20 porting thread
« Reply #5 on: 14 / October / 2009, 07:15:06 »
@neszt

Quote
1. I made a copy form sx10 -> sx20 (new and only PLATFORMSUB: 100f)
have you done this in both /platform and /loader ?

cheers,

wim

*

Offline neszt

  • ***
  • 174
Re: the sx20 porting thread
« Reply #6 on: 14 / October / 2009, 08:37:53 »
Yes, I made copies from all the required directories including /platform and /loader.

I suppose that was ok, because i was able to compile sx20 successfuly.

*

Offline reyalp

  • ******
  • 10069
Re: the sx20 porting thread
« Reply #7 on: 15 / October / 2009, 02:48:45 »
8. I got compile errors with unreferenced symols and i don't know why?
Post an example of the error message, or at least some of the missing symbols
Quote
10. Now of course the new bootdisk.bin won't boot :)
At the very least, you need to use one of the new diskboot encodings. See http://chdk.setepontos.com/index.php/topic,4095.0.html

Quote
11. I tried to debug with AF led blinking at the very first enrty point as the guide says, but nothing happens.
Because your diskboot is encoded with the wrong settings. The canon firmware loads *any* encoded diskboot, even if the encoding is wrong. It only recognizes and refuses to load un-encoded ones ;)

You can also try building an FI2 file. See http://chdk.setepontos.com/index.php/topic,2995.0.html and fi2.inc.txt in the platform directory of the source tree.
Don't forget what the H stands for.


*

Offline reyalp

  • ******
  • 10069
Re: the sx20 porting thread
« Reply #8 on: 15 / October / 2009, 03:20:28 »
FWIW, the sx20 dump from the dumping thread looks corrupt to me.

FF83AFE8 should be the string "\nStartDiskBoot\n"
Don't forget what the H stands for.

*

Offline neszt

  • ***
  • 174
Re: the sx20 porting thread
« Reply #9 on: 15 / October / 2009, 06:19:55 »
Because your diskboot is encoded with the wrong settings. The canon firmware loads *any* encoded diskboot, even if the encoding is wrong. It only recognizes and refuses to load un-encoded ones ;)
Ohh, thanx, i'll try it. Anyway the whole code copied from sx10 source. This means, that sx10 no need encoded diskboot?

FWIW, the sx20 dump from the dumping thread looks corrupt to me.

FF83AFE8 should be the string "\nStartDiskBoot\n"
The string you mentioned is at 0xFF83A7FC.

Can you please tell me, where the FF83AFE8 comes from?

If the sx20 dump is corrupt, i'll dump it again.

 

Related Topics