Hi guys,
I've been playing with ML some time ago (very early alpha builds). I've done some memory dumps to figure out some initial VRAM addresses back then. One day, when making a memory dump, ML stopped booting and I can't get it to boot ever since. The standard Canon stuff is still fine, though.
Possible cause:
Around that time, I was performing memory dumps in the 0x4 segment (on a very alpha code base). I also did repeated two succesive series of dumps from 0x0 to 0x4, though that would crash the camera often midway.
I also tried some dumps of the higher segments (all the way up to 0xF). The segments above 0xC (iirc) seemed very slow to dump (mapped to (slow?) rom?) and caused very frequent crashes. I never really tried dumping those again, but I believe that's about the time the problem started, so it may be related.
If I recall correctly, those crashes involved that the camera would stop dumping to the card midway dump (write LED of sdcard turned off) and I could not turn the camera off by flicking the on/off switch, so had to pull out battery.
I may have gotten some err:xx as well, don't remember exactly.
I've been unable to lead any autoexec.bin file since.
Tried remedies:
Obviously, I made sure the card was bootable, and double checked by dumping and examining the first sectors of the sdcard.
I've tried using churchin's .fir file from the opening post to set and unset/set the boot flag multiple times, without succes.
I've tried reflashing the stock Canon firmware and re-installing ML, without succes.
Peculiarity:
If I recall correctly, using Churchin's .fir to set the boot flag is supposed to crash the camera. The install guide explicitly says to take out the battery when the write LED goes off.
When installing ML for the first time, that .fir file did indeed crash the cam iirc, in the way that flicking the on/off switch did not turn the camera off and I needed to take out the battery.
If I use the .fir file now, I can just turn of the camera normally afterward. It turns of cleanly and I get the "sensor clearing" picture.
This makes me think it's somehow not setting the actual flag.
Another thing:
Trying to disable the bootflag from the config file by adding the line:
magic.disable_bootdiskf = 1
to the file magiclantern.cfg (and I've also tried magic.cfg, as they both seem to be mentioned here and there) still makes the .fir display "Set bootflag". Is this normal, even if you want to unset it?
Questions:
1) Has anyone ever had something similar happen and/or has a fix?
2) For the .fir file from churchin at the opening post of this thread: if you set the config file to unset the bootflag, is it supposed to show something different then "Set bootflag" on the screen?