Messages

Oh, okay. That just about nullifies everything I thought then, it can't be a timing issue related to the objective. If it was some SD cards being slow to start up or something, would guess the bug would appear with clean firmware then too and it clearly doesn't.

From testing it appears the bug is more to do with the SD Card.

The cases seemed mostly random, I didn't understand the issues with SD's. The only test that I see reproducing it every time in this thread so far is the 11-22mm objective. I don't own one, but if that is true, it would be easier to debug even if the problem had nothing to do with the objective but it just makes it happen.

Any news regarding the issue? Since there's been no replies for a good while I assume not, but as an EOS M owner myself too, I'd of course like to see this get solved. I would love to have focus peaking!

It seems weird that the bug appears also when TL is not loaded but the loader is used to fire up canon's code. The thing that with the 11-22mm objective fully extended always manifests the problem and fully retracted (storage position) doesn't, tells it very likely has something to do with the lens initialization and it might be very sensitive to timing at the first power on of the camera. I assume with the 11-22mm it's almost the same there was no lens installed if it's retracted.

How much does the configuration with minimal autoexec.bin add to the startup time? How long does it take from the power-on to the jump to canon code with TL versus without TL?

Could it be just that Canon's code works with pure chance, the code is just magically waiting at the correct location / done some required initializations if only clean Canon firmware is used? When TL adds a bit of code to the startup, the lens has done it's own stuff before Canon's code reaches some point it should've been at a few milliseconds before and thus won't work.

I might possibly find the answer to the next question by searching a bit, but I'm just going to ask.. Is the power to the objective hardwired or can it be controlled from the software? Could the objective power on command (or some other thing that tells the lens it is attached) be removed from the startup of Canon firmware and make TL command it after everything else has loaded properly?


Edit: Just an idea, if the above would be true, it could mean that with clean firmware, no TL, the bug could be reproduced by having the lens a bit loose, powering on, and very quickly (almost simultaneously) turning the lens so it gets contact. Could be almost impossible to get the timing right of course..