A2200 IS porting thread - page 4 - DryOS Development - CHDK Forum  

A2200 IS porting thread

  • 514 Replies
  • 96881 Views
Re: A2200 IS porting thread
« Reply #30 on: 25 / August / 2011, 19:24:31 »
Advertisements
Ah, this makes more sense now (following the wiki).

I wasn't sure of the purpose of init_file_modules_task(), but if it's function is to ensure the delay so that other modules get time to initialise, that explains why I was able to get to the splash screen after a few seconds when I commented it out assigning taskHook values.

I also figured why it wouldn't run, or more precisely, not boot the firmware. The camera doesn't boot if the taskHook has capt_seq_task, movie_record_task and exp_drv_task values to addresses assigned. With just mykbd_task and init_file_modules_task assigned it boots to the splash screen almost instantly.

Guess I'll focus on the keyboard first (commenting out the mykbd_task, I can power on and off the camera with the power button, but can't power it off if left assigned, so I take that as a sign that that works, just need to find the right values). I've noticed that with the newer revision I get some suggestions in the stubs_entry.S already, that's awesome.

Then hunt down if I need different taskHook definitions for each IRQ value or if I still need to do something somewhere.

Re: A2200 IS porting thread
« Reply #31 on: 25 / August / 2011, 22:15:18 »
The camera doesn't boot if the taskHook has capt_seq_task, movie_record_task and exp_drv_task values to addresses assigned.
More likely the camera boots, starts CHDK and then crashes when the capt_seq_task, movie_record_task and exp_drv_task start executing and are not completely correct.

Quote
I've noticed that with the newer revision I get some suggestions in the stubs_entry.S already, that's awesome.
You can thank philmoz for that one.

Quote
Then hunt down if I need different taskHook definitions for each IRQ value or if I still need to do something somewhere.
There are no IRQ's involved here.  The task hooks are changed to intercept the normal startup process of your camera such that when it goes to start three specific tasks,  it is intercepted and sent to your new capt_seq_task, movie_record_task and exp_drv_task instead.  Incidentally,  the new stub_entry.S also tells you what hex address to use for each task hook.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: A2200 IS porting thread
« Reply #32 on: 26 / August / 2011, 10:37:40 »
There are no IRQ's involved here.  The task hooks are changed to intercept the normal startup process of your camera such that when it goes to start three specific tasks,  it is intercepted and sent to your new capt_seq_task, movie_record_task and exp_drv_task instead.  Incidentally,  the new stub_entry.S also tells you what hex address to use for each task hook.

Thanks for pointing that out, the more I know the easier it will be. Browsing the forums I picked up somewhere that the number the taskHook is assigned is an interupt (*(int*)0x193C=(int)taskHook;). Maybe binge coding during a heat wave is not the best idea ever :P

Any way, I managed to get the OSD on and poke around with the keyboard a bit. But now I need to drop the porting for a while, since I have an exam in a few days. After that, I'll be back in full swing on this.

Re: A2200 IS porting thread
« Reply #33 on: 04 / September / 2011, 14:32:47 »
News about porting???


Re: A2200 IS porting thread
« Reply #34 on: 07 / September / 2011, 16:00:18 »
News about porting???

I'm still busy with uni this week, I'll be able to resume work sometime next week.

*

Offline dejco

  • *
  • 20
Re: A2200 IS porting thread
« Reply #35 on: 15 / September / 2011, 18:55:12 »
anything new?

Re: A2200 IS porting thread
« Reply #36 on: 26 / September / 2011, 13:50:50 »
Hi all... anything news????  :o

Re: A2200 IS porting thread
« Reply #37 on: 08 / October / 2011, 07:55:29 »
we must lose all hopes for this porting?


Re: A2200 IS porting thread
« Reply #38 on: 09 / October / 2011, 18:11:15 »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: A2200 IS porting thread
« Reply #39 on: 22 / October / 2011, 15:14:30 »
What happened to the last couple of posts? Was it all a dream?

Any way, quick update; I figured out the problem with capt_seq_task and exp_drv_task. Chalk it down to clumsiness, so I need to redo those and hope that fixes them.

On the other hand I haven't figured out he modmap table. I know in the newer version of CHDK the entries are suggested in the stubs_entry.S, but I only get reference for MODE_P and MODE_AUTO. The rest are just values and I don't know where to check which modes to assign them. I looked trough a few dumps and compared values but I don't see a pattern.

 

Related Topics