J-LINK SEGGER with STM32CubeIDE

[DYann.1]

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             

But I don't have an Application directory :

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

Regards

[Andrew Neil]

Again, the folder structure of the project doesn't have any effect at all on the debugger connection.

So having (or not having) an 'Application' folder won't solve this:

Or this:

[DYann.1]

Not sure, I know this errors message and sometimes the solution has nothing to do with the error message. In the video there are then other configurations and I am afraid that there will be conflicts. Sorry I've something todo and I come back later.

Thank you

[Andrew Neil]

The "Could not connect to target" definitely has nothing to do with the folder structure:  this is about establishing the basic connection between the debug probe and the target hardware.

[Karl Yamashita]

---

@DYann.1 wrote:

Not sure, I know this errors message and sometimes the solution has nothing to do with the error message. In the video there are then other configurations and I am afraid that there will be conflicts. Sorry I've something todo and I come back later.

Thank you

---

Just as @Andrew Neil has mentioned, the folder structure has nothing to do with J-Link not able to connect to the target. It's a hardware connection issue. Double check your connections. Draw schematic on how you've connected the J-Link to the target device.

[DYann.1]

The hardware is correct and you Didn't you see this message ? 

Of course the J-Link has something to do with configuration files and you haven't seen the video too I guess? So you haven't seen the hardware or software and you're giving advice ? If you have something specific I'm interested not something general and vague, Please.

[DYann.1]

Definitely you are 100% wrong no I would say 200%, during compilation the SEGGER and CUBE software establish links to find the compiler and the internal registers of the card to be able to establish communication so if it does not find the right one configuration of files it generates error messages And I'm sure that you have never done this configuration, which is why your explanations remain on the surface and do not give any solution but links and links....

[Karl Yamashita]

Again, the Application folder has nothing to do with the J-Link not being able to connect to the device. The Application folder could be called Foo and it would still work as long as you add the RTT files with the correct path. If you are sure you have connections correct then you have a configuration issue, not a missing Application folder issue. 

Now if you had said you can't get the project to build without errors, then you may have something valid to say about the Application folder.

[Andrew Neil]

---

@DYann.1 wrote:

The hardware is correct and you Didn't you see this message ? 

---

And yet the connection is not working:

So what's changed?

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

---

@DYann.1 wrote:

Of course the J-Link has something to do with configuration files 

---

Configuration files, yes - but nothing to do with the source files, nor the project structure.

[Andrew Neil]

---

@DYann.1 wrote:

 during compilation the SEGGER and CUBE software establish links .

---

No.

Compilation is completely independent of the debug probe. You can compile without even having any debug probe  installed - let alone connected.

The connection with the debug probe only happens when you start a debug session.

[Andrew Neil]

Your video is about how to set up RTT -  a Segger proprietary feature which works over the basic SWD hardware connection.

This error message:

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!

@DYann.1 wrote:

Yes I have already made the evaluation card work with J-LINK but with USB_STLK, but for my projet I've another card that doesn't have US_STLK (for consumption and card size). 

---

So which one is giving the connection error - the EV board, or your custom board?