Hi Alex, and everyone else,

Working with a LPC1114 I encountered the same problem. After having programmed the uC several times, it suddenly started failing to communicate through SWD.

I know the uC works because it still responds to commands sent through UART, leds blink, etc. And I know ULINK2 works because I tried it with other boards.

Did you find a solution to this problem?

I've tried Keils help

http://www.keil.com/support/man/docs/ulink2/ulink2_errors.htm

with no effect at any speed, reset configuration or whatever options I could click on. I also found this other solution, but this didn't work either.

http://zone.ni.com/reference/en-XX/help/372459A-01/lvarmhelp/arm_troubleshoot_build/

If anyone has any idea of what the cause of the problem is, I'd appreciate the help.

Thank you, Nicolas.

Hi:
>
>We are using LPC1752 with Keil uVision 3.70 with ULINK2 debugger
>
>We received our prototype board and started programming/debugging the application on it.
>Serial Port 0 is used for main application monitoring, and one pin of a RF module is connected to the P2.10 pin.
>
>After some programming/debugging cycles, the LPC1752 now says "SWD Communication Failure" and cannot reprogram or debug application.
>Just prior or at the same time the failure occur, it was noticed that the processor had entered the internal bootloader (as bootloader commands were seen in the serial port 0 terminal).
>
>ISP works and Flash Magic (V5.51.1862) is able to communicate with the internal bootloader, read the Chip ID, erase and program a new application. It reads the CRP and it is disabled. Erasing and reprogramming the chip doesn't seem to correct the operation of the SWD debug port.
>
>Tested the ULINK2 debugger with another prototype board and with a MCB1768 Evaluation board, and both work correctly (SWD Communication is OK), so the ULINK2 debugger is working.
>
>The questions are:
>
>1. Have this problem been observed before by anybody?
>
>2. Is there a workaround?
>
>3. Are the SWD pins electrically more sensitive to damage?
>
>4. Is it possible to disable somehow the SWD port when running the bootloader?
>
>5. Is there a way to prevent this to happen again, so that no more MCU are damaged?
>
>Regards,
>
>Alex
>
>
Start a New Thread