Attached diff is for finding the mentioned fw variable (I named it imager_active, suggestions for a better name are welcome).
vx and dryos, t2 version is still to be done. I only checked some of the results, but the others also look reasonable.Same variable causing different trouble here: https://chdk.setepontos.com/index.php?topic=11078.msg136913#msg136913
* The "Fail ImagerActivate(ErrorCode:%x)" string is referenced twice. The match uses the first one. The second one is similar but would end up with a different function for ImagerActivate
* M10 has an assert in the function found via "Fail ImagerActivate" (fc12821a in 110d) that doesn't seem to be present in any of the other firmwares. It still looks like the correct function, but it would be good to verify
* I made the callback a separate match just because it makes it easier to dump the disassembly for verification
I put a note about that in source (I'm not sure why the string is the same for both functions - perhaps a copy&paste error that they never fixed).
Quote* I made the callback a separate match just because it makes it easier to dump the disassembly for verificationI'll look into adding that. Probably worth it if we're about to use this variable.
What's interesting is that going into the rec menu does not touch imager_active, even though liveview stops while in menu.
=av=get_max_av96() set_av96_direct(av) press'shoot_half' repeat sleep(10) until hook_preshoot.count() > 0 return av,get_current_av96(), get_av96()9:return:6729:return:3529:return:672
=av=get_max_av96() set_av96_direct(av) press'shoot_half' repeat sleep(10) until hook_preshoot.count() > 0 press'shoot_full' repeat sleep(10) until hook_shoot.count() > 0 return av,get_current_av96(), get_av96()10:return:67210:return:67210:return:672
FWIW, I wasn't asking for this to be added to the other sig finders, though I certainly have no objection if you want to.
void add_func_name(char*, uint32_t, char*); add_func_name("imager_active_callback", a, "");
I check t2 matches with a shell script that disassembles the function for each camera model, and then visually verify they look similar.
It doesn't close the shutter, which the other sensor off modes seem to (on non-EOS cams at least)I wonder menu just stops updating the live view frame buffer, rather than actually turning the sensor off?
edit:As far as using this variable, I think it makes sense for the get_current_tv function, and maybe for other stuff like the MF issue. Exposing it in script could also be good, so scripts can detect when the camera has gone to "sleep"
Quote from: reyalp on 20 / November / 2018, 21:22:21FWIW, I wasn't asking for this to be added to the other sig finders, though I certainly have no objection if you want to.I'm now not so sure it makes much sense - the function has to pass several checks to be accepted and it looks quite boring when disassembled (doesn't reference anything known other than the variable).
Started by Stimpy
Started by chocochan
« 1 2 »
Started by Sen
General Help and Assistance on using CHDK stable releases
Started by Sen
Started by reyalp
« 1 2 ... 10 11 »
General Discussion and Assistance