LPCXpresso with Segger J-Link

lpcware · ‎06-15-2016

Content originally posted in LPCWare by galmiklos on Mon Sep 30 07:31:48 MST 2013
Is it possible to use the LPCXpresso IDE with Segger's J-Link? I thought LPCXpresso worked through GDB, so I connect my J-Link EDU to my target board, launch Segger's GDB server, it shows j-link connected, target connected, and waiting for GDB connection, but when I launch debug from LPCXpresso, it cannot find any "emulator".

The message in the pop-up window is "No compatible emulators available", while in the RedlinkServer console I can see:

[Started server]
[Connected on [color=#f03]port 3025[/color]]
redlink>ProbeList
No probes found

In the Segger GDB server log, I can see it's listening on port 2331.

SEGGER J-Link GDB Server V4.68a

JLinkARM.dll V4.68a (DLL compiled Apr 12 2013 13:26:50)

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link ARM V8 compiled Nov 14 2012 22:34:52
Hardware: V8.00
S/N: 268004691
OEM: SEGGER-EDU
Feature(s): FlashBP, GDB
Checking target voltage...
[color=#f03]Listening on TCP/IP port 2331[/color]
Connecting to target...
J-Link found 1 JTAG device, Total IRLen = 4
JTAG ID: 0x4BA00477 (Cortex-M3)
Connected to target
Waiting for GDB connection...

But I cannot see any option to change the port LPCXpresso is connecting to.

Is it just me, or is it just simply not supported?

Thank you,
Miki.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Wed May 27 02:39:25 MST 2015
Amongst other restrictions, the LPCXpresso Free Edition provides you with a license to download/debug images of up to 256 KB. We make no guarantees that any behaviour you might see today with regards to such limits will not change in the future.

If this restriction impacts on your ability to debug your project then we recommend that you look at LPCXpresso IDE Pro Edition. When combined with LPC-Link2 (or other supported debug probes), this is an inexpensive, powerful and high speed debug solution.

Regards,
LPCXpresso Support

lpcware · ‎06-15-2016

Content originally posted in LPCWare by giusloq on Tue May 26 06:26:30 MST 2015
Please, give a precise info. Is it possible to use LPCXpresso Free Edition with Segger J-Link, without the memory restriction?

Someone told me the restriction disappears, other exactly the opposite.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by 1234567890 on Tue May 12 08:57:58 MST 2015

Quote: hparracho

A fully supported J-Link probe would definitely be a neat addition to the LPCXpresso tool.
I [u]bet[/u] I'm not alone on this...

And the winner is ... hparracho

lpcware · ‎06-15-2016

Content originally posted in LPCWare by hparracho on Tue May 12 06:55:15 MST 2015

Quote: lpcxpresso-support
You can use J-Link with any version of LPCXpresso. However, with J-Link, LPCXpresso does not support the following
- Peripheral views
- 'Extra' registers in Register view (for example additional registers shown after a hard fault)
- SWO Trace

A fully supported J-Link probe would definitely be a neat addition to the LPCXpresso tool.
I bet I'm not alone on this...

lpcware · ‎06-15-2016

Content originally posted in LPCWare by giusloq on Tue May 12 06:48:01 MST 2015

Quote:
You can use J-Link with any version of LPCXpresso.

And what about debugging limitations on memory space? Could I use J-Link to debug 300KB object code with Free Edition?

Quote:
These are supported with LPC-Link2

Again, is the limitations on object code size during debugging present if LPC-Link2 is used with Free Edition?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Tue May 12 06:38:49 MST 2015
You can use J-Link with any version of LPCXpresso. However, with J-Link, LPCXpresso does not support the following
- Peripheral views
- 'Extra' registers in Register view (for example additional registers shown after a hard fault)
- SWO Trace

These are supported with LPC-Link2 (OM13054):
http://www.lpcware.com/lpclink2

lpcware · ‎06-15-2016

Content originally posted in LPCWare by giusloq on Tue May 12 04:01:04 MST 2015
I'm sorry for my dumb questions, but I'm new to LPCXpresso and NXP micros.

I understood J-Link debug probes from Segger are now compatible with NXP LPCXpresso IDE latest release. What I couldn't understand if I need the Pro Edition of LPCXpresso.
If LPCXpresso Free Edition is sufficient to use J-Link, will I always have the 256KB limitation during debugging even if using J-Link?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Tue May 12 01:05:00 MST 2015
You can use the exact same plugins in LPCXpresso. Segger are going to update their web pages. In the meantime, you can follow the instructions here:

https://www.segger.com/IDE_Integration_Eclipse.html

(See the section on GNU ARM plugin). There is one additional step for LPCXpresso: you need to also define the String variable "cross_prefix" to "arm-none-eabi-". Windows->Preferences, Run/Debug->String substitution

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lix on Tue May 12 00:41:45 MST 2015
Thanks for the fast answer (as always! ;-)).

It's a pity that NXP doesn't better integrate JLink support. It should be possible to start the GDB server directly from the LPCXpresso, not to speak about supporting the numerous features of the JLink.

I am not using LPCXpresso actually. I use both professionally as well as a hobbyist at home the Gnuarmeclipse plugins with a splendid support for JLink; it is a colleague who insists using LPCXpresso and couldn't use the JLink with it on the Mac.

Best regards,

Lix

lpcware · ‎06-15-2016

Content originally posted in LPCWare by SEGGER - Alex on Mon May 11 23:43:19 MST 2015
Hi Lix,

Maybe this way?:

./JLinkGDBServer -device LPC1768 -if SWD -speed 4000 -endian little

- Alex

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lix on Mon May 11 22:10:20 MST 2015
Hello Alex,

How would you start the J-Link GDB server on a Mac or Linux where you have only the command line version?

Tanks in advance.

Lix

lpcware · ‎06-15-2016

Content originally posted in LPCWare by SEGGER - Alex on Mon Dec 08 00:21:51 MST 2014
Hi,

Quote:
In this case it's working around the corner...

Not really... Just wanted to show you a generic debugging alternative.

Regarding the SFR problem:
As I wrote, all the IDE needs to do is, telling J-Link GDB Server to read memory from certain addresses (the ones of the SFRs).
It may be a problem with the non-complete support in LPCXpresso (NXP) or a problem with the J-Link plugin (created and maintained by an independent 3rd party).
We have no direct influence on both of these components.
Sorry that I cannot help here further.

- Alex

lpcware · ‎06-15-2016

Content originally posted in LPCWare by 1234567890 on Sat Dec 06 07:06:55 MST 2014

Quote:
We think it is a common interest for NXP and SEGGER to have good J-Link support in LPCXpresso.

The valued customer agrees...

Quote:
Maybe the J-Link debugger is an alternative for you? https://www.segger.com/j-link-debugger.html
It is a debugger that allows you to open ELF files and debug with J-Link. It also supports CMSIS SVD files for peripheral views.

I will have a look when there is a Linux version available. But generally it's a secondary solution for [u]this[/u] kind of problem (downloading a SVD file, starting another application and so on). In this case it's working around the corner...

lpcware · ‎06-15-2016

Content originally posted in LPCWare by SEGGER - Alex on Wed Dec 03 00:33:57 MST 2014
Hi,

Quote:
Sorry, but I don't know of any way to have the LPCXpresso Peripheral view when using J-Link.

On this, I cannot really comment because I do not know the internals of LPCXpresso, but to me, reading/writing memory and show it in a window, does not sound like a big challenge, if you have complete control over the IDE.
We (SEGGER) would also appreciate full J-Link support in LPCXpresso and are always open for technical questions / feature requests from the LPCXpresso team, if they are missing some features in J-Link GDB Server, to be able to provide full J-Link support.
We think it is a common interest for NXP and SEGGER to have good J-Link support in LPCXpresso.

To 1234567890:
Maybe the J-Link debugger is an alternative for you? https://www.segger.com/j-link-debugger.html
It is a debugger that allows you to open ELF files and debug with J-Link. It also supports CMSIS SVD files for peripheral views.

Best regards
Alex

lpcware · ‎06-15-2016

Content originally posted in LPCWare by 1234567890 on Tue Dec 02 05:57:34 MST 2014
Thanks. And no worries: I'm still a happy customer of both companies...
As it works fine with a separated LPC-Link 1 it's not a tragedy.
Using LPCXpresso with a reactivated elderly and well equiped ET-NXP LPC1768 board in combination with a J-Link would have been a very nice extra.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Tue Dec 02 05:44:48 MST 2014
Sorry, but I don't know of any way to have the LPCXpresso Peripheral view when using J-Link.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by 1234567890 on Tue Dec 02 05:32:59 MST 2014
O.k. guys, please calm down...

@SEGGER - Alex: I'm aboslutely not familiar with GDB. But all other logs I saw read other values; not zeroes.
So the real or next problem I thought to identify is that R8 can't be read.
I will do a little homework, I promise.

@lpcxpresso-support: Yes, I installed a foreign plugin. But only in need of the peripheral view.
If there is a supported way to use this feature with J-Link please let me know. As I wrote the recommended way works, but no peripheral...
Mixing 'modules' that are not intended for have never been a good idea. I know that; it was just a try.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Tue Dec 02 02:13:08 MST 2014
This is NOT LPCXpresso. The customer has installed a GNU ARM plugin and (as far as I can tell) that is what is causing the problem.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by SEGGER - Alex on Tue Dec 02 01:39:53 MST 2014
Hi,

Quote:
Read 1 bytes @ address 0x00000000 (Data = 0x00) <=========== PROBLEM starts

I do not really see what "problem" you mean here. LPCXpresso asks J-Link GDBServer to read memory, so it does.

Anyhow, I do not think that this is an issue on the J-Link side, but more on the LPCXpresso side.
All that needs to be done by LPCXpresso is requesting memory at the given SFR addresses. J-Link GDBServer will then read it.
So I will let the LPCXpresso team answer here.

- Alex

lpcware · ‎06-15-2016

Content originally posted in LPCWare by 1234567890 on Mon Dec 01 12:53:35 MST 2014
Hi,

after installing V4.94h on my Kubuntu 14.04 amd64 and customizing the Startup-Tab (device and so on) it works. I choose the 32-bit version of the pack.
***Edit***: Same behaviour with the 64-bit version.

But unfortunately the 'Peripherals' view is empty and so debugging is pretty impossible.

Therefore I installed the 'GNU ARM Eclipse SEGGER J-Link debugger plug-in' in hope of solving that issue. Without success:

SEGGER J-Link GDB Server V4.94h Command Line Version

JLinkARM.dll V4.94h (DLL compiled Nov 28 2014 17:54:16)

-----GDB Server start settings-----
GDBInit file:                  none
GDB Server Listening port:     2331
SWO raw output listening port: 2332
Terminal I/O port:             2333
Accept remote connection:      localhost only
Generate logfile:              off
Verify download:               on
Init regs on start:            on
Silent mode:                   off
Single run mode:               on
Target connection timeout:     5000 ms
------J-Link related settings------
J-Link Host interface:         USB
J-Link script:                 none
J-Link settings file:          none
------Target related settings------
Target device:                 LPC1768
Target interface:              SWD
Target interface speed:        1000kHz
Target endian:                 little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
Hardware: V8.00
S/N: 268000xxx
OEM: SEGGER-EDU
Feature(s): FlashBP
Checking target voltage...
Target voltage: 3.28 V
Listening on TCP/IP port 2331
Connecting to target...Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
Reading all registers
Read 1 bytes @ address 0x00000000 (Data = 0x00)     <=========== PROBLEM starts
Read 1 bytes @ address 0x00000000 (Data = 0x00)
Reading 64 bytes @ address 0x00000000
Reading 8 bytes @ address 0x00000000
Reading 7 bytes @ address 0x00000000
Target interface speed set to 1000 kHz
Resetting target
Halting target CPU...
...Target halted (PC = 0x00000170)
R0 = 00000000, R1 = 00000171, R2 = 00000000, R3 = 00000000
R4 = 3456ABCD, R5 = 3456ABCD, R6 = 12345678, R7 = 10007FE0
R8 = 6D9175DB, R9 = 54CE0464, R10= AD57C55A, R11= 3F3BE492
R12= 00000107, R13= 10008000, MSP= 10008000, PSP= F5A6BD00
R14(LR) = 1FFF0D5F, R15(PC) = 00000170
XPSR 61000000, APSR 60000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
Reading all registers
WARNING: Failed to read memory @ address 0x6D9175DB
WARNING: Failed to read memory @ address 0x6D9175DB
Reading 8 bytes @ address 0x6D9175DB
WARNING: Failed to read memory @ address 0x6D9175DB
Reading 7 bytes @ address 0x6D9175DB
WARNING: Failed to read memory @ address 0x6D9175DB
Reading 64 bytes @ address 0x6D9175C0
WARNING: Failed to read memory @ address 0x6D9175C0
Select auto target interface speed (2000 kHz)
Flash breakpoints enabled
Semi-hosting enabled (VectorAddr = 0x08)
Semihosting I/O set to TELNET Client
SWO disabled succesfully.
SWO enabled succesfully.
WARNING: Failed to read memory @ address 0x6D9175DB
WARNING: Failed to read memory @ address 0x6D9175DB
Reading 8 bytes @ address 0x6D9175DB
WARNING: Failed to read memory @ address 0x6D9175DB
Reading 7 bytes @ address 0x6D9175DB
WARNING: Failed to read memory @ address 0x6D9175DB
Reading 64 bytes @ address 0x6D9175C0
WARNING: Failed to read memory @ address 0x6D9175C0
Downloading 2756 bytes @ address 0x00000000 - Verified OK
Writing register (R8 = 0x00000171)
WARNING: Unsupported register (-1)
Reading register (PRIMASK = 0x00000000)
GDB closed TCP/IP connection

Obviously it doesn't work at an early point directly after connection of the gdbserver.
(reading 0x00 @ address 0x00000000).

Any suggestions?

Full support of the J-Link would be a great pleasure; especially when using custom boards.
Seperating a LPC-Link 1 and use LPCXpresso with a custom board works also fine, but when there is a J-Link available...