Public:Building and Debugging Code - Revision history

Scottjg3: Scottjg3 moved page Building and Debugging Code to Public:Building and Debugging Code: Used in electrical onboarding

2026-09-11T18:26:14Z

Scottjg3 moved page Building and Debugging Code to Public:Building and Debugging Code: Used in electrical onboarding

Dslin2: added -lcommon potential fixes

2026-05-30T18:54:54Z

added -lcommon potential fixes

Alan Shi: /* Building */

2025-03-06T02:06:01Z

Building

Alan Shi: /* Building */ Add calypso and quotation marks to linker paths / names

2025-03-06T02:02:49Z

Building: Add calypso and quotation marks to linker paths / names

Alan Shi: /* Creating a new MCUXpresso Project */

2025-03-06T01:35:41Z

Creating a new MCUXpresso Project

Gvi2: Gvi2 moved page Public:Building and Debugging Code to Building and Debugging Code over a redirect without leaving a redirect: Return back to private namespace.

2024-04-28T19:53:02Z

Gvi2 moved page Public:Building and Debugging Code to Building and Debugging Code over a redirect without leaving a redirect: Return back to private namespace.

Gvi2: WIP Changed the setup for MCUXpresso 11.9.1

2024-04-28T19:52:07Z

WIP Changed the setup for MCUXpresso 11.9.1

Gvi2: /* Flashing/Debugging */

2024-04-28T19:50:46Z

Flashing/Debugging

Gvi2: /* Notes and Common Problems */

2024-04-28T02:52:25Z

Notes and Common Problems

Adityaj5: Adityaj5 moved page Building and Debugging Code to Public:Building and Debugging Code

2021-09-11T04:31:04Z

Adityaj5 moved page Building and Debugging Code to Public:Building and Debugging Code

@@ Line 110: / Line 110: @@
 *** Connect debugger
 *** Flash code
-* Are you getting an error saying '''cannot find -lcommon''' or similar? Make sure that the active build configuration for common and mbed for the same microcontroller as your project and that they have the correct dialect selected.
+* Are you getting an error saying '''cannot find -lcommon''' or similar? Make sure that the active build configuration for common and mbed for the same microcontroller as your project and that they have the correct dialect selected. You could also try removing mbed and common from the MCUExpresso workspace then copying the .cproject and .project files from another working branch into both common and mbed, then finally running the shell script and re-importing mbed and common into the workspace.
 * Does it say '''cannot find -lcommon -lmbed''' close MCUExpresso, and delete .cproject and .project files in common and mbed then redo the setup process for these files.
 * Does it say '''cannot find -lzephyr-common''' remove zephyr common from Properties >  MCU Assembler > General

@@ Line 41: / Line 41: @@
 #Make sure that you have:
 ##Script name: chipname.ld such as: <code><small>"LPC1549.ld"</small></code> (Argo-FW) or <code><small>"LPC15x9.ld"</small></code> (B-FW or Calypso)
-##Argo, Brizo, or Calypso FW Script path: <code><small>"..\..\mbed\libraries\mbed\targets\cmsis\TARGET_NXP\TARGET_LPC15XX\TOOLCHAIN_GCC_CR"</small></code>
+##Script path: <code><small>"..\..\mbed\libraries\mbed\targets\cmsis\TARGET_NXP\TARGET_LPC15XX\TOOLCHAIN_GCC_CR"</small></code> (all cars)
 ##(If you can't change these uncheck &quot;Manage Linker Script&quot;)
 [[File:CheckScriptNameAndScriptPath.png]]

@@ Line 40: / Line 40: @@
 #In the &quot;Tool Settings&quot; tab go to ''MCU C++ Linker'' > ''Managed Linker Script''
 #Make sure that you have:
-##Script name: chipname.ld such as: <code><small>LPC1549.ld</small></code> (Argo-FW) or <code><small>"LPC15x9.ld"</small></code> (B-FW)
+##Script name: chipname.ld such as: <code><small>"LPC1549.ld"</small></code> (Argo-FW) or <code><small>"LPC15x9.ld"</small></code> (B-FW or Calypso)
-##Argo FW Script path: <code><small>..\..\mbed\libraries\mbed\targets\cmsis\TARGET_NXP\TARGET_LPC15XX\TOOLCHAIN_GCC_CR</small></code>
+##Argo, Brizo, or Calypso FW Script path: <code><small>"..\..\mbed\libraries\mbed\targets\cmsis\TARGET_NXP\TARGET_LPC15XX\TOOLCHAIN_GCC_CR"</small></code>
 ##(If you can't change these uncheck &quot;Manage Linker Script&quot;)
 [[File:CheckScriptNameAndScriptPath.png]]

@@ Line 10: / Line 10: @@
 Generally there is one project per board. To do so:
 # You should use the appropriate skeleton project for your chip as a starting point.
-## For ISC made boards that should be the <code><small>mbed1549_skeleton</small></code> (Argo) or <code><small>mbed15x9_skeleton</small></code> (Brizo)
+## For ISC made boards that should be the <code><small>mbed1549_skeleton</small></code> (Argo) or <code><small>mbed15x9_skeleton</small></code> (Brizo or Calypso)
 ## For older boards from CalSol you may need the <code><small>mbed11c14_skeleton</small></code>
 # In the project explorer right click on the appropriate skeleton and select &quot;Copy&quot;

@@ Line 81: / Line 81: @@
 ## Leave Project Name as default
 ## Under &quot;C/C++ Application&quot;, click ''Browse...'' and navigate to the project's folder inside the repository. The file will be located in that folder (in the repo) at <code>LPC15xx\projectname.axf</code>
-##*[[File:FindTheDotaxfFile.png|alt=]]
+##*[[File:MCUXPresso 11.9.1 Debugger Configurations.png|alt=|549x549px]]
 ##*
 ##*

@@ Line 99: / Line 99: @@
 [[File:CommonProblems.png]]
-<nowiki>*</nowiki> '''Shadows template parm 'int N'''' and ''some'' other build errors that complain about types. You probably didn't set the compiler language correctly. Double check step 5 in Building.
+<nowiki>*</nowiki> '''Shadows template parm 'int N'''' and ''some'' other build errors that complain about types. You probably didn't set the compiler language correctly. Double check step 4 in Building.
 * '''Did you get your code to upload, but now it's not letting you upload code?''' Make sure that you've ended any previous debugging sessions before trying to upload code again (you can either right click on an instance and terminate it or terminate all from the top menu in MCUXpresso). Sometimes, if you unplug debuggers with active debug sessions MCUXpresso may get very confused and not allow you to end active debug sessions. You will need to restart MCUXpresso (or sometimes your whole computer) to fix that.
 ** Was the device working previosly but it's not working any more? If you flashed bad code and now are getting error "'''Target error from Commit Flash write: Ep(08). Cannot access core regs when target running."''' you can try using the ISP pins to force boot mode. This procedure is not very reliable but if you try it enough times it'll work. First you will probalby have to solder wires to ISP0 and ISP1 generally the easiest way to do this in my experience is to solder wires to the resistors that pull up ISP1 and ISP0 on the sides that connect to the mcu. Here r the steps: