It Works!!!

[janzu77]

Thanks Martin for the explanation!

I kind of thought that it would work that way but wasn't sure that I understood the instructions correctly. This closes the case for me now

Exactly. If you insert a Bootable SD, prepared with either EOScard or the installer, and you delete the autoexec.bin, it will not boot and hang. Remove the battery and format the card, or copy the autoexec.bin to it.

Now, if you just FORMAT it, it will remove the bootable state and it will run normally like nothing happened. Same happens when you insert a new card, it has no bootable state, so it won't try to find the autoexec.bin on it. To make it bootable again, run the EOScard util and copy ML files to the root dir of the card.

Ok, I was a bit worried on the sentence in the manual:

If you have a bootable SD card and have the BOOTDISK flag set in the camera (which the installer does), and you do not have an AUTOEXEC.BIN file on the card the camera WILL NOT BOOT! It will hang and not wake up until the battery is removed.
If you encounter a "locked up" camera, quickly remove the battery.
When in doubt, remove the battery and reboot.

So I just wanted to make sure that I'm not misusing the FW somehow

--
Martin Ocando
-------------------------

--
http://kousja.kuvat.fi/kuvat/

 

[CyberpunkDad]

You really need to take the time to investigate the Magic Lantern Wiki located here:
http://magiclantern.wikia.com/wiki/Unified#Downloads

The process goes like this:
1) Remove any accessories like battery grip or flash.
2) Run process to update firmware to enable ability boot from card.
3) Add boot flag to card.

4) Add autoexec.bin and other files to card. Firmware file from step 2 no longer required.
5) Power on camera, wait for the custom code to load.
6) Press trash can (delete) button to access ML menu.

There is a lot more to it, and the PDF is essential.

That being said, the code is constantly being developed. If you want the most stable build, use the latest release. If you don't mind being bleeding edge, use the experimental.

That being said, I always, no matter what when I am done using my camera take out the battery to make sure I know it's powered off. The few times that I have had a problem with ML locking my T2i, I've known it instantly. I'm not willing to risk assuming though, so I pull my battery when done.

Not a big deal, takes 2 seconds with the batter grip, more of a pain for people who don't use the grip.

Just my two cents.

 

[beagle1]

awesome lighting shot !

I kind of thought that it would work that way but wasn't sure that I understood the instructions correctly. This closes the case for me now

Exactly. If you insert a Bootable SD, prepared with either EOScard or the installer, and you delete the autoexec.bin, it will not boot and hang. Remove the battery and format the card, or copy the autoexec.bin to it.

Now, if you just FORMAT it, it will remove the bootable state and it will run normally like nothing happened. Same happens when you insert a new card, it has no bootable state, so it won't try to find the autoexec.bin on it. To make it bootable again, run the EOScard util and copy ML files to the root dir of the card.

Ok, I was a bit worried on the sentence in the manual:

If you have a bootable SD card and have the BOOTDISK flag set in the camera (which the installer does), and you do not have an AUTOEXEC.BIN file on the card the camera WILL NOT BOOT! It will hang and not wake up until the battery is removed.
If you encounter a "locked up" camera, quickly remove the battery.
When in doubt, remove the battery and reboot.

So I just wanted to make sure that I'm not misusing the FW somehow

--
Martin Ocando
-------------------------

--
http://kousja.kuvat.fi/kuvat/