Re: magiclantern.fir - T2i

[ectobuilder]

Re: magiclantern.fir - T2i

Let's say I've installed Magic Lantern and everything works great. However when I format my SDCARD, then Magic Lantern should be "fully uninstalled"? Correct?

And when I reinstall Magic Lantern I have to do the "magiclantern.fir" step again?

Under which condition do I NOT do the "magiclantern.fir" step again?

What happens if I DON'T format the SDcard and just stick a new vanilla SDcard in without Magic Lantern. Does that mean it is uninstalled as well?

When does magiclantern.fir get deleted off of the NVRAM?

 

[kgimedia]

Let's say I've installed Magic Lantern and everything works great. However when I format my SDCARD, then Magic Lantern should be "fully uninstalled"? Correct?

Yes

And when I reinstall Magic Lantern I have to do the "magiclantern.fir" step again?

No

Under which condition do I NOT do the "magiclantern.fir" step again?

All except a new camera.

What happens if I DON'T format the SDcard and just stick a new vanilla SDcard in without Magic Lantern. Does that mean it is uninstalled as well?

Yes but the boot flag is still there on the camera. If the card is not bootable it will default to the camera.

When does magiclantern.fir get deleted off of the NVRAM?

Only when you want to stop using ML.

Have fun!

 

[deltoidjohn]

Once you install the magiclantern.fir it stays on the camera until you remove it. You only need to do it once. Basically what this does is install a bootflag which tells the camera to look for an autoexec.bin ML file on the SDHC card if the SDHC card is bootable. The autoexec.bin is what actually runs the Magic Lantern features, and stays on the SDHC card..

The two variables in running ML are whether or not the card is bootable, and whether or no the autoexec.bin file is loaded on the card. So once the magiclantern.fir has bee installed you have four possible outcomes:

1. Card is bootable, with autoexec.bin present: ML will load when turning the camera on.
2. Card is bootable with no autoexec.bin present: Camera will hang because it gets stuck in a loop looking for the ML file on the card.
3. Card is not bootable, with autoexec.bin present: Default firmware will load because card will not allow the bootflag to access ML.
4. Card is not bootable, no autoexec.bin present: Default firmware will load.

Formatting a card in camera removes the bootflag (edit - this should say "Formatting a card in camera makes in non-bootable") as well as deleting the ML files, so if you format a card it will run with default firmware only. If you make a card bootable but don't load ML onto it, or if you delete all ML files from the card without also making it non-bootable, you can damage your camera - if the camera hangs, remove the battery a.s.a.p.

Using a clean 'vanilla' SD card will run the default firmware. However you can instantly revert to ML by inserting a bootable card prepared with the autoexec.bin file, without having to reinstall the magiclanter.fir.

 

[ectobuilder]

Formatting a card in camera removes the bootflag

I thought that formatting the "card" (i.e. SDHC or SDXC) will remove the autoexec file but will keep the bootflag in NVRAM on the camera?

In the instruction manual it says to do the following to uninstall ML from the camera (not SDHC or SDXC):

"...put this in magic.cfg to reset the DISKBOOT flag from the
camera:
magic.disable_bootdiskf = 1"

 

[deltoidjohn]

Sorry, what I meant to say was formatting the card in camera makes it non-bootable.

Consistant with what I say in the first sentence of my post, the bootflag stays on the camera until you remove it by adding the extra line of code to the .cfg file.

Too many confusing terms and names!