This is a small program that saves the contents of your camera's ROM contents on the card.
It won't modify your camera - at least, not intentionally
This is *NO* Magic Lantern buildLatest download: autoexec.bin (2020Aug17, updated for EOS R/RP/90D/250D - only after enabling bootflag via UART)DIGIC 4+:
1300D 2000D 4000D DIGIC 6:
5D4 750D 760D 80D DIGIC 7:
200D 6D2 77D 800D DIGIC 8:
EOSR EOSRP 250D 90D M6 II G7X III M50 SX70 SX740 Master/Slave:
5DS 5DSR 7D2 7DOldies:
1000D 30D 400D 40D 450D 5D - built from
c019793 with CONFIG_BOOT_FULLFAT=y CONFIG_BOOT_DUMPER=y CONFIG_BOOT_SROM_DUMPER=y
-
green = confirmed working (either the last version, or a slightly older one)
-
blue = not tested, but likely to work (based on other similar models, or on previous tests)
-
purple = not tested, there may be surprises, but fixable (based on previous tests)
-
orange = not tested, but unlikely to work (based on previous failures)
-
red = not working, no idea how to fix
Supported cameras:
- tested in QEMU: 5D, 5D2, 5D3, 5D4, 6D, 6D2, 7D, 7D2, 40D, 50D, 60D, 70D, 77D, 80D, 400D, 450D, 500D, 550D, 600D, 650D, 700D, 750D, 760D, 800D, 100D, 200D, 1000D, 1100D, 1200D, 1300D, EOSM, EOSM2, M50, SX70.
- other models from the same generation may work, too (see the FIR list for models not yet running ML).
Not supported:
- cameras running PowerShot firmware (including EOS M3, M5, M6, M10, M100)
Requirements:- a memory card formatted as FAT12/16/32 (exFAT won't work)
- for autoexec.bin: boot flag enabled in the camera (e.g. ML already installed) + bootable card (EOSCard, MacBoot, make_bootable.sh, QEMU image)
- FIR versions do not require any boot flags (just place on the card and run Firmware Update)
- check MD5 checksums after dumping
(important!)Source code:
-
recovery branch- compiled from
platform/portable.000 with
CONFIG_BOOT_FULLFAT=y,
CONFIG_BOOT_DUMPER=y and
CONFIG_BOOT_SROM_DUMPER=y
Old limitations (for 2018 and earlier dumpers only):
Requirements:
- a very small SD card or filesystem (important!)
- no important files on the card (these routines are buggy and may destroy the filesystem!!!)
- boot flag enabled in the camera (e.g. ML already installed) + bootable card (EOSCard, MacBoot, make_bootable.sh, QEMU image)
- alternative: FIR version does not require any boot flags
- check MD5 checksums after dumping (important!)
Formatting a larger card at a much lower capacity (e.g. 256MB) does the trick. For example, you can write the SD image that comes with QEMU to your SD or CF card (follow this guide). This image contains the portable display test and is bootable (so, you can test it in the camera straight away).
Original post:
Lately I've got a few softbricked cameras to diagnose, and struggled a bit with the ROM dumper from bootloader: it wasn't quite reliable. A while ago, g3gg0 reimplemented it with low-level routines (which worked on his camera, but not on mine). Today I looked again at the old approach, and it looks like the file I/O routines from bootloader had to be called from RAM, not from ROM.
So, I've updated the code and need some testing. I've emulated this in QEMU, but the results may be different on real hardware.
What you have to do:
- download
autoexec.bin- place it on a card without any important data on it (it might corrupt the filesystem if anything goes wrong)
- the display looks roughly like this:
http://www.magiclantern.fm/forum/index.php?topic=14732- after it's finished, look on the card, and you will find 4 files: ROM[01].BIN and ROM[01].MD5.
- you
don't have to upload them, just check the MD5 checksum:
- Windows: you may use
http://www.winmd5.com/ - Mac, Linux: md5sum -c *.MD5
- repeat the test on the same card (let it overwrite the files), then on a card with different size (and maybe different filesystem).
Some cameras have only ROM1 connected, so dumping ROM0 will give just random noise. In this case, the ROM0 checksum may not match, but that's OK.
The ROM dumper should recognize all ML-enabled cameras, except for 5D2, 50D and 500D. These old models do not appear to have file writing routines in the bootloader (or, at least I could not find them). The QEMU simulation works even on exotic models like 1200D or EOS M2.
So, you don't have to upload any files or screenshots. Simply verify the MD5 checksums on your PC (if in doubt, paste the md5sum output).
That's it, thanks for testing.
