5D Mark II doesn't turn on, but write logs etc!

Started by ms_unlucky, May 16, 2013, 01:41:46 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

ms_unlucky

Dear all,

unfortunately it seems that my 5DMkII camera is bricked since a few days. All I remember is that I swapped cards with my other camera which does not have MagicLantern installed. The card from my other camera is not bootable and does not contain an autoexec.bin file. I always swap cards if the card of the camera I need is becoming full (and wait these five seconds), so this shouldn't be a problem.

After switching on the 5D2 camera it seemed to be dead. First I did was removing the battery and waiting for more than a day. A few years ago I encountered a similar issue after using another camera during heavy rain. There removing the battery for a long time helped excellent. ;)


Here's my diagnosis listed:
- Canon firmware 2.1.2 running
- removed battery and card and waited for 1.5 days
- inserted battery again, tried with two original, fully charged batteries
- if switching on without CF card nothing happens, but background illumination of large display switches on
- it is possible to toggle background illumination on and off with menu key
- if switching on camera with CF card inserted the card led blinks and background illumination of large display switches on
- same like without card it is possible to toggle background illumination on and off with menu key, but also background illumination can be switched off with release button
- with full press of release button card led is on for more than a second
- I didn't test camera with a lens attached now

- Of course I had a look how to help myself first
- I run the Diagnostic tools by replacing the autoexec.bin of my bootable MagicLantern card
- LED blink test: works
- Startup log: wrote four log files with file sizes from 12kB to 97kB, but too complicate for me to read
- ROM dump: dumped full 256MB ROM to card's root folder
- magic.cfg file has actual file date, so this seems to be updated


Unfortunately from now on I don't know how to unbrick the camera by myself.
Next step from my side is to buy a HDMI cable to see if this output works.

I appreciate your help very much! Thanks a lot in advance! :)

ms_unlucky

Dear all,

after investigated a bit I don't know any more if the described error is caused by MagicLantern. At least I got the logs with help of MagicLantern and copied the most interesting parts together from seven logs, so please don't be distracted by the line numbers.

Like planned I was able to get an HDMI cable and connected the cam to an external monitor. This monitor also remains black, the backlight of the large display doesn't turn ob, but I am not sure if the external screen is really recognized by the camera.

160:   125.394 [MC] HDMIConnect ---> (0)


The camera perceives that there is an error with the displays and wrote the following lines:

1612:  2713.778 [MC] Disp Error : 70

1640:  2726.621 [BIND] GUI_STATE : WARNING
1654:  2728.143 [GUI] IDLEHandler START_WARNING_CAMERA_ERR
1660:  2728.397 [MC] disp error.

1064:  2180.532 [LV] IMAGE_MUTE!i!i 1 3215
1127:  2217.383 [GUI] DlgLiveView.c VisibleDialogItemForBlackout
1128:  2234.307 < GUI Lock > GUILock_TurnOnDisplay (PUB)
1129:  2234.392 [GUI] PROP_LV_ACTION[0]

1149:  2251.137 ERROR [LVCAP]Image Power Failure
1157:  2253.749 [STARTUP] startupErrorRequestChangeCBR (0x82218001)
1158:  2253.829 [STARTUP] startupErrorRequestChangeCBR : ErrorSend (120, SHUTDOWN)

1159:  2269.847 [GUI] DlgLiveView.c UnvisibleLvDialogItemForBlackout



Further it is not possible to take any pictures. Pressing the shutter button is recognized, but as there is no control of the mirror no file is being written:

1324:   923.731 [FM] fmcStartCreateJob (ID = 1, 1, 100, 1163)
1325:   923.762 [FM] fmcStartCreateJob : Notified (0x519048b0)
1326:   923.798 [FM] fmExecCreateFile (Drive = 1, Dir = 100, File = 1163)
1327:   923.918 [FC] _FC_CreateFilePath (1, 100, 1163, 1)
1328:   924.082 [FW] A:/DCIM/100EOS5D/IMG_1163.CR2, off = 0x0, size = 0x2325a15
1329:   924.349 [FM] fmRemoveFile (0x519048b0)



There are a few erros and warnings I do not understand. The AdjustmentMemorySizeForDmac shows up more than ten times with different sizes after pressing the LiveView key.

118:   113.909 [PROPAD] ERROR GetPropertyData ID = 0x010100A5
119:   113.995 [PROPAD] ERROR GetPropertyData ID = 0x010100A6

722:   679.678 [GUI] MasterResultCBR_ErrBattery(0x8731b8)

1054:  2179.482 [LVCFG] WARN AdjustmentMemorySizeForDmac dumy = 64 bytes



Most logs end with VolumeSetTimeout which sounds good for me as this might be just the last item loaded.

1383:  3767.833 [AUDIO] _VolumeSetTimeout [/font]

Two logs end with PROP_EFIC_TEMP.

1129:  4221.014 [LVCFG] PROP_EFIC_TEMP 208 Ž
1130:  4221.139 [DL] PROP_EFIC_TEMP (80)



Conclusion: from my view there might be an error with the internal camera cache or so, but that's only an assumption. I will send in the camera to Canon beginning next week and try every tip I get before then.


Thanks and cheers!

a1ex

Is there any line saying ASSERT in the logs? That one contains the exact error message.

Post the full logs, maybe it helps.

But from "1149:  2251.137 ERROR [LVCAP]Image Power Failure"... it doesn't sound good at all.

ms_unlucky

Hi Alex, thanks a lot for your help. There is no ASSERT in the logs.

I've uploaded the most recent full log to http://www.datenschlepper.de/log006.log now. There I also pressed some keys and tried to investigate what is possible and what not.

ms_unlucky

So, the camera is in a repair shop since Monday and will hopefully be fixed there.

Previously I managed to connect the cam to my computer and write the original Canon firmware using Canon EOS Utility. This "update" from version 2.1.2 to 2.1.2 unfortunately didn't change anything.

The interesting part is, that in the last step of preparing the firmware update which cannot be done via EOS Utility the camera display turned on, but was very dark, having low contrast and lots of stripes. At least I was able to see something to go through the writing process, but based on this observation I assume that the camera has a hardware failure.