KDS 3.2.0 debugging two applications?

[scornelius]

Using KDS 3.1.0 I have been running two KDS sessions to debug two different application.

I have two FRDM-K64F boards talking to each other.
I am using OpenSDA, and DEBUG-FRDM-K64F_Pemicro_v108a_for_OpenSDA_v2.0.bin.
The only thing I needed to do “special” was to set the port numbers differently.

his is in the GDB  PEmicro Interface Debugging” -> “Debug Configurations” in the “Debugger” tab .
In one KDS session it’s 7224, the other: 7226.

After installing KDS 3.2.0 I can debug either the host, or the target, but not both.

When I try to start the debugger on the second instance the programming LED on the board blinks, and then
I get:

After installing KDS 3.2.0 I did “eclipse update software”, so everything should be current.

For “GNU ARM PEMicro Interface Debugging Support”, the versions are:
In KDS 3.1.0 I’m using 2.1.0.201506041101.
For  KDS 3.2.0 it’s 2.4.1.201603202153.

I remember having a problem that caused needed an earlier P&E load at one time. I believe from Erich Styger.

Anybody else having this problem?
Thanks,
Steve

[BlackNight]

Hi Steve,

yes, I noticed as well that USB ports are disappearing. I was undert he impression that the connection is not using USB1 or USB2, but that number after that, so it should not matter if both are USB1. I might be wrong.

Erich

[scornelius]

Thanks Eric. Love your site. Lots of well presented info.

We've been using the port selection method for a while, but in two KDS instances.

In 3.2.0 I just re-tried opening both in the same instance, and have the same problem.

"Error in services launch sequence" (Attached above).

To quote your other article: "The bad thing with Eclipse and GDB is: if something is failing, then all what I get is a very cryptic error message when I launch the debugger:"

The one thing that I did notice is that the USB indexes are moving around!

Still within a single KDS 3.2.0, when I hook up three boards, I show three debuggers:

If I start the one using USB1 (41301E4C), and try to start another, I get a list again starting with USB1!

Alternately, if I start the one using USB2 (414E1E0F), and try to start another,
  I get a different collapsed list again starting with USB1.

Trying to use either of the remaining USB devices gets me the error.

Also, since the debug config seems to be using the USB number rather than the OpenSDA index, my PE config is changing.

Thoughts?

Steve

[scornelius]

Erich,

In KDS 3.1.0 I have two different workspaces, and projects: Host, and Target.
They share libraries, but the applications are separate.
With your KDS 3.2.0 installation, are you able to open KDS twice, and debug two different projects?

In 3.1 this works.

Thanks again,

Steve

[BlackNight]

Hi Steve,

>>With your KDS 3.2.0 installation, are you able to open KDS twice, and debug two different projects?

Yes, this has been working all the time for me, in all versions.

What is new that I can now debug multiple targets with the same binary (same project) or with different binaries (different projects), all inside the same IDE.

Should be able to publish a short article about this tonight if time permits.

Erich

[BlackNight]

Hi Steve,

I have posted it here: https://mcuoneclipse.com/2016/04/12/debugging-multiple-nxp-boards-with-gdb-and-pe/

Erich

[scornelius]

Hey Eric,

I see that you can debug two in a single KDS instance.

Currently, in 3.1.0, I'm debugging both sides of a SPI master to slave.
I use two separate KDS instances so that my common library (lSPI) didn't get confused with different breakpoints in the same file.

With your set-up, do you have the same problem running two KDS instances that I see with 3.2.0?

Thanks,

Steve

[BlackNight]

Hi Steve,

I can debug the same binary (elf file) on two different boards in parallel.

It is true that in this case the breakpoints are 'shared'. You really want to have them separate, I think you would have to debug a  copy of the projects as the breakpoints are file oriented.

Erich

[BlackNight]

Hi Steve,

I'm able to debug two FRDM boards with P&E OpenSDA on it with KDS v3.2.0, side by side from the same IDE using KDS v3.2.0:

I think I might need to publish an article about that?

Regards,

Erich

[Alice_Yang]

Hello Steve,

I find the DOC Erich write you mentioned.

I also test two board use  GDB  PEmicro Interface  , it is the same with you.

While use the GDB SEGGER J-LINK Debugging , it can work well , so please

change the  board firmware to "JLink_OpenSDA_V2.bin" , then use  GDB SEGGER J-LINK Debugging .

About how to change firmware ,please refer to the "FRDM-K64F Freedom Development Platform -Quick Start Guide.pdf",

pay attention copy & paste the "JLink_OpenSDA_V2.bin"(attachment )

Hope it helps

Have a great day,
Alice

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[scornelius]

Allice,

Thanks  for the feedback. I'm glad that you could duplicate the problem.

To your questions on my setup.

I have two KDS sessions up, each debugging a different work-space.

Each is debugging into it's own FRDM-K64F.

Again, this is running using KDS 3.1.0.

Thanks for testing and finding the Segger solution.
I can change for intra-board development, but also have a PEmicro Multilink that can be used with production boards.

Do you know if PE Micro aware of the problem?

Thanks again,

Steve

[Alice_Yang]

Hello Steve,

Do you meaning open two KDS 3.2 windows for each FRDM-K64 board?

What about the projects ?

Could you please tell us the steps one by one how to reproduce the

error ? I will test it on my side .

BR

Alice