EOS 550D shows up Err 70

Started by Manik2303, December 28, 2015, 06:36:20 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Manik2303

I got my Canon 550d bricked like many others who had reported similar issues. This is what I had tried so far,
Tried upgrading the firmware.
Ran the below command,
gphoto2 --set-config /main/imgsettings/imageformat=0
gphoto2 --set-config /main/imgsettings/imageformatsd=0

Tried changing few C.Fn settings.

Downloaded autoexec.bin which a1ex had uploaded for a similar issue.
Initiated debugging thru "do not click me!" in ML and found out the below line. Later changed the ISO to a different value.
ASSERT : Iso != 0

After changing ISO to different value the new debug log didn't show up "ASSERT". But ERR 70 continues to show up on screen when i take a picture or move dial to movie mode.

Appreciate if any one can point me to right direction .....

a1ex

So, you are not getting ERR70 right after you boot, and you can also use Canon and ML menus, correct?

Instead, you are getting ERR70:
- when you try to take a picture
- when you try to switch to movie mode
- when you enter LiveView in photo mode (?)

Did you find any crash logs on the card?

Also, which autoexec did you download?

Manik2303

You are right, I am able to get through the menu without issues and the camera boots up fine. The error 70 shows up when I take a picture or shoot a movie.
I have the autoexec.bin which I used,

autoexec - "https://www.dropbox.com/s/zkfdepw4xheqgz8/autoexec.bin?dl=0"

DM Log - "https://www.dropbox.com/s/g7masr9qx1kn84a/DM%20%282%29.LOG?dl=0"

Crash log - "https://www.dropbox.com/s/5ewz62w6f8at6br/LOG000.LOG?dl=0"

a1ex

I assume you already tried to clear all Canon settings.

The DM log (which shows what happens when capturing a full-res picture - just the capture part, no mechanics or CR2/JPEG conversion) shows at some point:


**INTERRUP:ff280aa8:93:06: Head Error(22497)


I'm not sure what to do about it. Next week I can try to flash your ROM onto my 550D, to see if I can reproduce the issue (though, I doubt it). If that won't work, I'm afraid it might be a hardware issue.