Debug in Eclipse, Mandatory "Config options:"

Tagged: eclipse debug, stm32

This topic has 6 replies, 5 voices, and was last updated 7 years, 8 months ago by mbutura.

Viewing 7 posts - 1 through 7 (of 7 total)

Author

Posts
February 5, 2017 at 7:13 pm #6032

nefarious
Participant

I double checked, triple checked the Debug Configuration to be sure I had what you suggested. When I try to run the debug configuration I get a dialog that tells me

Missing mandatory configuration. Fill-in the ‘Config options:’ field in the Debugger tab.

I put in some garbage values and I got the same message.

February 6, 2017 at 7:48 am #6034

Carmine Noviello
Keymaster

This bug affects the latest GNU ARM Eclipse plug-ins release. I’ve already filed a bug report lo Liviu:

https://github.com/gnuarmeclipse/plug-ins/issues/173

In the meantime, I suggest to avoid the usage of the External Tool configuration.

February 15, 2017 at 8:53 pm #6161

LLH
Participant

I just posted a message with this same symptom. Does this bug which prevents using the External Tool configuration mean GDB OpenOCD Debugging of a nucleo board cannot be done until bug is fixed?

Is the there any other debug procedure described in book which can be used to debug nucleo board over USB interface? Thanks.

Larry H

March 19, 2017 at 1:43 am #6581

TonyRadice
Participant

I have also hit this bug, and tried adding the following argument to the Debug Configurations => {Individual Configuration} => Debugger tab => GDB Client Setup -> Other options field:
-f board/stm32f4discovery.cfg (PS: This IS the board I am working with) .
Unfortunately, No Joy.
I Look forward to hearing of a response.

Tony

March 19, 2017 at 2:22 am #6583

TonyRadice
Participant

Ladies and Gentlemen –
I may have a solution to this – please review and comment.
Referring to page 157 of Mastering STM32, Figure 8.
a. CHECK Start OpenOCD locally
b. In the config options it is necessary to include the target board. The boards may be found in the openocd/scripts/board directory. In my case it was “-f stm32f4discovery.cfg”
c. It was necessary for me to define the $openocd_path variable to get the tool to operate. In my case it is C:/STMToolchain/openocd/bin

I Look forward to hearing comments from my more experienced colleagues. Also – are there any additional warnings I should be aware of now that I am starting OpenOCD locally? ALSO – reference my earlier post; I CLEARED the value in the GDB Client Setup -> Other options field.

Thank You!

Tony

March 19, 2017 at 5:53 pm #6588
mbutura
Participant
I managed to solve this problem a while back just as @tony radice but only a bit differently:

I use Ubuntu 16.04 and I have my debugger tab OpenOCD Setup as:

<Executable>: /<absolute path prefix>/openocd/bin/openocd

<GDB port>: 3333

<Telnet port>: 4444

<Config options>: -f /<absolute path prefix>/openocd/scripts/board/st_nucleo_f4.cfg

Note: After you have done this on your Linux/Unix system, unchecked the “Start OpenOCD Locally” button.

Apply the above and close.

Thus to successfully debug:
1. Start Openocd as an external program.
2. Run the debug configuration as in the book with the modifications in this post reply to avoid the error.

On windows it should be the same as linux but only with a different absolute path and path separators(“\” instead of “/”).

Hope it helps!

Best,
Mbutura.
Nairobi, Kenya.
- This reply was modified 7 years, 8 months ago by mbutura.
March 19, 2017 at 6:16 pm #6591

mbutura
Participant

Kindly update your openocd version from Liviu. The issue has been closed:

https://github.com/gnuarmeclipse/plug-ins/issues/173

Keep the same path prefix and just replace the openocd working folder. It should work with no modifications to your IDE-Toolchain setup.

Best,
Mbutura.
Author

Posts