reko VS dnSpy

In the zip are 3 firmwares, NXP, PD and Scalar. NXP is the USB microcontroller that's used to update the scalar firmware, and PD is for USB-C stuff. The scalar firmware's name was 28MQ780_MSTAR_MST9W00V4_V3.3.0_0x12FBF031_shad4015bb_220317.bin, which already gave me a few more data points, specifically the chip that's used, the MStar MST9W00V4. Eventually I found this extremely annoying post which had the compiler used for the chip and this page telling me that my scalar's CPU architecture was proprietary, but based on OpenRisc. It turned out that the stars had aligned or something and there were no less than 3 people interested in this particular ISA in the last 3 weeks, because someone else had asked about it and apparently a niche disassembler added partial support for it.

Reko has the ambition of supporting decompilation of various processor architectures and executable file formats with minimal user intervention. For a complete list, see the supported binaries page.

For some examples of hand-written parsers in C#, take a look at my project https://github.com/reko. There is both a C and a Pascal parser, located at https://github.com/uxmal/reko/tree/master/src/Core/CLanguage and https://github.com/uxmal/reko/tree/master/src/Core/Pascal, respectively. DM me if you're curious, I be glad to tutor.

If you're interested in poking around/tweaking existing Unity games I'd recommend checking out dnSpy.

Unfortunately dnSpy was archived by the main author a while back out of the blue. There's an attempt to revive it at https://github.com/dnSpyRevived/dnSpy. I've general use JetBrains dotPeek now, which is a shame because I feel dnSpy was better and more performant.