V1.1.0, segger j-link support gone?

Forum|Forum|6 years ago
November 14, 2019
6 replies
2800 views

Hi I installed STM32CubeIDE V1.1.0 and now I can't select J-Link as a debug probe, only ST-link (GDB & OpenOCD).

I get the J-link if the project was created in an older STM32CubeIDE version, but not in the new 1.1.0.

Any hints on how to enable J-link?

This topic has been closed for replies.

Best answer by Markus GIRDLAND

The internal weekly build we do has fixed this so you will be able to use J-link in the next version of CubeIDE. I've tested it myself and now there's a pop-up warning that there's no support if you would choose a dual-core H7 with J-link (or some other incompatible probe and target) instead of filtering.

B

BillR

Visitor II

Sorry I don't have a solution for you but I am having the same problem. In my case I fortunately had an STLink V2 laying around which is working fine for me. It might be a little slower to load but fine for at least general debugging so far. Also at $29 vs hundreds for the JLink I think they are a bargain.

C

Cartu38 OpenDev

Graduate II

Which target are you working with ?

F

FZher.1665Author

Visitor II

@BillR I have one to, but I want to use System View from Segger to debug FreeRTOS. Its nice to have unlimited break points and better speed as well.

@Cartu38 OpenDev I use STM32H753.

@Markus GIRDLAND Is there any solution or workaround?

M

Markus GIRDLAND

ST Employee

The J-link option is disabled on all H7 devices. This is because the dual-core H7 devices does not have J-link support. However, this gets the negative side-effect that single core H7 devices gets blocked as well.

I don't believe there's a workaround but I know the debate about whether to block these devices or not is still ongoing so I will lift this thread as an example of negative consequences that can come from this.