Skip to main content
Associate II
February 19, 2024
Question

STM32H747i j-tag debugging

  • February 19, 2024
  • 5 replies
  • 5176 views

Hello everyone,

 

I am currently working on the SMT32H747i_DISCO board and I was wondering if it is possible to use the Segger J-Link debugger on the Board. There is a j-tag pin out connected to the Dev board which suggests that it should be possible. I didn't have any luck so far. Are there additional ports necessary? Am I missing something. I can't find any documentation to the purpose of the connection. Thanks for any help.

 

Regards Maikel

5 replies

Andrew Neil
Super User
February 19, 2024

See the Segger documentation for supported microcontrollers, but the J-Link's big claim to fame is that it works with pretty much every ARM Cortex-M there is.

The board says it has an On-board STLINK-V3E debugger/programmer - are you sure you have disabled/disconnected that before trying to use the J-Link?

 


@Heisenberg wrote:

I didn't have any luck so far. Are there additional ports necessary? Am I missing something. I can't find any documentation to the purpose of the connection. Thanks for any help.

 

Regards Maikel


So what, exactly, did you try?
What, exactly, was/were the problem(s) you experienced?

Segger has a page on how to debug connection problems:

https://wiki.segger.com/J-Link_cannot_connect_to_the_CPU 

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.
Tesla DeLorean
Guru
February 19, 2024

>> Am I missing something.

Hard to say, not party to anything you wired or tested.

SWO/TDO (PB3) would be generally helpful for the debug communications channel.

Not sure what you need JTAG for, you'll need the full complement if you want to boundary scan or daisy chain.

Should be able to wire the standard ARM 10-pin connector if you need that, and can spare the pins.

Tips, Buy me a coffee, or three.. PayPal VenmoUp vote any posts that you find helpful, it shows what's working..
Associate II
February 19, 2024

I'm sorry I made a mistake. I did use the SWO connector for communications. It is however not working with the J-Link adapter.

Andrew Neil
Super User
February 19, 2024

@Heisenberg wrote:

I can't find any documentation to the purpose of the connection. Thanks for any help.


It's in the User Manual - UM2411:

 

AndrewNeil_4-1708353069764.png

So it's a TAG-Connect 10-pin footprint.

This is a 10-pin TAG-Connect:

AndrewNeil_5-1708353238431.png

https://www.tag-connect.com/product/tc2050-idc-nl-10-pin-no-legs-cable-with-ribbon-connector 

Details relating to J-Link:

https://www.tag-connect.com/debugger-cable-selection-installation-instructions/segger-j-link

https://www.segger.com/products/debug-probes/j-link/accessories/adapters/10-pin-needle-adapter/ 

 

AndrewNeil_0-1708352756341.png

"DAP" is the Debug Access Port

The "TAG Connector" is here:

AndrewNeil_1-1708352916198.png

The pinout is here:

AndrewNeil_2-1708352959242.png

 

 

 

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.
Associate II
February 19, 2024

So I flashed a Zephyr example blinky application via west flash to the board (Using the st-link connection). The led blinks. Connected the Segger J-Link debugger to the development board via the 10 PIN STDC connector CN13. I didn't change any power sources. The J-Link debugger gets detected and a attempt is made to flash the code via Ozone to the board. A error appears with connection failed. The reason why I want to use J-Link is because it has Zephyrs RTOS awareness, a feature that is widely missing with ST-Link.

 

Regards Maikel

Andrew Neil
Super User
February 19, 2024

So, again, have you disabled/disconnected the onboard ST-Link before trying to use the J-Link?

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.
Associate II
February 19, 2024

I didn't find any instructions on how to achieve that. I used the j-link debugger on other boards and there wasn't a need for any disable or disconnect operations.

regards

Andrew Neil
Super User
February 21, 2024

ST also have a page on resolving debugger connection issues:

https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693 

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.