Messages

Now this might have been obvious to folks, it was not to me and I found it when I was retrying the whole process again.

With 32gd card -
1) Formatted the card in the camera
2) Not sure if this formats the boot flag so Quick Format it with the computer.
3) Extract ML and copy the extract + Boot fir file to the card
4) EOScard to update EOS Dev and boot flag on the card
5) insert card in the camera, start the camera
6) Try to update firmware, the camera says battery is too low to update (Previously at this step, after firmware update, I would get message about Magic Lantern Rescue and to remove the battery)
7) Exit Menu... groaning that I need to charge the battery before I try this again, I press the trash can button
8 ) and ML Loads!!

Ofcourse thinking about it it makes sense. The BOOT fir file only flips the boot flag on the camera, this has already happened. so from the second card onwards, I dont need the BOOT fir file or the firmware update process. I only need the card as bootable and ML on the card.

Thing is: if that was a checksum problem, camera wouldn't work (either black screen or a crash) as it would still load the (broken) binary.

With that problematic card (after preparation, and with ML files on it) - do you see any activity from card access LED immediately after turning the camera on?

The behaviour I saw with the current problematic card is how it was with the other card too. for sake of clarity in discussing lets call the previous card 64gb (which worked after renaming autoexec) and the second card as 32gb (because that is the capacity of the cards).

So 64gb card-
Format card, Camera in M mode, remove card, extract ML to the card, copy BOOT FIR, EOScard updates card to bootable, insert card into camera, run firmware update, ML Rescue screen asking to remove battery, battery removed, card removed, on computer - update autoexec file name on the card, insert card back to camera, camera does not appear to start, press SET and start, camera starts, rename autoexec on computer, reinsert card, start camera, ML loads on pressing trash can button.

32gb card -
Format card, camera in M mode, remove card, extract ML to the card, copy BOOT FIR, EOS card updates card to bootable, insert card into camera, run firmware updaate, ML Rescue screen asking to remove battery, battery removed and reinserted, camera started, ML did not load.

I removed 32gb card, inserted 64gb card, used camera on the weekend.

After Kitor's message just now, inserted 32gb card, LED shows long blink and one bleep after closing compartment. Started camera, LED showed one long blink and then rapid blinks more than 4 (couldnt count, probably 5 or 6). however this time, pressing trash can button loads ML.

wonder if Camera has a cache or something that is taking time to clear.

Trying the whole process again with 32gb card.

First card, which worked after renaming autoexec to debug
D:\>certutil -hashfile autoexec.bin MD5
MD5 hash of autoexec.bin:
c62ebcd2e8281610e1e53fa64ecb4e4a
CertUtil: -hashfile command completed successfully.

second card
D:\>certutil -hashfile autoexec.bin MD5
MD5 hash of autoexec.bin:
c62ebcd2e8281610e1e53fa64ecb4e4a
CertUtil: -hashfile command completed successfully.

Sorry late reply. Priority to Work that pays the bills

C:\somepath.where.ML.is.extracted>certutil -hashfile autoexec.bin MD5
MD5 hash of autoexec.bin:
c62ebcd2e8281610e1e53fa64ecb4e4a
CertUtil: -hashfile command completed successfully.

Yes and yes.

Renaming was for debugging and won't solve any issue with black screen.
Don't create myths.

ok boss! no intention of creating myths, just trying to figure out how to install ML.

I dont understand how would I create another ML card. I have tried the process with another card now -
1) Format card in the camera 2) change camera to M mode 3) remove card, extract ML to the root of the card, copy the BOOT200D FIR to the root of the card, use EOScard.exe to make the card Bootable 4) insert card into camera 5) get into menu, firmware update - results in Magic Lantern Rescue screen asking to remove battery 6) Remove battery, reinsert, restart, ML has not loaded, pressing trash can does nothing.


I will reiterate my appreciation to everyone who created the build and to Walter for helping me debug.

I wonder where you got this.

Current release is stable. Just lacking features.

Main use cases:
1) Webcam via HDMI. 30-minute timer can be disabled via ML menu
2) Cropmark overlays for liveview composition. Up to 9 can be stored on card and you can build your own customized cropmarks.

I read that and thought I could disable 30 min timer via ML menu.

Option 2 is not available in this build and don't ask for a release date.

ok, I wont

Copy extracted build content to card and run EOSutility as described above.

This did not work until I followed your instructions to rename the autoexec.bin and then started camera while pressing the set button.

Thank you for all the help and no doubt the hard work behind the scenes!

Thanks for the help Walter. Followed instructions, pressing the Set button and switching on the camera did start the camera (phew!). however trashcan button did nothing, switched off and on again, now trash can button starts ML (yay!)

however the main reason why I wanted ML - record movies for more than 30 min - does not seem to be enabled. The Movie Menu of ML is empty (see picture).

Could you please help with -
How would I install ML on other cards? Do I follow the same renaming autoexec.bin to autoexec.bin_, let the camera get stuck, then start by pressing the set button?

How do I uninstall ML to go back - follow the process of updating the firmware and waiting for 60 sec to uninstall or format card? how do I reset the bootflag back?

Is the movie menu expected to remain blank? the posts above mentioned that this was a working feature.

Followed the instructions fully expecting nothing different to happen... but!
Removed battery and card, renamed autoexec.bin to autoexec.bin_
inserted card, inserted battery, closed compartment door, tried to start up the cam - nothing happens, camera does not start, screen remains dark. Removed Battery and Card.

reporting back. (must say I am worried now that the camera is not starting!)

No difference to the files on the card btw, no logs, no additional files generated.

thanks for the reply again. Restarting cam and pressing trash can button does nothing.  the camera is not recognising autoexec.bin yet.

Thanks for replying Walter. This has however not worked.

I started EOScard as Admin user, checked the boxes for EOS_DEVELOP and BOOTDISK as in the picture below and Saved. Did not get any errors and the save was successful.


Attaching another picture showing the contents of the card before I inserted it into the camera. The contents are - ML folder, DCIM and MISC folder, autoexec.bin and BOOT200d.FIR.



Inserted the card into the camera, went through firmware update and still got the same Magic Lantern Rescue screen. The before and after update of boot flags shows no change. The firmware update process ends with the line that says 'You may now remove the battery'. Magic Lantern does not get installed.

I am new to Magic Lantern, trying to install it to my EOS 200d. Followed the instructions -
1) Camera in Manual Mode, firmware confirmed 1.0.1
2) tried with 64GB SD card as well as 32GB micro SD with adapter. Formatted the card
3) Extracted files/folders from the link from the first post in this thread to root of SD card on my laptop running windows 11 (also tried on windows 10 laptop)
4) Copied fir file to root of SD card using my laptop running windows 11  (also tried on windows 10 laptop)
5) inserted the card back into the camera, started camera, in camera mode went to the menu for firmware, Camera asked for updating firmware, proceeded with firmware update.

6) Instead of updating the firmware, it looks like only boot flag was attempted to be flipped and I got the Magic Lantern Rescue screen as attached. Restarting, removing battery/restarting nothing is working and the installation is not successful. logically it seems like the autoexec.bin is not getting executed.


</a>



scratching my head on how to get this to work. Can anyone help please?