Closed davidrib closed 2 years ago
My chip version is GD32F130C6 and I have more two boards with GD32F130C8, not tested yet but should work they have more memory, even so, only because 44 Bites is not possible adapt the firmware to fit in 32K ?? I'm not a big programmer but culd someone help?
Success shortened some console messages I think the project could be updated Thanks
Maybe we could use a define to enable/disable all Debug messages.
Maybe we could use a define to enable/disable all Debug messages.
I'm not a advanced programmer is the first time I use platforio, but I'm wondering if the compiled version has or not debugging information to start/stop add breackpoints to some debugger that could be disabled? Should save a lot of space? (Sorry my bad English)
Done! 35% free space!
Maybe we could use a define to enable/disable all Debug messages.
I'm so 🥇 dumb 🥇 :((((((((
Sorry
This just defines the VARIANT_DEBUG macro which is used through out the code. If you comment it out, you will not have debug pieces of code in the compilation. So, it won't be the VARIANT_DEBUG anymore.
I just updated travis build and I also get 44 bytes overflow. I think the new platformio or better said new librarier from platformio use more resources... it happened before.. I will see what can be done soon.
44 bytes oversize is really on the edge. I know it built before with an earlier version of my platform-gd32. So, if new features aren't needed and rather, stability is needed, I can do a PR for the platformio.ini
to use fixed git commit hashes that results in a good build.
(But then possible new features in platform-gd32 can't be taken advantage of)
This problem was foreshadowed in https://github.com/EFeru/hoverboard-sideboard-hack-GD/pull/16.
I've proposed a fix for it in https://github.com/EFeru/hoverboard-sideboard-hack-GD/pull/19.
Could someone help-me here?? Exceeds 44 bites :((((((( I'm not a strong programmer, with any change.
The others are OK: