Quote from: a1ex on November 30, 2019, 07:27:53 AM
I've seen official firmware updates getting stuck at some percentage in the past, but never understood why (and back then, I didn't know how to start troubleshooting such issues). Now I can at least give it a try.
Translation: the main firmware flag is disabled.
If you already have the boot flag enabled (if this camera had ML installed before the event), the first step would be to run the portable ROM dumper, and send me (privately) a copy of the ROMs. Your camera will accept autoexec.bin files in this state, as long as you make the card bootable manually (EosCard/MacBoot/make_bootable.sh).
If your boot flag is not enabled, I'll prepare a FIR version of the ROM dumper.
Then, to diagnose the firmware update, we have 2 options:
- UART adapter (easiest and probably safest option, if you are comfortable with such things)
- software-level diagnostics (I did such experiments in the past, but in QEMU only; didn't have the guts to run them on a real camera)
Option #2 may take longer.
Hi A1ex,
Thanks for your input. The camera hasn't ever had ML installed on it so suspect option 1 is no go.
I'm not totally green to things like this but no expert and doing it on my 5D....eeeek!!
If I can connect up to the UART adapter, what would be available to me for diagnostics? Is there software available?
Thanks
Andy.