• Design Considerations for Debug

    Debug related signals and considerations  JTAG was the traditional mechanism for debug connections for ARM7/9 parts, but with the Cortex-M family, ARM introduced the Serial Wire Debug (SWD) Interface. SWD is des...
    LPCware Support
    last modified by LPCware Support
  • LPC40xx SPIFI Flash Driver

    New In LPCXpresso IDE v8.20 is support for SPIFI flash programming on the LPC407x and LPC408x MCUs.   Introduction  The NXP LPC40xx series of MCUs support the connection of external SPIFI flash devices to e...
    peter.henry
    last modified by ebiz_ws_prod
  • LPC-Link2 fails to enumerate with CMSIS-DAP firmware

    Notes: This FAQ applies to both the standalone version of LPC-Link2, as well as the version built into LPCXpresso V2/V3 boards. For further background information see the FAQ: Booting LPC-Link2   Introduction&#...
    LPCware Support
    last modified by LPCware Support
  • How to use ITM Printf

    Updated: Now also compatible with the newlib nohost library.   ITM Overview  As part of its SWO Trace functionality, LPCXpresso IDE v8.0.0 introduced the ability to make use of the ITM : The Instrumentation...
    LPCware Support
    last modified by LPCware Support
  • Enabling ROM divide causes hard fault on LPC11U1x

    As described in the FAQ "ROM Divide", the LPCXpresso IDE provides support for making use of the ROM Divide routines contained in certain Cortex-M0 / M0+ MCUs, including the LPC11Uxx family of parts.   However it...
    LPCware Support
    last modified by LPCware Support
  • Using an LPC-Link2 as an LPC4370 evaluation board

    As well as being a standalone debug probe, the LPC-Link2 can also be used as a simple LPC4370 evaluation board. The following notes may assist in such usage.   Debug connection  Make sure that you have conn...
    LPCware Support
    last modified by LPCware Support
  • Configuring projects to span multiple flash devices

    Background Historically, LPCXpresso IDE could only associate a single flash driver with a particular project. This meant that if the target system had more than one type of flash (typically an LPC18xx / LPC43xx with i...
    LPCware Support
    last modified by LPCware Support
  • Which debug probes are supported by LPCXpresso IDE with which MCUs?

    Primary debug probes  The following debug probes are directly supported by LPCXpresso IDE for general debug connections:   LPC-Link2  The LPC-Link2 debug probe is available as a standalone debug probe...
    LPCware Support
    last modified by LPCware Support
  • CMSIS-DAP support in LPCXpresso

    CMSIS-DAP is an interface defined by ARM that provides a standardized way to access the Coresight Debug Access Port (DAP) of an ARM Cortex microcontroller via USB. For more information on CMSIS-DAP, please visit the A...
    LPCware Support
    last modified by LPCware Support
  • Where can I get training resources for LPCXpresso IDE?

    A 3 hour training session on the LPCXpresso IDE was held at FTF 2016, and the training materials from that course are available here: DES-N1973 Hands-On Workshop Master Development on the LPCXpresso Toolchain with Ou...
    Brendon Slade
    last modified by Brendon Slade
  • Regaining debug access to target MCU

    It is possible to download an image into the flash on the target that will then prevent any further debug access or connections. The classic cases of this are:   The image contains code that sets the MCU clocks ...
    LPCware Support
    last modified by LPCware Support
  • Debugger disconnect behavior

    When the debugger disconnects from the target, you control the behavior of the target processor using the process described below.   1. Select the project in the Project Explorer     2. Refer to the...
  • Booting LPC-Link2

    Overview  The recommended way to use LPC-Link2 with the LPCXpresso IDE is to boot and soft load a debug firmware image at the start of a debug session.   Normally, LPC-Link 2 is booted automatically, howev...
    LPCware Support
    last modified by LPCware Support
  • 02: Failed on connect: Ep(01). Target marked as not debuggable

    If the error "02: Failed on connect: Ep(01). Target marked as not debuggable" is seen when trying to start a debug connection, this normally means one of:   The cable between the debug probe (e.g. Red Probe+, LP...
    LPCware Support
    last modified by LPCware Support
  • "Connection Refused" error when starting a debug session on Linux

    On some Linux systems, when starting a debug session a "Connection refused" error may be displayed. This is because a critical system library is not installed where we expect to find it. The location of the library de...
    LPCware Support
    last modified by LPCware Support
  • 10: Could not start execution from stop

    Sometimes, when start a debug session - typically when a CMSIS-DAP probe, you may see an error message of the form: 10: Could not start execution from stop ACK Fault In this situation, try modifying the "Reset Handlin...
    LPCware Support
    last modified by LPCware Support
  • 15: Target error from Commit Flash write

    Errors of the form "15: Target error from Commit Flash write" are typically reported when the debugger is attempting to write to the flash, and the verify fails.   The most common cause for this error is insuffi...
    LPCware Support
    last modified by LPCware Support
  • 15: Target error from Register access: Ee(FF). Undocumented error.

    Occasionally when terminating a debug connection, you may see an error message of the form:   15: Target error from Register access: Ee(FF). Undocumented error.   The cause of this is under investigation fo...
    LPCware Support
    last modified by LPCware Support
  • 53: License does not permit flash operations from the command line

    If you try to directly use the GUI flash programmer, or the command line flash programmer, but have not activated your LPCXpresso license, then you will see an error such as:   53: License does not permit flash o...
    LPCware Support
    last modified by LPCware Support
  • 16: Target error from status-poll: Ee(02). Not connected to emulator

    During a debug session, whilst your target is executing , the debug tools will poll the target to determine whether it has halted on a breakpoint or event. A "16: Target error from status-poll: Ee(02). Not connected t...
    LPCware Support
    last modified by LPCware Support