topic Re: Multicore debugging session fails on NXP LPC54102 board. in LPC Microcontrollers

Multicore debugging session fails on NXP LPC54102 board.

lpcware — Wed, 15 Jun 2016 19:57:22 GMT

Content originally posted in LPCWare by waleed on Tue Apr 14 01:24:23 MST 2015
I want to debug bare metal application on both cores of NXP LPC54102 board.

My application for m4 core contains boot address and stack address for m0+ core.Thus my application for m4 core is setting up the environment for m0+ core.

I first connect to m4 core and start a debugging session on it and insert breakpoints at different locations, my m4 application set coprocessor stack and coprocessor boot reg, resets m0+ core and enable it's clock by writing to cpu control register.After this i connect to m0+ core and start a debug session on it and insert breakpoints at different locations.

Now if i give "c" command from GDB in m4 debugging session, i am able to hit all of my breakpoints and debugging works fine.But as soon as i give "c" command in m4 debugging session and after this i give "c" command in m0+ debugging session i get following error from GDB:
(gdb) c
continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0xfffffffe in ?? ()

Any suggestion what am i doing wrong?

Re: Multicore debugging session fails on NXP LPC54102 board.

lpcware — Wed, 15 Jun 2016 19:57:23 GMT

Content originally posted in LPCWare by TheFallGuy on Tue Apr 14 01:43:40 MST 2015
Which toolchain?
Which debug probe?
How are you connecting to both cores?

Re: Multicore debugging session fails on NXP LPC54102 board.

lpcware — Wed, 15 Jun 2016 19:57:24 GMT

Content originally posted in LPCWare by waleed on Tue Apr 14 03:28:58 MST 2015
GNU toolchain
Jlink
J-Link GDB server to connect to m4 core and to connect to m0+ core i am also passing script file to J-Link GDB server.

Re: Multicore debugging session fails on NXP LPC54102 board.

lpcware — Wed, 15 Jun 2016 19:57:24 GMT

Content originally posted in LPCWare by TheFallGuy on Tue Apr 14 04:23:08 MST 2015
Sorry, I can't help you. I use LPCXpresso/LPC-Link2 and it works for me.

Re: Multicore debugging session fails on NXP LPC54102 board.

lpcware — Wed, 15 Jun 2016 19:57:25 GMT

Content originally posted in LPCWare by waleed on Tue Apr 14 08:18:58 MST 2015
Hi NXP Technical Support,

Any suggestions, what might be the problem

Re: Multicore debugging session fails on NXP LPC54102 board.

lpcware — Wed, 15 Jun 2016 19:57:26 GMT

Content originally posted in LPCWare by xianghuiwang on Fri Apr 24 09:45:04 MST 2015
if you do not do 'c' on M4, would you be able to do 'c' on M0+?
please share your script file, we may take a look.
regards,

Re: Multicore debugging session fails on NXP LPC54102 board.

lpcware — Wed, 15 Jun 2016 19:57:26 GMT

Content originally posted in LPCWare by waleed on Fri Apr 24 11:49:45 MST 2015
Yes. If i do not do "c" on m4, m0+ debugging session works fine. I have also attached the script file.

Re: Multicore debugging session fails on NXP LPC54102 board.

lpcware — Wed, 15 Jun 2016 19:57:27 GMT

Content originally posted in LPCWare by xianghuiwang on Fri Apr 24 17:13:58 MST 2015
can you try to reduce the m4 code - there might be something wrong with your m4 code?