IXUS 1000 HS Porting Thread - page 15 - DryOS Development - CHDK Forum

IXUS 1000 HS Porting Thread

  • 439 Replies
  • 132972 Views
Re: IXUS 1000 HS Porting Thread
« Reply #140 on: 13 / November / 2010, 11:26:32 »
Advertisements
>About the key stuff, for my dosn't work allways with the set, I changed it for testing for up-right, >and the result is moreless the same, maybe changing it for soft presses insted of hard one could >be better,

yes thats the problem because the rom firmware process keys.but this have nothing to do with the way to change in alt mode.the best way to change in alt is really a softpress, but this can reach to easy by random

maybe you can find in the asm source a better place to call ,my_kbd_xxxx

I test also the script execute, i use the script save romlog.but this is not store.its sure that shoot half press work ok, but maybe you can tell me how i can test if shoot full press work ok.i see script.c file, but i have no idea what code is execute when i press shoot full press and alt mode enable


another Problem i see, is that firmware update is not possible when battery go under 3.4 Volts.
the IX1000 show then 2 bars of 3 and it can work long time more, before it show only 1 bar.

the IX1000 battery have only 3.5 volt, the sx210 3.7 volts, so i subtract 0.2 volts and add this in

long get_vbatt_min()
{
   return 3080;  // min observed was 3.408, then it died
}

But still same, firmware cant update, even if the battery have enough power so the Camera can use without chdk 10 minutes more(in record view mode)

when have luck and do a firmware update with over 3.4 volt, then you can use chdk longer and i see 3.2 Volt show too 2 bars.

Here i find some information about LiIon battery.so 3 volt is ok to use

"""""
http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries

There are several safeguards to prevent excessive discharge. The equipment protects the battery by cutting off when the cell reaches 2.7 to 3.0V/cell. Battery manufacturers ship the batteries with a 40% charge to allow some self-discharge during storage
"""""

Ixus 1000 HS

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: IXUS 1000 HS Porting Thread
« Reply #141 on: 13 / November / 2010, 13:09:27 »
@Bernd R
I think there is another issue with the kbd.c , when you enter alt mode and you return, you cant use any more the standar keys for normal cam operation

This is the new raw.c to solve the directory issues change it at core
http://www.4shared.com/file/dffJTBc1/ixus1000rawc.html

-This is the new captseq, test it for yor cam
http://www.4shared.com/file/rgg1t7MU/captseqcixus1000-100D-v004.html

Here you have a raw dng file, works but the color is purple,
http://www.4shared.com/file/XO8MBwJG/ixus1000rawtest1.html

I think this is wrong
Code: [Select]
#define cam_CFAPattern 0x02010100 // Red  Green  Green  Blue

I tested the the two options defined at raw.c , and same reusult, diferent colors

we need to find a new one and insert it here

Code: [Select]
#if cam_CFAPattern==0x02010100    // Red  Green  Green  Blue
    r=gamma[get_raw_pixel((x/2)*2,(y/2)*2)>>(CAM_SENSOR_BITS_PER_PIXEL-8)]; // red pixel
    g=gamma[6*(get_raw_pixel((x/2)*2+1,(y/2)*2)>>(CAM_SENSOR_BITS_PER_PIXEL-8))/10]; // green pixel
    b=gamma[get_raw_pixel((x/2)*2+1,(y/2)*2+1)>>(CAM_SENSOR_BITS_PER_PIXEL-8)]; //blue pixel
#elif cam_CFAPattern==0x01000201 // Green  Blue  Red  Green
    r=gamma[get_raw_pixel((x/2)*2,(y/2)*2+1)>>(CAM_SENSOR_BITS_PER_PIXEL-8)]; // red pixel
    g=gamma[6*(get_raw_pixel((x/2)*2,(y/2)*2)>>(CAM_SENSOR_BITS_PER_PIXEL-8))/10]; // green pixel
    b=gamma[get_raw_pixel((x/2)*2+1,(y/2)*2)>>(CAM_SENSOR_BITS_PER_PIXEL-8)]; //blue pixel

« Last Edit: 13 / November / 2010, 13:55:50 by asm1989 »

Re: IXUS 1000 HS Porting Thread
« Reply #142 on: 13 / November / 2010, 13:38:35 »
>I think there is another issue with the kbd.c , when you enter alt mode and you return, you cant >use any more the standar keys for normal cam operation

you can press each key left right down up menu and set and it continue to work

thats the problem because the Canon Firmware store somewhere before my_kbd_read_keys(

what key is press for each key possible.this should the ROM not do and so i think  my_kbd_read_keys must call earlier so ROM store teh values it get from chdk

but now when change to alt mode, the store is do for a key press, but the ROM never recieve the correct value it store  from my_kbd_read_keys(

in a later function

So all keys hang until you press them all in non alt mode once

Here you have a raw dng file, works but the color ir purple,
http://www.4shared.com/file/XO8MBwJG/ixus1000rawtest1.html

good, i can show your crw file.
how have you done it ?.i cant show my crw files

maybe when  photograph  something full blue, green, red best from TFT Monitor.maybe this make more clear how color pattern work.

« Last Edit: 13 / November / 2010, 13:40:10 by Bernd R »
Ixus 1000 HS

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: IXUS 1000 HS Porting Thread
« Reply #143 on: 13 / November / 2010, 13:58:28 »
For the new captseq

-This is the new captseq, test it for yor cam
http://www.4shared.com/file/rgg1t7MU/captseqcixus1000-100D-v004.html

you need this at boot.c too
Code: [Select]
if (p[0] == 0xFF8CCA88)
p[0] = (int) exp_drv_task;

To be able to see the crw files you need to generat a dng -> And raw only generates a good image if you set the cam in auto

you need a dumy badpixel.bin at  the CHDK folder, here you have one

http://www.4shared.com/file/4BAhlCR8/badpixelbinwrong.html


we need to enable runing the badpixel script, maybe thats why the colors are wrong
since that badpixel is from sx210
« Last Edit: 13 / November / 2010, 14:09:21 by asm1989 »


*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: IXUS 1000 HS Porting Thread
« Reply #144 on: 13 / November / 2010, 14:32:45 »
Here you have the new boot.c , I discarded the s95 old hooking style and convert it to the new one, on 100F works
please test in 100D

http://www.4shared.com/file/7Du3Gz3r/bootcixus1000-100Dv007NewHooks.html


also here you have the new propset3 for testing
http://www.4shared.com/file/8PLJdFIQ/propset3sx210ixus1000.html
« Last Edit: 13 / November / 2010, 15:43:31 by asm1989 »

Re: IXUS 1000 HS Porting Thread
« Reply #145 on: 13 / November / 2010, 15:45:28 »
I test now a little more the script function  program flow and use your V4 captseq.

the Keyboard with SHOOT_FULL work.see the testcode.when i have alt mode on and press full shoot, the display get black during time of the shoot.When the recorded image is show then i get the message before process script and after the delay i get the message after process script.

i need search more, what went wrong tomorrow, or maybe you have a idea wy the script not work. 

in core/kybd.c the func

long kbd_process()
{

.......

 if (state_kbd_script_run)
        {
             sprintf(osd_buf, "before process script    %8x ", key_pressed);
      draw_txt_string(20, 12, osd_buf, MAKE_COLOR(0xdd,0x6f));
      msleep(500);
            process_script();
                 sprintf(osd_buf, "after process script    %8x ", key_pressed);
      draw_txt_string(20, 12, osd_buf, MAKE_COLOR(0xdd,0x6f));
      }


I test also  your boot.c.give lots of linker errors.

boot.c:(.text+0x5dc): undefined reference to `sub_FF863A68'
../platform/ixus1000_sd4500/sub/100d/libplatformsub.a(boot.o): In function `loc_FF863700':
boot.c:(.text+0x6b4): undefined reference to `sub_FF863A40'
../platform/ixus1000_sd4500/sub/100d/libplatformsub.a(boot.o): In function `loc_FF863708':
boot.c:(.text+0x6c4): undefined reference to `sub_FF83BDB8'
boot.c:(.text+0x6d8): undefined reference to `sub_FF83BCD4'
../platform/ixus1000_sd4500/sub/100d/libplatformsub.a(boot.o): In function `loc_FF863740':
boot.c:(.text+0x744): undefined reference to `sub_FF83BDB8'
boot.c:(.text+0x758): undefined reference to `sub_FF83BCD4'
../platform/ixus1000_sd4500/sub/100d/libplatformsub.a(boot.o): In function `loc_FF863800':
boot.c:(.text+0x7e4): undefined reference to `sub_FF89C2E4'
../platform/ixus1000_sd4500/sub/100d/libplatformsub.a(boot.o): In function `loc_FF863838':
boot.c:(.text+0x7ec): undefined reference to `sub_FF89C2E4'
../platform/ixus1000_sd4500/sub/100d/libplatformsub.a(boot.o): In function `loc_FF86383C':
boot.c:(.text+0x800): undefined reference to `sub_FF89C20C'
boot.c:(.text+0x820): undefined reference to `sub_FF83BDB8'
boot.c:(.text+0x834): undefined reference to `sub_FF83BCD4'
../platform/ixus1000_sd4500/sub/100d/libplatformsub.a(boot.o): In function `loc_FF8638A0':
boot.c:(.text+0x880): undefined reference to `sub_FF83BCD4'
../platform/ixus1000_sd4500/sub/100d/libplatformsub.a(boot.o): In function `loc_FF863938':
boot.c:(.text+0x8d0): undefined reference to `sub_FF89C2E4'
Ixus 1000 HS

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: IXUS 1000 HS Porting Thread
« Reply #146 on: 13 / November / 2010, 16:04:26 »
I dont have this errors,

maybe because I have the bin file in the folder?

anyway you can solve them including in stubs_entry_2.S , the missing subs

STUB(FF863A68)
...  and the same with all the undefined references

*

Offline reyalp

  • ******
  • 13440
Re: IXUS 1000 HS Porting Thread
« Reply #147 on: 13 / November / 2010, 16:22:09 »
I would suggest generating stubs_auto.S instead. This should be done automatically by the build process.
Don't forget what the H stands for.


*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: IXUS 1000 HS Porting Thread
« Reply #148 on: 14 / November / 2010, 04:33:28 »
@bernrd  here you have your latest boot.c , with the new hook system and the fileinit stuff included
http://www.4shared.com/file/3ffIGRXX/bootcixus1000-100Dv008Initfile.html

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: IXUS 1000 HS Porting Thread
« Reply #149 on: 14 / November / 2010, 05:09:30 »
@reyalp

I'm working on movie_rec.c , it could be interesting to mess up with the 240fps movie mode!!

and I need to override this
Code: [Select]
" LDR R6, =0xFF986050\n"
could I do it with this:
Code: [Select]
" LDR R6, =sub_FF986050_my\n" ?

 

Related Topics