Red Suite / LPCXpresso FAQ

• Search support articles

  search this site only

• Top level of Code Red Support website

• Red Suite Documentation

Which Version of Red Suite / LPCXpresso do I have?

• Finding your version number

• Latest Version numbers for all Code Red products

• Upgrading to a newer major release in the Red Suite family

  • For example, Red Suite 3 to Red Suite 4, or Red Suite 4 to Red Suite 5

• Updating to a new minor release of a Red Suite family product

  • For example Red Suite 4.x. to Red Suite 4.y
  • Also covers LPCXpresso major version upgrading, for example LPCXpresso 3 to 4.

• Can I install multiple versions of the Code Red tools?

• New Functionality in Code Red IDE Version 4

  • STM32 Support (new in version 4.1.0)

  • Freescale Kinetis Support (new in version 4.3.0)

• New Functionality in Code Red IDE Version 5

• Migrating existing projects to a new version of the Code Red IDE

Tools Licensing

• How can I evaluate Red Suite?

• License Types and Restrictions

• How do the "Corporate" and "Standard" versions of Red Suite compare?

• Can I use Red Suite on more than one computer?

• License and Activation

• Moving licensing between computers (Reactivation)

• How to request an evaluation license

• My evaluation license doesn't work with...

• License Re-activation lockout

• Multi User Installation

• Error(18) when activating

• Where is my license (CDM file) stored?

• LPCXpresso License diagnostics

• How can I change the email address associated with an activation code?

• LPCXpresso IDE - activation email not received

• End User License Agreements:

  • Red Suite

  • LPCXpresso

General IDE usage and settings and installing plugins

• Using the IDE as a limited (non administrator) user on Windows

• Status bar shortcuts

• Increasing the memory available to Java

• Increasing the number of lines in the build console

• make fails with 'Virtual Alloc pointer is null' error

• Using/installing Version Control (SVN, SourceSafe) from within the Code Red tools

• Editor Hints and tips

• Linux GUI issues

Projects

• Migrating existing projects to Code Red IDE Version 4

• Examples supplied with the Code Red IDE

• How to use resources outside your Red Suite Project

• Import/Export: moving projects between workspaces or computers

• Copying Projects

• Using Environment Variable in project settings

• How include paths work

• Adding paths to StellarisWare libraries

• How do I switch between Debug and Release builds?

• Changing the current build configuration of multiple projects

• Project versus per-file properties

• Support for CMSIS (Cortex Microcontroller Software Interface Standard)

• Differences between CMSIS 1.30 and 2.00

• Updating projects from CMSIS 1.30 to CMSIS 2.0

• CMSIS 2.00 DSP Library

• Creating Library Projects (Code Red IDE v3)

• Using library projects from your own projects

• Target MCU selection for static library projects

• Enhanced Static Library Support in Code Red IDE v4

• Build Behavior when using Library Projects

• Porting code from other toolchains

• Changing the Project Target MCU

• Changing clock speed of NXP LPC1xxx MCUs

• How do I add semihosting to an existing project?

• LPC12xx Watchdog Support

• LPC12xx ROM Divide

• LPC11Uxx ROM Divide

• Code Read Protect (CRP)

• LPC18xx / LPC43xx Support

• Creating an LPC43xx Cortex-M4 / M0 Dual Core Application (v5.12 and earlier)

• Creating LPC43xx Cortex-M4 / M0 Multicore Applications (v5.22 and later)

Building

• Linking results in undefined reference to `xxx`

• Linker Error "cannot find -l<lib_name>"

• Linker CRP Enabled, but no CRP_WORD provided within application

• 'LPC_SYSCON_TypeDef' has no member named 'SYSTICKCLKDIV'

• How do I increase the Stack Size?

• Stack Problems

• How to reserve space in Flash

• Automated build from command line

• Build Macros

• "Invalid project path" warning messages

• Debug build too big to fit into flash

• Errors relating to cr_section_macros.h and NXP/crp.h

• Problems compiling "__attribute__((at"

• The Build Console

• Make error not cleared from Problem View

Compiler/Assembler/Linker

• Compiler Optimization

• Bit-Banding

• Porting ARM assembler code to Cortex-M3

• Creating a link map

• Using your own linker scripts

• Enhanced Managed Linker Scripts

• 'Noinit' Memory Sections

• Memory Configuration Editor and External Flash Driver mechanism

• Reserving RAM for IAP Flash Programming

• Placing data at an address

• Placing Code in RAM

• Packed Structures

• Where is the GCC documentation?

• Using C++ in embedded applications

• '~PRES8' errors or warning when linking objects with armlink

• Application Flash / RAM size

• Reducing Code Size when CRP enabled

• Cortex-M4 Floating Point Support

• Unused Section Elimination

• Interrupt Handlers in C++ applications

C Library

• What are Redlib and Newlib?

• What is semihosting?

• What are none, nohost and semihost libraries?

• Switching the selected C library

• Using printf in your applications (Semihosting)

• Retargeting printf/scanf to use a UART

• Notes on Redlib_v2

• Extending LMI's examples to use C library functions

• Newlib and math functions

• C Library Documentation

• itoa() and uitoa() in Redlib

Output file formats

• Creating srec, binary, ihex files

• Disassembling objects and executables

• Post-processing your linked application

Debug

* Debugger Configuration

• Viewing Variables during debug

• Debug Emulator Selection Dialog

• How do I stop build before debug?

• Peripherals

• How do I debug from Reset?

• Stack errors while debugging

• Debug a running system (without loading an application)

• Using the command line flash programming tool

• Using the GUI flash programming tool

• Debugging a hard fault

• Debugging and Compiler Optimization

• Changing the initial breakpoint on debug startup

• Debugger disconnect behavior

• Displaying assembly instructions when debugging

• Default display formats

• Semihosting support in the debugger

• Using command line GDB

• Accessing GDB command line from within debugger GUI

• Connecting to a JTAG target

• Multiple devices on a JTAG scan chain

• The Debug Log

• Debugging through a bootloader

• Memory Configuration Editor and External Flash Driver mechanism

• How many breakpoints can I set?

• LPC18xx / LPC43xx Support

• LPC18xx/43xx Internal Flash Support

• LPC18xx/43xx External Flash Support

• Launch Configuration Menu

• Debug issues caused by Unused Section Elimination

• User loadable flash drivers

• Debugging NXP LPC11xxLV parts

• Error while launching command: gdb --version

Debug target connections

• SWD/JTAG connectors and pinout

• Debug Emulator Selection Dialog

• Does Red Suite support the use of TI's ICDI debug probe?

• Connecting Red Probe+ to the MCU of an LPCXpresso board

• Debugging another board using an LPCXpresso board's LPC-Link

• Errors during debugging

• USB or driver problems

• Failed to connect: Not connected to emulator

• Windows does not recognise LPCXpresso board

• Debug connection problems with LPC2xxx

• 02: Failed on connect: Ep(01). Target marked as not debuggable

• 03: Failed on chip setup: Ec(01). Invalid, mismatched, or unknown part

• 15: Target error from Commit Flash write

• Flash driver not found after updating to v5.2.2 or later

• 16: Target error from status-poll: Ee(02). Not connected to emulator

• Getting debug access to target chip

• Diagnostics for connecting to LPC-Link

• LPCXpresso - License restriction: Flash image too large for this license

• Setting the crystal and PLL for a target board

• LPC8xx Flash programming fails after using MTB instruction trace

Running the product on a Virtual Machine

• LPC-Link may not be found when IDE run under Virtual Machine

• Problems with Red Probe/LPC-Link/RDB-Link under VMWare

Running the product on Linux

• Notes on running on Linux hosts

Running the product on Mac OS X

• LPC-Link may not initialize on Mac OS X

Red Trace

• Red Trace Overview

• Instruction Trace Overview

• YouTube Video : MTB Instruction Trace on the NXP LPC812 with Red Suite / LPCXpresso

• MTB Setup

• LPC8xx Flash programming fails after using MTB instruction trace

• SWV functions overlap addresses - will affect profiling

• Red Trace and EKT-LM3S811/EK-LM3S6965-RevA boards