Author Topic: EOS M with err 70 - Diagnostic Logs included - Help  (Read 533 times)

sirminder

  • New to the forum
  • *
  • Posts: 9
EOS M with err 70 - Diagnostic Logs included - Help
« on: November 11, 2020, 12:20:10 AM »
I picked up a second EOS M at a good price considering it had the dreaded Err 70 message.  Also, some of the buttons are not working on it: Up, Right, Set, Turn Wheel Left or Right.  Lucky for me, the touch screen is working so I can at least navigate using it.

However, upon exiting the Canon menu, the err 70 message is displayed.  Removing the battery trick does not work and upon turning the camera on, I am greeted with the set the Date option.  After setting it, the error message comes up again.  If I by-pass the Date option and set the date when navigating in the menu and turn the camera off and on, err 70 comes up right away.  It is not until I remove the battery, that it asks to set the date again upon turning the camera back on.  Not sure if that is of any help, but it does not hold the date settings in memory when battery is removed.

Searching for the err 70 has become a daily routine and I have already tried a few things.  Luckily, the camera still allowed me to install ML via the firmware option and it also had fw 2.0.2.  I loaded up the latest nightly of the M and one of Danne's build that I also had on my other M to test things.  Sadly, I did not get any further than before and err 70 is still there.

I then used the Diagnostic tools to run a few tests and logs:

1. Picture after using the portable display test.



2. I saw it blink only once, so I hope that means it passed the LED blink test.

3. Here is a link to the ROM*.bin files [removed]

4. After running the Startup-log-mpu, a DM-0000.LOG was generated.
 - https://pastebin.com/raw/Es4R6bVC

5. Here is another log file. 3 errors were found at lines 777,778 and 908, but do not know what to do with them.
 - https://pastebin.com/raw/LbkAVxjX


At some point during testing of what works and what does not, I must have cleared the Canon settings and defaulted to the CA photo mode.  Now, I no longer have the extra menu options listed along with the update firmware options.  No matter if I boot in Video mode, I am still locked out.  The good thing is that the bootflag is still set and I can at least use cards from my other M running ML.

Other things tried:
- Start camera with & without card
- Start camera with & without lens
- Start camera with manual lens

If someone is able to help, it would be greatly appreciated.

sirminder

  • New to the forum
  • *
  • Posts: 9
Re: EOS M with err 70 - Diagnostic Logs included - Help
« Reply #1 on: November 11, 2020, 12:30:21 AM »
Removed embedded code attempt.

IDA_ML

  • Hero Member
  • *****
  • Posts: 885
Re: EOS M with err 70 - Diagnostic Logs included - Help
« Reply #2 on: November 11, 2020, 02:23:26 PM »
Do you get the camera working in Life View?  Do you see the image on the screen?  If not, your sensor may be damaged and needs replacement.  This was the case with my EOS-M.  I couldn't see an image on the screen in Life View.

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 12466
Re: EOS M with err 70 - Diagnostic Logs included - Help
« Reply #3 on: November 11, 2020, 05:21:19 PM »
The error from lines 777 etc, is not something to worry about - I've got it in many startup logs saved from good EOS M's.

The DM-000 log looks quite good - but it doesn't cover the ERR70 event. Can you trigger the error within the first 20 seconds, so it will be included in the log?

sirminder

  • New to the forum
  • *
  • Posts: 9
Re: EOS M with err 70 - Diagnostic Logs included - Help
« Reply #4 on: November 12, 2020, 12:27:13 AM »
Thanks for the response guys.

Do you get the camera working in Life View?  Do you see the image on the screen?

No, I cannot get the live view to work. The only thing being displayed is the canon menu.   I took a picture with my other M and swapped the cards to view picture.  Only a very small portion of the actual picture is seen on all for corners of the screen.  The rest of the screen is black, but the histograms and file information is visible.

How did you go about replacing the sensor? Or, did you?  :-\

The error from lines 777 etc, is not something to worry about - I've got it in many startup logs saved from good EOS M's.

The DM-000 log looks quite good - but it doesn't cover the ERR70 event. Can you trigger the error within the first 20 seconds, so it will be included in the log?

I did another test and got the err 70 before the 20 seconds were up.  Here is the link to the DM-002 log file:

https://www.dropbox.com/s/jxehpkbif0ty6f9/DM-0002.LOG?dl=0

I could not open the log file completely let alone get it to paste correctly in pastebin.

Once the camera was on, I did the Konami code (UP, UP, DOWN, DOWN, LEFT, RIGHT, LEFT, RIGHT, INFO, SET) to verify if the buttons are being detected or are actually faulty.  I then half pressed the shutter button and triggered the err70.

Again, many thanks for assisting.

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 12466
Re: EOS M with err 70 - Diagnostic Logs included - Help
« Reply #5 on: November 12, 2020, 07:06:46 AM »
Quote
14.217.667         Evf:00034e78:91:06: Image Power Failure

That explains why you are not able to enter LiveView. I don't know if replacing the sensor is enough to fix this, or whether it's a bad connector or a faulty driver circuit on the main board. If you find out, please keep me posted, as this is an error I've seen a few times - but no way to diagnose it without opening the camera.

IDA has a different issue - iirc an intermittent one - but it's also on the image capture side. I wasn't able to diagnose it remotely, without physical access to the camera.

The last line appears to indicate a bug in the logging code. The debug string was "[Post]%s %s(%s)(%d) %s", and there was an issue with the (%s) argument. Hopefully the error can be reproduced on a good camera as well :D


IDA_ML

  • Hero Member
  • *****
  • Posts: 885
Re: EOS M with err 70 - Diagnostic Logs included - Help
« Reply #6 on: November 12, 2020, 08:31:41 AM »
Sirminder,

I did not replace the sensor - that is beyond my technical skills.  I am not even sure that it is the sensor causing the trouble.  I just opened the camera and reseated all the connectors as A1ex suggested but this did not fix the issue.  Repair would have been more expensive than buying a new one.  Fortunately, I found a used one in a good condition and bought it at a good price.  The old one is now sitting in its box and I plan to keep it for spare parts if I may need them.

A1ex, did you manage to fix yours?

sirminder

  • New to the forum
  • *
  • Posts: 9
Re: EOS M with err 70 - Diagnostic Logs included - Help
« Reply #7 on: November 12, 2020, 11:10:42 AM »
I think this might have something to do with the issue.



Now I really have to open up the camera and look inside to see if there is anymore of this going on.  If so, I'll give it a shot to either clean up and make sure everything is seated properly as IDA did.

@a1ex  Before the error came up, were you able to see if the button sequence I pressed showed up in the log?  I know that this would be the least of my problems, but I could at least scratch that off the list of things to repair if needed.

More to come.

Thanks.

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 12466
Re: EOS M with err 70 - Diagnostic Logs included - Help
« Reply #8 on: November 12, 2020, 11:52:49 AM »
Here you go (howto):

Code: [Select]
0.676.391  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 11 01 00)                               ; GMT_GUICMD_LOCK_ON
0.676.600  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 12 00 00)                               ; GMT_GUICMD_CLOSE_SLOT_COVER
0.676.733  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 26 01 00)                               ; GMT_GUICMD_PRESS_BUTTON_SOMETHING
0.711.587  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 0a 00 00)                               ; BGMT_UNPRESS_ZOOM_OUT
0.711.746  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 09 00 00)                               ; BGMT_UNPRESS_ZOOM_IN
0.713.322  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 1c 00 00)                               ; Unknown GUI event
4.141.943  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 26 01 00)                               ; GMT_GUICMD_PRESS_BUTTON_SOMETHING
4.142.166  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 00 01 00)                               ; BGMT_MENU
4.184.613  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 0a 00 00)                               ; BGMT_UNPRESS_ZOOM_OUT
4.184.777  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 09 00 00)                               ; BGMT_UNPRESS_ZOOM_IN
4.186.119  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 1c 00 00)                               ; Unknown GUI event
7.094.984  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 26 01 00)                               ; GMT_GUICMD_PRESS_BUTTON_SOMETHING
7.095.216  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 19 01 00)                               ; BGMT_PRESS_DOWN
7.228.965  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 19 00 00)                               ; BGMT_UNPRESS_DOWN
7.298.088  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 26 01 00)                               ; GMT_GUICMD_PRESS_BUTTON_SOMETHING
7.298.252  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 19 01 00)                               ; BGMT_PRESS_DOWN
7.447.705  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 19 00 00)                               ; BGMT_UNPRESS_DOWN
7.899.904  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 26 01 00)                               ; GMT_GUICMD_PRESS_BUTTON_SOMETHING
7.900.048  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 1b 01 00)                               ; BGMT_PRESS_LEFT
8.065.160  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 1b 00 00)                               ; BGMT_UNPRESS_LEFT
8.860.851  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 26 01 00)                               ; GMT_GUICMD_PRESS_BUTTON_SOMETHING
8.861.006  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 1b 01 00)                               ; BGMT_PRESS_LEFT
9.018.022  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 1b 00 00)                               ; BGMT_UNPRESS_LEFT
9.876.111  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 26 01 00)                               ; GMT_GUICMD_PRESS_BUTTON_SOMETHING
9.876.346  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 01 01 00)                               ; BGMT_INFO
10.072.643  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 01 00 00)                               ; Unknown GUI event
14.048.170  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 26 01 00)                               ; GMT_GUICMD_PRESS_BUTTON_SOMETHING
14.048.894  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 0a 00 00)                               ; BGMT_UNPRESS_ZOOM_OUT
14.049.030  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 09 00 00)                               ; BGMT_UNPRESS_ZOOM_IN
14.061.437  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 26 01 00)                               ; GMT_GUICMD_PRESS_BUTTON_SOMETHING
14.074.828  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 04 05 00 00)                                  ; EVENTID_METERING_START_SW1ON
14.160.863  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 05 06 26 01 00)                               ; GMT_GUICMD_PRESS_BUTTON_SOMETHING
14.162.888  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 04 05 0b 00)                                  ; EVENTID_METERING_TIMER_START_SW1OFF
14.163.138  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 04 05 07 00)                                  ; EVENTID_ACCUMULATION_STOP
14.163.356  **INT-36h*:0001dedc:00:00: *** mpu_recv(06 04 05 00 00)                                  ; EVENTID_METERING_START_SW1ON

Ignore the zoom events - they are sent internally by the MPU when switching GUI modes. Also, GMT_GUICMD_PRESS_BUTTON_SOMETHING means some button was pressed - it's sent together with some other button events.

IDA_ML

  • Hero Member
  • *****
  • Posts: 885
Re: EOS M with err 70 - Diagnostic Logs included - Help
« Reply #9 on: November 12, 2020, 12:50:58 PM »
Now I really have to open up the camera and look inside to see if there is anymore of this going on.  If so, I'll give it a shot to either clean up and make sure everything is seated properly as IDA did.

Just make sure you get the right screw driver for that.  The screws have been fixed with some kind of blue adhesive and are very difficult to unscrew. If you do not have the proper screw driver, you can easily damage their heads.

Here is a detailed video on how to open the EOS-M:


Good luck!