the collaborative CHDK build - page 7 - CHDK Releases - CHDK Forum  

the collaborative CHDK build

  • 249 Replies
  • 147965 Views
*

Offline fe50

  • ******
  • 3136
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: the collaborative CHDK build
« Reply #60 on: 28 / July / 2008, 08:19:32 »
Advertisements
Hi PhyrePhoX,

the juciphox#459 needs more MEMISOSIZE on the SD870 (camera bricks with blue LED), you'll see that also in the compile log:
   -> main.elf
      text      data       bss       dec       hex   filename
    241156     11388     80640    333184     51580   main.elf
With a size of 52000 it runs on the SD870...

The video pause function is not working, after 2s the cam crashes, the video file is corrupted, stored on the card but not visible in playback mode and not playable on pc...so you can add the SD870 (Digic III, DryOS) to your list of fractious models...

*EDIT: Attached a compiled version (juciphox #459) for SD870, so others can do their tests....
« Last Edit: 28 / July / 2008, 08:22:02 by fe50 »

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: the collaborative CHDK build
« Reply #61 on: 28 / July / 2008, 08:33:02 »
i wonder how we can catch this memiso thing in either the makefile or in some other way. thanks for reporting :)

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
Re: the collaborative CHDK build
« Reply #62 on: 28 / July / 2008, 09:11:29 »
I'll increase the memisosize to 55000 in the next commit. (Might be today, I'll do a bit patching first.)

*

Offline fe50

  • ******
  • 3136
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: the collaborative CHDK build
« Reply #63 on: 28 / July / 2008, 09:21:42 »
i wonder how we can catch this memiso thing in either the makefile or in some other way. thanks for reporting :)

A very quick & dirty check (under windows):

findstr /n /s "MEMISOSIZE=0x" makefile.inc>1.txt
(running from the source-code base dir, you'll get all declarations listed in 1.txt)

for %f in (log-*.txt) do findstr /R "\$-> main.elf" %f>>2.txt
(run this from the dir with the compile logs)

Then you've got 2 text files to check it manually...


*

Offline lukg

  • ***
  • 162
  • Eos 450D+18-55is+55-250is & Powershot S5is - 1.01a
Re: the collaborative CHDK build
« Reply #64 on: 28 / July / 2008, 09:41:28 »
A little question. I updated chdk to recent build. When I delete jpg in play mode, it seems that chdk deletes the related crw. (I had to use the purge raw function before). Is it normal?
Thanks

*

Offline reyalp

  • ******
  • 13502
Re: the collaborative CHDK build
« Reply #65 on: 29 / July / 2008, 17:15:50 »
Quick and dirty patch to making ubasic-run compile. The #ifdef TEST stuff in ubasic.c isn't really right (unintialized values)

make.test shows how I compiled it (using cygwins regular compiler)
Don't forget what the H stands for.

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: the collaborative CHDK build
« Reply #66 on: 29 / July / 2008, 17:52:18 »
A little question. I updated chdk to recent build. When I delete jpg in play mode, it seems that chdk deletes the related crw. (I had to use the purge raw function before). Is it normal?
Thanks
yes, this is normal and this "feature" is there since the beginning. but it only works if you reboot the cam after you shot a jpg (with raw).

thanks reyalp for the patch, i hope jucifer will look into it ;) :D :p

edit: attached latest diff, not intended for use, just a "backup". including get_temperature (for osd AND ubasic) and playsound (ubasic). lot of stub adresses added, about 25 firmwares to go. thanks for helping, Hacki, reyalP & LjL

missing adresses from the following cameras:

Quote
ixus55_sd450 100d x (no dump)
a650 x
a450 x
a460 x
g7 100e x (no dump)
ixus60_sd600 100a
ixus60_sd600 100d
ixus65_sd630
ixus70_sd1000 100c
ixus70_sd1000 101b
ixus70_sd1000 102a
ixus700_sd500 101a
ixus700_sd500 101b
ixus750_sd550 100g
ixus800_sd700 100b
ixus800_sd700 101b
ixus850_sd800
ixus860_sd870
ixus950_sd850
s5is 101a
s5is 101b
s80
tx1 100g
tx1 101b
« Last Edit: 29 / July / 2008, 20:40:32 by PhyrePhoX »



*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: the collaborative CHDK build
« Reply #68 on: 30 / July / 2008, 03:09:27 »
well it was my private list, i meant "i found no dump", not "there is no dump at all". maybe i didnt look too hard.
one thing i noticed is that a few of the dumps arent stripped of zeros properly, and i dont find a way how to do that on windows. hacki helped me with this issue.

*

Offline Hacki

  • ****
  • 358
  • SX100
Re: the collaborative CHDK build
« Reply #69 on: 30 / July / 2008, 05:39:19 »
Code: [Select]
Ixus 55 1.00d:
GetOpticalTemperature 0xFF82C6AC
GetCCDTemperature 0xFF82C6C0
GetBatteryTemperature 0xFF82C6D4
PT_PlaySound 0xFF957554

Ixus 60/SD600 1.00a:
GetOpticaltemperature 0xFF82D248
GetCCDTemperature 0xFF82D25C
GetBatteryTemperature 0xFF82D270
PT_PlaySound 0xFF969874

Ixus 60/SD600 1.00d:
GetOpticaltemperature 0xFF82D248
GetCCDTemperature 0xFF82D25C
GetBatteryTemperature 0xFF82D270
PT_PlaySound 0xFF96A36C

Should all be right, confirmed it with the address off VbattGet, but still - would be nice if someone could test it..


 

Related Topics