Messages

Wow! The 50% of the ML users are Hungarian...

Another question regarding stability..

I don't understand if anyone prefers stability why even think about to use alpha stage software...

["firmware update programupdate file cannot be found.Please check the memory card and reload the battery and try again."]

"firmware update program
update file cannot be found.
Please check the memory card and reload the battery and try again."

It seems the camera stuck in a firmware update procedure. It needs a valid .fir file to finish the update.
Follow the instruction below:
Remove the card from the camera.
Remove the battery from the camera.
Turn your camera off.
Format a card on your computer.
Put an original Canon fw file to it. (Get http://pel.hu/down/eos5d2-v212-win.zip unzip it, copy the .fir file to the card's root)
Insert the prepared card to the camera.
Insert a fully charged battery to your camera.
Turn it on.
Wait until the camera finds the .fir file.
OK to enable the firmware update.
Wait until the firmware update finishes.

Stability is crucial to me..

Then wait for the stable version.

[New Fairly Stable Build Here: http://www.magiclantern.fm/forum/index.php?topic=7987]

New Fairly Stable Build Here: http://www.magiclantern.fm/forum/index.php?topic=7987

Let me know if this is stable enough so I should set up this to use by EOScard.

i just sent my t5i back after 2 weeks to get the 70d. it was a tough decision knowing that ml isn't available for the 70d, but i got a price that was too good to pass up on.

i have development experience. i'm fluent in .net, c++, objective c. i'm learning java (for android development) as well.

i've already downloaded the dev environment so i'm ready to get cracking on this 70d port as soon as we get some fw from canon.

Theoretically it's not necessary to wait until the first fw upgrade released by Canon.
I don't remember which camera was but there was a camera dumped without Canon fw upgrade.
The program searched the IO routines in the ROM then used them to dump the ROM.
Unfortunately I've never seen the source code of this...
...and I can not sign a fw upgrade file properly for 70D but you should ask Indy who is the master of these things.
Also there is another option to dump the ROM by LED blinking... (you have to find the LED address first, and it has the same signing problem)
With the ROM dump, you can start to port ML to 70D.

... there is a limit of maximum minutes that 7D can record (say 5 or 10 minutes? I have to consult the manual), I reckon that the recording might very likely cut itself out way before it reaches the 4GB limit.

No, it is no 5 or 10 minutes limit.
The limit is 29:59 min or 4GB (which comes first).

So technically speaking, 7D is more like a still camera with limited capacity for video capture rather than a video camera.

As all the other DSLRs like the 5D3.

Feedback please?  Did you install?

You are so patient...

  What about getting a dump of 1.2.3, does that also require decrypting 5D300123.FIR or can it be pulled off the camera?

The bootflag fir also dumps the ROM.
If you dumped the 1.2.3 please send me a PM.

BTW this guy claims to have done it : http://www.magiclantern.fm/forum/index.php?topic=6035.msg78315#msg78315

This is the third link of chris_overseas...
And there is another guy too...

I don't know of any reason why the 5D3 would be any different to the other cameras when it comes to making this call, I just don't think the work has been done to create a disablebootflag.fir for it yet. I don't know how to make such a .fir file myself (I'm going to try when I have some more time). Alternatively I could create an autoexec.bin that contained the code from bootflag_toggle() in it that gets triggered somewhere "sensible". Whether that is wise/safe to do I'm not at all sure...

On a related note, does anyone know how/if I can get the source to 5d3-113-bootflag.fir? Does it originate from bootflags.c, or perhaps by enabling CONFIG_DUMPER_BOOTFLAG (as in boot-hack.c)? Given time I can hopefully figure this out myself but if someone knows already and was willing to point me in the right direction that would be helpful. I want to understand what it does not just to look at the bootflag handling but also because I would like to get a dump of the 1.2.3 firmware and try to get a port to that underway.

Still not clear why we should worry about to call DisableBootDisk on 5D3 and should not worry on the older cameras.
Anyway, instead of create a modified autoexec.bin it would be more safe to create a disableboot.fir.
Unfortunately the signing method is not public for the new cameras so I cannot make this by myself and could not even check the code in the 5d3-113-bootflag.fir

... and b) to get to know why this is working on digic4-based cameras but not on 5d3/6d: If it's not for the lack of trying, I could imagine Canon intentionally changed their design so that the bootflag cannot be removed, and this would be mean they're at last taking semi-official note of ML, though not in a very commendable way.

For me the EnableBootDisk and DisableBootDisk routines  on the 5D3 seem very similar to the earlier cameras' routines.
I asked before in different topics but maybe I missed the answer so could you tell me what is the difference on these new cameras in the way they handle the bootflag?
Or the first ML fw update how enables it? Is there any trick besides to call the EnableBootDisk?
If Canon wants to disable booting from the card then they can easily do it in many different ways but the routines are still there and I cannot see any sign of intentional change.

[change the sensor]

Its a firmware update not a hardware update, you have to send it in because they are not releasing the firmware.

No, it is not only a fw update but they change the sensor.

Thanks

What I don't get though is why the cropped-mode gives magnified images.

If I take the 1920x1080, for example, and crop out the center area, it doesn't magnify it- it's just a crop?

Don't be lazy just think about it...

Pelican, A little bit late but I may have a solution for you. Unregister all batteries from your 1DX, clear all settings and custom functions, detach the lens. Take the main battery out. Now, reboot the camera with no lens attached, a freshly charged Canon battery and run the firmware update.

Thank you but what you suggest is impossible. If I can boot the camera to do anything like unregister batteries then the problem is not exists at all.
And the battery was not registered and there was no lens attached.
Anyway, the camera went to the Canon service and they fixed it in two days.

I did it several times and it worked every time for me, so just follow the instructions exactly.
Check the fir file and be sure if not the same as the 1.1.0 and then try the fw update again on your camera.
Make sure you copy ONLY ONE .fir file to your card.

It means you didn't alter the 1.1.0 fw with the patch or you copied the wrong fir to the card...

"Increased IR sensitivity for astrophotography (IR cut filter is modified to achieve a hydrogen-alpha (Hα) light (656nm) transparency approximately three times higher than the EOS 60D) allowing crisp, clear images of reddish, diffuse nebulae." - Canon
So you cannot do the same with any filter. The sensor get more spectrum of light, not less.

As I see 1% merge the changes from the main repo regularly to his fork so the two versions are not so different.
However I hope he will send his important changes back to the main repo soon.

Use EOS Utility to downgrade your firmware.
Follow the user's manual if you are not sure how to do it.

[All]

All of the Komputerbay 128GB cards are known not to work with 5D2 if you just copy the files to them.

I do not yet own a Lexar but if people on this board a correct it seems the 1000x cards are the way to go, the 800x for some reason even rated at 120mbs seem to have trouble reaching even half that speed. I would be interested to hear if anyone with a 800x has managed to hit 80mbs on their 7D?

The Lexar 800x cards have Max. Read Speed: 120 MB/s and Max. Write Speed: 45 MB/s.
So don't expect too much from that card.
(The Lexar 1000x has 150/145 MB/s spec.)

Most probably you haven't bricked your camera.
Follow the troubleshooting steps and you will see.

Following the steps given by britom on page 31, it seems to me that the EOS Utility 2.8.1 no longer exists in the linked dropbox location. Any help? To my understanding it needs to be this exact version of EOS Utility, or will the newer ones do as well?

BTW big thanks to the amazing Magic Lantern Team for their great work and to everyone involved!

You don't need the EU at all...

I have six Yongnuo RF-603 (4 for Canon, 2 for Nikon, these are working with Pentax too). Works great, cheap, easy to use.
I worked with some RF-622 for Nikon but never tried the Canon version.
I've also built some DIY radio remote controller for Nikon flash (the protocol is more or less reverse-engineered), but hard to find a fast radio transmitter (without a long delay) so finally got the radio chip out from the RF-622s and use that.