A blog about electronics and programming

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • March 19, 2017 at 2:22 am in reply to: Debug in Eclipse, Mandatory "Config options:" #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 1:43 am in reply to: Debug in Eclipse, Mandatory "Config options:" #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

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)