Q For which LPC microcontrollers are LPCXpresso boards available?
A LPCXpresso boards are currently available for LPC13xx series and support for LPC11xx is planned. Users can always use the LPCXpresso platform with other target boards by using the LPC-Link standalone.
Q Is the LPCXpresso IDE limited in terms of code development?
A No. The LPCXpresso platform will allow the user to build an executable of any size, but there is a restriction in terms of code download which is 128KB.
Q I am working with the LPC1768 and my project download size is 256KB. Do I have to upgrade to a full version of Red Suite?
A Code Red is providing two low-cost upgrades of Red Suite for LPCXpresso to handle higher download sizes of 256KB and 512KB. Please visit the Code Red website for more information.
Q Is LPC-Link just like any other JTAG debug probe?
A Yes! LPC-Link is equipped with a 10-pin JTAG header, and it seamlessly connects to the target via USB. Cutting the traces between the LPC-Link and the target board will make the LPC-Link a stand-alone JTAG debug probe, enabling it to connect to any LPC evaluation boards.
Q Does the LPCXpresso IDE work with any other JTAG debug probes?
A Yes. In addition to the LPC-Link, the IDE also works with the Red Probe (from Code Red).
Q How do I get support for LPCXpresso?
A NXP has launched an exclusive forum for the LPCXpresso community. The NXP applications team will be moderating this forum and supporting users as they progress with LPCXpresso.
Q I am seeing unusual debugging issues when optimization is enabled. Is there a fix for this?
A When optimization is enabled, it will reorder code to improve performance. Changes like these might make the code confusing to debug. It is best to always use -O0 for debugging.
Q How can I display assembly instructions in the debugger?
A Click the i-> icon. This changes the Instruction Stepping Mode to step by processor instructions, rather than by source lines. This also shows the disassembly view around the current instruction.
Q How can I reduce my code size? I am using printf.
A When optimizing a project for size, if you are using printf, make sure that Redlib or Redlib (none) is selected as the standard library in the Projects Properties dialog. This option must be set in two different places, to configure both the header files, and the libraries. It should also be set both for the Debug target and the Release target. See the "Getting Started" guide for a step-by-step walkthrough of how to configure these settings.
Q Is optimization helpful to reduce code size?
A Optimization can do a lot to save flash memory. It can be configured in the same dialog as the C standard library. Choose "Optimization" under "MCU C Compiler" in the "Tool Settings" tab. Higher levels of optimization will typically result in higher performance, but may result in larger code size. It is best to use -O0 for debugging and higher levels for release. For best code, size try -Os -mword-relocations. There are many optimization options available for GCC. Visit http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html to see all of them.
Q I closed a view. How can I get it back?
A If you accidentally close a view, you can open it again by going to the Window menu and choosing Show View and Other. It is a good idea to browse through the Show View window to see what is available. See the "Tips & Tricks" section in the Getting Started Guide for more details on how to access this dialog.
Q How can I view peripheral bitfields and flags?
A LPCXpresso includes full, annotated, and interactive debug views of all the peripherals. Access to the views is found on the Peripherals View (click the Peripherals tab) behind the Core Registers view. Each peripheral can be selected, and it is displayed in the "Memory" view which is located behind the "Console" view at the bottom of the LPCXpresso desktop. See the "Getting Familiar..." section in the Getting Started Guide for more information on the peripheral view.