1
Camera-specific Development / Re: Magic Lantern for 5D Mark III 1.2.3
« on: March 17, 2014, 09:13:15 PM »
This is fantastic news! Thanks to chris_overseas, A1ex, and everyone else who helped make this happen!
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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.
No one has some hints for me? It seems a bit crazy to reinvent the wheel.Chris, you've made this offer a number of times since early November. Clearly it's been seen, and those with the relevant knowledge have decided not to respond. Seems rude to me that they haven't responded at all -- you're after all not simply complaining about wanting some new feature, but willing to do the work, which the administrators and devs are always encouraging complainers to do -- but perhaps they have their reasons for not even telling you 'no'. Maybe try sending a PM.
I would like to try and update ML so it runs with firmware 1.2.3 on the 5D Mark III. My understanding is that I need to do the following:I'm new to this however and I've hit a wall at the very first step. How do I get a dump of 1.2.3? I tried updating my 5D3 to 1.2.3 and then flashing 5D3-113-bootflag.fir. Perhaps not surprisingly, this dies with the following error: "Update file error. Please check the memory card and reload the battery and try again". I've also tried to run both the scripts here: http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper but nothing is produced. I'm not convinced the scripts even run. As instructed I set the "SCRIPT" string in the boot sector (using EOScard) and created the appropriate script.req and extend.m files - is there something else I need to do too or does Canon Basic scripting not work on DSLRs, just the point'n'shoots? Can I perhaps extract and decrypt the dump from Canon's 5D300123.FIR file instead? If I need to create my own .fir file for 1.2.3 to dump the ROM, how would I go about doing that - presumably it needs signing? Can I make an autoexec.bin to dump it? Is there another trick I can try?
- Obtain a ROM dump of the 1.1.3 and 1.2.3 firmwares.
- Load these dumps into ARMu.exe.
- For each address is platform/5D3.113/stubs.S, find the equivalent address in the 1.2.3 firmware by comparing the disassemblies.
- Create a new platform/5D3.123/stubs.S file using these newly discovered addresses.
- Update various build/compile scripts as required.
Obviously various developers here know how to get a ROM dump but I haven't been able to find this process documented in detail anywhere. Any hints would be greatly appreciated!
Appealing to Pelican, coutts, 1%, a1ex, g3gg0, or anyone else who can help me learn more about this.
A couple of relvant threads:
http://www.magiclantern.fm/forum/index.php?topic=2602.msg73403#msg73403
http://www.magiclantern.fm/forum/index.php?topic=5695.msg61657#msg61657
does anyone know if they will update ML to work with the latest FW from canon?No idea when ML will move to 1.2.3. I've downgraded to 1.1.3 and so have many others on this forum. I've had no problems, nor to the best of my knowledge has anyone on this forum ever reported a problem from their downgrading to 1.1.3. See here: http://www.magiclantern.fm/forum/index.php?topic=9248.0
I am at the latest and heard that you cannot go back to the 113 ver….?
I am desperate to try it out but don't want to damage anything…..
I am a virgin to ML and not willing to fry my MKIII to just test it out…
Tobias
can anybody direct me to where i can find 1.1.3 its no longer on the European canon site. And my body has been updated to 1.2.3.
i would jump for joy for the windows version!
I go straight to import seq in PPro CC and edit.
I have been going raw to dng to acr to psd. would be nice to go raw to psd.
my thoughts went to unicode/ascii (chracterencoding) and something like that. maybe it cant read/write/find the proper file because of differences in right that. wrong character-encoding leads to "FileNotFound". i didnt had such an issue, so finally cant help by now, but maybe "our" worldwideweb can.. have to search and read about it.
regards chmee
@mvaHi chmee,
(1) Do you have .net4.0 installed?
(2) what OS? Windows-core or emulation/virtual system?
(as every time: more information leads to more accurate answer)
regards chmee
Disabling the bootflag is very easy, one line of code in fact. The problem arises because of how risky it is to disable it, the devs don't want people claiming ML bricked their camera and so to prevent this the ability has been taken away for now until a more reliable way has been found.
a1ex should be able to create a .fir to disable the bootflag safely.
I am not able to disable the bootflag on my T5I.
If this delay is not tolerable you have to reset the flag.
Perhaps because it goes against their maintenance policy, in other words words Canon supports their own upgrade but won't endorse old software. The way I read it is that Canon cannot restore the old software for you.