Please attach the build log as shown in the yellow box at the top so we can be 100% sure on the core in use.

What actions lead to the code above being shown? (from Arduino_STM32\STM32F1\cores\maple\libmaple\usb\stm32f1\usb_cdcacm.c by the looks of it)

e.g. Start Debugging, Step Into functionx(), etc....  and if any specific project code is needed please let us know.

We are referencing the box at the top of all forum pages:-


This is so we can understand your environment, and any error messages in detail before investigating or asking further questions to understand the problem.  Without this information it can be very difficult to investigate or assist accurately, which is why we ask for this in virtually all cases.

Thanks for the information.

What happens once you press continue from this point in the USBInit() code?

Would it be possible to send your sketch to us so we can investigate further?

Thanks, can you confirm what bootloader you are running on your board?

(When testing earlier I never entered the code shown, even following the same actions, on the same core, with a virtually identical sketch)

At present all I can see is that the code being entered (USBInit) is part of the Virtual COM Port USB Code for the STM32.

Which is either being hit due to Serial Usage, or potentially the DFU Bootloader still running (which could be a timing issue, though expect the same from all debuggers in this case).

Are you looking at it? The OpenOCD like GDB are a mystery to me.

This Topic was moved here from Hardware Debugging (GDB, GDB WiFi, GDB Stub) [move by] Visual Micro.