Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - pfluger

#1
Quote from: themichael on August 02, 2013, 10:43:20 PM
Sorry, I wasn't clearer. The three ROM bin files are after the update in the camera.
If you have the three ROM bin files this means the bootflag in camera was successfully set.

Quote
EOScard 1.36 crashed on two computers (Win7 and XP) even if nothing is clicked.

Will try once more with all new downloads.

**EDIT: Still no joy. The autoexec.bin goes in the root corrct? I am using a 16MB 133x card. Somebody have a checksum for the generated firmware file?
Copying the autoexec.bin and ML folder is not enough, you have to use the EOScard tool to enable the bootflag on the CF card. Even with the bootflag enabled in camera using the patched firmware, it will only boot the CF card if that too is marked for boot.
#2
I finally managed to get autoboot working. I thought it might help someone if I shared roughly the steps I took:

- Get the 7D 1.23 firmware file (7d000123.fir) and patch per the instructions at http://www.magiclantern.fm/forum/index.php?topic=3974.msg58898#msg58898

- Flash this patched firmware file using EOS Utility. I used a very old 2.8.1.0 version of EOS Utility. I got an error (something like cannot write to media  card). I could work around it by putting the 1.23 fir file on the CF card and then starting the firmware update with EOS Utility. It still showed the error message but then started the firmware update using the .fir file I copied manually. I recommend using an empty CF card.

- Take the CF card out of the camera.

- If the flashing was successful you should see a couple of new files on the CF card (named something like ROM...bin). You can delete them.

- Copy the ML folder from the 7D Magic Lantern Alpha 2 to the CF card. Copy the autoexec.bin to the root folder of the CF card.

- Download the EOScard utility. You can find a link at http://wiki.magiclantern.fm/3rd_party_software

- Enable the EOS_DEVELOP and BOOTDISK flags (not sure if EOS_DEVELOP has to be enabled, but it didn't work without it for me)

- Put the CF card back in and start the camera. You should now be able to access Magic Lantern as usual by pressing the trash button.

Disclaimer: These steps worked for me, but I take no guarantee these will work for you :)
#3
Quote from: ty66 on July 13, 2013, 02:08:05 PM
It's running fine. You can also use non bootable CF card to run the official alpha 2 version instead of autoexec/autoboot version.
Did you have to build the autoexec version yourself or is it somewhere available for download?
#4
Quote from: tonybeccar on July 03, 2013, 03:16:29 AM
Wha-wha-wha-what????! We can???! Could you please be a GOD and orientate us OR better upload the compiled version??? DYING for a bootable alpha.. using it every day with my 7D!!!

Thank youuuu!!!! :)
+1000 Pretty please :)
#5
Quote from: gmfbln on May 08, 2013, 10:41:28 AM
I know there's lots of amazing things on the horizon for ML - but for me and maybemany others an interims version which does not have to be loaded via firmware update all the time would be a real relief.

Could such a thing be released without too much work on dev's side or isthis functionality just not ready yet?

Thanks and sorry if I asked a question posed 100 times before.

Good luck with your endeavour!
+1

I think the devs said only once it reaches beta/stable will this be added.

Definitely the only missing feature for me, too. Sometimes there is just not the time to manually load the firmware.
#6
Quote from: Pelican on May 05, 2013, 12:37:47 PM
You can compile the autoexec.bin for your 7D, the main repo contains all the necessary sources, just type 'make 7D'.
The extra step you need is enabling the bootflag on your camera.
There is a dumper fwupdate  which dumps the memory and enables bootflag. It's for an old fw version maybe for 1.1.0 so you should downgrade your camera's fw first with EOS Utility.
But much better if you trust in the developers and use the alpha until they decide to make a beta version which autoloads itself.
You can compile your own autoexec to 7D from the beginning.
Thanks a bunch for that info! Too bad about having to downgrade, that's definitely a showstopper for me. So yeah, I will patiently wait for a beta ;-)
#7
Before I start digging through all the dev stuff and repositories, is there everything in the repositories to easily compile an autostarting version for the 7D (without any additional coding)? If so, a pointer to where to look for would be great. Thanks :-)
#8
Archived porting threads / Re: First 7D alpha released!
November 18, 2012, 12:51:09 AM
Any news on getting ML to autostart? I am actually pretty happy with how this alpha 1 works, and any additional features would just be icing on the cake. It has been working without a problem for me the last weeks. Loving focus peaking, zebras and histogram.

Only thing is having to load ML everytime I turn on the camera. So many times I didn't use ML because I needed the camera right away.

Not sure what is involved, but if it is a copyright issue, maybe this could be circumvented by providing a patch tool to the end user to merge parts of the official firmware update file into the MIL fir file?