• How include paths work

    When you add a directory under the "Directories" section of the compiler, you are setting the compilers "-I" option.   "-I" adds a directory to the compiler search path for include files. When the compiler tries...
    LPCware Support
    last modified by LPCware Support
  • How do I switch between Debug and Release builds?

    You can switch between Debug and Release build configurations by selecting the project you want to change the build configuration of in the Project Explorer view, then using one of the below methods:   Select t...
    LPCware Support
    last modified by LPCware Support
  • LPC12 Watchdog

    Unlike most MCU's, NXP's LPC12xx family start up with the "Windowed Watchdog Timer" (WWDT) enabled.   This configuration is not "debug friendly" (as the watchdog is likely to timeout whilst debug operations take...
    LPCware Support
    last modified by LPCware Support
  • Migrating existing projects to a new version of LPCXpresso IDE

    This FAQ provides a number of hints and suggestions for things that you should do or consider when migrating to a new version of the LPCXpresso IDE. These are primarily focussed at moving between major releases (for e...
    LPCware Support
    last modified by LPCware Support
  • Migrating to a new version of LPCXpresso IDE

    Introduction Generally, migrating from one version of the LPCXpresso IDE to a later version should be straightforward, though you should always browse the release notes, the supplied documentation and online FAQ mater...
    LPCware Support
    last modified by LPCware Support
  • 'Noinit' Memory Sections

    Normally global variables in an application will end up in either a ".data" (initialized) or ".bss" (zero-initialized) data section within your linked application. Then when your application starts executing, the star...
    LPCware Support
    last modified by LPCware Support
  • LPC541xx Cortex-M4 / M0+ Multicore Applications

    Introduction  The LPC541xx series of MCUs contain a main or 'Master' Cortex M4 core, plus an optional 'Slave' Cortex M0+ core. At the time of writing the parts are:   MCUs with Cortex M4 only LPC54101J256 ...
    LPCware Support
    last modified by LPCware Support
  • Porting Code from other toolchains

    Generally where example code is provided for another toolchain it will normally port across to the LPCXpresso IDE fairly easily. Simply create a new project within the LPCXpresso IDE, then copy the required source fil...
    LPCware Support
    last modified by LPCware Support
  • Project vs per-file properties

    In most cases, the properties for the files being built as part of a project are controlled at the project level (with one set of properties being maintained per Build Configuration - Debug and Release).   Thus ...
    LPCware Support
    last modified by LPCware Support
  • Red Probe+ support

    What is Red Probe+?  Red Probe+ is a debug probe designed and sold by Code Red Technologies before their acquisition by NXP.  It was designed explicitly for use with Code Red's "Red Suite" IDE, as well as t...
    LPCware Support
    last modified by LPCware Support
  • Reserving RAM for IAP Flash Programming

    The IAP flash programming routines available in NXP's MCUs make use of some of the onchip RAM when executed. For example on the LPC1343 the top 32 bytes of onchip RAM are used. Thus if you are calling the IAP routines...
    LPCware Support
    last modified by LPCware Support
  • Reserving RAM for ROM drivers

    Some NXP MCUs have peripherals drivers built into the ROM - for example, the CAN driver for certain LPC11 parts, and the USB driver for certain LPC13 parts. On some MCUs these drivers need some internal memory that is...
    LPCware Support
    last modified by LPCware Support
  • ROM Divide

    Background  Unlike the Cortex-M3 and M4, the Cortex-M0 does not provide support for divides in hardware. This means that when application code carries out a divide operation, the compiler will insert a call to a...
    LPCware Support
    last modified by LPCware Support
  • Status bar shortcuts

    The 'Status Bar', at the bottom of the LPCXpresso IDE, has a useful set of hot links looking something like the image below:     Hover over the project name to reveal the full system path to your project o...
    LPCware Support
    last modified by LPCware Support
  • Switching the selected C library

    Overview  The LPCXpresso IDE is provided with two different C libraries - Redlib and Newlib, each of which is supplied in a number of library variants. LPCXpresso v7 also introduced a further library, Newlib-Nan...
    LPCware Support
    last modified by LPCware Support
  • Overview of Trace support in LPCXpresso IDE

    This FAQ provides an overview of the various forms of trace available within the LPCXpresso IDE: SWO Trace Instruction Trace For more details, please see the LPCXpresso User Guide installed within the product. ...
    LPCware Support
    last modified by LPCware Support
  • Symbol Viewer

    LPCXpresso 7.6.0 introduced a Symbol Viewer feature to provide a simple way of displaying the symbols in an object/library/executable. By default, this is located in the top left of the LPCXpresso window, in parallel ...
    LPCware Support
    last modified by LPCware Support
  • Target MCU selection for Static Library projects

    When creating a static library project, it is necessary to select a specific target MCU (for example LPC1768 or LPC1114/301).   However this selection primarily controls the compiler/assembler options (for examp...
    LPCware Support
    last modified by LPCware Support
  • LPC43xx Cortex-M4 / M0 Multicore Applications

    Basic principles  The LPC43xx family of MCUs contain a Cortex-M4 ‘Master’ core and one (or more) Cortex-M0 ‘Slave’ core. After a power-on or Reset, the Master core boots and is then respo...
    LPCware Support
    last modified by LPCware Support
  • Using the IDE as a Limited User in Windows

    The LPCXpresso IDEs work best when run from a user account with Administrator privileges. By default, the IDE cannot be run by Limited (non-privileged) users because some information is written into files and folders ...
    LPCware Support
    last modified by LPCware Support