Open lcha78 opened 2 years ago
There is no reason, it is just an oversight. Thanks for the report.
As for burning mosfets with v20.1C.3-NEW, I don't know what to say. I had thought of a compilation problem only with a specific version of SDCC, since there are those who still use that version of OSF today without problems. Your hypothesis also makes sense.
I notice differences with compilation flags (speed optimization flags) according to the repositories: TSDZ2-Smart-EBike-* and TSDZ2-Smart-EBike-LCD3 have
CFLAGS = -m$(PLATFORM) -Ddouble=float --std-c99 --nolospre
TSDZ2-Smart-EBike-860C and TSDZ2-ESP32/TSDZ2-Smart-EBike (from mspider65) have
CFLAGS = -m$(PLATFORM) -Ddouble=float --std-c99 --nolospre --opt-code-speed --peep-asm --peep-file peep.txt
Is there a good reason to compile non-optimized code on TSDZ2-Smart-EBike-* and TSDZ2-Smart-EBike-LCD3 ? Could this be the cause of the v20.1C.3-NEW issue ?
N.B. : mspider65 recently update his peep.txt file.