again error 15

[lpcware]

Content originally posted in LPCWare by timer on Fri Jan 13 09:32:59 MST 2012
Hi,

I read a lot about this error but I have stil a problem.

My situation:

- as a kind of "rookie" for my LPC1769 I turn on the watchdog timer
- so I get the error 15 target ...
- with both, the vector catch and ISP I can get a connection to the board
- and the software is running (now without any watchdog stuff)
- but if I don't get into the ISP-Mode or turn on the vector cache I get the error again

Do I have to erase with the magic tool or is there anything what I can do else?

Greetings Tim

[lpcware]

Content originally posted in LPCWare by timer on Fri Jan 13 11:31:54 MST 2012
Thanks, I found the failure I think.
I changed the
     cr_startup_lpc17.c
to the
     cr_startup_lpc176x.c
Now I change back and it works fine.

Best regards, Tim

[lpcware]

Content originally posted in LPCWare by Ex-Zero on Fri Jan 13 11:17:34 MST 2012
A simple way to avoid problems like this is to include your watchdog enable code with:

#if[COLOR=Red]n[/COLOR]def  DEBUG
//whatever is in here is [COLOR=Red]not included[/COLOR] in Debug build
//because Symbol 'DEBUG' is defined in properties
#endif

So watchdog doesn't disturb you while debugging in 'Debug build' and if you make a final 'Release build' it's included again :rolleyes:

[lpcware]

Content originally posted in LPCWare by timer on Fri Jan 13 10:52:00 MST 2012
Erstmal großen Dank an deine Mühe.

Ich hatte schon

NVIC_DisableIRQ(WDT_IRQn);

probiert und jetzt habe ich noch

LPC_WDT->WDMOD = 0;

im Register ist er auch ausgeschaltet, aber es bleibt dabei. :(

[lpcware]

Content originally posted in LPCWare by Ex-Zero on Fri Jan 13 10:19:18 MST 2012
Do you understand this?

---

Quote:

It is possible to download an image into the flash on the target that will then prevent further debug connections. The classic cases of this are
...
    The image contains code that enables a watchdog timer.

---

Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.

Solution: Switch to ISP to reprogram your flash with

#1 disabled watchdog

or

#2 enabled watchdog. Enabled watchdog is killing your debug connection -> no SWD -> no programming / debugging via LPC-Link.
...

[lpcware]

Content originally posted in LPCWare by timer on Fri Jan 13 10:06:44 MST 2012
Yes, with this information I get access to the board.
But do I now have to use one of this way forever?
Or is there a way to get access as before the error?

[lpcware]

Content originally posted in LPCWare by Ex-Zero on Fri Jan 13 09:48:31 MST 2012
Did you read this ?

---

Quote:

Getting debug access to target chip

It is possible to download an image into the flash on the target that will then prevent further debug connections. The classic cases of this are
    The image contains code that sets the MCU clocks up "incorrectly".
    The image contains code that enables a watchdog timer.
    The image contains code that "switches off" some, or all of the multiplexed debug pins (JTAG/SWD).

---

See: http://support.code-red-tech.com/CodeRedWiki/DebugAccessChip?highlight=%28watchdog%29