Hello,
since yesterday my 5dm2 shows Err 70's typically (but not always) after a restart, either due to auto-power off or power on-off via main switch. This error occurs independently whether I use ML or not.
This typically happens only on the first shot - subsequent shots typically work (obiously without restart).
I already tried:
- complete reset of Camera and Cx modes (via menu)
- external & internal format of CF card
- installed latest ML nightly build
- complete reset of ML settings
any hints?
here is a logfile:
QuoteSat Jul 9 09:34:55 2016
(waiting for log file contents)
sorry, but qouting it does not work and I see no possibility to attach it... you can grab it here:
logfile (http://www.kis.uni-freiburg.de/~albe/log000.log)
ok, some days later:
* I get the err 70 on 95% of all startups
* it does not produce a crash log, although it says "Saving debug log..."
* it's independent from the CF card used (tried 16GB, 4g and even a 1GB Microdrive)
* running CF card benchmarks does not lead to any error
* I can continue shooting after the err 70!
* I never got a second err 70 after the cam has booted
the situation is a bit frustrating, although I can live with it - I set the power down time to 30 minutes....
--alex.
Relevant lines from the error log:
1826: 10890.143 [FC] _FC_CreateFileStart (1, 100, 2081, 0)(0x2)
1827: 10890.181 [FC] ERROR _FC_CreateFileStart : Already Exist (0x2)(0x2)
1828: 10890.278 [FM] ERROR fmcNotifyCreateJob : FC_CreateFileStart (0x82110013)
1829: 10890.424 [STARTUP] startupErrorRequestChangeCBR (0x82110013)
1830: 10890.472 [STARTUP] startupErrorRequestChangeCBR : ErrorSend (119, SHUTDOWN)
...
1903: 10965.827 [MC] Disp Error : 70
If this error is caused by some setting saved in the ROM, I should be able to reproduce the error in QEMU. I'm not there yet with CF file I/O emulation, and neither with still image capture emulation, but both are doable, so I'll keep an eye on this issue.
Meanwhile, please PM me a recent copy of your ROM (after the error) and - if you still have one - an older copy (before the error). They can be found in ML/LOGS on your card.
things got worse :(
from time to time it is not possible at all to shoot with the camera after a "warm boot" (either wakeup from sleep or off-on); when I press the shutter button simply nothing happens. In addition the Display is not working, i.e., I cannot open the Menu... the top (LCD) display is working. Again, there are no crash logs.
in the log files there are some "new" error messages:
Quote
5: 10.216 [STARTUP] startupEntry
6: 30.112 [PROPAD] ERROR Not Exist Valid ComboPackages!!
...
31: 90.631 [PROPAD] ERROR SIZE SetPropertyData ID = 0x02070007(0)(4)
...
104: 112.813 [PROPAD] ERROR GetPropertyData ID = 0x02070008
105: 112.879 [PRP] ERROR NOT FOUND PROPERTY ID = 0x02070008 L:1102
106: 113.301 [PROPAD] ERROR GetPropertyData ID = 0x02090000
107: 113.340 [PRP] ERROR NOT FOUND PROPERTY ID = 0x02090000 L:1102
...
805: 548.223 [GUI] CurrentLensName[EF24-105mm f/4L IS USM]
806: 548.476 [GUI] MainEventHandler PROP_ERROR_FOR_DISPLAY(0)
807: 548.570 [GUI] PROP_PHOTO_STUDIO_MODE (0)
complete logfile can be found at: http://www.kis.uni-freiburg.de/~albe/log000-160724.log
after a "reboot" (removal of battery) i can shoot as "normal" - some chance for an err 70, some chance for normal operation.
--alex.
Hm, this smells like ROM corruption...
I'm tempted to try restoring default Canon settings, but I'm not sure whether this will solve anything or create even more trouble.
the only "positive" thing about it is that the err. 70 after reboot only appear in roughly one of three cases.
--alex.
This deepens the mystery. I've recovered a 5D3 with a similar error (could not find some properties), but once it managed to boot with a correct property block, the other (invalid) property blocks were no longer used, and were overwritten with correct data eventually.
Do I have the chance to "boot with a correct property block" - where should that come from?
Does it make any sense to switch the ML version?
--alex.
Quote from: f6l613 on July 28, 2016, 03:42:36 PM
Do I have the chance to "boot with a correct property block" - where should that come from?
I'll look into it, but it's not straightforward.
Quote
Does it make any sense to switch the ML version?
I'd rather say you should use plain Canon firmware for a while. Just don't disable the bootflag in the camera, since if anything wrong happens after that and the camera will no longer boot, I'd have no way to troubleshoot it any more.
Problem is, until I'll be able to reproduce your error (either in QEMU or on my 5D2), I'm not sure what advice to give.
QuoteJust don't disable the bootflag in the camera
sorry I do not understand what this means...
Means: Don't run "Firmware update" with ML card inserted.
If you want to switch ML versions: Just delete Autoexec.bin, *.FIR and ML directory and copy extracted nightly build contents to card.
ok... also found it in the FAQ.
So i formatted one CF card and things changed:
Now I cannot continue shooting after an Err 70 - camera says busy (on top lcd and in the viewfinder). And this behavior is independent whether I use ML or the Canon firmware. I.e., now I have to remove the battery, switch on the camere, hope that there is no Err 70. If this works, the camera shows no abnormal behavior - strange!
things got even worse, now the rear display completly stopped working. This makes it difficult to diagnose what's happening...
I guess the motherboard of the camera is slowly dying - probably the best option is to get the camera repaired.
--alex.