(...)You feed it a disassembly snippet originating from Chr's disassembly perl script and it spits out something that is hopefully very close to being acceptably formatted for direct inclusion in CHDK platform source code. I used it with the a650 long exposure port above (which remains untested) and it seemed to work rather fine, but make sure you read all the comments in the script.. it's not a particularly smart one and likely requires some tuning/additions for each firmware but ought to make ones life easier nonetheless...

Yes, full version of IDA is not free..But, as you say; I don't need IDA 'cause I just want to modify some parts of the code and compile it.So, I'll use my usual editor and I'll see.

Thanks for informations -.^

To implement long exposures, you need to disassemble a large chunk of your cameras firmware code, in a format similar to that used by IDA. You cannot copy this from another camera, and you can't just make it with a text editor. If you have sufficient knowledge, you can do it with the GPL tools rather than IDA. The stuff fudgey linked will help.

regarding your compile errors, it looks like stubs_auto.S was not generated correctly.

You should never need to edit stubs_auto.S manually (and if you do it should have no effect). You may need to delete it manually to force regeneration, though (happened to me once from svn trunk for one of these long exposure things; someone committed code that didn't include updated stubs_auto.S and my make didn't recreate it for some reason... I have no clue why).

stubs_auto.S is generated build-time thanks to an infernally beautiful chunk of regexp shell stuff in platform/makefile_sub.inc. For what I can understand of that, it looks for strings of format 'sub_xxxxxxxx' in platform code files (STUBS_AUTO_DEPS as defined in platform/*/sub/*/Makefile, I suppose) and creates stubs for all matches.

I already told you. Look at one of the previous checkins that added long exposure support. Then do the equivalent thing, by disassembling the corresponding part of your cameras firmware and adding exp_drv_task to your cameras port.

All the autogenerated files have a comment at the top warning you that they are generated.

I try generate dark frame(s) with 460 sec. This is difficult. The optical element very weak, do not use any lens cap! I try use "black box", with 10 sec timer, the camera now in the "black box". The dark frame image very bad, very bright, non-usable. I think the problem, the camera own light, the two blinking LED and the black, but not totally black LCD screen. The best method to record dark frame, the canon ring and wide angle converter with own lens cap of wide angle converter. Now the dark frame near ok, only small exposured circle the problem (i think, the canon ring or the wide angle converter not 100% block the external light. Of course the single dark frame noisy, i see number of hot spot, and have amplifier glow. (possibly the ccd amplifier on/off with CHDK?, amplifier glow strong, but not fatal)

Next i try record set of dark frame, with internal canon function (user timer). The 1. picture recording, the two leds blinking, but if 2. picture recording the two leds not blinking, i think, the camera is freeze, but no, both picture recorded correctly. I not understand. Currently i have not fully processed images to master dark.

I have some test images, if anybody interested, the test picture upload to forum is correct?Real astrophotography test images not available yet, many night rainy or cloudy.

I try this ugly,and risky script, see under. I want to write the script, with user selectable long exposure time in sec. I not understand, how i do it. I find some information on forum. This script takes 150 sec. = 150* 1 000 000 uSec. image. I think apex2us convert it, but i not know how it. What formula used to convert seconds to this value (-694). Or this script idea bad, more elegant function to control exposure time for this script available?

I've just tested the a650 with the experimental code: the exposure limit is still 64sec even if i set the time to 80 and 101 in a second try. I'm sorry that i can't help you in the development of the code (i'm not a very skilled programmer) but if i can help in some way I'm here, just tell me what to do (i study electronic engineering so i understand the matter but i really don't know how to dirt my hands - i hope i'll find the time to learn something on chdk coding this summer)