Hi,

Did you connect the STLink reset output to the F4 reset pin ?

If yes, you can use the connect under reset mode.

If no, use the Software system reset mode.

Then, if still not working, add -d in debug openocd options to get a more verbose output.

Rgds,
Laurent

Hi Laurent,
Thanks for your rapid reply.

The F4 Reset pin is indeed connected to the STLink reset output (pin5 of the SWD port).
(For information, it’s actually an NRST contact on both the STlink SWD port and on the Bleucoin board.)
With “Mode Setup” placed on “Hardware Reset”, this results in the situation I mentioned before.

I tried to use Software system reset mode as you noticed, combined with “-d” written in “OpenOCD option”.
This results in a Problem Occurred again, but with a different details :
Error in services launch sequence
Timed out trying to launch GDB.

With this, the problem seems to be located only on GDB launching.
What do you think?

Hi,

Are you trying the debug config in shareable mode stlink ?
Try in normal mode first.

And the “Connect under reset” mode, is it the same ?

Yes, it seems gdb can’t start.

Can you check there is no other gdb or openocd running.

Also, can you try a simple project for the nucleo board mcu, is it working fine ?

Rgds,
Laurent

Hi,

I did have my debug config in Shareable mode StLink. I tried in normal mode. Same result.

I tried all 3 reset mode with same results.

How can I check for other gdb or ocd running? (Ac6 is my only IDE running.)

I also tried to run the debug of the F303 nucleo board. And i indeed have the same Occurred problem result (Error in services launch sequence
Timed out trying to launch GDB.)

For well comprehension, I attach the screenshot of the debug config for both the BleuCoin and the F303 projects.

http://www.openstm32.org/tiki-download_file.php?display&fileId=470Question
http://www.openstm32.org/tiki-download_file.php?display&fileId=471Question

Regards,
David

http://www.openstm32.org/tiki-download_file.php?display&fileId=470
http://www.openstm32.org/tiki-download_file.php?display&fileId=471

To check for other gdb or ocd running, i meant to check the processes on windows and see if there is nothing already running before launching debug.

Hi Laurent,

I checked on other gdb and ocd running on win10. Indeed there was few gdb tasks running. I’ve ended these tasks via widows tasks manager, and tried my debug again. Same result.

To be sure, I restarted my system and launcha AC6 Debug as first thing. The result is back to this Problem Occurred message :
Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:7184

Error message from debugger back end:
Bogus trace status reply from target: timeout
Bogus trace status reply from target: timeout

I will try now to run my nucleo board with the F303 on the “getting started” setup with AC6. This is a more experienced setup, and I may make it work well.
If not, I’ll try it again after uninstall and reinstall of AC6.

What do you think?

Regards,
David