OM13085 LPCXpresso CMSIS-DAP (peripheral) reset problems.

[daantimmer]

I am working on a project that previously worked with the OM13000 LPCXpresso board.

I have to get the code working and am failing at that.

One of the problems I am facing is with the peripherals of the LPC1769. When I am debugging and I issue a restart from LPCXpresso the peripherals do not reset and stay in the state prior to restarting.

This results in strange I2C and UART behaviour regarding interrupts.

I am already debugging using Vector-catch on, with reset handling set to VECTRESET. But I already read that VECTRESET only does a core reset and not a system reset. And a core reset is not enough to reset the peripherals.

When I set reset handling to SYSRESETREQ the debugger stops working after flashing the device. The reported error is as follows: "16: Target error from status-poll: Ee(FF). Redlink interface error 255."

I am at a loss on how to continue.

[nicolamasarone]

Hi Daan,

just to add that I found a similar problem with OM13085.

With previous OM13000 I used to test expansion connectors (manually soldered) with a very simple procedure: I launched any project (like periph_blinky) via the debugger and then, when it stopped itself at the first instruction (before any I/O setting), the LPC1769 was in its reset state, with all pins at default values (as in the User Manual). Most pins were in GPIO-INPUT mode with PULLUP enabled and I used this condition to apply an external LED-resistor circuit to check every position in 27x2 expansion connector. When position was with a GPIO-INPUT with PULLUP LED light was very weak, while on other few positions it was strong (3.3V or I2C external board-pull-up) or completely dark (not connected).

Now, with OM13085, this behavior has changed. With exactly the same procedure I find some pins out of reset state and I can obtain the previous result only using the new reset button present on OM13085.

Hope this can help.

Regards

Nicola Masarone

[lpcxpresso_supp]

There are some restrictions upon what can actually be done via the Restart button within the IDE. And things also can be different between probe types too, as you have seen.

Things to try ...

- Use the "Terminate, Build and Debug" option on the Quickstart panel instead of Restart

- Update the startup code within your application so that you carry out the required initialisation yourself.

- Switch to an external probe like an LPC-Link2

Regards,

LPCXpresso Support

[jeremyzhou]

Hi Daan Timmer,

Thank you for your interest in NXP Semiconductor products and the opportunity to serve.

I was wondering if you can tell some particular procedure steps to replicate the unexpected restart issue, for instance what demo and debug tool use,etc.

I'm looking forward to your reply.
Have a great day,
Ping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------