EOS M srewed up (doesn't seem bricked however)

Started by Ernani, November 27, 2015, 01:49:08 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Ernani

ok, will retry. what am I supposed to see if everything goes right? a readable error message?

a1ex


Ernani

no matter what settings I use I only get gibberish. I suspect the problem is on the way the M is blinking its LED: instead of a solid color alternating on and off (which I believe would be the proper manner) it alternates between green, red and yellow rapidly. seems we're running out of options.

a1ex

Indeed.

Let's see if we can do file i/o. Delete ML/LOGS/ROM*.BIN (since you already made backups) and try to start ML (with a regular nightly). After about 1 minute, remove the card and see if the ROM files were re-created.

No need to upload them, I only want to know if they were created or not.


Ernani

however all I did was reinstate the original autoexe.bin. maybe I should try a fresh build?

Ernani


Ernani

From the install guide:

Right after opening the card door, Canon firmware accesses the card without turning on the LED (yes, with the main switch turned off). If you remove the card too early, the camera will freeze and will drain the battery, or even cause permanent damage! You will be running random code (remember you are loading executable code from the card), and we can't do anything about it without reflashing Canon firmware with our own code.

Does anyone know what that means? could it be tried as an "all or nothing" last chance?

a1ex

Since the display test didn't work, I wouldn't rush to reflash the main firmware. The display test only uses bootloader routines, so it should work even if the main firmware is corrupted.

We can still try to ignore the green LED - just tell me the RGB spotmeter values for the 3 colors.

Ernani

ok, will try to read the blinks anyway and post a screenshot of it.

Ernani

Quotetell me the RGB spotmeter values for the 3 colors.
if that is what u meant.

Ernani

wait, what if I place a colour filter in front of the lens? long shot but maybe...

Ernani

here is a short clip of how the M uses its LED. http://we.tl/ZeO47hXPwy

side note: I was using the dualiso module in conjunction with the full res silent picture build when it started to bug. might be related.

Ernani


a1ex

If you use a red filter, I suggest fine-tuning it like this:
- first make only the green LED blink, and bring down the exposure until the other camera detects no pulses
- then, let the diagnostic blinker run, and hope it syncs


Ernani

 :o :o :o It worked!!
I'll try and save a snapshot every time the screen is full. good news is that the M doesn't seem to get tired and goes beyond the 15 minutes merrily blinking away.

I must confess it is quite exhilarating to watch this dead camera using its secondary processor to talk about "the other side" via a blinking LED while I hold 3d glasses in front of it to filter the green signals... kudos to you a1ex!

Ernani

http://www.mediafire.com/download/8blueag7jxvah6l/New+folder.rar

these are the screens I captured.  after that first lucky time (VRAM5.PPM) I couldn't again make it work even if I used the same exposure (f2.0 - iso 6400 - shutter 640).

in the meantime the camera somehow turned on a couple of times and I could use it normally. if it happens again is there anything I can do that would help?

Ernani

today I am having better luck  with the blinker. will be posting screenshots soon. (is it ok to send them via mediafire? I don't know how to post pictures here in the forum)

ernani

dfort

There are probably several of us watching on the sidelines and we'd love to see some photos and screenshots. This post helped me:

http://www.magiclantern.fm/forum/index.php?topic=10760.0

Basically what I do is copy the BBcode URL that Flickr generates and only keep what is in the "img" tags in the post. (Including the opening and closing "img" tags in the brackets of course.)

Ernani

My internet connection was down for a couple of days so I went on troubleshooting the eos m and made a PDF with snapshots and the progress I made.
http://www.mediafire.com/view/4el1ssn7ktn7smc/magic_lantern_fix.pdf
will also post some screenshots here soon.

later

a1ex

Since the camera is working now, I'd say just use it. As long as you have a ROM backup, it should be fine.

Regarding the errors:

- 206000a: this was fixed recently (110efb0). I thought the error affected only 650D and 700D, but at a closer look, the EOS M was affected as well.

- mlv_snd depends on mlv_rec (the error message could be a little more clear).

Ernani

As I feared I'm back at point zero. i.e.: camera with ML card - red LED blink and nothing else.   camera without ML card - green LED blink and nothing else.
During the 2 days it worked I would occasionally get errors like it suddenly turning off or the display going dark while the camera kept working (I could still take pictures or shoot videos even if nothing showed up on the screen).
now I'm re-running the deblink to check if anything changed.

say, that loop at the end of the deblink I posted (disable power save / enable power save); isn't that strange? the errors I was getting (dark display, turning off) seemed as if the camera was mistakenly going into power save mode.


a1ex

Quote from: Ernani on December 04, 2015, 06:58:51 PM
display going dark while the camera kept working

To me, this suggests a hardware issue on the display side (most likely weak electric contact). At startup, Canon code probably expects the display hardware to reply something back - if it doesn't, camera doesn't boot.

I assume the display test doesn't work either (that is, only the backlight is active).

The powersave messages are harmless - they appear every time there is a communication from the MPU to the main CPU.

Ernani

I was afraid that might be the case  :'(
well, if it is of interest to anyone I'll keep posting here for any further development (display replacement, unexpected fix...)

thanks a1ex and all ML developers for turning these otherwise rather lame cameras into little powerhouses!

LSeww

Quote from: dfort on November 27, 2015, 05:23:43 AM
It seems that maybe it is hanging when reading the card. Have you tried other cards? You might also try this:

Remove card, remove battery, reinsert battery and start camera without card--that usually works for me. Next step is in the Canon menus reset to default settings. If that helps you should probably also delete the ML settings file on the card to go back to the ML default settings. If you're still having problems turn off the camera boot flag by running the ML installer and waiting a minute for it to turn off the boot flag. Worse case scenario reinstall the Canon 2.0.2 firmware and hope for the best.
Resetting settings worked for me, thank you!