Bitcraze Forums

Using the virtual machine provided by BitCraze, I followed the instructions on https://www.bitcraze.io/documentation/r ... debugging/ to enable on-chip debug on VS code. Still, the GDB times out before starting the debug session, with the following message: failed to launch openocd gdb server: timeout. Does anyone had the same issue and got it solved?

Hi!

The first thing to check is probably that the VM can access the debugger via USB. The LED on the debugger (if you have an ST link) should flicker a bit when you start a debug session and the computer communicates with it

This is actually the case. When the process starts, the led(s) on the j-link, as stated, start flickering (red/green), right after the debug session is launched. I can even read the target voltage from the console. Can you confirm that the JSON file offered as in the example in https://www.bitcraze.io/documentation/r ... debugging/ still holds? I'm attaching screens from the debug console and terminal if it is of any help.

hi!

It seems that the gdb server is started and then closed afterwards as you said so it is not an USB problem.

Hmmm this issue looks a bit familiar to me. It might be that you have too many watch and breakpoints. Could you try to remove all of them, and try again?

Thanks for the reply. Actually, there are no breakpoints/watchpoints inserted. I think that what the info msg is saying (stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints) refers to the actual hardware capabilities of the MCU.

Ah yes you are right about that line.

I've downloaded a fresh copy of the VM, setup the debugging and such, and yes I saw a similar problem. The thing is, that I first did a make, updated the projects and then setup the debugging. The culprit is that the location of the cf2.elf has change in the mean time, as of the latest changes with the kbuild system in the firmware now.

You should change this line in the json file: In my case, it grabbed the old cf2.elf I made in a older version of the firmware, therefore the openocd debugging failed on me, so I'm expecting that you have a similar problem that you still have an old cf2.elf in your repo (since you are not getting an error that it can't find the executable). If you have your important changes commited, please do a clean of your repository with or remove the old cf2.elf in the root by hand.

Let me know if this fixes anything for you!