LPCLink not connected

lpcware · ‎06-15-2016

Content originally posted in LPCWare by blasiis on Mon May 31 05:33:09 MST 2010
I have work with my application, and now, after a correct build I cannot connect to LPCLink, the console write :

No symbol "new" in current context.
set remotetimeout 60000
set mem inaccessible-by-default off
mon ondisconnect nochange
mi_cmd_var_create: unable to create variable object
mi_cmd_var_create: unable to create variable object
Note: automatically using hardware breakpoints for read-only addresses.

Please help me

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Mon May 31 23:56:02 MST 2010
There is no 'play' button because the application hasn't hit the first breakpoint. My guess is that it has hit an exception somewhere in the startup code. To find out what it is doing, just hit the 'Pause' button - it will show what code it is executing.

To find out where it is going wrong, you need to change the initial breakpoint to the reset handler (ResetISR by default) and then single step through the code. See this for details:
http://lpcxpresso.code-red-tech.com/LPCXpresso/node/48

Just to re-iterate, there is nothing wrong with LPC-Link or the debugger. It is your code that is causing this.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by blasiis on Mon May 31 23:51:45 MST 2010

Quote: blasiis
Yes I work withoy problem with LPCLINK and my board from about two week !
Now, I cannot start the debug, if I open mannualy the debug windows, the play button it isn't enabled, like in the attached jpg file.
I have checked the connection between lpclink and board, and tried to use a simple example program, but does not work!
It is possible that I have inadvertently changed a parameter that is causing this problem?

Thanks for helping

Solved the problem !!!!
The error was in P2.10 to GND.
With this condition the µP start from bootloader !

lpcware · ‎06-15-2016

Content originally posted in LPCWare by blasiis on Mon May 31 23:30:58 MST 2010

Quote: CodeRedSupport
Again, I don't see anything wrong in the messages.
[IMG]file:///C:/Documents%20and%20Settings/Stefano.PORTORICO/Desktop/degug.JPG[/IMG]
I notice from the log that you are debugging an LPC1758. Therefore, I conclude that you are trying to debug one of your own boards. Can you confirm that is what you are doing? If so, have you correctly wired up the SWD debug signals on the target board?

Yes I work withoy problem with LPCLINK and my board from about two week !
Now, I cannot start the debug, if I open mannualy the debug windows, the play button it isn't enabled, like in the attached jpg file.
I have checked the connection between lpclink and board, and tried to use a simple example program, but does not work!
It is possible that I have inadvertently changed a parameter that is causing this problem?

Thanks for helping

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Mon May 31 09:43:01 MST 2010
Again, I don't see anything wrong in the messages.

I notice from the log that you are debugging an LPC1758. Therefore, I conclude that you are trying to debug one of your own boards. Can you confirm that is what you are doing? If so, have you correctly wired up the SWD debug signals on the target board?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by blasiis on Mon May 31 06:18:35 MST 2010

Quote: CodeRedSupport
There is nothing wrong in what you have posted. These are all normal messages. Why do you think you can't connect?

LPCLink not connected, the red led in the LPCLINK is on, but in the lpcxpresso, debug window don't start

this is more message when stop:

LPCXpresso Debug Driver v2.0 (Apr 8 2010 14:58:49)
Looked for chip XML file in C:/nxp/lpcxpresso_3.3/bin/LPC1758.xml
Looked for vendor directory XML file in C:/nxp/lpcxpresso_3.3/bin/nxp_directory.xml
Found generic directory XML file in C:/nxp/lpcxpresso_3.3/bin/crt_directory.xml
NXP: LPC1758 Part ID: 25013F37
Connected: was_reset=true. was_stopped=false
v Registered license, download limit of 128K
Writing 25900 bytes to 0000 in Flash (assumed clock: 14.748MHz)
Verified-same page 0-6 with 25900 bytes in 1539msec
Flash write Done
nSRST assert (if available)
Executing in bootloader.
Stopped (Was Reset) [Reset from PowerOn, External]
GDB trying to set entry point of 0x25AD, but correct entry is 0x1FFF0080
nSRST assert (if available)
Executing in bootloader.
Stopped: Halt
LPCXpresso Debug Driver v2.0 (Apr 8 2010 14:58:49)
Looked for chip XML file in C:/nxp/lpcxpresso_3.3/bin/LPC1758.xml
Looked for vendor directory XML file in C:/nxp/lpcxpresso_3.3/bin/nxp_directory.xml
Found generic directory XML file in C:/nxp/lpcxpresso_3.3/bin/crt_directory.xml
NXP: LPC1758 Part ID: 25013F37
Connected: was_reset=false. was_stopped=true
v Registered license, download limit of 128K
Writing 25900 bytes to 0000 in Flash (assumed clock: 14.748MHz)
Verified-same page 0-6 with 25900 bytes in 1515msec
Flash write Done
nSRST assert (if available)
Executing in bootloader.
Stopped (Was Reset) [Reset from Unknown]
GDB trying to set entry point of 0x25AD, but correct entry is 0x1FFF0080
nSRST assert (if available)
Executing in bootloader.
Stopped: Halt
LPCXpresso Debug Driver v2.0 (Apr 8 2010 14:58:49)
Looked for chip XML file in C:/nxp/lpcxpresso_3.3/bin/LPC1758.xml
Looked for vendor directory XML file in C:/nxp/lpcxpresso_3.3/bin/nxp_directory.xml
Found generic directory XML file in C:/nxp/lpcxpresso_3.3/bin/crt_directory.xml
NXP: LPC1758 Part ID: 25013F37
Connected: was_reset=false. was_stopped=true
v Registered license, download limit of 128K
Writing 25900 bytes to 0000 in Flash (assumed clock: 14.748MHz)
Verified-same page 0-6 with 25900 bytes in 1528msec
Flash write Done
nSRST assert (if available)
Executing in bootloader.
Stopped (Was Reset) [Reset from Unknown]
GDB trying to set entry point of 0x25AD, but correct entry is 0x1FFF0080
nSRST assert (if available)
Executing in bootloader.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Mon May 31 06:15:56 MST 2010
There is nothing wrong in what you have posted. These are all normal messages. Why do you think you can't connect?