topic Re: LpcXpresso 6.1.4 restart debug section in LPCXpresso IDE

LpcXpresso 6.1.4 restart debug section

lpcware — Wed, 15 Jun 2016 23:04:09 GMT

Content originally posted in LPCWare by vostro1000 on Tue Jan 28 16:23:49 MST 2014
Any one knows how to enable restart debug section in this release?

Re: LpcXpresso 6.1.4 restart debug section

lpcware — Wed, 15 Jun 2016 23:04:09 GMT

Content originally posted in LPCWare by lpcxpresso-support on Wed Jan 29 02:31:01 MST 2014
There is a problem in the product that sometimes causes the Restart button to not appear in the Toolbar.

However, the Restart functionality is still available. In the Debug view, right-click on the entry containing the name of the axf (executable) file and select Restart from the context menu.

Re: LpcXpresso 6.1.4 restart debug section

lpcware — Wed, 15 Jun 2016 23:04:10 GMT

Content originally posted in LPCWare by vostro1000 on Wed Jan 29 04:20:39 MST 2014
Many thanks for the tip! But in this release to start the debugger section is a bit problematic...

My config is: LPC4357 using Ulink2 cmsis dap swd conection.

Some times I need to enable vetor catch opition when something problematic happen like when config pll and other stuff can leave the micro in a "freezed" state but in normal usage it gives lot of problems like:(This happen even when the chip have a not problematic behavior)

LPCXpresso RedlinkMulti Driver v6.0 (Jan 8 2014 13:55:09 - crt_emu_cm_redlink build 256)
Looked for chip XML file in C:/nxp/LPCXpresso_6.1.4_194/lpcxpresso/bin/LPC4357.xml
Looked for vendor directory XML file in C:/nxp/LPCXpresso_6.1.4_194/lpcxpresso/bin/NXP_directory.xml
Found generic directory XML file in C:/nxp/LPCXpresso_6.1.4_194/lpcxpresso/bin/crt_directory.xml
Cannot halt processor
Failed on connect: Ep(04). Cannot halt processor.
Conn&Reset. Was: None. DpID: 2BA01477. CpuID: 00000000. Info: (null)

And to start the debug section I need to keeping reconecting my usb cables when "vector catch" is enabled even when the chip are "health"!! Also sometimes when it's in the begining of the debug section it crash and a messege on botton "stalled on bus operation" happen.

redlinkserver and gdb traces log also attached see below!

Any hint on this?

Re: LpcXpresso 6.1.4 restart debug section

lpcware — Wed, 15 Jun 2016 23:04:10 GMT

Content originally posted in LPCWare by lpcxpresso-support on Wed Jan 29 04:30:35 MST 2014
Please post the Debug Log:
http://www.lpcware.com/content/faq/lpcxpresso/debug-log

Re: LpcXpresso 6.1.4 restart debug section

lpcware — Wed, 15 Jun 2016 23:04:11 GMT

Content originally posted in LPCWare by vostro1000 on Wed Jan 29 06:53:40 MST 2014
Debug messages:

LPCXpresso RedlinkMulti Driver v6.0 (Jan 8 2014 13:55:09 - crt_emu_cm_redlink build 256)
Looked for chip XML file in C:/nxp/LPCXpresso_6.1.4_194/lpcxpresso/bin/LPC4357.xml
Looked for vendor directory XML file in C:/nxp/LPCXpresso_6.1.4_194/lpcxpresso/bin/NXP_directory.xml
Found generic directory XML file in C:/nxp/LPCXpresso_6.1.4_194/lpcxpresso/bin/crt_directory.xml
Cannot halt processor
Failed on connect: Ep(04). Cannot halt processor.
Conn&Reset. Was: None. DpID: 2BA01477. CpuID: 00000000. Info: (null)

Re: LpcXpresso 6.1.4 restart debug section

lpcware — Wed, 15 Jun 2016 23:04:12 GMT

Content originally posted in LPCWare by lpcxpresso-support on Wed Jan 29 16:49:27 MST 2014

The Redlink server console output shows the target did not successfully switch to the serial wire protocol, otherwise you would have seen the following:

DpID = 2BA01477

versus

DpID = 00000000

We'll investigate this. If you're using a custom board, you should review the following FAQ:

http://www.lpcware.com/content/faq/lpcxpresso/debug-design

Regards,

LPCXpresso-Support

Re: LpcXpresso 6.1.4 restart debug section

lpcware — Wed, 15 Jun 2016 23:04:12 GMT

Content originally posted in LPCWare by vostro1000 on Thu Jan 30 06:05:00 MST 2014
I'am not using a custom board ok!

Re: LpcXpresso 6.1.4 restart debug section

lpcware — Wed, 15 Jun 2016 23:04:13 GMT

Content originally posted in LPCWare by larryvc on Thu Jan 30 14:21:51 MST 2014

Quote: vostro1000
Debug messages:

LPCXpresso RedlinkMulti Driver v6.0 (Jan 8 2014 13:55:09 - crt_emu_cm_redlink build 256)
Looked for chip XML file in C:/nxp/LPCXpresso_6.1.4_194/lpcxpresso/bin/LPC4357.xml
Looked for vendor directory XML file in C:/nxp/LPCXpresso_6.1.4_194/lpcxpresso/bin/NXP_directory.xml
Found generic directory XML file in C:/nxp/LPCXpresso_6.1.4_194/lpcxpresso/bin/crt_directory.xml
Cannot halt processor
Failed on connect: Ep(04). Cannot halt processor.
Conn&Reset. Was: None. DpID: 2BA01477. CpuID: 00000000. Info: (null)

Quote: lpcxpresso-support
The Redlink server console output shows the target did not successfully switch to the serial wire protocol, otherwise you would have seen the following:

DpID = 2BA01477

versus

DpID = 00000000

Isn't the value in vostro1000's last post DpID = 2BA01477?

EDIT: lpcxpresso-support, what you said above does not make any sense given the context.