cancel
Showing results for 
Search instead for 
Did you mean: 

J-LINK SEGGER with STM32CubeIDE

DYann.1
Senior II

Hello,

I would like to know How to configure the J-LINK Segger to work with STM32CubeIDE, after a little searching I found this video : https://www.youtube.com/watch?v=Rf-NKOoPYUc

But at 12:11 I can see this configuration in the video             
DYann1_0-1730723182830.png

But I don't have an Application directory :

DYann1_1-1730723371353.png

In this case, do you have an idea how to do it ? Thank you for your helps.

Regards

38 REPLIES 38

@Andrew Neil wrote:

So what's changed?

If you go back to what you had before, does the connection work again?


 

 


It's not the same, at the beginning I converted to J-LINK so I don't know if it's the same configuration :

DYann1_0-1730798745370.png

Now I have an folder and no errors when compiling.

DYann1_1-1730798828855.pngDYann1_2-1730798854345.png

Now my errors is at the end to validate the operation. Now I try to connect

DYann1_4-1730799158418.png

DYann1_3-1730798986965.png

Now when I go into DEBUG mode there is an error, for me it is actually a hardware problem now since when compiling, I compile well with the J-LINK tool.

So do you have any idea now ?


@Andrew Neil wrote:

This error message:

AndrewNeil_0-1730798892823.png

tells you that it's the basic SWD hardware connection that's failing - it hasn't got as far as anything to do with RTT at that point!

Yes you're right but I have already configured the tool now I will check again to see what it gives. After checking nothing is works 

DYann1_0-1730799834265.png

that I try to connect via SWD or JTAG nothing works, so it is normal that STM32CubeMX cannot communicate with the J-LINK


@DYann.1 wrote:

Yes you're right but I have already configured the tool


So this is not about the tool configuration - it is a basic hardware problem:

AndrewNeil_0-1730800264401.png

 

Are you also going to complain to Segger about giving you "useless" (sic) links?

AndrewNeil_1-1730800360432.png

 


@DYann.1 wrote:

so it is normal that STM32CubeMX cannot communicate with the J-LINK

When the basic hardware connection is not working, nothing which needs to use that connection can work!


@Andrew Neil wrote:

Your video is about how to set up RTT 


The only part of that video which has anything to do with the J-Link itself (the basic hardware connection) is the 28 seconds from 17:18-46 https://www.youtube.com/watch?v=Rf-NKOoPYUc&t=1038s

The rest is all about RTT.

I don't see your video link but one thing what I am certain is that the connector is compatible with the evaluation card. When I connect with J-LINK and USB_STLK :

DYann1_0-1730809637200.png

Now when I need to only with J-LINK for program and Debug (without USB_STLK) I have this picture : 

DYann1_1-1730809882161.png

 

 

 

DYann.1
Senior II

Hi, thank you every body now I can work with my J-LINK . In fact in any case I

DYann1_0-1730810299382.png

I still have to connect USB_STLK even if I don't use ST-LINK (from what I understand).

DYann1_0-1730811102681.png

operation is correct


 


@DYann.1 wrote:

I still have to connect USB_STLK even if I don't use ST-LINK (from what I understand).


I'm not clear what you mean by that?

What do you mean by "USB_STLK" here?

You can only have one debug probe attached at a time.

Is this on the EV board, or your custom board?

Show  diagrams.

On my EV board first after I can switch to my real board. "USB_STLK" look on the evaluation card where the connector is located "USB_STLK"

OK, so that's CN22 - the micro-USB for the on-board ST-Link.

AndrewNeil_0-1730812219815.png

and you're connecting your JLink-EDU to the CN10 JTAG connector:

AndrewNeil_1-1730812406547.png

Yes?

 

So you're using CN22 to power the board:

AndrewNeil_2-1730812527504.png