cancel
Showing results for 
Search instead for 
Did you mean: 

NUCLEO H753Z: ST Link V3

JhonVijay
Associate II

Hello everyone,

I am using the NUCLEO H753ZI microcontroller it has ST Link V3 can i debug this board with the ST Link can you tell me what version of ST do i need to get to debug my board and also can you provied me the document for debugging with ST link.
                           Thank you

1 ACCEPTED SOLUTION

Accepted Solutions

This is to use a printf over the serial wire viewer

You can refer to this article: Using the ITM console for printf redirects and LWIP debug messages

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

View solution in original post

11 REPLIES 11
mƎALLEm
ST Employee

Hello @JhonVijay and welcome the the ST community,

Not sure I understood the question. The on board STLINK-V3 is intended to connect to the on-board MCU in your case: STM32H753 MCU.

You can use it with STM32CubeIDE for debug, you can use it with STM32CubeProgrammer to upload, read to/from the internal or (if available) an external flash.

You can also refer to the board's user manual UM2407 / section 7.3 Embedded STLINK-V3E

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.
JhonVijay
Associate II

I had debugged my Nucleo board with the J Link with the segger RTT. Now i like to change to STLINK So l would like to know what version of ST external debuger support my board which can be used for debuging my device

You can connect a J-LINK on CN5 connector on NUCLEO H753ZI:

mALLEm_0-1763121074179.png

Please refer to the user manual of the board UM2407 / section 7.3.3 Using an external debug tool to program and debug the on-board STM32H7

For STLINK you can use the external version STLINK-V3 (I don't know what the reason to use an external version while there is one on board)

Hope that does answer your question

 

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

@JhonVijay wrote:

I had debugged my Nucleo board with the J Link with the segger RTT.


Note that RTT is proprietary to Segger - it is not supported on ST-Link.

 


@JhonVijay wrote:

 i like to change to STLINK So l would like to know what version of ST external debuger support my board 


Why external? Your board already has the ST-Link built in!

 

As for ST software, that's STM32CubeIDE.

You can also use STM32CubeProgrammer for programming.

 

All of this is linked from your Board's Product Page:

https://www.st.com/en/evaluation-tools/nucleo-h753zi.html#tools-software

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

@JhonVijay wrote:

I had debugged my Nucleo board with the J Link with the segger RTT. 


@Andrew Neil  .. If you remember our discussion ;)

@Amel NASRI 

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

Thank you @mƎALLEm  The thing is i had tryied to debug using the internal debugger to print the debugging messages by refering this vedio but i couldn't see the any debug messages so i wanted to try the external STLINK.Can you please proveide any documentation on debuging with the internal STLINK 

This is to use a printf over the serial wire viewer

You can refer to this article: Using the ITM console for printf redirects and LWIP debug messages

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

@JhonVijay wrote:

i had tried to debug using the internal debugger to print the debugging messages by refering this vedio but i couldn't see the any debug messages  


But you could load your code OK, and use other debugger features like stepping, breakpoints, examining variables, etc?

 

As @mƎALLEm said, that video is about using SWV.

 

You can also get debug messages from a UART via the ST-Link's VCP (Virtual COM Port) ...

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Thank you @mƎALLEm  I can able to debug using the onboard debugger 

JhonVijay_0-1763133376581.png