See a1ex's answer dated 07:55 - 19. Jan. 2019
That answer was about ROM dumpers - these carry very little risk on new models. On M50, the ROM dumper was already confirmed to work, so the answer no longer applies.
Is that digic6-dumper branch not safe to run on camera or what?
The digic6-dumper branch works out of the box, but once you attempt to run the 80D experiments, it will fail. The issue is that Canon's DebugMsg is in RAM on DIGIC 6/7 (where we can override it easily), while on DIGIC 8 is in ROM (where we can override it with a little more coding). I didn't attempt to solve it yet, but I've documented the
MMU configuration about 2 years ago.
Safety-wise, it's probably OK (but it's worth noting that Canon firmware
reflashes the main ROM at shutdown, so...)
If my camera won't turn into a brick maybe I'll give it a shot
I cannot guarantee that. Risks were explained for e.g.
DIGIC 7,
5D4 etc. Enabling the boot flag
will modify your camera, so there is a tiny chance of things going wrong when running this procedure on a new camera model.
Enabling the boot flag will enable anyone with (basic) programming skills to run the proof of concept code on their camera and experiment with it. You will still need QEMU for debugging and for understanding how your code will run. The logging code does not work yet; debugging will have to be done in QEMU. On hardware, you've only got LED blinks, file I/O (as long as the camera doesn't crash) and... display from bootloader context (but do check the 80D thread).
Still with me? If you are OK with the risks, just drop me a PM.