kautsu / 400plus

Automatically exported from code.google.com/p/400plus
0 stars 0 forks source link

Lens control #309

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
As in issue 85,106,303, 154, I think if will be added some functions for 
lenses, it must be individual for each other. That is must be presets for each 
lenses. Lens name and parameters must be loaded and saved as profiles. And some 
settings for each lens can be configurable, as microadjusment, af confirm 
e.t.c., and may be protocol change (for old sigma, tamron). MAy be set 
permanent profiles for 10(20) lenses and assign each other for their profile.
And how you work? You have disassembled dump, or clear dump? Where can I see it?

Original issue reported on code.google.com by gen...@gmail.com on 4 Dec 2012 at 6:00

GoogleCodeExporter commented 9 years ago
Considering most functions you mention are still unknown to us, I would not 
hold much hope on seen them in profiles.

You can find info about the internals in the original thread at the CHDK forum 
(http://chdk.setepontos.com/index.php?topic=3290) or the CHDK wiki 
(http://chdk.wikia.com/wiki/400D).

Firmware dumps contain copyrighted code from Canon, and thus cannot be shared; 
sorry. You could easily obtain one modifying 400plus, some people also 
decrypted a firmware update package.

Original comment by eduardo....@gmail.com on 4 Dec 2012 at 7:25

GoogleCodeExporter commented 9 years ago
I read this thread, but I more understand if I will see original canon code. I 
was try to decompile it, but not have result.

Original comment by gen...@gmail.com on 4 Dec 2012 at 10:28

GoogleCodeExporter commented 9 years ago
You can try to decompile a dump, but most you'll get is an assembler version, 
not the original Canon code.

Original comment by eduardo....@gmail.com on 4 Dec 2012 at 11:26

GoogleCodeExporter commented 9 years ago
I would not expect much here.
The lens are controlled by the a companion chip Tx19a, this chip communicates 
with the main processor - Digic (ARM), but behaves on it's own. Like Alex said 
somewhere, you can totally block the firmware in the init process ( while(1) {} 
) and the camera will still be able to take photos (though not saved to the CF 
card of course). The lens will focus and the shutter will work.
This is so, because this Tx19a chip takes care of the buttons and does the 
photo by itself (hence focus the lens).
We know almost nothing about this chip, neither we know how to communicate with 
it.
There are speculations that the .fir file can update the firmware in this chip 
too, but it's a MIPS architecture (not ARM, like the main processor) and so far 
noone has hacked into this chip.

Then again, it's not possible with the current knowledge.

About the firmware, you can obtain it as Edu suggested, or from someone. But 
then you will need to know/learn ASM for ARM and use tools like IDA to start 
reverse engineering.
If you are interested, you can contact me in private on GTalk 
(firedust@gmail.com),
I can help you with information.
Another good source of info is the relatively new ML forum - 
http://magiclantern.fm

Edu, I would close all lens related issues with NotPossible and wait for better 
times, but I would hear your opinion first. When/If it became possible, I 
believe many of this ideas will come to mind again. If you prefer to have them 
open, I'm ok with this.

Original comment by fired...@gmail.com on 4 Dec 2012 at 2:26

GoogleCodeExporter commented 9 years ago
I tend to forget everything quite easily, and tend to prefer to have an issue 
open for a long time than to forget about it later...

Original comment by eduardo....@gmail.com on 4 Dec 2012 at 2:56

GoogleCodeExporter commented 9 years ago

Original comment by eduardo....@gmail.com on 20 Feb 2013 at 8:23