One of the numbers in the above log points to "ClrCalc_GetWbGain". Must be something in LiveView, likely interference from crop_rec or raw video recording.
A totally different thing is when your camera no longer boots. In both cases, Canon firmware may print ERR70 on the screen, but they are really not the same.
Alright, so Bilal was mostly right with his initial guess. There were two things I've announced today:
M50 portYes, it's real. I've got one a few weeks ago, in order to jump-start the DIGIC 6/7/8 development. At least the GUI code is going to be identical, for all other new models. Hello World is already working, or expected to work, on all new models (from 80D to EOS R).
Unbricking serviceYes, it's not a joke either. Lately I've learned quite a bit around Canon internals (in particular, UART, ROM reflashing and other similar low-level stuff), and I've got quite a few requests (privately) to help diagnosing cameras. Some were successful, others not. One of the screenshots comes from Danne's EOS M, not yet solved, but still working on it.
I'm pretty sure service technicians, or regular people having trouble with their camera, will find my knowledge useful. Or, even if you have no problems now, I believe it's still useful for your peace of mind - should anything happen to your camera, I'll be able to look into it (and hopefully tell whether your problem was caused by ML, or it's faulty hardware). The portable ROM dumper is going to be the most important diagnostic tool for cameras running ML, alongside with ability to run the firmware in QEMU.
Even if your camera is not running ML, I can still diagnose it via UART, with the same procedure we used to run code on the EOS R. I don't know if this is something routinely done by service technicians or not, but if it's not done, I might have found a niche on the market.
Which brings me to the last, but the most important, point. Lately I've been effectively struggling to find time to work on ML. Although I'm present on the forum nearly every day, most of that time is either during breaks at my job, or in the evening, when I'm usually too tired to do anything useful. Yet, all of the reverse engineering I did during these years gave me a significant amount of knowledge on Canon internals, that others simply don't have. I've tried to write down some of it (e.g. QEMU docs), but it's not the same. What's the point if I can barely find the time to put this knowledge to good use?
I see only one way out of this: to be able to allocate more of my
productive time to Magic Lantern development. That is, without worrying about some deadline I have to meet at the job, or about what I'm going to put on the table for my (growing) family.
At the same time, the Magic Lantern project needs to stay non-commercial. Given the reverse engineering nature of this project, many developers or contributors would be uncomfortable if the project would be commercial, and rightly so. We had the discussion of going commercial a few years ago, and decided to keep Magic Lantern in the FOSS domain. This was a good decision and will not change anytime soon.
This - i.e. getting more time for ML development - is what I hoped to achieve with Apertus, some years ago. Unfortunately, things didn't go as planned - they are simply not in the position to pay a salary. So, I've ended with two projects competing for my spare (read: unpaid) time. Not a good deal...
Before that, I used to accept donations, but... I was no longer comfortable handling them since
the 2013 rumour about 1DX/1DC. It's been 6 years since then, with no signs from the sleeping giant. Maybe it's time to reconsider.
We still accept
Bitcoin, but... with only 3 pledges in 2018, and nothing at all in 2019... somehow it doesn't feel right.
These repair tricks, if there is indeed a market for them, might be good for a side business outside Magic Lantern. That's right - I'm tempted to try freelancing!
I might also consider custom software development, or maybe a smartphone app. It's still not very clear to me what path I'll choose - in any case, it has to be one that all other developers are OK with. For now, I'm welcoming your suggestions!
https://www.magiclantern.fm/unbrick.html
Updated this page with the serious version, including a short FAQ.