Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - sirminder

#1
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.
#2
Thanks for the response guys.

Quote from: IDA_ML 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?

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?  :-\

Quote from: a1ex 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?

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.
#3
Removed embedded code attempt.
#4
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.
#5
You are correct. Nowhere in your statement did you suggest that.

However, you hinted that a possible reason for the problem was that he formatted the card "inside a cam without ML".

That left me wondering if reformatting the card after installing ML was a little known secret or just good practice.
#6
Quote from: Walter Schulz on July 13, 2019, 09:38:48 AM
Sounds like you formatted the card with a cardreader or inside a cam without ML or inside an ML cam with Q option activated -> card no longer bootable.
Easiest workaround: Reinstall ML.
So are you suggesting to format a card Twice? Once prior to installing ML and then again after installing ML?

Sent from my SM-G930F using Tapatalk

#7
Quote from: a1ex on June 23, 2019, 04:53:30 PM
To troubleshoot this problem, try the current lua_fix build from the download page. In case of incomplete shutdown, it should keep the SD LED always on, so you should notice it right away.

That change doesn't seem to be included in Danne's builds.

Quote from: Danne on June 24, 2019, 04:19:06 PM
New version:

- Shutdown routine from lua_fix(Thanks a1ex)
.
.
.
EDIT: Noticed lua isnĀ“t compiling. Will take a look. Stay tuned.[/s] FIXED!

I did a few tests with Danne's JUN25 build and there is still some battery drain when the camera is set to OFF.

For the record, the issue that I am having does indeed seem to be with the Viltrox speed booster, AND NOT ML as I previously stated.  Even though I have the latest FW on the Viltrox, I am still having this problem and I seem to be the only one.

Other than removing the battery or even the Viltrox, does anyone have any other suggestions?

Thnx

#8
Thanks for the help and feedback. I will troubleshoot further as suggested and report back my findings.

Sent from my SM-G930F using Tapatalk

#9
Hi everyone, new guy here.  After seeing some of Zeek's videos, I was motivated to jump on the MLV bandwagon and got me a used EOS M.

I loaded it with Danne's ML from early in June (thanks for your work and dedication Danne!).  Also, I went ahead and got the Viltrox EF-EOS M2 Speedbooster, so I can use some of my EF lenses.

I have been doing some tests using the Canon 50mm 1.8 and I am very pleased with the results so far, but still need to go through all the settings and menus.  However, I seem to be having a battery drain issue...only when the SD card with ML is inserted.  I have been going through some of the 116 pages that are now in this thread, but I cannot find the answer to fix this.  Some people had said upgrading the firmware on the Viltrox to 1.4 fixed their problem, so made sure fw1.4 was on mine.  Still, if I leave the battery in the camera along the Viltrox attached and the ML SD card, the battery will be drained while the camera is off.

To test what the problem could be, I did the following:
- Camera Off, Viltrox w/50mm 1.8 attached, 64G ML SD Card inserted, I switched from AF to MF on Lens and back - led on camera flashes a few times = battery drain.
- Camera Off, Viltrox w/50mm 1.8 attached, NO ML SD Card inserted, I switched from AF to MF on Lens and back - NO led at all and battery keeps its charge.

Unfortunately, I do not have an EOS lens to test without the Viltrox.

Is there a menu setting that covers this? Sorry if this has already been covered before, but I am still reading through everything here.

Thanks.