Messages

All right, the problem was what i expected. After running 'install.sh' again from the 70D branch it was resolved. Now I'm getting 'SFDATA.BIN missing' error. So I need https://bitbucket.org/hudson/magic-lantern/src/unified/modules/sf_dump/. A couple of days and I think I will be able to the qemu successfully. 

Here's what I'm doing to load 70D 1.1.2 firmware ( Digic 5 )

1. Load ROM1.bin
2. Select ARM
3. Procesor options -> Edit ARM Architecture -> ARMv5TEJ -> OK -> OK https://i.imgur.com/zXWXlaM.png
4. Kernel Options 1 -> Uncheck ''Delete instructions with no xrefs' and 'Perform no-return analysis' -> OK https://i.imgur.com/IEPqtAg.png
5. Press OK to load the .bin
6. Check 'create RAM section'
7. Here are the values that I've put into 'Disassembly memory organisation' https://i.imgur.com/oB2yW0G.png
8. Jump to FFFF0000, press C
9. JUMP to 'i don't remember' look at A1ex post, and press C

I believe that works good, hope that will help somebody.

I'm having a problem with running './run_canon_fw.sh 70D,firmware="boot=0" -d romcpy' command. Im getting the fallowing error:

Code Select Expand

(process:13481): GLib-WARNING **: 22:40:59.262: ../../../../glib/gmem.c:489: custom memory allocation vtable not supported

I've changed the branch to 70D_merge_fw112, repeated all the steps, no luck. I haven't run 'install.sh' script from 'contrib/qemu' though. Was that necessary?

Yes, please try the portable ROM dumper. You should be able to replace autoexec.bin on some older ML card; if that doesn't work, you will have to make the card bootable (EosCard/MacBoot/make_bootable.sh).

Hello Alex! I don't think I get it. There is no developer that has 70D to try that out? I own 70D, and doesn't use ML that often, so I could sacrifice not having ML for 'noone knows how long'. Though.. How likely is it, that It won't be supported at all?