supplierdeeply

SX200is Porting

  • 1105 Replies
  • 155010 Views
*

Offline Darkness

  • **
  • 72
  • SX200IS 100D
  • Publish
    Re: SX200is Porting
    « Reply #60 on: 24 / August / 2009, 15:18:35 »
    Advertisements
    OldGit,

    Any chance you had to add something to core/kbd.c ?
    I get a compile error for not finding ZSTEP_TABLE_SIZE and nTxtbl.

    From looking at the file, I suppose we need to add a camera specific definition there?
    SX200IS 100D

    *

    Offline OldGit

    • ****
    • 303
  • Publish
    Re: SX200is Porting
    « Reply #61 on: 24 / August / 2009, 15:37:17 »
    Yes, sorry forgot that one here it is
    SX200 IS-100C

    *

    Offline Darkness

    • **
    • 72
    • SX200IS 100D
  • Publish
    Re: SX200is Porting
    « Reply #62 on: 24 / August / 2009, 15:45:18 »
    thanks, I tried something similar already, same result...  :(

    When I boot, my own splash image shows, lens comes out and then camera shuts down.  :-X
    SX200IS 100D

    *

    Offline OldGit

    • ****
    • 303
  • Publish
    Re: SX200is Porting
    « Reply #63 on: 24 / August / 2009, 16:24:09 »
    Darkness,
    I didn't think that this would work "out of the box" on a 100D, you only need one address to be out by a few bytes.
    You should be able to check the code addresses in the 100C dump and find the same code in the 100D, adjust the sources and move forward.

    Just be carfull not to replicate any errors I have introduced.
    (there must be some, I am still working on it)

    What did the splash look like ?.
    OldGit
    SX200 IS-100C


    *

    Offline OldGit

    • ****
    • 303
  • Publish
    Re: SX200is Porting
    « Reply #64 on: 24 / August / 2009, 16:39:34 »
    I just remembered that I had problems with timing.
    Then I remembered that I hadn't included the loader

    See here sx200is.7z - 0.00MB

    The timing is in the top level entry.s
    SX200 IS-100C

    *

    Offline Darkness

    • **
    • 72
    • SX200IS 100D
  • Publish
    Re: SX200is Porting
    « Reply #65 on: 24 / August / 2009, 17:34:19 »
    Darkness,
    I didn't think that this would work "out of the box" on a 100D, you only need one address to be out by a few bytes.
    You should be able to check the code addresses in the 100C dump and find the same code in the 100D, adjust the sources and move forward.

    Just be carfull not to replicate any errors I have introduced.
    (there must be some, I am still working on it)

    What did the splash look like ?.
    OldGit
    didn't expect it to work from the start but it's a steep learning curve :(

    splash image looked normal, nothing wrong like you reported earlier.

    concerning "adjust the sources", are those addresses in a specific source file?
    The ones in sub/boot.c:taskCreateHook seem correct.

    I guess I will have to investigate the boot process a bit more in detail...
    SX200IS 100D

    *

    Offline reyalp

    • ******
    • 9957
    Don't forget what the H stands for.

    *

    Offline OldGit

    • ****
    • 303
  • Publish
    Re: SX200is Porting
    « Reply #67 on: 25 / August / 2009, 00:57:01 »
    splash image looked normal, nothing wrong like you reported earlier.
    Thats interesting, the 100D can't be that different, I must have a problem in my setup,
    can you suggest anything you are doing differently ?.
    Quote
    concerning "adjust the sources", are those addresses in a specific source file?
    The ones in sub/boot.c:taskCreateHook seem correct.

    I guess I will have to investigate the boot process a bit more in detail...
    See links in post from reyalp, you need to understand fully how this boots, the Wiki gives you a logical porting process,
    I would suggest that you follow it through and get a good understanding, this will also allow you to check each source and test each one.

    Steep learning curve, for me it is almost vertical, but you do get a sense of achivement when you crack a problem,
    and of course at the end you get an even better camera to play with.

    One tip, check ALL address in stubs files, not just the ones ADI can't find or has as less than 100 %.
    Both memory allocation addresses caused me a problem.
    One of these caused a crash after the lens was fully extended (sound familiar ?), try commenting out the hooks in boot.c,
    again see the Wiki.

    Good Luck and keep in touch, OldGit
    SX200 IS-100C


  • Publish
    Re: SX200is Porting
    « Reply #68 on: 25 / August / 2009, 06:36:45 »
    Just wanted to add another encouragement, I've joined to CHDK community as a new SX200 IS owner, itching to get my hands on the enhancements CHDK provides.  :)

    Thanks to all involved for their efforts, I shall keep watching closely. And if you can fix the flash as well, well, I would be in your debt!

    Good luck!

  • Publish
    Re: SX200is Porting
    « Reply #69 on: 26 / August / 2009, 01:00:10 »
    I have now Compiled the Source from the 1.00c Firmware and have now one DISKBOOT.bin
    But the Cam would not Booting when the Card is write Protected.

    What is wrong with my File?

    caminfo.txt: sx200is-100c (dryos, #12736): MEMISOSIZE used: 0x42cc4

    Smartkiller
    SX200 IS Firm. 100c
    SX1 IS Firm. 201a

     

    Related Topics