G9 porting progress - page 6 - DryOS Development - CHDK Forum  

G9 porting progress

  • 281 Replies
  • 102249 Views
*

Offline reyalp

  • ******
  • 11902
Re: G9 porting progress
« Reply #50 on: 01 / October / 2008, 21:15:16 »
Advertisements
bongo_bingo 100d dump here zSHARE - g9-1.00d.dat

It looks ok to me, no leading zeros.
Don't forget what the H stands for.

Enjoy CHDK!
« Reply #51 on: 02 / October / 2008, 07:24:25 »
Hi all,
attached the 100d diskboot bin, compiled from uvv src adding only the dump from reyalp in the sub\100d directory.

Hope it works.
« Last Edit: 02 / October / 2008, 07:26:09 by bongo_bingo »

Re: G9 porting progress
« Reply #52 on: 02 / October / 2008, 09:09:20 »
Here is the 100f version, it works quite well on my g9 (it still doesn't save the chdk raw, but script and overrides seems to work).
I've only added:

NSTUB(PutInNdFilter, 0xFF810958) //nullsub
NSTUB(PutOutNdFilter, 0xFF810958) //nullsub

to stubs_entry_2.S, because gcc asked for this addresses which I'm not able to find.
This is the only differece with the uvv src.
« Last Edit: 02 / October / 2008, 09:14:25 by bongo_bingo »

*

Offline uvvv

  • *
  • 11
  • G9
Re: G9 porting progress
« Reply #53 on: 02 / October / 2008, 10:10:09 »
Hello,
to bongo_bingo , reyalp and Titan_G9 ...
I have compared dumps for G9-100G with G9-100F and have found that they identical,
therefore the version for 100G works on 100F... :)

dumps for G9-100D and G9-100H differ from G9-100G...
And addresses of some or all programs for G9-100D and G9-100H differ...
For start CHDK on G9-100D and G9-100H except modification of files stubs_entry.S ,stubs_entry_2.S and stubs_min.S
it is necessary to change some or all address in code assembler in files boot.c, movie_rec.c, capt_seq.c ,lib.c
from IDA with loaded dumps G9-100D or G9-100H...
almost all work that was is made for G9-100G it is necessary to repeat for G9-100D and G9-100H... :(

For example it can be seen on working CHDK for S5is
the files specified by me for versions 101a and 101b differ among themselves...
« Last Edit: 02 / October / 2008, 10:40:54 by uvvv »


Re: G9 porting progress
« Reply #54 on: 02 / October / 2008, 10:36:41 »
Comparing 100D and 100G dumps. In 100G the function at 0xFF8FF96C does a bit more. It means all the following functions after 0xFF8FF990 are located with offset +0x70 (so 0xFF8FF990 in 100D becomes 0xFF8FFA00 in 100G).
I have not checked what else chnged but as a quick test it might be enough to take files from 100g and just replace all referenced addresses that starts from 0xFF900000 by substracting 0x70 from them.

Re: G9 porting progress
« Reply #55 on: 02 / October / 2008, 11:43:36 »
Hi bongo_bingo.

Well, it's the same as before, only the blue led come up and after 1 sec. it turns off.
I'm sorry, but uvvv has right! (Reply #53)
So changes needed in the relevant files.

By the way it was a nice try... thanks. ;)

Cheers,


Hi all,
attached the 100d diskboot bin, compiled from uvv src adding only the dump from reyalp in the sub\100d directory.

Hope it works.

Re: G9 porting progress
« Reply #56 on: 02 / October / 2008, 18:50:06 »
I loaded the 100g and the 100f the script files seem to work but.  the interval timer will fire once but will not continue the interval timer.

« Last Edit: 02 / October / 2008, 18:53:25 by blacklightblue »

Re: G9 porting progress
« Reply #57 on: 02 / October / 2008, 18:51:25 »
Hi bongo_bingo.

Well, it's the same as before, only the blue led come up and after 1 sec. it turns off.
I'm sorry, but uvvv has right! (Reply #53)
So changes needed in the relevant files.

By the way it was a nice try... thanks. ;)

Cheers,


Hi all,
attached the 100d diskboot bin, compiled from uvv src adding only the dump from reyalp in the sub\100d directory.

Hope it works.

did you add trunk files to your sd card?


*

Offline uvvv

  • *
  • 11
  • G9
Re: G9 porting progress
« Reply #58 on: 03 / October / 2008, 05:04:13 »
Hi all.
I have chdk for g9-100g with working RAW!!!  :D

In attach files there is my last version for g9-100g (100f) - trunk_g9.rar ...
and also there is a test build  -  DISKBOOT.rar    for g9-100g with TimeStamp... :)
I am sorry for the developer (CHDK + with timestamp) canons5is.clan.su
for use of their code with a view of testing of working RAW on CHDK for G9...

there is example RAW with TimeStamp made with CHDK for Canon G9 -> RapidShare: Easy Filehosting
and JPEG file -> RapidShare: Easy Filehosting

below I have filled the report from jeff666 under my version for g9-100g

Tasks:
  • Get the cam started.
    • start cam under chdk-control without any extensions
    • create led-blinker-test-task
    Progress: all done
  • GUI output.
    • General output
    • Histogramm
    • Zebra mode
    Progress: all done
  • hijack Keyboard handler (this includes USB-support)
    • JogDial
    Progress: all done
  • hijack shoot-task.
    • control darkframe subtraction.
    • implement raw-save: This might be unnecessary, since the G9 saves raw itself, but it should be simple thus I'll include it anyway.
    Progress: all done
  • hijack movie-task.
    Progress: testing (some done)
  • Include multipartition/boot from SDHC support.
    Progress: all done
  • BASIC scripting.
    Progress: all done
  • Lua scripting.
    Progress: all done
  • Overrides.
    • AV
    • TV
    • ISO
    • Subject Distance
    • Bracketing in cont' mode
    Progress: all done
  • Image enhancement.
    • Bad Pixel removal
    • custom curves
    Progress: testing (some done)


Now I'm working with next task
  • testing movie-task
« Last Edit: 03 / October / 2008, 11:10:22 by uvvv »

Re: G9 porting progress
« Reply #59 on: 03 / October / 2008, 07:20:31 »
Hi All,
It is almost I said, moving offset a bit (extra for memcpy), including canon_data_src offset in boot.c. This is only I did. I have the CHDK screen. But it needs some more check.
It is based on the previous uvvv 100g code (not on the latest uvvv code from the post above).

 

Related Topics