Thank you!Razerban wrote: ↑30 May 2021, 17:32I agree with you on the fact that the code might not be 100% the code that Soarer wrote. I think that Arakula added some comments here and there and made some adjustments so that the code could be built after the decompilation.ifohancroft wrote: ↑29 May 2021, 18:47Perhaps it is true.
We don't know (at least I, currently don't know on top of my head) if he made any further improvements to the code. Also, despite my changes allowing the code to compile without errors (and IIRC without warnings), I don't know if they are correct.
Also, the code may produce a binary that's functionally the same, so I don't know if it's reasonable for me to expect the two binaries to be exactly the same byte for byte when compiled.
I can't test if they work the same, because as much as I am ashamed to admit it, I don't actually have any old/retro boards. There are many such boards that I want but I couldn't afford buying them so far.
I had some errors too while trying to compile the code on macOS. I believe that I'm using a more recent version of GCC than the one that Arakula used at the time he was making this work. But I was able to successfully compile the code and test the resulting firmware on a spare Teensy 2.0 (not attached to a keyboard yet). I was able to upload a configuration file and then download it from the converter without any issues.
The next step would be to test it on an already Soarer-converted keyboard. For that I would need to go to my storage unit and grab one of my test keyboards.
The firmware size being not the same as the ones published by Soarer on DT and GH is quite expected as it can be the result of the following things:
- The code may have been altered during the decompilation process
- Different versions of the build tools than the ones used by Soarer when he built the firmware
- Different libraries versions than the ones used by Soarer when he built the firmware
PS: Some of you might object this, but let me know if I can share the hex files here for others to test the firmware too
I think it should be fine if you share the hex files for others to test as well.