Skip navigation
1 2 Previous Next

MCUXpresso IDE

27 posts



As part of the MCUXpresso IDE v11.0.1 release, we had to make some major changes to our LinkServer debugging mechanism to support the latest silicon revision of the LPC55xx family of devices (revision 1B) and the more secure debug request mechanism required by these parts. Such silicon is supplied on LPC55S69-EVK boards marked Revision A2 (or later) on the board silkscreen.


It has been found since the MCUXpresso IDE v11.0.1 release that these changes to LinkServer can, in certain circumstances, provoke problems when starting debug sessions to the earlier revision 0A production silicon. Such silicon is supplied on LPC55S69-EVK boards marked Revision A1 on the board silkscreen. Boards received before November 2019 are very likely to be this revision. Such issues will often manifest as various error popups being displayed by the IDE and the LinkServer flash driver failing to run to completion during the debug startup sequence, meaning that the debug session fails.


This will be resolved in the next MCUXpresso IDE release, but in the meantime the issue can be avoided using the supplied updated LinkServer debug configuration script.


NOTE 1: This updated script is only needed if debugging revision 0A silicon, but should not cause issues if used with revision 1B. It is also only needed if debugging using a LinkServer debug connection (typically CMSIS-DAP).


NOTE 2: Boards marked as LPC55S69-EVK Revision 1, 2 or A are fitted with pre-production silicon and not supported by the latest tools (including those from 3rd party partners) and should no longer be used. Note that if you purchased your board from NXP or one of our distributors it will not be Revision 1, 2 or A. Contact your NXP representative to arrange for a replacement unit if using one of these boards.


Installation Instructions


To install this updated script file:


  • Unzip the attached ZIP file to a temporary location.


  • Ensure that MCUXpresso IDE v11.0.1 is not running.


  • If you are running on Windows and you have MCUXpresso IDE v11.0.1 installed into the standard installation directory (C:\nxp\MCUXpressoIDE_11.0.1_2563), then you install the patch into your IDE installation by simply running the supplied "install.bat" batch file by either:
    • Double clicking on the batch file in Windows Explorer, or
    • Running the batch file from a Command Prompt Window opened onto the directory containing the unzipped patch files.


  • If you are running on Mac OS / Ubuntu, or on Windows with a non-standard IDE installation location:
    • Navigate to the following subdirectory within your IDE v11.0.1 installation folder


  • Rename the existing file "LS_preconnect_LPC55xx.scp" to "LS_preconnect_LPC55xx.scp.bak".
  • Now copy the supplied new version of the "LS_preconnect_LPC55xx.scp" file into the ToolScripts folder.


Now restart the IDE, and click on the "Clean up Debug" button on the main toolbar, to ensure that no debug process have been left running from any previous failed debug attempts.


You should now be able to debug successfully. If further problems are seen, please delete any .launch files within your project, along with the build directories (typically "Debug" and/or "Release") before trying again.



An issue has been identified that impacts the debugging of older LPC devices using SEGGER Jlink via the version of MCUXpresso IDE v11.0.1 released on 4th September 2019.


This issue will be seen only when debugging an LPC device that use the IDE's Preinstalled part support i.e. parts that do not require an SDK - a debug operation via SEGGER Jlink will lead to an error as below:



In this instance, the reported error does not accurately identify the cause of this problem.


Note: This problem does not impact version 11.0.0 of MCUXpresso IDE. Also, this update is of no benefit for version 11.0.1 users of MCUXpresso IDE unless they are debugging LPC parts via SEGGER JLink and experience the above error.




The IDE team have made a fix for this issue which is now available via the standard Eclipse update mechanism. However, this fix is not suitable (or required) for the previous version of MCUXpresso IDE (version 11.0.0). Therefore a dedicated Update Site has been created for MCUXpresso IDE v11.0.1 users to deliver this 'hotfix'.


To access this new update site, a small edit should be made to the MCUXpresso IDE Update Site path held within the IDE's preferences. To locate the Preferences dialogue from the IDE:


On Windows and Linux: Window -> Preferences

On Mac: MCUXpresso IDE -> Preferences


The change can then be made as follows:


  • Enter 'update' into the filter field and locate 'Available Software Sites'
  • Select the MCUXpresso IDE Update Site line and click Edit
  • Add the text '_1' to the version making the complete version 'v11_0_1/'
  • Click 'Apply and Close'
    • the graphic below shows the updated dialogue



Note: this hotfix will be located more quickly if only the MCUXpresso IDE Update site is ticked in the Available Software Sites (above)


To locate and apply this update from within the IDE, select: Help -> Check for Updates (as below)



This will launch a dialogue as below and all selected update locations will be checked for new features:



After a short while, the hotfix update will be found (as below):



Click Next and you will be presented with a License dialogue (as below):



To progress, you must click to accept the license agreement and click Finish. Finally, you will see an installation warning as below:



This update is a .jar and currently individual .jar files are not signed, hence you can click 'Install anyway' and accept the option to Restart the IDE.



Once the IDE has restarted, you can view that this hotfix update has been performed. From the IDE select Help -> About -> Installation Details and see the dialogue as below:



You should now see the Third-party debug solution support plugin is version 11.0.2... and the hotfix has been applied successfully.

We are pleased to announce that MCUXpresso IDE v11.0.1 (build 2563) is now available.


This is a maintenance release that builds upon the previous MCUXpresso IDE v11.0.0 release, and we recommend that all existing users download and install this new version. It also incorporates a minor update to the integrated MCUXpresso Config Tools.


To download the installers for all platforms, please login to our download site via:


IMPORTANT NOTE 1 : An issue has been identified with MCUXpresso IDE v11.0.1 that impacts the debugging of older LPC devices using SEGGER J-Link. This issue will be seen only when debugging an LPC device that uses the IDE's preinstalled part support i.e. parts that do not require an SDK. For more details, along with a hotfix patch to resolve this issue, please see:


IMPORTANT NOTE 2 : An issue has been identified with MCUXpresso IDE v11.0.1 that impacts the debugging of LPC55S6x Revision 0A silicon devices (as found on LPCXpresso55S69 Revision A1 boards) in some circumstances via LinkServer debug connections (typically CMSIS-DAP). For more details, along with a hotfix patch, please see:


Summary of Changes - version 11.0.1 - September 2019

  • Updates to allow LinkServer debug connections (ie CMSIS-DAP) to LPC55S6x "rev 1B" silicon and other devices that implement "debug mailbox request" mechanism. Note that these changes mean that some pre-production LPC55S6x silicon can no longer be supported
  • Updates to support new devices, including K32L3A and i.MX RT1010 families
  • Link to now provided in New Project and Import SDK example(s) wizards, improving accessibility for downloading additional SDKs
  • Updates to map file awareness, including improvements to loading speed
  • Fixed various issues with Image Info view
  • Fixed issue with floating point options being incorrectly set for SDK example projects with C++ nature in some circumstances
  • Extended "include paths" indexer fix implemented in IDE v11.0.0 to also work with library projects
  • Fixed issue with SDK multicore examples importing with managed linker script settings not being configured correctly in some circumstances
  • Fixed memory leak in Installed SDKs view when regeneration of part support info triggered
  • Managed linker script mechanism now generates references to "CodeQuickAccess"", "DataQuickAccess" and "RamFunction" input sections (required by some SDK examples/ drivers) in default .data output section
  • Fixed issue with Debug Shortcuts in QuickStart Panel incorrectly selecting attach/debug option in some circumstances
  • Fixed various minor issues with GUI Flash Tool
  • Fixed issue with Global Variables view slowing down debug launches with C++ projects
  • Fixed addresses > 0x80000000 issue with Heap and Stack Usage view
  • Fixed issue with Global Variables view graphs updating when target suspended
  • Fixed issue with Peripherals View with LPC17xx devices, particularly effecting display of certain enumerations
  • Fixed issue with Peripherals View refresh. This could cause some registers to sometimes be erroneously displayed as unavailable
  • Fixed issue with LinkServer launch configuration wirespeed setting being ignored in some circumstances
  • Updated the way the IDE autodetects installed SEGGER software. This is required due to changes SEGGER have made to the default options of their Windows installer in v6.46 and later of their software
  • Fixed issue with P&E and SEGGER implementations of live variables service (required to support live update of globals in Global Variables view). This issue could provoke problems in some circumstances when debugging via these probes including slow debug performance and failure to display locals inside the Variables view
  • Fixed issue with display of large arrays when using P&E or SEGGER debug connections
  • Fixed issue which could trigger error when manually creating a J-Link launch configuration
  • Upgraded to a later version of the P&E Micro plugin (v4.2.5)
  • Upgraded to a later version of the SEGGER J-Link software (v6.46k)
  • Fixed build issue with MCUXpresso IDE v11.0.0 User Guide which caused last chapter ("Appendix – Additional Hints and Tips") to be merged into the previous chapter ("Multicore Projects") as section 19.6 onwards. Actual content of manuals provided with IDE v11.0.1 otherwise unchanged from v11.0.0 manuals

The Windows installer for SEGGER J-Link has changed behaviour for version after V6.44 i.e. after the version installed with V11.0.0 of the IDE. Previously each SEGGER installation was located in a versioned directory e.g. JLink_V644g, now each new installation will by default, write to C:\Program Files (x86)\SEGGER\JLink.


This change will only impact Windows users who manually install a later version of SEGGER J-Link for use within MCUXpresso IDE.


For reference, please also see the MCUXpresso IDE User Guide v11.0.0 section 5.8.1 'SEGGER software installation' which details the handling of SEGGER installations within the IDE.


There are two scenarios where problems may be seen and these are discussed below:


A user installs and wishes to use a newer version of SEGGER J-Link with MCUXpresso IDE


Previously, when a new workspace was created, the newest SEGGER installation would automatically be selected for use. Alternatively, Windows -> Preferences -> MCUXpresso IDE -> J-Link Options -> Restore Defaults could be used to automatically search for the latest installation and update the path to the required server.


Now to use the new install the user must manually browse to the new server location via the preference at:  Windows -> Preferences -> MCUXpresso IDE -> J-Link Option and select:

C:\Program Files (x86)\SEGGER\JLink\JLinkGDBServerCL.exe


This must be done for any existing workspace or when a new workspace is chosen, otherwise the most recent install using the old scheme will be selected for use.


All existing SEGGER J-Link installations have been uninstalled and a new installation has been performed


Previously, the IDE would have recognised that its SEGGER path information was incorrect and automatically searched for a latest install. However, this mechanism will not find an installation using the new default location. Therefore the user must manually browse to select the Server as described above.


Note: this issue will be addressed in the next update to MCUXpresso IDE later this year.

We are pleased to announce that MCUXpresso IDE v11.0.0 (build 2516) is now available.


This is a major new version of the IDE, and contains many new features and enhancements over the previous MCUXpresso IDE v10.3.1 and earlier releases. The attached presentation, recommended viewing for all users (new or experienced), provides an overview of many of the major changes, as well as things to be aware of when upgrading from an earlier release:


To download the installers for all platforms, please login to our download site via: 


Additional information can be found in the updated User Guide and other documentation, which can be accessed from the built in help system available via IDE's Help menu and in PDF form from within the installation directory or downloaded from:


Summary of Changes - version 11.0.0 - June 2019

  • Upgraded underlying Eclipse Framework to 4.10.0v201812 / CDT 9.6.0

  • Upgraded supplied GNU ARM Embedded Toolchain to GCC8 (2018q4-major)

  • Windows version of product now only runs on Win64 (IDE v10.3.1 and earlier ran on Win32 & Win64 platforms). Note that this change has been driven by the fact that Eclipse framework is now 64-bit only. [ Ubuntu and MacOS versions of product already only ran on 64-bit platforms.]

  • Updated version of "busybox", used on Windows to provide a Unix-like layer for GCC tools to run under, to "GNU MCU Eclipse Windows Build Tools" v2.12 (64bit)

  • Added support for MCUXpresso SDK v2.6

  • Upgraded integrated version of MCUXpresso Config Tools to v6

  • Revamped Develop Perspective with some new and additional views shown by default. Also decluttered by removal of some less commonly used views. Most of the removed views can be added back via the new 'Analysis' menu

  • New "Image Info" View improves and extends on the functionality previously provided by the “Symbols Browser” view, giving the following analysis of a project build:

    • Overall memory usage
    • Content of memory regions

    • Static call graph, including stack usage information

  • New "Heap and Stack Usage" view provides ability to track heap and stack usage during debug of baremetal projects

  • Implemented "editor awareness" for linker map files, linker scripts and linker script templates, providing syntax coloring as well as navigation of file contents via the Outline view

  • Improved display of components in New Project Wizard and Managed Components dialog. Display of different component types is now tabbed, with an additional summary of the components selected

  • The New Project Wizard will now open the main source file in the Editor view after project creation

  • When importing a single SDK example, the wizard will now attempt to open the main source file in the Editor view after project creation. This functionality can also be enabled when importing multiple examples through a workspace preference

  • Improved support for Cortex-M33 Secure / Non-Secure projects. Improvements include :

    • Secure and Non-Secure projects more closely linked from build / project configuration point of view
    • Debugging Secure project will automatically build Non-Secure project and program it into flash, before launching Secure project debug session
    • Symbols for Non-Secure project automatically loaded into debug session to allow user to step from Secure world into Non-Secure (with source code visibility)

Note that these improvements also require SDK v2.6 for the MCU being targeted

  • Improved Launch Configurations for LinkServer. Main user impact is that this allows a more friendly way of editing launch configuration settings. Some launch configuration functionality now also provided in “standard” Eclipse/CDT tabs rather than in LinkServer specific manner. LinkServer Launch configurations from older IDE versions will be automatically converted to the new format
  • New launch configuration tab (for all debug probe types) to allow loading of debug symbols from additional images (in addition to the ones from the main image being debugged)

  • Improvements to performance of single stepping for LinkServer debug connections

  • Implemented support for SWO Trace on Cortex-M33 based MCUs

  • "Live Variables" functionality inside the Global Variables view now supported using SEGGER J-Link and P&E Micro debug probes (in addition to LinkServer debug connections)

  • FreeRTOS TAD functionality now directly implemented within the IDE, rather than being a separate plugin

    • Improved look and feel to better match rest of IDE
    • Timeout period for FreeRTOS TAD increased, to help prevent reading of data failing on slow debug connections. IDE preference also added to allow timeout period to be changed
    • Fixed issue with Runtime not showing when compiler optimizations turned on
    • Fixed issue with Timer List with FreeRTOS 10.2 release
  • Fixed issue with IDE losing C library include paths. This did not prevent projects from building but meant that indexer-related functionality reliant on these paths would not work correctly (for instance trying to open a C library include file from the editor). This issue could also cause Newlib projects to sometimes appear to be using Redlib include files.

Note: Existing projects can be "fixed" using Tools->Fixup Parsers option on the Project Properties view's context sensitive menu

  • New projects now compile with the --fstack-usage option by default (needed for callgraph functionality in the "Image Info" view)

  • Quickstart Panel - Quick Settings menu can now indicate current value for Debug Console, Floating Point and Library settings for current build configuration of selected project

  • New projects now link with --cref option by default (increasing level of information provided in linker map files)

  • Improved performance of installing/loading SDKs, largely by re-architecting the way that SVD peripheral definition files from the SDK are processed

  • Installed SDKs view updated so that detailed information on contents of selected SDK is hidden by default, but with new Hide/Show button to display when required

  • SDK default folder mechanism updated to install SDKs into an "02" subdirectory by default. This means that SDKs installed by IDE v11.0.0 will not be visible to older versions of the IDE

  • Improved ability to select debug console type (semihosting vs UART vs any preference specified by example definition) when importing SDK examples. This is particularly useful when multiple projects are selected for importing at the same time

  • Tweaked code generated for main() by New Project Wizard for SDK projects such that the infinite loop at the end of the function can be successfully single stepped at the source level

  • Fixed issue with default compiler options set by SDK New Project wizard when creating C++ projects. Such projects now also created with "cpp_config.cpp" file containing minimal implementations of the new/delete operators and the verbose terminate handler for exceptions suitable for embedded use. This brings SDK C++ projects inline with C++ projects created with the New Project Wizard for preinstalled parts

  • Some performance improvements when making a board selection in New Project Wizard and Import SDK example(s) wizard

  • Fixed issue with IDE incorrectly warning about overlapping memory regions when importing some SDK examples, when the memory regions are actually just adjacent

  • Fixed issue with IDE being unable to show the context sensitive menu in the Project Properties view for makefile projects in some circumstances

  • Fixed issue with handling of part support information for MCUs which are supported by internal part support, but for which an SDK exists and has been installed into the IDE

  • Various updates and clean up of icons. In particular, new icon for "LinkServer" now used in various places instead of general MCUXpresso IDE one

  • Fixed issue with various tables displayed by IDE failing to display "..." to indicate truncation, when amount of text to
    display exceeds space currently available in column

  • Various fixes to SDK Editor / Creator

  • Fixed issue with managed linker script mechanism when building master projects linking in slave projects containing data with larger than normal alignment

  • Fixed issue with managed linker script mechanism which was causing some sections (such as .bss) to be erroneously assigned unnecessary load addresses

  • Fixed issue with section name wildcards used in managed linker script mechanism , which could prevent __BSS/__DATA macros from working as expected in some circumstances

  • On Managed Linker Script page of Project Properties, IDE now autoconverts any "\" directory separators entered into "Script path" to Unix style "/" expected by the linker

  • Added implementations of inverse hypobolic functions to Redlib (acosh/acoshf, asinh/asinhf and atanh/atanhf)

  • Improved Redlib definition of HUGE_VAL (and other related defines) in math.h. Also updated way float_t defined

  • arm_acle.h header file now on the search path for projects linking against Redlib (providing various ARM C language extension intrinsics). Previously this was only available for Newlib linked projects

  • IDE now prioritizes use of IDE supplied LinkServer flash drivers over any contained in installed SDKs (rather than the other way around). This behaviour can be reverted if necessary using an IDE workspace preference

  • Fixed various issues with creation of multiple launch configurations for a particular build configuration in a project

  • Fixed issue with creation of launch configurations if previous attempt was cancelled

  • "Attach-only" debug sessions no longer trigger a build before starting the debug connection (as long as image has already built)

  • Improved size and layout of Launch Configuration Selection Dialog (displayed when project contains launch configurations for multiple probe types)

  • Fixed issue with display of cycle counters in Registers View

  • Fixed issue with GUI Flash Tool via LinkServer with LPC51U68 and KL28 MCUs

  • Fixed issue with debug restart with QN9080 via LinkServer

  • Fixed issue with LinkServer FreeRTOS thread awareness with Cortex-M33 based MCUs (and CM33 aware versions of FreeRTOS)

  • Implemented preliminary support for carrying out SWO Trace using CMSIS-DAP probes that implement "CMSIS-SWO commands" (as opposed to the bespoke SWO support implemented by NXP's LPC-Link2 CMSIS-DAP firmware). This has currently only received limited tested using ULINKplus probes with CMSIS-DAP v1.x.x firmware.
    Note : MCUXpresso IDE does not support the use of WinUSB endpoints as provided by CMSIS-DAP v2.x.x firmware

  • New IDE workspace preference to allow debug launch configurations for SEGGER J-Link probes to be created with FreeRTOS thread awareness already enabled (off by default)

  • Upgraded to a later version of the P&E Micro plugin (v4.1.3)

  • Upgraded to a later version of the SEGGER software (v6.44i)

This article discusses the use of SDK Trustzone example (Hello World) for the LPC55S69 MCU within MCUXpresso IDE.


The following are required to follow this blog post:


  1. MCUXpresso IDE Version 11.0.x
  2. LPCXpresso 55S69 EVK development board
  3. LPCXpresso 55S69 EVK version 2.6 SDK


Older version of MCUXpresso IDE and/or SDK will have different and inferior performance when used with Trustzone examples and are therefore not recommended.


A conceptual understanding of Arm Trustzone will also help understand the features shown in this article. Please also see the community article on Trustzone on the LPC55S6x.


Finally, a familiarity with the use of MCUXpresso IDE and SDK installation is assumed.



In essence, MCUs incorporating Arm Trustzone technology are able to provide system wide isolation between Secure (S) and Non Secure (NS) worlds. Within the Non Secure environment, access to certain operations, peripherals etc. are controlled from the Secure world. This behaviour is delivered by a single CPU with execution time being shared between these two worlds.


Developing for systems using Trustzone features presents a number of challenges in particular providing Secure World services for Non Secure application developers, debugging of both Secure and Non Secure code (projects) and delivering a usage model within the IDE that can be easily used and understood.


The examples supplied with the SDK contain both Secure and Non Secure linked projects and are configured within the IDE to demonstrate development from the point of view of both Secure and Non Secure development.


However, a more typical 'real world' situation may be for developers working on Non Secure project development and treating the Secure world as a 'Black Box' (or Bootloader) that provides a number of explicit secure operations. This use case will be discussed in a subsequent article.


Note: the LPC55S69 is a multicore MCU as in it contains two physical CPUs - numbered 0 and 1. In these examples all code is targeted at CPU 0, and the use of CPU 1 is outside the scope of this article.


Importing (Linked) Example Project


First, ensure you have installed version SDK version 2.6 for the LPCXpresso55S69 EVK board into MCUXpresso IDE. Once installed it will be visible within the Installed SDKs view and its version shown as below:

Installed SDK view


From the Quickstart view, launch the 'Import SDK example(s)' Wizard, then select the LPCXpresso55S69 board and click <next>

Example Import Selection


Expand the trustzone examples and click either of the Hello World projects. Since these projects are linked, both the Secure (_s) and Non Secure (_ns) examples will be selected. Click <finish> to start the import.


Note: Linked projects are coloured yellow within the wizard. This project linkage is set because the Non Secure project relies on Secure project for access to allowed Secure operations (calls). Where as the Secure project references the Non Secure project for debug operations (flash programming).


Project Selection

Once imported, you will see the Project Explorer view contains the projects as expected.


Project View


Project Settings Exploration


Memory Configuration


The memory allocation of each project can be seen in the Project Explorer view by opening the Project Settings Node and then the Memory Node. From here you can see the input memory ranges set for the managed linker script mechanism (for each project):


Apart from the veneer table, these projects can be considered as separate entities and must have non overlapping memory regions.


Secure: A feature of the address space security is that the setting of address bit 28 signifies a secure location (odd numbers in the most significant nibble).

Memory Usage Secure


The flash region PROGRAM_FLASH at 0x10000000 specifies the secure LinkServer flash driver LPC55xx_S.cfx.

The SG_veneer_table block at 0x1000FE00 is used for code to provide a gateway to (certain) secure functions and inherits the same flash driver. Note: the name SG_veneer_table is a 'magic' string recognised by the IDE as an option for veneer placement (see later)


Non Secure: For these addresses, bit 28 is not set signifying non secure locations (even numbers in the most significant nibble)

Memory Usage Non Secure

The flash region PROGRAM_FLASH at 0x10000 specifies the non secure LinkServer flash driver LPC55xx.cfx.


Project Properties


Trustzone capable MCUs have a number of dedicated Project Properties primarily addressing linkage and debug.


A project set to be Secure will have further options available, including a setting for the location of the Secure veneer table, and check box to cause the generation of the Import Library. An additional Secure Gateway Import Library can also be specified.


Secure: Below is shown the MCU Linker -> Trustzone properties dialogue.


Note the Secure Gateway Placement (Secure veneers to shared secure operations) is set to use the 'magic' flash memory region (mentioned in the previous section) for placement.

Project Properties Secure

Also observe the MCU Debugger -> Trustzone option. If used (as in this example), this takes the name of the associated non secure project which will then automatically be (built and) programmed when the Secure project debug operation is performed. In addition the symbols for this associated project will be added to allow source level debugging of both projects.


When selected, it will look like below:

Project Properties Secure Debug Link


Non Secure: Below is shown the MCU Linker -> Trustzone properties dialogue: Note the Secure Gateway Import Library references the Secure projects generated library location.

Project Properties Non Secure


Building the Example Projects


Building the examples is as simple selecting the project and clicking Build in the Quickstart panel. Be aware that building the Non Secure project will force the Secure project to build first to provide linkage to the Secure Gateway library. 


Assuming neither project has been built before, building the Non Secure Hello World project will result in the generation of both Secure and Non Secure .axf(s) and generate the output as below:

Memory region         Used Size  Region Size  %age Used
   PROGRAM_FLASH:       16872 B      65024 B     25.95%
 SG_veneer_table:          32 B        512 B      6.25%
            Ram0:        4388 B        32 KB     13.39%
Finished building target: lpcxpresso55s69_hello_world_s.axf

Memory region         Used Size  Region Size  %age Used
   PROGRAM_FLASH:        7372 B       456 KB      1.58%
            Ram0:        8448 B       172 KB      4.80%            
Finished building target: lpcxpresso55s69_hello_world_ns.axf


Note: building the Secure project does not force a build of the Non Secure since there are no build dependencies in this direction.

Debugging the Example Projects


As already mentioned, these examples demonstrate development from the point of view of both Secure and Non Secure projects. Hence the initial flow is intended to show startup within a the Secure world and then the migration to the Non Secure where a secure operation will be performed.


Therefore, begin by selecting the Secure Project in the Project Explorer view and clicking Debug in the Quickstart Panel. Since we have the option set to enable the pre-programming of the Non Secure binary there will be two stages to this debug operation.


Note: If this is the first time this project has been debugged, you will be presented with the option to select a debug probe. Then, since this is a MultiCore MCU, you must also select the core to use (be sure that this is set to Core 0).


First, the Non Secure binary will be programmed into flash memory - this automatic step will proceed like a normal binary programming operation and generate a log associated with Non Secure project, a fragment shown below:


Flash variant 'LPC55xx (608KB)' detected (608KB = 19*32K at 0x0)
Writing 7372 bytes to address 0x00010000 in Flash
1 of 1 (  0) Writing pages 2-2 at 0x00010000 with 7372 bytes
(  0) at 00010000: 0 bytes - 0/7372
(100) at 00010000: 8192 bytes - 8192/7372
Erased/Wrote sector  2-2 with 7372 bytes in 122msec
Closing flash driver LPC55xx.cfx
(100) Finished writing Flash successfully.
Flash Write Done
Loaded 0x1CCC bytes in 417ms (about 17kB/s)


Secondly, the Secure project will then be programmed in the normal way, this will generate a standard debug log associated with the Secure project, a fragment is shown below: 


Note: again if this is the first time, the debug probe and MCU core must be selected. For subsequent debug operations, these options will be remembered.


Flash variant 'LPC55xx (608KB) (Secure)' detected (608KB = 19*32K at 0x10000000)
Writing 32 bytes to address 0x1000FE00 in Flash
1000A000 done  25% (8192 out of 32288)
1000C000 done  50% (16384 out of 32288)
1000E000 done  76% (24576 out of 32288)
10010000 done 100% (32768 out of 32288)
Erased/Wrote sector  1-1 with 32 bytes in 709msec
Closing flash driver LPC55xx_S.cfx
Flash Write Done
Flash Program Summary: 16904 bytes in 1.00 seconds (16.59 KB/sec)
Starting execution using system reset and halt target with a stall address
Retask read watchpoint 1 at 0x50000040 for boot ROM stall
Restore internally retasked watch #1 no type address 0x0 (unused)
Note - system reset leaves VTOR at 0x13000000 (not 0x10000000 which a booted image might assume)
Stopped (Was Reset)  [Reset from Unknown]
Stopped: Breakpoint #2


Once programming is complete, you should arrive at the default Breakpoint on main within the Secure world as below:

Secure Project Debug


Click Run and this project will first perform some board/MCU initialisation, print a greeting (as below), then setup the environment for the Non Secure project to execute.


Note: this step is necessary because the non secure project is not run from reset, so cannot rely on the default hardware behaviour for initialisation of Stack, Interrupt handlers etc. This is essentially the same operation that a bootloader would perform.

Secure Console

Next, a jump will be made to the Non Secure world.


Note: since the non secure project is not debugged directly, it will have no default breakpoint on its main function. To explore the execution, it is recommended to open the Non Secure projects Source -> hello_world_ns.c and manually set a breakpoint as shown below:


Non Secure Debug

Reminder, since we have the option set to enable the pre-programming of the Non Secure binary this also enabled the loading of Non Secure symbols (which can be observed in the Secure projects debug launch configuration (shown below). It is the loading of these symbols which enables source level debug of the Non Secure project while we are actually debugging the Secure project.


Secure Launch Symbols


Finally, click Run to run this example to termination and observe the output.


Secure Console Non Secure output


Note: the significance of this example is that the String Compare operation was supplied to the Non Secure project by the Secure project and accessed securely via the Non Secure Entry (NSE).


This step concludes the expected use of this example.


Another mode of operation is to perform a Debug operation directly on the Non Secure project. This is a perfectly valid operation provided the Secure project has first been programmed into flash. If so the Non Secure project will behave like a standard project and arrive the breakpoint on main ()... However, if the Secure Project has not been pre-loaded, the debug operation will fail.



If Debug operations fail...


It is possible to program an image into flash that when run prevents further debug operations succeeding. Should this occur, please follow the steps below:


  • Click on the "Clean Up debug" button on the main IDE toolbar - this kills any stale low level debug operations
  • Disconnect the USB cable from your board to remove power
  • Place a jumper on the ISP header (J10) - this will prevent the board booting the image in flash by forcing the MCU to enter ISP mode
  • Now reconnect the USB cable to Debug Link connector (P6)
  • Now select a project in the Project Explorer view, and then click on the GUI Flash Tool on the main IDE toolbar - and use this to mass erase the flash. [More details on using the GUI Flash Tools can be found inside the supplied IDE v11.0 User Guide]


If this succeeds, then:

  • Disconnect the USB cable from your board
  • Remove the jumper on the ISP header (J10)
  • Now reconnect the USB cable to Debug Link connector (P6)


Now try starting a debug session for your project again using the Quickstart Panel's Debug button. If this problem occurs as part of application development, try programming a known working example to ensure there are no underlying problems.

When using the QN9080 with SDK v2.2 2019-01-29, or earlier, there is an issue in the SDK internal data which can lead to MCUXpresso IDE v11.0.0 failing to set consistent floating point options when importing multiple examples. This issue can lead to linker errors when example projects are built relating to "VFP register arguments": 


This issue will be resolved in a future release of the QN9080 SDK. But with the current QN9080 SDK, then to avoid this issue, you can:

  • Import example projects individually, or
  • Before importing the projects, go to:
    • Window -> Preferences -> MCUXpresso IDE -> SDK Handling -> Misc

and untick the "Enable SDK options check" option:



Notes :  

  • Turning this option off is not generally recommended.
  • On macOS, the Preferences dialog is available from the "MCUXpresso IDE" menu entry rather than "Window".


Alternatively to fix projects that you have already imported that are generating linker errors relating to "VFP register arguments", then

  • Select the project(s) in the Project Explorer View
  • Then select Quickstart Panel -> Quick Settings -> Set Floating Point type -> FPv4-SP (Hard ABI)


With the cost of an single pin, many ARM Cortex-M boards including the NXP i.MX RT1064 can produde SWO data: think about a pin able to stream data out of the chip in realtime. For example interrupt activity which otherwise might be hard to capture:

SWO Interrupt Trace

SWO Interrupt Trace



This article describes how to enable and use the SWO (Single Wire Output) of the ARM Cortex-M7 present in the NXP i.MX RT1064 device.

i.MX RT1064-EVK Board

i.MX RT1064-EVK Board

While this is a very valuable feature, not every development tool supports capturing SWO data. And not every board has the SWO pin routed to the debug header which is a prerequisite to get the data.


JTAG TDO Pin (Source: NXP i.MX RT1064 Schematics)

The pin is connected to the AD_B0_10 pin of the i.MX RT1064 device.

Software and tools used:

  • Eclipse: NXP MCUXpresso IDE 10.3.1
  • SDK: NXP MCUXpresso SDK 2.4.1 for i.MX RT1064-EVK

Check SDK Manifest File

To use SWO, it has to be enabled in the SDK manifest file. So let’s check this first.

In the IDE, open the location where the SDK zip files are installed:

Open Location

Open Location

 Best to close the IDE now, as we might need to change the content on disk.

Open the archive:

Open SDK zip file

Open SDK zip file

Locate the manifest XML file:

SDK Manifest File

SDK Manifest File

To check/edit the manifext XML file I can use an external editor or the IDE:

Using the IDE

I can use the IDE to edit the XML (this is useful if I want to change the SDK sources).

To check/edit the file in the IDE workspace preferences, disable the ‘Selected files from SDK View open in read-only mode:

Selected Files Open Option

Selected Files Open Option

Open with the context menu the XML description:

Show XML Description

Show XML Description

In the XML editor, click on the ‘Source’ tab. Search for internal.has_swo:

XML Source tab

XML Source tab

Verify that it has a ‘true’ value. If not, change it to true and save the file.

Using external editor

Below are the steps using an external editor.

Open the file with a text editor and search for ‘internal_has_swo’ and check if it has a ‘true’ value. If not: change the value to true:



If that change is needed: update the zip file with the new content/file.

 if that setting is set to false, the IDE does not offer the SWO feature and buttons/views will be grayed out/disabled.

Now I can start the IDE again. If I had to modify the XML file, best to recreate the part information in the IDE:

Recreate Part Information

Recreate Part Information

Muxing SWO Pin

Locate the file ‘pin_mux.c’ and add the following lines to BOARD_InitPins():

      IOMUXC_GPIO_AD_B0_10_ARM_CM7_TRACE_SWO,     /* GPIO_AD_B0_10 is configured as ARM_TRACE_SWO */
      0U);                                        /* Software Input On Field: Input Path is determined by functionality */


Open ‘clock_config.c’ and search for the following inside the function BOARD_BootClockRUN():

/* Set TRACE_PODF. */
CLOCK_SetDiv(kCLOCK_TraceDiv, 2);
/* Set Trace clock source. */
CLOCK_SetMux(kCLOCK_TraceMux, 2);

and change it to

/* Set TRACE_PODF. */
CLOCK_SetDiv(kCLOCK_TraceDiv, 0);
/* Set Trace clock source. */
CLOCK_SetMux(kCLOCK_TraceMux, 3);
clock div and mux

clock div and mux

Finally, add the following to the end of the function BOARD_BootClockRUN(), or add it to main() after the clocks have been initialized.

#if 1 /* enable SWO */
*((uint32_t *)(0x400E0600)) = (1 << 11);  /* enable TPIU clock */


The onboard DAPLink debug probe does *not* support SWO, so I’m using an external debug probe (LPC-Link2). Alternatively, the EVK board can be loaded with a LPC-Link2 firmware.

Debugging i.MX RT1064 Board with LPCLink2

Debugging i.MX RT1064 Board with LPC-Link2

In the SWO Trace Config view, the ‘change’ button shall now be enabled:

SWO Trace Config

SWO Trace Config

Use the ‘Detect’ button to detect the SWO speed (note that for the application shall have already passed the clock configuration code):

Detect SWO speed

Detect SWO speed

SWO Views

After this, I can open the various SWO views:

Open SWO views

Open SWO views

The views have a green ‘start’ button to start data collection from SWO:

start button

start button

SWO Counters view:

SWO counters

SWO counters

SWO statistical profiling:

SWO Profile View

SWO Profile View

SWO Data Trace:

SWO Data Trace

SWO Data Trace

Text output with SWO:

ITM Text Output

ITM Text Output

SWO Interrupt Trace:

SWO Interrupt Trace

SWO Interrupt Trace

 The IDE reveference manual/online help describes the views in more detail.


SWO on the i.MX RT1064 board is a fine thing: it requires some setup and a SWO capable debug probe. But with that extra ARM SWO pin I get extended debug views and data which are very valuable.

I have put an example project on GitHub (see Links section).

Happy SWOing 




- - -

Originally published on June 3, 2019 by Erich Styger

First Release v1.00 : 22nd February 2019


Please find attached a document detailing how to create, build and debug LPC55xx multicore applications using the LPC55S69-EVK LPCXpresso55S69 Development Board with MCUXpresso IDE v10.3.1 and MCUXpresso SDK v2.5.0



MCUXpresso IDE Support

We are pleased to announce that MCUXpresso IDE v10.3.1 (build 2233) is now available.


This is a maintenance release that builds upon the previous MCUXpresso IDE v10.3.0 release, and we recommend that all existing users download and install this new version.


To download the installers for all platforms, please login to our download site via:



MCUXpresso IDE v10.3.1 will be the last release to be compatible with both 32-bit and 64-bit versions of Windows. Future releases will only be compatible with 64-bit versions of Windows. (The MacOS and Ubuntu versions of MCUXpresso IDE are already 64-bit only.)


Summary of Changes - version 10.3.1 - February 2019

  • Improvements to support for i.MX RT600 MCUs
  • Improvements to support for LPC5500 MCUs
  • Added managed linker script and LinkServer debug support for i.MX RT1015
  • Fixed issue with permissions within IDE installation directory on MacOS and Ubuntu which could cause failure of FreeRTOS TAD plugin and also prevent installation and update of third party plugins (e.g. from Eclipse Marketplace)
    Managed linker script mechanism now includes libgcc.a in the list of libraries to be linked against when using Redlib
    (to resolve any runtime support functions generated by compiler that have no specific implementation in Redlib)
  • Improved error checking in Memory Configuration Editor
  • Managed Linker Script settings in Project Properties now more thoroughly checks alignment / region size when calculating "Default" stack size - preventing potential issues with incorrect stack alignment
  • Fixed issue with handling of "preinclude file" option when importing "Connectivity" example projects available in SDKs for certain MCUs (such as Kinetis KW devices)
  • Fixed issue with the SDK project wizards such that new projects could, in some circumstances, inherit memory configuration information from a previous instance of the project wizard
  • Fixed issue when importing SDK example projects that could cause projects to lose part of their configuration
  • Fixed issue with "Select All" option failing when trying to add SDK Middleware components to a project with some SDKs
  • Improved handling of incorrect SDKs
  • Fixed issue with Project Properties right-click menu which could cause it to fail to display for non-SDK projects
  • Various fixes to SDK Editor / Creator
  • Binary Utilities options are now disabled in certain cases for "CDT virtual nodes" in the Project Explorer view (when such nodes are pointing to "files" that don't actually exist in the file system)
  • Fixed issue in Fault Views which could cause certain fault registers to be displayed when they were not valid for the
    current fault
  • Fixed issue with the display of registers in their "natural" format in the Register view. This in particular means that floating point registers will now be displayed in floating point format by default instead of hex
  • Fixed issue with display of Registers View when the target is running
  • Fixed issue with the handling of Peripherals View for SDK-based multicore MCUs
  • Fixed issue with "Resume All" button being enabled even when all debug sessions are already running
  • Enhanced Global Variables view to allow live variables update to be started/stopped whilst target is paused
  • Fixed issue with LinkServer debug which could cause connection failures when debugging MCUs (such as LPC8xx) which use the "-vc" debug option by default
  • Fixed issue with LinkServer flash driver handling causing unnecessary memory accesses to be made, which could cause flash programming failures with some very RAM limited MCUs
  • Fixed issue with LinkServer related to debugging applications in RAM, which could prevent correct setting of breakpoints
  • Fixed issue with LinkServer attaching to projects running in RAM
  • Improved LinkServer debug connections to RT10xx devices to avoid occasional "wire ack" fault that could occur when resetting MCU at the end of flash programming
  • LinkServer debug connections now default to using the same Peripheral View service as used by SEGGER and P&E debug connections. The LinkServer native service can currently be reenabled via a preference, though this functionality will be removed in a future release
  • Fixed issue that could cause LinkServer debug to occasionally slow down
  • Improved LinkServer command line programming stability
  • IDE now displays double precision registers in Register View with SEGGER and P&E Micro debug connections by default (where available on MCU)
  • Upgraded to a later version of the P&E Micro plugin (v3.9.9)
  • Upgraded to a later version of the SEGGER software (v6.42b)

The following article is a step-by-step tutorial how to use the NXP MCUXpresso SDK & IDE to create a SD card bootable image on i.MX RT. It features the i.MX RT1050-EVK(B) but is with minor changes applicable to any other i.MX RT device:

Tutorial: Booting the NXP i.MX RT from Micro SD Card

  • Creating a project running in RAM
  • Generating S19 file
  • Running application in RAM
  • Creating SD card boot image with Flashloader and elftosb
  • Loading image to SD card with MfgTool
  • Booting i.MX from SD card image


I hope you find it useful,


Updated v1.02  1st March 2019


Please find attached a document detailing various features related to using the iMXRT1060-EVK evaluation board with MCUXpresso IDE v10.3.x and SDK v2.5, including details of how to enable SWO trace on this MCU.


Updated to include a section on the MIMXRT1064 EVK.


Also attached are:


  • an example project demonstrating how SWO trace features may be enabled
  • an updated LinkServer (CMSIS-DAP) flash driver for the iMXRT1064 containing a fix for Mass Erase




MCUXpresso IDE Support

We are pleased to announce that MCUXpresso IDE v10.3.0 (build 2200) is now available.


This is a major new version of the IDE, and contains many new features and enhancements over the previous v10.2.1 and earlier releases. The attached presentation, recommended viewing for all users (new or experienced), provides an overview of many of the major changes, as well as things to be aware of when upgrading from an earlier release:



To download the installers for all platforms, please login to our download site via: 


Additional information can be found in the updated User Guide and other documentation, which can be accessed from the built in help system available via IDE's Help menu and in PDF form from within the installation directory or downloaded from:


Summary of Changes - version 10.3.0 - December 2018


  • Major restructure of product installation structure to allow future minor product updates to be potentially delivered via Eclipse Software Update mechanism
  • Upgraded supplied GNU ARM Embedded Toolchain to GCC7 2018q2-update
  • Added support for MCUXpresso SDK v2.5.0
  • Upgraded integrated version of MCUXpresso Config Tools to v5
  • IDE now provides a workspace preference to allow the location of the SDK Drag&Drop installation folder to be changed. However by default a central 'mcuxpresso' folder is still used. Current install location label displayed in the "Installed SDKs" View
  • IDE now generates part support information from installed SDKs into the workspace rather than into a central 'mcuxpresso' folder, improving behavior when multiple IDE instances are being used
  • New "Faults" view compatible with LinkServer, P&E and SEGGER debug connections implemented (replacing the previous "vectpc" pseudo-register in Registers view for LinkServer debug connections). This view provides a decoding of the Cortex-M cpu's fault registers and stack backtrace to assist the user in tracking down the cause of hard faults and other processor exceptions
  • New implementation of the "Registers" View, allowing categorisation of certain registers groups, as well as providing
    access to additional CPU registers for P&E and SEGGER debug connections
  • SWO Trace now supported via SEGGER J-Link and P&E Micro debug probes (in addition to LinkServer LPC-Link2 debug connections). 
  • NXP LPC-LINK2 CMSIS-DAP firmware soft-loaded by IDE updated to v5.224, providing noticeable performance improvements over previous v5.183. For standard (debug+SWO) firmware, flash programming speed increases of typically ~10% along with increases in SWO trace speed. For Non-bridged firmware (debug only), flash programming speed increases of typically ~20%
  • Project Explorer View enhanced to emphasise currently selected project, along with displaying its current build configuration
  • Editing Memory Configuration for projects is now done in place rather than spawning separate editing dialog
  • IDE now only creates a debug launch configuration for the current build configuration when a project is debugged (if one does not yet exist), rather than for all build configurations
  • New SDK creator wizard to create a "board SDK" from an existing project (with settings modified using the MCUXpresso Config Tools). This "board SDK" can then be used to create new projects for custom boards
  • Package associated with an SDK project can now be modified via the MCU entry of the project's "Project Settings" virtual nodes in the Project Explorer view
  • IDE now supports additional build configurations being specified in SDK example definition files
  • Added Linux Tools Libhover to preinstalled plugins (providing tooltips for standard C library calls)
  • Upgraded to a later version of the P&E Micro plugin (v3.8.3)
  • Upgraded to a later version of the SEGGER software (v6.40)
  • Updated FreeRTOS TAD plugin to v1.0.8
    • Support heap using Newlib (identified as heap #6)
    • Support FreeRTOS 10.1.1
    • Fix highlight of free section in Heap Usage view
  • Windows version of IDE now uses "busybox" (from "GNU MCU Eclipse Windows Build Tools" project) , to provide a Unix-like layer for GCC tools to run under, rather than the "msys" package used by previous releases
  • Modified order of entries added to local shell's path when building projects under Windows - providing small improvement in build speeds
  • Additional LinkServer flash drivers provided for RT1060 and RT1064
  • Preliminary LinkServer support for LPC55xx devices
  • Added basic support for Cortex-M33 secure projects
  • Added support for Cortex-M33 No DSP variant
  • LinkServer debug executable now allows probe selection by serial number (mainly intended for command line flash programming operations)
  • Redlib updates
    • Fixed snprintf() / vsnprintf() to prevent hard fault when NULL buffer passed
    • Fixed issue with number sequences generated by rand()
  • Made ordering of C Libraries in drop down lists consistant across various menus
  • Allow user to only choose valid FPU settings in the Architecture tab of Project Settings
  • "Quick Settings" option now allows reconfiguring multiple projects (where projects have compatible settings)
  • Fixed issue that could cause a project to lose modifications to its memory configuration
  • Grouped SDK actions under new "SDK Management" entry of Project Explorer popup menu
  • Fixed issue that could cause a project's list of associated SDK components to be lost
  • Fixed issue with sorting of boards in SDK project wizards not taking any current selection into account
  • Fixed issue with default peripherals.c/h files being automatically (and incorrectly) added during SDK example import
  • Fixed issue with Import of >1 SDK examples sometimes failing to correctly pickup some IDE default settings
  • Fixed issue with SDK Project Component Manager when adding components with conditional sources to an existing project
  • Improved handling of C library family setting when importing multiple SDK examples
  • Fixed issue that could cause the IDE to block if requested to change the SDK associated with a project
  • Fixed issue with SDKs become unusable after cancelling an unzipping operation
  • Fixed issue with SDK New Project Wizard when no board selected which could cause wrong header files to be generated
  • Fixed issue with SDK New Project Wizard such that main.c file always included the BOARD_InitDebugConsole() call even when the debug console component is not selected
  • Fixed issue with handling of derived peripherals containing '_' in name
  • Implemented partial workaround for underlying Eclipse issue that can cause a "Target Not Available" dialog if starting a debug session with the Disassembly view open
  • Fixed issue with SEGGER launch configurations failing to reset MCU after programming flash
  • Fixed issue with launch configurations created using standard Eclipse functionality, as opposed to automatically created using MCUXpresso IDE
  • Enhanced handling of additional bespoke launch configurations
  • Fixed issue with sorting in Probe selection dialog
  • Fixed long standing issue with LinkServer launch configuration tabs changing order every time the launch config editor is open
  • Fixed issue that could cause the launch configuration selection dialog to be displayed twice in some circumstances
  • Fixed longstanding issue with that prevented Instruction Trace and SWO Trace being used together
  • Fixed issue with Instruction Trace Config view not correctly loading saved configuration files
  • GUI Flash Tool will now automatically select the highlighted binary file from Project Explorer View

First Release


Please find attached a document detailing various features related to using the iMXRT1020-EVK evaluation board with MCUXpresso IDE v10.2.1 and SDK v2.4.




MCUXpresso IDE Support

We are pleased to announce that MCUXpresso IDE v10.2.1 (build 795) is now available.


This is a maintenance release that builds upon the previous MCUXpresso IDE v10.2.0 release, and we recommend that all existing users download and install this new version.


To download the installers for all platforms, please login to our download site via:

Summary of Changes - version 10.2.1 - July 2018

  • Fixed issue in New Project Wizard when switching between a board and a generic device (or vice versa)
  • Fixed issue with floating point settings when importing SDK example projects for Cortex-M7 based MCUs
  • Fixed issue with notification of missing dependencies when Add/Remove Component used with SDK v2.4 packages
  • Improved options to handle part selection when project importing in cases where associated SDK is not installed
  • Fixed issue which could prevent a renamed project from being debugged in some circumstances
  • Resolved various issues with user interface of GUI Flash Tool
  • Resolved issue with workspace preferences when trying to configure the Debug perspective to be used for debugging projects (instead of the default Develop perspective)
  • Improved reliability of LinkServer debug sessions via enhancements to the way the IDE connects to the server process, as well as enhancements in the server itself
  • Improved the IDE's display of the LinkServer "RedlinkServer" console
  • Fixed issue with LinkServer "Disconnect behavior" always using "cont", even when configured to use another disconnect option
  • Option to terminate debug session added to IDE's LinkServer error dialog
  • Fixed issue with handling of number formats for entries in Global Variables view
  • Live Global Variable graphing no longer inserts spurious zero entry when target paused
  • Fixed issue with enumerated bitfield handling in the Peripheral Register viewer
  • Fixed issue with display of PriMask, BasePri, FaultMask and Control special registers in Registers view for LinkServer debug sessions. This change also now allows these registers to be edited
  • Fixed issue with LinkServer erroneously setting VTOR in some circumstances after programming flash
  • Fixed issue with zoom function on SWO Interrupt Trace view
  • Fixed issue with Instruction Trace view, which could prevent profile information being displayed in source and disassembly views in some circumstances
  • Fixed issue with Instruction Trace Config view, which prevented a modified configuration being saved
  • Preliminary LinkServer SPI flash drivers that self-configure using JEDEC SFDP information read from the device are now included for i.MX RT1020 (QSPI) and RT1050 (QSPI and Hyperflash)
  • Example device specific flash driver projects provided for i.MX RT1020 and RT1050. These can be used as a starting point for writing flash drivers for custom boards fitted with flash devices that do not support SFDP information
  • Updated FreeRTOS TAD plugin to v1.0.6
    • Fixed issues with Pause button
    • Added more verbose log for determining heap type
    • Removed problematic heap identification from available variables
  • Fixed issue which prevented the P&E Micro plugin updating from the P&E update server
  • Upgraded to a later version of the P&E Micro plugin (v3.5.6)
  • Upgraded to a later version of the SEGGER software (v6.32h)