[Solved - Shutter button stuck] T5i button operation broken

Started by anation, August 21, 2020, 05:00:43 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

anation

I used ML on my T5i for 3 weeks just find. A few days ago the buttons stopped working. ML still boots up. I see the information, but I cannot get a response from any buttons. No opening menus, preview, live view, Q, etc. I was able to get into the canon menu by turning to video mode and moving the dial around and quickly pressing the Menu button. This allowed me to format a new card, try to reload ML and finally downgrade my firmware to 1.1.4. The downgrading of firmware did not help the button problem. I am trying to understand how ML caused the buttons to not work and a firmware change did not fix. Does ML change internal code?
Does anyone know how I can revert the camera back to original, so I can install the firmware?
thanks for the help

anation

I found that I can get to review my photos, if I go into video mode, get the menu to show and they press the review button. All buttons work for reviewing photos. I upgraded my firmware to 1.1.5 and buttons still not working correctly. ML still is functioning. I get the lens information, zoom preview in live preview (only in video mode).
Auto focus does not work or 1/2 press shutter button, but i can take photos (very limited abilities)

anation

I have tried uninstalling ML from the camera and the firmware update process just keeps saying "ML already installed" BootDisk flag is set. How can i remove the bootdisk flag if ML will not uninstall?

anation

I have been unable to
Hold the set button to stop ML from loading
Use the Format Card option to remove ML from the card. When I format ML is still there on restart.
Select the Firmware update option and remove ML that way. It always says ML is already installed, restart the camera.

right now I need a way to reset the camera's ROM to something that does not ML on it.

Walter Schulz

Reinstall ML again, wait for 60 seconds after message screen appears. Restart cam.

anation

no change in operations after waiting 60s and restarting

anation

I tried starting with no card in and clearing the settings. Then re-installing ML, waiting 60s then restart. Same results with buttons.

Walter Schulz

What is the actual question?

a) How to deinstall ML?
Answered.

b) How to make button work again?
Not affected by ML.

anation

Was the reinstalling ML to get it to uninstall?  I would like to uninstall but the option does not appear for me. If you could help me get it uninstalled that would be great.

names_are_hard

ML does not install onto the camera.  It is on the card.  Use a new, blank card and ML is "uninstalled".

Walter Schulz

https://wiki.magiclantern.fm/install -> Uninstalling Magic Lantern.
After installation you have to wait 60 seconds and ML will uninstall itself.

Quote from: names_are_hard on September 09, 2020, 05:52:33 PM
ML does not install onto the camera.  It is on the card.  Use a new, blank card and ML is "uninstalled".

Umm ... not quite, it does change the camera a bit: Bootflag. And the only way to reset it is to run ML installation.
A cam with bootflag set will constantly looking for a bootable card, therefore slighty slow down startup and wake-up from powersave. Furthermore it will react with an error screen if a bootable card is found with a different ML version. And older Eye-Fi cards (first gen, I believe) will lock the cam.

names_are_hard

Well, yes, but it's hard to call bootflag enabling "installing".  I was trying to answer anation's earlier question: "Does ML change internal code?" - no, it does not, as soon as you stop using a ML card.

anation

When I wait the 60s after installing, i never get the uninstalling message. And when i reboot the camera ML is loaded, so the boot flag is still set. Is there a way to drain the internal battery so the camera needs to be reloaded?
I have been unable to
Use the Format Card option to remove ML from the card. When I format ML is still there on restart.
Select the Firmware update option and remove ML that way. It always says ML is already installed, restart the camera.

Walter Schulz

Take a small vid of the install process by firmware update option.

anation

Here is a video of starting the T5i, moving to video setting and getting the menu to open, running the firmware update, which starts ML. Allow to stay running for over 60s. Showing the buttons only work in certain situations. Restarting the T5i to see if ML is uninstalled. ML still loaded.


a1ex

Try running these builds; one of them should save a log that might hopefully show what's going on.

https://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log/
https://builds.magiclantern.fm/jenkins/view/Experiments/job/startup-log-mpu/

Best guess so far: half-shutter stuck.

anation

The light only blinked for a few seconds, like it normally reads the SD card. I don't know what it would have gotten on the log files.  It created a CRASH00.LOG and a LOG000.LOG. Can I use these to further investigate?
I could not find how to read the LOG files. Below is the feed from them

CRASH00.LOG
ASSERT: pDialog != NULL
at ./Dialog/Dialog.c:1098, task debug_task
lv:1 mode:0

debug_task stack: 1bdd10 [1bdde8-1bbde8]
0x0008AA1C @ 8b8c8:1bdd50
0x00001900 @ ff4b7c94:1bdd48
0x0007EF78 @ 7f19c:1bdd10

Magic Lantern version : Nightly.2018Jul03.700D115
Mercurial changeset   : 7a3b5fa3f4c6 (unified) tip
Built on 2018-07-02 22:18:41 UTC by jenkins@nightly.
Free Memory  : 175K + 3378K


LOG000.LOG

anation

I was mistaken. Those files are from my ML card. Those were created on August 23. I put the files from the StartUp Log link on a different SD card and started the camera, but it would not record a LOG file.

anation

If someone could tell me how to use the LOG files to understand the possible problems with My T5i, I would greatly appreciate that. I have searched in the forum and on Magic Lantern site to find information about using the LOG files, but cannot find the needed help.

Walter Schulz

Take your ML SD-card. Rename ML folder and autoexec.bin. Copy extracted build contents to card. Insert card and startup cam.
Test both linked versions.

And please edit your previous post. It's a PITA to scroll up and down.

anation

Is there a way to attach files or make the LOG information better to post? I could not find help to figure that out.

anation

I have both of the DM-0000.LOG files. How should I put them in the chat?

names_are_hard



anation

If someone could help me understand how to use the logs to troubleshoot, I would greatly appreciate that.

names_are_hard

Realistically, you can't use these logs to troubleshoot.  We wanted to see them so that someone who understands them well can look at them.  I skimmed them.  No very obvious errors jumped out.

The most likely thing is that the physical button is broken and this is nothing to do with ML.  What happens if you use a completely empty card, does the button work?  If it doesn't, it's probably the button itself that is broken.  If the button works with an empty card, but doesn't work with an ML card, then it might be ML.

a1ex

Using this approach, I've got the following annotated logs:

T5i startup log-a.log
T5i startup Log MPU-a.log

Looking for SW1 (half-shutter) entries:

0.260.933    EventMgr:ff2273dc:8d:03: Already SW1OFF
0.281.407  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 00 00)                                  ; EVENTID_METERING_START_SW1ON
0.281.520    EventMgr:ff227524:8d:03: emDeliverMulticastEvent : SW1ON
0.306.714    Fstorage:ff1d0788:9e:03: fssSW1On
0.381.686     PropMgr:ff2a6e98:33:03: PROP_REMOTE_SW1[0]
9.586.010  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 0b 00)                                  ; EVENTID_METERING_TIMER_START_SW1OFF
9.586.215    EventMgr:ff22769c:8d:03: emDeliverMulticastEvent : SW1OFF
9.620.344  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 00 00)                                  ; EVENTID_METERING_START_SW1ON
9.620.442    EventMgr:ff227524:8d:03: emDeliverMulticastEvent : SW1ON
9.693.040     CtrlSrv:ff39e860:83:03: IDLEHandler UNPRESS_SW1_BUTTON
9.698.658     CtrlSrv:ff39e7bc:83:03: IDLEHandler PRESS_SW1_BUTTON
10.091.657  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 0b 00)                                  ; EVENTID_METERING_TIMER_START_SW1OFF
10.091.793    EventMgr:ff22769c:8d:03: emDeliverMulticastEvent : SW1OFF
10.092.026  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 00 00)                                  ; EVENTID_METERING_START_SW1ON
10.092.128    EventMgr:ff227524:8d:03: emDeliverMulticastEvent : SW1ON
10.230.766     CtrlSrv:ff39e860:83:03: IDLEHandler UNPRESS_SW1_BUTTON
10.230.923     CtrlSrv:ff39e7bc:83:03: IDLEHandler PRESS_SW1_BUTTON
10.459.433    Fstorage:ff1d0788:9e:03: fssSW1On
10.459.472    Fstorage:ff1d0788:9e:03: fssSW1On
11.895.314  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 0b 00)                                  ; EVENTID_METERING_TIMER_START_SW1OFF
11.895.457    EventMgr:ff22769c:8d:03: emDeliverMulticastEvent : SW1OFF
12.011.518     CtrlSrv:ff39e860:83:03: IDLEHandler UNPRESS_SW1_BUTTON
18.676.057  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 00 00)                                  ; EVENTID_METERING_START_SW1ON
18.676.142    EventMgr:ff227524:8d:03: emDeliverMulticastEvent : SW1ON
18.678.878    Fstorage:ff1d0788:9e:03: fssSW1On
18.778.213     CtrlSrv:ff39e7bc:83:03: IDLEHandler PRESS_SW1_BUTTON
0.260.933    EventMgr:ff2273dc:8d:03: Already SW1OFF
0.281.407  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 00 00)                                  ; EVENTID_METERING_START_SW1ON
0.281.520    EventMgr:ff227524:8d:03: emDeliverMulticastEvent : SW1ON
0.306.714    Fstorage:ff1d0788:9e:03: fssSW1On
0.381.686     PropMgr:ff2a6e98:33:03: PROP_REMOTE_SW1[0]
9.586.010  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 0b 00)                                  ; EVENTID_METERING_TIMER_START_SW1OFF
9.586.215    EventMgr:ff22769c:8d:03: emDeliverMulticastEvent : SW1OFF
9.620.344  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 00 00)                                  ; EVENTID_METERING_START_SW1ON
9.620.442    EventMgr:ff227524:8d:03: emDeliverMulticastEvent : SW1ON
9.693.040     CtrlSrv:ff39e860:83:03: IDLEHandler UNPRESS_SW1_BUTTON
9.698.658     CtrlSrv:ff39e7bc:83:03: IDLEHandler PRESS_SW1_BUTTON
10.091.657  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 0b 00)                                  ; EVENTID_METERING_TIMER_START_SW1OFF
10.091.793    EventMgr:ff22769c:8d:03: emDeliverMulticastEvent : SW1OFF
10.092.026  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 00 00)                                  ; EVENTID_METERING_START_SW1ON
10.092.128    EventMgr:ff227524:8d:03: emDeliverMulticastEvent : SW1ON
10.230.766     CtrlSrv:ff39e860:83:03: IDLEHandler UNPRESS_SW1_BUTTON
10.230.923     CtrlSrv:ff39e7bc:83:03: IDLEHandler PRESS_SW1_BUTTON
10.459.433    Fstorage:ff1d0788:9e:03: fssSW1On
10.459.472    Fstorage:ff1d0788:9e:03: fssSW1On
11.895.314  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 0b 00)                                  ; EVENTID_METERING_TIMER_START_SW1OFF
11.895.457    EventMgr:ff22769c:8d:03: emDeliverMulticastEvent : SW1OFF
12.011.518     CtrlSrv:ff39e860:83:03: IDLEHandler UNPRESS_SW1_BUTTON
18.676.057  **INT-36h*:ff31af1c:00:00: *** mpu_recv(06 04 05 00 00)                                  ; EVENTID_METERING_START_SW1ON
18.676.142    EventMgr:ff227524:8d:03: emDeliverMulticastEvent : SW1ON
18.678.878    Fstorage:ff1d0788:9e:03: fssSW1On
18.778.213     CtrlSrv:ff39e7bc:83:03: IDLEHandler PRESS_SW1_BUTTON


In a normal startup log, these entries won't appear, unless you press half-shutter manually (but the first attempt appeared ~ 0.3 seconds after power on - unlikely to be you pressing this button). Half-shutter events are also triggered by the star (*) button, AF-ON (where present) and DOF preview (with electronic lenses only).

There is a sequence of half-shutter press/unpress events after about 9.5 seconds; that's when you tried to navigate Canon menu, from what I could tell. There are events about shooting mode changing around that time, so it might be the MPU temporarily resetting the half-shutter state:

0.143.558     PropMgr:ff0f2e90:81:03: dwNewAeModeDial = 0     ; P
9.571.943     PropMgr:ff0f2e90:81:03: dwNewAeModeDial = 22    ; A+


After 18 seconds, you went back to LiveView using the recording button:

18.660.731     CtrlSrv:ff39dd00:83:03: GuiMainEventHandler.c PRESS_LV_MOVIE_START_BUTTON/PRESS_LV_START_BUTTON


and shortly afterwards, the MPU locked half-shutter again.

I could reproduce the defect on 60D with the following procedure:

1) hold the AF-ON button pressed while in LiveView
2) while still holding the AF-ON button, press MENU to make sure it doesn't work (it shouldn't open Canon menu)
3) while still holding the AF-ON button, perform a mode switch that gets the camera out of LiveView
4) while still holding the AF-ON button, press MENU - this time it should open Canon menu
5) while still holding the AF-ON button, go back to LiveView using the recording button
6) while still holding the AF-ON button, press MENU - this time it shouldn't work (it shouldn't open Canon menu)

Also worth noting:
- When using the half-shutter button, mode switches from/to LiveView did not unlock the MENU button
- when using the * button, I could open Canon menu at step 6 (repeatable); from your logs, I wouldn't expect this
- on 5D3, I could not unlock the MENU button at all using the same procedure

Based on this test:
- is there any unusual autofocus activity, e.g. at camera startup, or after leaving Canon menu?
- if you touch the half-shutter button, or the * button, does this unlock the keys, even temporarily?
- if you change the functionality of the * button from CFn (try all available options), does it help?
- can anyone with a 700D perform the above test and document the expected behavior?
- if the faulty button is half-shutter, I can try a workaround, to manually "unpress" it from software, without any guarantees of success. Are you able to compile from source?

In any case, I believe the defect is on the hardware side (half-shutter signal somehow stuck, possibly the * button). These events are not coming from the main CPU, where ML runs, but for the MPU (a small microcontroller handling buttons, shutter mechanism and a few other functions). Updating the firmware or uninstalling ML will probably not change anything.

anation

Thank you A1ex for looking into the logs and Names_are_hard for guiding me. It is a hardware problem and nothing related to ML. Before I replaced the shutter components I tried this fix from Youtube. A WARNING: You can damage your camera by inserting the battery before all moisture is out of the electronics. I left mine over night to make sure all the alcohol was evaporated. DO NOT create a new problem for your camera.



It worked, a true miracle, what a blessing. The half-shutter click is now working. Everything is functional like both of you had pointed out as the issue.
I have learned lots and glad I am able to keep using ML on this camera.
Thank you again

names_are_hard

Hurrah!  Just a dirty switch - really happy you found a fix :)