GDB not flashing the mcu

[olivier.cornez@me.com]

Hi,

I have several issues while debugging and also trying to understand how UART works with interlocks.
I had strange outputs and even if it was due to addressing out of memory variable I did not understand why it was working for a while then suddenly I had another strange output.

Until I realised the Nucleo mcu was not correctly flashed or updated when I started a new debug session.
The output did not match the code until I disconnected the board from usb and restart the debug session.

Is it a better way to debug? Flashing from openocd in the terminal then start gdb?

Kind Regards,
Olivier

[Carmine Noviello]

Hi Oliver,
Which GCC/GDB version are you using? Please, take note that the current GNU ARM Eclipse official release doesn’t support ARM GCC 6.x.
Moreover, ensure that your ST-LINK interface is updated to the latest version, and you are using the latest OpenOCD 0.10 stable branch.
Finally, I suggest you to switch to J-LINK firmware for the ST-LINK interface and to SEGGER tools. In the chapter about advanced debugging you’ll find all the information you need to get started with it.

[olivier.cornez@me.com]

Hi Carmine,

I am using openOCD 0.10 and gcc 5.4 and st-link v2.1 (updated as per book instruction).
Thanks for the info I will check advanced debugging chapter.

PS: this weekend I started writing I2C scanner and MCP9808 (temp sensor) application by myself and surprised myself because I was not looking in the book every 5 minutes.
So thanks again for your book you reach your target 😉

[Author]

Posts