Philipp Klaus Krause
Philipp Klaus Krause
The risk here is that the flash / eeprom / ram / peripheral might be physically present, but have failed a test. I do not know how much testing ST...
While I can see the advantage of using autotools to detect libusb, using autotools also adds some overhead. It makes it harder for users to compile the program (especially since...
AC_PROG_CC_STDC will AFAIk still fall back to a C80/C90 compiler. I am not an autotools expert, but I think AC_PROG_CC_C99 and checking ac_cv_prog_cc_c99 is still needed. Do we really want...
Any news on this one?
Well, I don't know cmake either. My experience with autotools is limited, but I'd still feel more comfortable reviewing a autotools pull request than a cmake one. My comment above...
What is the problem? I assume .ino.hex is a .hex file, and the message you show (an informative message, not an error message) looks fine to me.
I don't see anything wrong with the current code. I don't even see how the "fix" would change anything (apart from making stm8flash fail to compile where rindex is not...
If the message is a problem for your workflow, maybe we should have a --verbose option, and only emit it then?
Maybe, until someone make the esp stuff work on windows, we should pick the NO_ESP macro from https://github.com/tenbaht/stm8flash/tree/disable-esp to make compilation for Windows easier.
Is the incorrect processing of S1 records a regression in that pull request?