A have firmware GM1.00F. Checked same functions.
works:
- optical zoom works during movie recording
- saving DNG
- histogram
Aperture (F) display shows only value 2,8 or "?"
if I zoom and under very bright light conditions only it shows only "?"
Thank you for the report.
About the aperture display: The question mark appeared, because the values in a table were wrong for the A410 (copied from another port). I'll fix that soon, and post a fresh build.
To reyalp:
I've checked this in, but not added to the autobuilds yet. If you feel it is functional enough to be beta in the autobuild, just let me know.
Thank you. I didn't ask for including it yet because of no success reports other than mine.
(The A420 port is not ready yet, still working on it.)
I made a couple changes:
In capt_seq.c, you had
" B 0xffc107c8"
This generally does not do what you want, and my compiler does not accept it:
../platform/a410/sub/100f/libplatformsub.a(capt_seq.o): In function `loc_FFCD9F9C':
capt_seq.c:(.text+0x6c8): undefined reference to `no symbol'
I converted this to
" LDR PC,=0xffc107c8\n"
Also thanks for this. I didn't notice warnings with the arm-gcc toolchain I'm using (linux, gcc 4.3.2, precompiled, I got it from here somewhere). I'm not exactly a "pro" in ARM-assembly, and the disassemblies produced by various tools have big differences. I'll try to be more careful.
Still amazing, how a possibly wrong code causes no (visible) trouble. In the A430 port for example, at least capt_seq.c contains some instructions, values, that differ from the original firmware's code, for (to me) unknown reason. I'll have a patch for that sometimes soon.
I also converted the comments like
" BL sub_ffc03b58 @DebugAssert\n"
to C++ style comments outside the inline asm.
Well, I was lazy... I'll get rid of those in the future.
Any chance you have a clue about the task named "WBInteg"? A410 crashes there when MakeAFScan is attempted during video recording. A430 (and I bet A420 too) also crashes there, but only when the movie resolution is 640x480. I would think of WhiteBalanceIntegrity, but that doesn't make too much sense to me...