Cannot start debugging in Eclipse

[LLH]

The following message error pops up when the “Figure 11: The Debug icon to start debugging in Eclipse” startup operation is completed. See Sec5-1-3_Fig11_Error,png attachment.

The Debugger tab of Debug Configurations window (Figure 8: The Debug Configuration dialog – Debugger section) is as shown in the book. See Sec5-1-3_Fig8.png

After reopening the Debugger tab of Debug Configurations window, the ‘Config options:’ field is grayed out. How can this field be enabled and what needs to be changed to fix the following condition? Thanks.

Missing mandatory configuration in ‘Config options:’ field prevents starting debugging in Eclipse

“Figure 6: The OpenOCD output in the Eclipse console” results looks okay for nucleo-f446 board.

Larry

Attachments:

You must be logged in to view attached files.

[olivier.cornez@me.com]

Hi,

I hope I do not hurt Carmine by answering your post.
You should be able to run openOCD locally by checking “Start openOCD locally”checkbox on sec5-1-3_fig8.png
Then fill Config options with correct parameters for your board. :
-f interface/stlink-v2-1.cfg -f board/st_nucleo_f4.cfg

Note: the -f interface… option is not mandatory.

Then you do not use the openOCD external tool configured but start the debug config. Sometimes it does not work and you must disconnect the board from usb and reconnect it.

Good luck.

[LLH]

Olivier,

Thanks for the reply. By placing the two -f options on separate lines, the debugger starts up and stops at the first statement in main.c
See Sec5-1-3_fig8_StartOpenOCD_locally.png

The console output after starting debugger is shown in Sec5-1-3_Fig12_DebugPerspective_OpenOCD_locally.png attachment. Can I assume the one error line
Error: already specified hl_layout stlink
is not crucial?
ST-Link Red/Green interface LED is blinking on nucleo-f446 board.

I’ll continue from this point in book using local openOCD debug configuration until it is not applicable to a specific section of the book.

Larry

Attachments:

You must be logged in to view attached files.

[olivier.cornez@me.com]

Hi Larry,

I am on a Mac so maybe you should tune a little bit the options.
I tuned it in a terminal until it worked (use cmd with windows): everything is in the openOCD/scripts folder.
I think I’d start without the interface option and see what happens.
once ok update the Eclipse debug configuration.

FYI: yesterday I switched to J-Link debugging. I had too many strange behaviour with openOCD. That was too confusing especiallly when you have to learn something new.
So I follow the advanced debugging chapter near the end of the book.
It is very easy, reversible and up to now I do not have any problem with it.

Good Luck

[Author]

Posts