Forum Replies Created
-
Posts
-
Another very prominent place where the debugger seems to hang is ‘static void uart_irq(int id)’ located in ‘serial_api.c’.
This place othen is involved, when the debugger seems to take forever to reach the next code-line. The moment one presses “pause” the debugger often stops somewhere within ‘static void uart_irq(int id)’.
It was a problem that occured during the build phase.
I solved it by explicitly forcing the used language-standard for c and c++ files.
Thank you for your reply. The mentioned problem of entering the “unsupported” path of the mbed-os when using ethernet support seems to be solved with this. Thereafter another new problem arose, which I’m now trying to figure out, why it occures.
The moment the compiler reaches “platform.h”, this header includes cstddef, cstdlib, cstdio and cstring as part of the used Toolchain, which then are reported as not existant file / folder.
I treid bot Toolchains, the official GNU_ARM-none-eabi-gcc Toolchain and the Sysprogs arm-eabi Toolchain. Both yield the same result. Do I somehoe need to explicitly define my project as an cpp Project?
