LPC MicrocontrollersのトピックRe: P&E Micro Multilink Universal Debug ISsue for LPC4367

P&E Micro Multilink Universal and LPC Link2 debug isuue for LPC4367

gauravmore — Wed, 20 Feb 2019 09:42:42 GMT

I am using P&E Micro Multilink Universal for debugging my development board. I am using LPC4367. It was ok till the time i was using LPC link3 which is there in the evaluation board OM13088.

Since our new development board has come and alreasy we have multilink universal used in our other projects, i want to use thesame for debugging this development board.

Following is the error which I am facing.

unable to proceed further please suggest the solution for the same.

Thanks

Gaurav More

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

converse — Wed, 20 Feb 2019 11:19:03 GMT

Is this a brand-new board design, that you have never debugged before? If so, I suggest you read:

https://community.nxp.com/thread/388998

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

gauravmore — Thu, 21 Feb 2019 05:37:50 GMT

Hi Con Verse

As per the link i refered and check. It is proper . I also refer Using the LPCXpresso V2/V3 Boards to Debug an external Board | MCU on Eclipse which says that using the eval boad youcan program the external controller as well. So I am trying to connect OM13088 Eval boards LPC link2 to ny Eval board using the below mentioned connector and jumper modifications.

But it gives following error msg.

Trying to debug byt need your suggesstion for the same.

Thanks

Gaurav More

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

converse — Thu, 21 Feb 2019 08:29:35 GMT

So, you are trying to connect an LPC-Lin2 to your (new) board? Please confirm.

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

gauravmore — Thu, 21 Feb 2019 09:06:07 GMT

Hi Con Verse,

Yes I am trying to debug mt development board using LPCexpresso evaluation board OM13088. I made the connection and tried to program. I refered this line mentioned in

UM10946 / LPCXpresso4367/43S67/18S37 Rev B Boards/ Rev. 1.0 — 18 November 2015 User manual , Point 6.3

mentioned below.

And initiiating the debugging i got msg.

It seems that I am not able to get the JTag Device detected. Any suggestion for the same.

Thanks

Gaurav More

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

Alice_Yang — Thu, 21 Feb 2019 09:10:27 GMT

Hello Gaurav More,

- The debugger on LPCXpresso V2/V3 board or LPC link-2 doesn't support P&E probe. It only support Liner server and J-link.

-Before debug, please delete the Debug file under Debug folder, or the debugger will use the old one.

then click debug button:

- When short JP1, it means your target board do not need external power.

- Also as Con Verse mentioned, how about link-2 ?

Have a great day,
TIC

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

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

gauravmore — Thu, 21 Feb 2019 09:24:29 GMT

Hi Alice,

I followed the same procedure but still it is giving the same error msg as mentioned above.

0 avialable Jtag Detected.

Now i am trying to debug LPC11u68 board with the same board.to check whether there is a problem with the developement board,

Please suggest till i check the other ways around.

I tried to debug from one MO13088 to another OM13088 and i am able to programm and debug as per the guiddelines provided in User manual

UM10946
LPCXpresso4367/43S67/18S37 Rev B Boards
Rev. 1.0 — 18 November 2015 User manual

But still not success in debugging my Board. The difference between my board and the the eval board is mine is LPC4367JBD208

But still what is missing has anyboy tried with there development board. if so then plese share the board files for the mentioned part number and method of debugging the same.

Thanks

Gaurav More

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

converse — Thu, 21 Feb 2019 16:46:17 GMT

The debug circuit for your development board is broken. Fix it, and you will be able to debug. Read the Design Consideration for Debug document (2nd post, above) and then check your circuit. And then check it again...

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

gauravmore — Fri, 22 Feb 2019 06:01:12 GMT

Hi Con Verse,

As per the input i have checked but still would like to share the Schematics of my board or reference,

Please comment on ths same. Mean while I am also checking the same at my end.

Thanks

Gaurav More

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

gauravmore — Tue, 26 Feb 2019 04:09:33 GMT

Hi Con Verse,

Any input regarding the schematics shared.

Thanks

Gaurav More

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

gauravmore — Wed, 27 Feb 2019 09:41:49 GMT

Hi Con Verse / Jeremy

I have checked the Schematic and made the modification in it since it is observed that Jtag TRST not connected to the MCU reset line and TRST line of Controller was not pulled up. Now I am able to program the development board but only when it is powered up with Evaluation board. When I am applying the power supply from my board and the Evaluation board is also powered,then it is programing and generating an error of flash initialization and due to whihc is it stopping in between.

Let me know what would be the issue.

Thanks

Gaurav More

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

converse — Wed, 27 Feb 2019 15:34:36 GMT

Sounds like a power problem to me. Programing flash significantly increases current draw.

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

gauravmore — Mon, 04 Mar 2019 11:02:58 GMT

Hi Con Verse

Initially it was programming when it was powered through JTag, but then when I put the RC circuit on REset as per the schematic of OM13088 it stopped debugging Even after powered Through JTag,

While debugging I am getting Follwing Error and the debugging stops while launching

MCUXpresso IDE RedlinkMulti Driver v10.3 (Nov 28 2018 02:33:57 - crt_emu_cm_redlink build 748)
Found chip XML file in D:/GAURAV MORE/PROJECTS/NEW FEEDER RELAY/ESE/Code/CPU/MCUXpresso/March2019/ESE_F4_CPU_04Mar19/NFR_M4/Debug\LPC4367.xml
Reconnected to existing link server
Connecting to probe 1 core 0 (using server started externally) gave 'OK'
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.224 (NXP Semiconductors)
Serial Number: HQA2BQEQ
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#8&215c9953&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
debug interface type = Cortex-M3/4 (DAP DP ID 4BA00477) over JTAG TAP 0
processor type = Cortex-M4 (CPU ID 00000C24) on DAP AP 0
number of h/w breakpoints = 6
number of flash patches = 2
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 4BA00477. CpuID: 00000C24. Info: <None>
Debug protocol: JTAG. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FF000: CID B105100D PID 04000BB4C4 ROM (type 0x1)
ROM 1 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 1 E0001000: CID B105E00D PID 04003BB002 Gen DWT (type 0x0)
ROM 1 E0002000: CID B105E00D PID 04002BB003 Gen FPB (type 0x0)
ROM 1 E0000000: CID B105E00D PID 04003BB001 Gen ITM (type 0x0)
ROM 1 E0040000: CID B105900D PID 04000BB9A1 CSt TPIU type 0x11 Trace Sink - TPIU
ROM 1 E0041000: CID B105900D PID 04000BB925 CSt ETM type 0x13 Trace Source - Core
NXP: LPC4367
DAP stride is 4096 bytes (1024 words)
Inspected v.2 On-chip Flash Memory LPC18x7_43x7_2x512_BootA.cfx
Image 'LPC18x7/LPC43x7 2x512KB (Boot Bank A) Oct 25 2018 11:58:16'
( 65) Chip Setup Complete
Connected: was_reset=true. was_stopped=false
Awaiting telnet connection to port 3333 ...
GDB nonstop mode enabled
Opening flash driver LPC18x7_43x7_2x512_BootA.cfx
Sending VECTRESET to run flash driver
There was a problem after we succesfully downloaded flash driver code to the target, so we are going to compare the flash driver code with the memory where it was loaded.
Note that, after driver initialization, some difference is normal in 'generic' drivers.

Driver from AXF file:
10000184: f104682b 47980118 b96069a0 3000f8d8 +h.....G.i`....0
10000194: 9000e9c4 3703e9c4 462060a6 f104682b .......7.` F+h..
100001A4: 47980118 e8bd69a0 bf0083f8 100003b8 ...G.i..........
100001B4: 10400100 100003b4 41f0e92d f7ff4607 ..@.....-..A.F..
100001C4: 280eff8d d8424680 4c222335 5fd8f1b7 ...(.FB.5#"L..._
100001D4: 3000e9c4 2300bf34 39012301 60e3180d ...04..#.#.9...`
100001E4: 4b1e4e1d f1a660a5 681b0018 47984631 .N.K.`.....h1F.G
100001F4: 280869a0 2332d129 5fd8f1b7 3c18f846 .i.().2#..._F..<
10000204: 2300bf34 e9c42301 60e38501 4b134912 4..#.#.....`.I.K
10000214: 0018f1a1 4798681b b9b069a0 f8462334 .....h.G.i..4#F.
10000224: 4b0f3c18 5fd8f1b7 e9c4681b 60e38501 .<.K..._.h.....`
10000234: 2301bf28 bf284908 4b086123 6120bf38 (..#.I(.#a.K8. a
10000244: f1a1681b 47980018 e8bd69a0 200181f0 .h.....G.i.....
10000254: bf00e7fb 100003b8 100003d0 10400100 ..............@.
10000264: 100003b4 47f0e92d 460e4605 46074690 ....-..G.F.F.F.F
10000274: f8df4c2b 463890b8 ff30f7ff d84d280e +L....8F..0..(M.
10000284: f1b52332 e9c45fd8 bf343000 23012300 2#..._...04..#.#
10000294: 60a04924 f1a160e3 f8d90018 47983000 $I.`.`.......0.G
100002A4: 280069a0 2333d136 3700e9c4 0305eba8 .i.(6.3#...7....
100002B4: 60a3443b 5380f44f 60e34a1b f1b56813 ;D.`O..S.J.`.h..
100002C4: 61235fd8 2301bf28 bf344916 61636160 ._#a(..#.I4.`aca
100002D4: 0018f1a1 3000f8d9 47984692 b9c869a0 .......0.F.G.i..
100002E4: 5f80f5b6 f44fbf38 f5b65680 f5075080 ..._8.O..V...P..
100002F4: d1115780 5fd0f1b5 233cd10c 3000e9c4 .W....._..<#...0
10000304: 3000f8da 60a34907 0018f1a1 3000f8d9 ...0.I.`.......0
10000314: 69a04798 87f0e8bd e7ac4606 e7f92001 .G.i.....F... ..
10000324: 100003b8 100003d0 100003b4 10400100 ..............@.
10000334: 7380f020 5fd0f1b3 4606b570 4614460d ..s..._p..F.F.F
10000344: 221cd111 f0004621 b108f811 bd70200a ..."!F....... p.
10000354: 0220f1a5 0120f104 0020f106 f806f000 .. ... ... .....
10000364: d0f42800 460ae7f2 e7f74621 0301ea40 .(.....F!F..@...
10000374: b570079b 4604d10c 2a03460b 46204619 ..p....F.F.*.F F
10000384: 6806d906 3404680d f10342ae d0040304 ...h.h.4.B......
10000394: 4291440a 2000d103 3a04e008 f810e7ed .D.B... ...:....
100003A4: f8113b01 42a34b01 1b18d0f3 0000bd70 .;...K.B....p...
100003B4: 00000000 00000000 00000000 00000000 ................
100003C4: 00000000 00000000 00000000 00000000 ................
100003D4: 00000000 00000000 ........
Driver code in memory:
10000184: 00000007 00000007 00000007 00010001 ................
10000194: 90000001 3703e9c4 462060a6 f104682b .......7.` F+h..
100001A4: 47980118 e8bd69a0 bf0083f8 100003b8 ...G.i..........
100001B4: 10400100 100003b4 41f0e92d f7ff4607 ..@.....-..A.F..
100001C4: 280eff8d d8424680 4c222335 5fd8f1b7 ...(.FB.5#"L..._
100001D4: 3000e9c4 2300bf34 39012301 60e3180d ...04..#.#.9...`
100001E4: 4b1e4e1d f1a660a5 681b0018 47984631 .N.K.`.....h1F.G
100001F4: 280869a0 2332d129 5fd8f1b7 3c18f846 .i.().2#..._F..<
10000204: 2300bf34 e9c42301 60e38501 4b134912 4..#.#.....`.I.K
10000214: 0018f1a1 4798681b b9b069a0 f8462334 .....h.G.i..4#F.
10000224: 4b0f3c18 5fd8f1b7 e9c4681b 60e38501 .<.K..._.h.....`
10000234: 2301bf28 bf284908 4b086123 6120bf38 (..#.I(.#a.K8. a
10000244: f1a1681b 47980018 e8bd69a0 200181f0 .h.....G.i.....
10000254: bf00e7fb 100003b8 100003d0 10400100 ..............@.
10000264: 100003b4 47f0e92d 460e4605 46074690 ....-..G.F.F.F.F
10000274: f8df4c2b 463890b8 ff30f7ff d84d280e +L....8F..0..(M.
10000284: f1b52332 e9c45fd8 bf343000 23012300 2#..._...04..#.#
10000294: 60a04924 f1a160e3 f8d90018 47983000 $I.`.`.......0.G
100002A4: 280069a0 2333d136 3700e9c4 0305eba8 .i.(6.3#...7....
100002B4: 60a3443b 5380f44f 60e34a1b f1b56813 ;D.`O..S.J.`.h..
100002C4: 61235fd8 2301bf28 bf344916 61636160 ._#a(..#.I4.`aca
100002D4: 0018f1a1 3000f8d9 47984692 b9c869a0 .......0.F.G.i..
100002E4: 5f80f5b6 f44fbf38 f5b65680 f5075080 ..._8.O..V...P..
100002F4: d1115780 5fd0f1b5 233cd10c 3000e9c4 .W....._..<#...0
10000304: 3000f8da 60a34907 0018f1a1 3000f8d9 ...0.I.`.......0
10000314: 69a04798 87f0e8bd e7ac4606 e7f92001 .G.i.....F... ..
10000324: 100003b8 100003d0 100003b4 10400100 ..............@.
10000334: 7380f020 5fd0f1b3 4606b570 4614460d ..s..._p..F.F.F
10000344: 221cd111 f0004621 b108f811 bd70200a ..."!F....... p.
10000354: 0220f1a5 0120f104 0020f106 f806f000 .. ... ... .....
10000364: d0f42800 460ae7f2 e7f74621 0301ea40 .(.....F!F..@...
10000374: b570079b 4604d10c 2a03460b 46204619 ..p....F.F.*.F F
10000384: 6806d906 3404680d f10342ae d0040304 ...h.h.4.B......
10000394: 4291440a 2000d103 3a04e008 f810e7ed .D.B... ...:....
100003A4: f8113b01 42a34b01 1b18d0f3 0000bd70 .;...K.B....p...
100003B4: 00000000 00000000 00000000 00000000 ................
100003C4: 00000000 00000000 00000000 00000000 ................
100003D4: 00000000 00000000 ........
(100) Writing Flash ended with an error.
Target error from Write Flash: Ef(50): Flash driver failed to initialize
GDB stub (crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.

What would be the reson as I am also refering the forum

https://community.nxp.com/thread/491549

But still no success, Please let me know what is missing.

Thanks

Gaurav More

Re: P&E Micro Multilink Universal Debug ISsue for LPC4367

gauravmore — Wed, 06 Mar 2019 06:24:04 GMT

We have observed the flaws in our schematic and accordingly modified it in the development board in order to check whether the observed changes are right.

We have two set of boards. We did the modification on both the boards. Now I am able to program and debug one board and another board it gives me an error Refer the attachment.

In attachment I have provided the log of both the board Working and Non-working. There I found in non-working board first word in corrupted see the lines below.

code (at 0x10000000) not set as written - corrupted at 0x10000000 (word 0)

Driver from AXF file:

10000000: 23010020 54000045 00001032 10000000 ..#E..T2.......

Driver code in memory:

10000000: 018785f2 54000045 00001032 10000000 ....E..T2.......

I have highlighted the words which are not matching but the same code is getting programmed in other board. I tried multiple times. I did this with LPC xpresso.

I referred the forums as mentioned earlier MCUXpresso IDE v10.3.0 [Build 2200] Problem [BUG?]. In that they have mentioned how to get the debug access. But It is not working for me.

Is there any provision to erase the flash before writing in LPC Xpresso?

Thanks

Gaurav More

Re: P&E Micro Multilink Universal and LPC Link2 debug isuue for LPC4367

brendonslade — Sat, 09 Mar 2019 00:31:54 GMT

Gaurav,

the debug circuit on LPCXpresso V2/V3 boards only supports debug of SWD systems, not JTAG. On the LPC43xx/LPC18xx devices you can only do multi-core debug using JTAG (since SWD didnt support multicore at the time these devices were designed).

You can still debug the main core of the LPC4367 using this type of setup. You would need to buy a P&E, SEGGER or LPC-Link2 probe to get access to the M0 cores in your device, provided your circuit is designed for SWD. Looking at your JTAG connector, it is not laid out as a standard ARM SWD connector.

I would suggest checking that the LPC11U68 board you have can connect to the OM13088 as a first step, using an SWD connection.