As a heads-up: several uses reported a problems with downloading the MCUXpresso IDE setup/installer program. If pressing the 'Download' button, you might come back to the login screen (to log into your NXP user account): The likely reason for this is that your NXP account needs re-activation. You should see a link to open a SR (Service Request) which you could use. Otherwise post a comment here so your account can be re-activated. I hope this helps, Erich

Semihosting printf with MCUXpresso IDE When importing MCUXpresso SDK projects into MCUXpresso IDE, they will be configured by default to use “semihosting” for the terminal output. This means the project will use the debugger connection to send terminal characters instead of the UART. More information on semihosting can be found on this Community document and in Section 11.4 of the MCUXpresso User Guide.   Note that the information in this post is only applicable when using the MCUXpresso IDE, as the projects for other IDEs will use the UART by default when opening up their respective MCUXpresso SDK projects. Also semihosting only works when there is an active debug connection to the device.    printf with semihosting:   printf with UART Terminal (with TeraTerm):   How to choose UART output during the project import In order to use the UART for MCUXpresso IDE projects, some configuration settings need to be modified when importing in the project. First, you will need to uncheck the “Enable semihosting” option to clear the box. This will tell the project to use the normal libraries and not the semihosting libraries.   Then on the next screen, you’ll want to uncheck the “Redirect SDK “PRINTF” to C library “printf”” box to clear it. This will tell the project to use the MCUXpresso SDK source files for printf instead of the generic C files. This allows you to debug, and modify if desired, the printf functionality found inside the MCUXpresso SDK. Section 5.1.2 of the MCUXpresso IDE User Guide describes the options on this screen in more detail.     Switching between semihosting and UART If you’re already imported the project and wish to switch between using semihosting or the UART, you can do this from the “Quick Settings” menu inside the Quickstart panel.    If moving from semi-hosting to UART, this will change the library used to “nohost-nf” and set SDK_DEBUGCONSOLE define to 1 inside the pre-processor settings. If moving from UART to semi-hosting, this will change the library to “semihost-nf” and set SDK_DEBUGCONSOLE define to 0.    If you're not seeing any printf output, double check you have the right settings.    Note that when importing the project initially and “Enable semihosting” is deselected and “Redirect SDK “PRINTF” to C library “printf”” is deselected in order to use the UART for terminal output, there is no SDK_DEBUGCONSOLE defined in the project settings. However inside the debug console SDK code itself, there is a #if statement so that if that value is not defined, then that define is set to 1, and hence why the SDK debug console is still used in that case.

This document provides some sample codes and steps for relocating Code and Data into RAM/FLASH. Please look at them with projects in attachment. It is based on “MCUXpresso_IDE_User_Guide.pdf”, so about the understanding of some macros, you can check on that document. This document is based on FRDM-K64, MCUXpressoIDE_10.0.2_411. You can use it on other chips too.   1. Introduce the “Memory configuration editor” 2.1. Relocating Data into RAM 2.1 Relocating Code into RAM 2.3 Relocating Code into Flash 3.Reference  

MCUXpresso IDE combines the best features of the LPCXpresso IDE and Kinetis Design Studio. For users more familiar with KDS, here’s a high level overview of some of the things that are different in basic interactions with this new tool.   Quickstart Panel. One of the biggest and most useful changes is the Quickstart panel in the lower left hand corner of the IDE. This is where users import MCUXpresso SDK projects, build projects, debug projects, and modify some project settings.   Importing SDK Example Projects This is now done via the Quickstart Panel, and by default will create a unique copy of the project inside the workspace directory with all the necessary source files for the board, drivers, and source so it can be easily shared.   Debugging SDK Projects This is also now done via the Quickstart Panel, and is straightforward. One important thing to note though is that if you want to change the debugger protocol (ie move from CMSIS-DAP to Segger JLink) you need to delete both the .launch files in the project so that the debugger settings will reset.   Semihosting If default options are kept when importing in SDK projects, semihosting is used for printf commands. See this Community post for details on how to use the UART for printf instead (which is connected to the OpenSDA circuit on development boards), as well as how to switch between the two options.   Importing SDKs New device support is added to MCUXpresso IDE by importing SDK packages. There’s an XML file inside the SDK packages that tell it all the information the IDE needs to know. Reference this Community post for some of the options you have in how to import an SDK into the IDE, and also refer to Section 4 of the MCUXpresso User Guide or this in-depth training video.   MCUXpresso SDK This is just a re-branding of Kinetis SDK 2.x now that it supports more than just Kinetis devices, so there are no significant differences with this new name change.   Porting a KDS project to MCUXpresso There is no automatic tool to take a KDS project and convert it to a MCUXpresso project, so there is some manual work involved in porting a KDS project to MCUXpresso IDE. The recommended path would be to import/create the closest MCUXpresso SDK project, and then copy in the custom source code and other modifications. Minimal code re-write should be required since the drivers are the same. They are also both Eclipse/GCC based IDEs so predefines should be straight forward to port over. 

Dear Community, The purpose of this document is to show how to integrate projects from the file system to MCUXpresso IDE. It is actually not that complicated as you might have imagined.  Let's begin... The import project(s) from file system option is included in the Quickstart Panel, which is located in the lower left corner of the IDE. Type / Paste the location of the folder (either zipped or unpacked). Then, click Next button. Finally, select all the project folders / examples you want to be imported. Now, they will be accessible and available from the Project explorer. Happy development! Best regards, Ivan R.

MCUXpresso SDK packages are downloaded as .zip files. If you are using a 3 rd party IDE such as IAR or Keil, then the package must be unzipped in order to access the project files. Also an unzipped SDK folder must be available for the MCUXpresso Config Tools. This is why the default recommendation is to go ahead and unzip a downloaded SDK package.   However if using MCUXpresso IDE, then either the zipped or unzipped SDK can be imported into the MCUXpresso IDE. A zipped SDK will save disk space and can be imported into the IDE more quickly than an unzipped SDK folder. MCUXpresso’s IDE part support is extended by importing MCUXpresso SDKs into the IDE, so this can save some time if you need to add a new device. Also note that your SDK package must support MCUXpresso, and thus must have been recently created in the SDK Builder (after March 24th) with explicit support for MCUXpresso in the package, else you will get an error when trying to import it.  When an MCUXpresso SDK zip package or folder is drag-and-dropped into the IDE, a copy of that zip/folder is made and put into the C:\Users\<user_name>\mcuxpresso\SDKPackages directory. Thus you can delete the original copy that was downloaded to save disk space.     If the imported SDK was zipped, then when creating or importing example projects, the SDK source files are always copied into the workspace. If the imported SDK was unzipped, then you are given the option to either copy the SDK source files into the workspace (which is the default), or the SDK files can be referenced directly as linked references.   If an SDK is imported as a zipped file, it can be later unzipped from inside the MCUXpresso IDE. This unzipping has been optimized so it’s much faster than unzipping it via a program like WinZip. When unzipping inside the MCUXpresso IDE, the zip file that was in the MCUXpresso SDKPackages folder will automatically be deleted from the hard drive once its finished unzipping. You can then use this unzipped folder for that SDK location when using the MCUXpresso Config tools.       You can also add MCUXpresso SDKs by placing an SDK package (zipped or unzipped) into that default SDKPackages directory (C:\Users\<user_name>\mcuxpresso\SDKPackage) and restarting the MCUXpresso IDE.    Finally you can also specify additional directories that MCUXpresso IDE should search for SDK files (both zipped or unzipped) by going to Window -> Preferences -> MCUXpresso IDE -> SDK Options. This can be useful for keeping a repository of SDKs in a special location on your hard drive. For SDKs stored outside the default location though, the "Delete SDK" function is disabled inside the IDE, and the extra search paths are only saved per workspace, so if you choose another workspace, it won't know about the new SDK folders until you re-add the path. If multiple SDKs are found for the same device in different locations, the IDE select the package to use by priority on the list (top has priority).    More detailed information on pre-installed part support and importing SDKs can be found in Section 4 of the MCUXpresso IDE User's Guide, as well as in this informative training video. 

The MCUXpresso IDE has a versatile way to create different binary files (S-Record/S19, Intel Hex or raw Binary) which then can be used by other tools like flash programmer or bootloaders. Check out the IDE documentation (menu Help > MCUXpresso IDE User Guide): where you can search for any topics like this: See as well the following article (external link) on that subject: MCUXpresso IDE: S-Record, Intel Hex and Binary Files | MCU on Eclipse  Enjoy!

This document contains a history of the releases of MCUXpresso IDE, with links to the announcement blog for each release.   Receive email notification for new releases If you would like to receive notifications when a new version of MCUXpresso IDE is released, please make sure to follow this document.   Release History   January 2024 MCUXpresso IDE v11.9.0 October 2023 MCUXpresso IDE v11.8.1 August 2023 MCUXpresso IDE v11.8.0  March 2023 MCUXpresso IDE v11.7.1  January 2023 MCUXpresso IDE v11.7.0  October 2022 MCUXpresso IDE v11.6.1  July 2022 MCUXpresso IDE v11.6.0  April 2022 MCUXpresso IDE v11.5.1  January 2022 MCUXpresso IDE v11.5.0  September 2021 MCUXpresso IDE v11.4.1  August 2021 MCUXpresso IDE v11.4.0 b6224 replaced by b6237 to fix an eclipse updater issue. July 2021 MCUXpresso IDE v11.4.0  April 2021 MCUXpresso IDE v11.3.1  January 2021 MCUXpresso IDE v11.3.0  October 2020 MCUXpresso IDE v11.2.1  July 2020 MCUXpresso IDE v11.2.0   March 2020 MCUXpresso IDE v11.1.1  December 2019 MCUXpresso IDE v11.1.0  MCUXpresso IDE v11.1.0 SDK Handling Hotfix (January 2020) September 2019 MCUXpresso IDE v11.0.1 MCUXpresso IDE v11.0.1 Segger-LPC Debug Hotfix (September 2019) MCUXpresso IDE v11.0.1 LPC55xx Debug Hotfix (October 2019) June 2019 MCUXpresso IDE v11.0.0 February 2019 MCUXpresso IDE v10.3.1 December 2018 MCUXpresso IDE v10.3.0 July 2018 MCUXpresso IDE v10.2.1 May 2018 MCUXpresso IDE v10.2.0 January 2018 MCUXpresso IDE v10.1.1 November 2017 MCUXpresso IDE v10.1.0 July 2017 MCUXpresso IDE v10.0.2 March 2017 MCUXpresso IDE v10.0.0

For the previous KDS or CodeWarrior users, they may not create and use static library under MCUXpresso IDE without a hitch, because the methods are not exactly same. MCUXpresso IDE supports adding static library in user project with “Smart Update” wizard. This feature is derived from LPCXpresso IDE.  However, “Smart Update” wizard is only available for natively supported LPC products in MCUXpresso 10.1.0 and lower versions.  It will support all LPC and Kinetis product in MCUXpresso IDE future release. For MCUXpresso natively supported LPC product, using “Smart Update” to add library is very convenient. User can learn its usage from this article: Creating and Linking to Library Projectshttps://community.nxp.com/message/630594 For Kinetis product, the only way to add library to project is by hand. This article will take an example with MK64F demo, illustrating how to create and use static library under MCUXpresso IDE step by step.  It will also be good for all LPC and Kinetis users to understand how user project works with external static libraries under MCUXpresso.  If user needs demo code of this article, please send me community internal message. Thanks for the suggestion from LPCX support        

Important Note. Previously announced MCUXpresso IDE v11.4.0 build 6224 has been replaced by build 6237 to address a potential problem related to the Eclipse updater mechanism which under some circumstances could inadvertently update the Java Runtime Environment to a newer version (jre-15) which is incompatible with the IDE. When this problem arises the MCUXpresso IDE will no longer start. In the case you have previously installed MCUXpresso IDE build 6224, it is highly recommended to uninstall it and install build 6237 instead.   We are pleased to announce that MCUXpresso IDE v11.4.0 (build 6237) is now available. This is a major new version of the IDE and contains new features, enhancements and bug fixes over the previous versions, including latest announced MCUXpresso IDE v11.3.1.   Installer Downloads To download the installers for all platforms, please login to our download site via:  https://www.nxp.com/mcuxpresso/ide/download   Documentation 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: https://www.nxp.com/mcuxpresso/ide/documentation    Notification of future releases To receive notifications about future releases, please follow: MCUXpresso IDE - Release History    Summary of Changes - version 11.4.0 - July 2021 Upgraded: Eclipse version to 2020.12 (Eclipse Platform 4.18.0 /  CDT 10.1.0). Upgraded: IDE now integrates with OpenJDK11 (HotSpot engine,  v11.0.10). Upgraded: GNU ARM Embedded Toolchain to 10-2020-q4-major. Note that on top of GNU ARM Embedded Toolchain 10-2020-q4-major,  gcclib was recompiled using the bug fix from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99157. This patch prevents the run-time application corruption when using -mcmse support (applied for armv8m only). Upgraded: Version v10 of MCUXpresso Config Tools. Upgraded: Newer SEGGER J-Link software (v7.50, 32-bit version on Windows, 64-bit version on Linux/macOS). Note that v7.50 comes with a 64-bit version of Windows. This 64-bit version is compatible and can be used if desired, but please note that the MCUXpresso IDE 11.4.0 installation does not include this and only partial testing has been possible due to timing of the release. If you prefer to use the 64-bit version on Windows: Install 64-bit Windows SEGGER J-Link software Go to IDE -> Preferences -> MCUXpresso IDE -> Debug Options ->  J-Link Options -> J-Link Server executable and change it from the existing path to the 64-bit version installation path, i.e. for the default installation path:  C:\Program Files\SEGGER\JLink\JLinkGDBServerCL.exe Upgraded: Newer PEmicro plugin (v5.0.4). Upgraded: FreeRTOS TAD synchronization with FreeRTOS v10.4.3. Added: MKE1xZ support. Feature: [Azure RTOS ThreadX] Added GDB thread awareness. The user is able to see threads in Debug view (only when using all-stop debug mode, similar to FreeRTOS usage) and also the register context associated with the current selected thread. Feature: [Azure RTOS ThreadX] Added views, similar to the FreeRTOS, for: Thread list, Message queues, Semaphores, Mutexes, Event flags, Timers, Memory block pools, Memory byte pools. These views are available under a new menu group called "RTOS", where older FreeRTOS views can be also found. Feature: [Azure RTOS ThreadX] Added the ability to export trace data generated by the application at run-time. Decoding of exported data is done using Microsoft's Azure RTOS TraceX host-based analysis tool. Detailed procedure is described in the Azure RTOS User Guide. Feature: [Energy Measurement] Added measurement/plot capability for MCU-Link Pro and on-board probes. Power measurement can be done using: The new MCU-Link double channel measurement capability (simultaneously measured current and voltage); Existing capability (used over LPC-Link2 probes) of caching voltage measurement to use on power computation over current measurement. Feature: [Offline Peripherals] Added offline peripheral view. With this view, the peripheral registers can be inspected outside of a debug session. A device selector or the current project selection can be used to load register information for a particular device. Additionally, an SVD file can be imported. Feature: [Debugger][MCU-Link] Differentiation of MCU-Link product names used when MCU-Link probes enumerate on USB: Example: base model: MCU-LINK (r0FF) CMSIS-DAP V2.219 Pro model : MCU-LINK Pro (r0C7) CMSIS-DAP V2.219 on-board  : MCU-LINK on-board (r0CF) CMSIS-DAP V2.219 Feature: [Debugger][J-Link] Added possibility to connect to a remote gdb server. In launch configuration -> J-Link Debugger tab -> GDB Server Settings, use Server execution option to set a remote server. Improvement: [Debugger][J-Link] Add nickname for J-Link probes in Probes Discovered Dialog and in J-Link Debugger tab. Improvement: [Debugger][PEmicro] Added nickname for PEmicro probes in Probes Discovered Dialog. Feature: [SDK Integration] UART console is the default debug console when importing a project. Feature: [Flash Programmer] External flash drivers for i.MX RT500 and i.MX RT600 available as examples in <install_dir>/ide/Examples/Flashdrivers/NXP/iMXRT. Improvement: [Peripherals+] Peripherals+ view design was changed to support register group expansion directly into the Peripherals+ view, with no extra Memory View usage. Consequently, all elements shown before in Memory View are now available directly in the Peripherals+ view: values, bitfields, details. Reset value can be inspected as well together with the rest of the register elements. Improvement: [IDE] Added a link to MCU-Link firmware page in 'Additional resources' menu entry under Help's main menu. Improvement: [IDE] Toolbar naming and grouping: some icons re-grouped to reflect better categories and functionalities. Improvement: [SWO] Adapt SWO trace config error to better reflect possible causes. Improvement: [Flash Programmer] Use probe serial number instead of probe index when generating command line. Fixed: [Flash Programmer][Command Prompt] Wrong usage of double quotes in GUI Flash Tool Command Line generates errors in command prompt execution. Fixed: [Flash Programmer][J-Link][Command Prompt - Windows] GUI Flash Tool preview command - lower pane script not working when project name contains spaces. Fixed: [Flash Programmer] Cannot program flash from Quickstart Panel if "preview command" is checked in launch config. Fixed: [Flash Programmer] Wrong usage of double quotes in GUI Flash Tool Command Line. Fixed: [Debugger] Cannot relaunch (using "Terminate and Relaunch") a running session. Fixed: [Debugger] Suspend "bubble" project crashes debugger connection on LinkServer when using Non-Stop mode. Fixed: [Debugger] Debugger sets two breakpoints at the same address when debugging with J-Link. This generates a warning when trying to restart the debug session. Fixed: [Debugger] Always meet "Not Responding" issue when clicking the debug button without build first (for larger projects). Fixed: [Debugger] J-Link debug button does nothing when load image is set. Fixed: [Debugger] hello_world doesn't read the input from the console. Fixed: [Debugger] "Interrupt failed" pop-up error window during debug with FRDM-K64F and LPC-Link2 for some projects. Fixed: [Debugger] First attempt to manually modify the PC register is ignored. Fixed: [Debugger] Exceptions occurring while closing a project with an active debug session. Fixed: [Debugger] Restart not working in attach mode. Fixed: [Debugger][88MW320] Attach to a running target with PEmicro on FreeRTOS projects starts with faults. Fixed: [Debugger][88MW320] Cannot debug twice with J-Link and PEmicro. Fixed: [Debugger][FreeRTOS] Heap and Stack Usage View shall work with FreeRTOS enabled projects. Fixed: [Debugger] Multiple J-Link instances (named as "3rd party CMSIS-DAP") appear in Probes Discovered view: now these are filtered out. If a user still wants to see them, check the option from Preferences -> Debug Options -> J-Link Options -> Enable discovering of "3rd party CMSIS-DAP" probes. Fixed: [Debugger][J-Link] Master core in multicore context will be attached (instead a regular debug session) to target after debugging. Fixed: [Debugger][iMX RT595] Unable to flash application using crt_emu_cm_redlink raw command: Added preconnectscript argument to stub; Added --preconnectscript in the IDE's flash tool preview command window bottom; Note: Preconnect scripts have been changed to use variable a% instead of p% to receive the probe index. The user might need to update custom preconnect scripts. Fixed: [Energy Measurement] Format Y axis using a scale suitable for all displayed values (when having large Oy scale to represent data). Fixed: [Energy measurement] Unable to exit probe discovery for boards with unsupported firmware for SWO. Fixed: [Energy Measurement] The Energy measurement cannot collect if associated with a debug session and SWO is not initialized. Fixed: [Energy Measurement] Making a selection on the plot may lose part of the status line. Fixed: [Energy Measurement] Negative zero (-0.00) values shown. Fixed: [Energy Measurement] Lot of remaining allocated heap after clearing a plot. Fixed: [Energy Measurement] Incorrect representation of individual samples when the probe has been booted for some time: there are multiple values represented at the same point in time. Fixed: [Energy Measurement] Table containing analog sources not empty after terminating analysis session. Fixed: [Energy Measurement] When a view is already connected to a board and the underlying board is changed (without using the Terminate button), a subsequent operation will cause an error dialog with two entries and no useful information. View becomes unusable after this point. Fixed: [Energy Measurement] Export contains much more data than intended. Fixed: [Energy Measurement] Power/energy info in status line does not follow the currently visible part of the measurement. Fixed: [Energy Measurement] IDE now reports an error in the case the connection was interrupted while collecting power measurement data. Fixed: [Energy Measurement] Wrong resistor values displayed for QN9090 measurement circuit. Fixed: [Energy Measurement] Fixed 'None' in Tooltip for Cursor options in the Energy measurement toolbar. Fixed: [Energy Measurement] Export contains much more data than intended (from previous measurements). Fixed: [Energy Measurement] Old recorded values displayed on the graph. This makes a starting graph to look having unexpected data. Fixed: [Energy Measurement] Reading from target never finishes in some situations. Fixed: [Energy Measurement] Not all plotted values are using the same scale. This results into some values being displayed with wrong values. Fixed: [SWO][RT1010/RT1170/RT1160] Fixed SWO support for LinkServer. Fixed: [SWO] detecting clock feature is not overwriting the value. This is inducing some errors on enabling SWO features. Fixed: [SWO] Misleading error message when trying to enable SWO on sub-cores in a multicore environment. Fixed: [FreeRTOS] Sometimes cannot suspend FreeRTOS application using LinkServer. Fixed: [FreeRTOS] Modifying a register causes it to be set to 0. Fixed: [FreeRTOS] Attach to a FreeRTOS application returns faults. Fixed: [FreeRTOS] Empty tooltip for "Runtime" column from Tasks list view. Fixed: [FreeRTOS] Queue items incorrectly decoded in the Queues list view. Fixed: [FreeRTOS] No FreeRTOS queue data details shown. Fixed: [FreeRTOS] LinkServer FreeRTOS awareness does not activate in case of secure projects. Fixed: [FreeRTOS] GDB shuts-down when restarting RTOS debug session while stopped at BP. Fixed: [SDK Integration] The 'Open SDK handling preference page' button opens an unexpected option from Preferences. Fixed: [SDK Integration] SDK component replacement options is ignored. Fixed: [SDK Integration] It is not possible to disable "--sort-section=alignment" linker option from SDK generators. Fixed: [SDK Integration][SDK Details Page] Various NPE when using the details in Outline view. Fixed: [SDK Importer] Sometimes, board memory ranges are missing when importing an example project. Fixed: [SDK Importer] MCUXIDE mixes files from different versions of packages while importing examples. Fixed: [SDK Importer] All SDKs are present after clicking on the outside of SDKs image areas. Fixed: [SDK Importer] The linked example from Board SDK Wizard is not visible in Import SDK example Wizard. Fixed: [SDK Importer] Selected SDK, in the case of multiple SDKs using the same device, is not honored when importing or creating an example project. Fixed: [SDK Importer] SDK Import Wizard gives the wrong selection after it's opened and choose expand arrow. Fixed: [SDK Importer] CMSIS component with "type: CMSIS" is ignored when importing sdk project. Fixed: [SDK Importer] Boards vs device filter doesn't work when clicking in "Available boards" section but outside the board picture areas. Fixed: [SDK Importer] Non-multicore projects of boards with multicore support have master decorator when created. Fixed: [SDK Importer] Doc folder is declared as source folder in versions 2.9.x of the RT SDK. Fixed: [SDK Importer] SDK cannot set default launch config options for J-Link. Fixed: [SDK Importer] Fail to use an SDK with "/" included in the family name. Fixed: [SDK Importer] Project-specific linker file is ignored for MCUXIDE. Fixed: [SDK Importer] Default components are now displayed for a device project. Fixed: [SDK Importer] "Select SDKs for selected MCU" widget is not correctly populated when 2 SDK are installed for the same device. Fixed: [SDK CLI] project.build command exits with null pointer exception when use.all.components is set on true. Fixed: [SDK CLI] example.build command not working on multicore projects. Fixed: [SDK CLI] Command line will generate project name with not allowed character ("(", ")"). Fixed: [SDK CLI] Null pointer exception when using sdk.validate command. Fixed: [SDK CLI] Null pointer exception obtained when using -help argument. Fixed: [NPW] Creating a project using "Makefile Project using Existing Code" template, fails at debugging with LinkServer. Fixed: [NPW] Device project template is not correctly referred when using NPW to create a project with "selected device without board". Fixed: [NPW] Unable to create a project for the second board when 2 SDK for the same device are installed. Fixed: [Image Info] missing functions from CallGraph building in release build configuration. Fixed: [Image Info] CallGraph doesn't display stack info for c symbols located within cpp sources. Fixed: [IDE] Key binding conflict reported with new workspace. Fixed: [IDE] Tooltips missing for PEmicro Debugger Launch Configuration Startup Tab. Fixed: [Dark Theme] Usage in Heap and Stack Usage view. Fixed: [Dark Theme] pop-up hover not readable for longer preference text. Fixed: [Dark Theme] Selection is not visible in the Installed SDKs list. Fixed: [Dark Theme] MCUXpresso Icon in Smart Import Wizard shows white corners. Fixed: [Installer] Uninstaller error in the case of uninstall with a started eclipse session.   Known issues LPC55S16 TrustZone examples might not work with J-Link. Workaround: Use LPC-Link2 FW on on-board probes for TrustZone projects. SWO issues on iMX RT500 / iMX RT600 / LPC55xx when debugging with J-Link. Workaround: Choose other debugger probes for SWO usage on that particular list of devices. ITM console does not work as input console. Workaround: none, this will be fixed in a further release version. While installing the product, users may encounter a security alert from the operating system stating that some of the software comes from an unknown publisher. Workaround: If this happens it is safe to allow access. This will be corrected in a future release. In the case of an SDK component removal, the build process will fail if the component was also containing linked libraries. Workaround: Manually remove the libraries referenced by that component at project settings -> MCU Linker -> Libraries, then rebuild. 88MW320 with PEmicro and SDK version 2.9.5 or older: Debugging a project linked to flash with a PEmicro probe stops with faults at the start of the debug session. The target does reach main() if the execution is continued after the faults. Workaround: To remove the faults, enable "Launch Configuration -> Startup tab -> Set PC (absolute hex address or symbol)" and set it to "ResetISR". This workaround should not be used when attaching. "Open MCUXpresso SDK Builder" web link (from "Installed SDKs" view) is not correctly rendered within Eclipse's Internal Browser feature due to discontinued support for Internet Explorer for NXP web pages. Workaround: Go to Preferences -> General -> Web Browser and select "Use external web browser".

  We are pleased to announce that MCUXpresso IDE v11.2.1 (build 4149) is now available. This is a maintenance release that builds upon the previous MCUXpresso IDE v11.2.0 release, and we recommend that all existing users download and install this new version.   Installer Downloads  To download the installers for all platforms, please login to our download site via:  https://www.nxp.com/mcuxpresso/ide/download   Documentation  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: https://www.nxp.com/mcuxpresso/ide/documentation   Notification of future releases  To receive notifications about future releases, please follow : MCUXpresso IDE - Release History    Summary of Changes - version 11.2.1 - October 2020 Upgraded: newer SEGGER J-Link software (v6.86). Upgraded: newer PEmicro plugin (v4.7.6). Upgraded: Version v8.1 of MCUXpresso Config Tools. Added: i.MX RT1170 B0 support. Added: i.MX RT1024 support. Added: LPC55S06 support. Added: K32W061 support. Added: MCU-Link debug probe support. MCU-Link is a new debug probe solution being developed for NXP LPC, Kinetis and i.MX RT targets. Feature: Auto-debug slave project(s) for multicore projects option becomes default option for multicore debug purpose (for LinkServer debug connection only). That means, in the case of multicore projects on which master project refers one or several slave projects, debug sessions will be automatically started for slave projects after initiating debug with the master project. Option is set by default on: Window -> Preferences -> MCUXpresso IDE -> Debug Options -> LinkServer Options -> Miscellaneous -> Enable Auto-debug slave project(s) for multicore projects. If you don't want to have this feature enabled (so if you want to start debug sessions for each core independently), uncheck this option. Improvement: Community forum accessible now from the main toolbar too (together with the older link from Help->MCUXpresso IDE support forum). The default selection will open the community web inside the IDE. If you want to set the default browser as external browser, use Window->Preferences->General->Web browser->"Use external web browser". Improvement: [RT600] Clean up on RT600 flash drivers (SDK now references the new drivers): Add drivers for MXIC_OPI connected via FlexSPI_A port Add drivers for QSPI drivers (SFDP) connected via FlexSPI_B port Add drivers for QSPI drivers (SFDP) connected via FlexSPI_A port Remove MIMXRT600_SFDP_* drivers generated by the old project Fixed: [RT595] Cannot debug flash application with J-Link. Fixed: [RT500][RT600] JLink launch config default resets: Re-enable resets in JLink launches for RT500/RT600 The most recent JLink versions properly handle resets for RT500 & RT600 devices. Fixed: [RT500] QSPI flash drivers: driver was incorrectly using QSPI DDR instead of SDR. Fixed: [LPC55S69] Implemented DWT (Data Watchpoint and Trace) component for ArmV8. This fixes the SWO Data trace not working issue. Fixed: Sometimes the linkserver semihosting console stops working. Fixed: 'mismatched input' warning reported for linker file. Fixed: Flash programming using JLink via JTAG. Fixed: The running environment (PC/SP) for RAM applications is now properly initialized by the debugger when using JLink/PEmicro. Fixed: JLink scripts needed by SDK examples are not copied correctly when installing the SDK from a folder. Fixed: Selection of a driver in NPW makes the Library Type and Floating Type to become empty. Fixed: [Dark Theme] highlighting makes text unreadable. Fixed: [Dark Theme] not working on Ubuntu 18. Fixed: [Dark Theme] Text is not visible for Blocked jobs in FreeRTOS. Fixed: [Dark Theme] Peripherals view - some registers have yellow background making it hard to read. Fixed: [Dark Theme] Line highlighting in editor makes variables text unreadable. Fixed: [Dark Theme] Display issue for the "Probes discovered" window on Mac. Fixed: [Dark Theme] Low contrast on text vs. background when a word is high-lighted by having cursor selection on it. Fixed: [RT5xx] Unable to Restart flash-based session on EVK Rev C1 board. Fixed: [LPC55xx] LinkServer debug cannot recover LPC55xx from deep sleep. Fixed: [LPC4337] Flash programming over JTAG not working on the M4 core. Fixed: [LPC845] Debug fails when SRAM is split into sub-blocks. Fixed: [Dark Theme] Low contrast on text vs. background when a word is high-lighted by having cursor selection on it. Fixed: Outline view displays empty table header when selecting an SDK. Fixed: Not all dependency components are linked to project when the dependency is added from Config Tools. Fixed: Initialize execution environment when debugging RAM target application using Segger J-Link. Fixed: NPE occurred while using board SDK creator and adding a flash driver.

We are pleased to announce that MCUXpresso IDE v11.8.0 (build 1165) is now available. This is  a major new version of the IDE and contains new features, enhancements and bug fixes over the previous versions, including latest announced MCUXpresso IDE v11.7.1.   Installer Downloads  To download the installers for all platforms, please login to our download site via:  https://www.nxp.com/mcuxpresso/ide/download   Documentation  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.   Notification of future releases  To receive notifications about future releases, please follow: MCUXpresso IDE - Release History    Summary of Changes - version 11.8.0 - August 2023 Upgraded: Eclipse version to 2022.12 (Eclipse Platform 4.26.0 / CDT 11.0.0). Upgraded: MCUXpresso IDE integrated with OpenJDK Runtime Environment Temurin-17.0.5+8. Upgraded: GNU ARM Embedded Toolchain to version 12.2.Rel1. Upgraded: Version v14 of MCUXpresso Config Tools. Upgraded: ARM CMSIS-Pack Eclipse Plug-ins 2.8.0. Upgraded: Newer SEGGER J-Link software (v7.88m). Upgraded: Newer PEmicro plugin (v5.6.7). Synchronization with SDK v2.14.x. Added support for MCXN9xx devices. Added support for RW61x devices. Feature: New IDE build for Mac with native Apple silicon support. See download section for the new product. Feature: LinkServer LPC-Link2 firmware now softloaded as v5.460 which offers support for powering certain RT1xxx EVK boards (which incorporate on-board debug probes based on LPC-Link2 hardware) through the USB debug connection. Feature: [Open-CMSIS-Pack] Extended integration with ARM CMSIS-Pack Eclipse Plug-ins.  Now adding a new Open-CMSIS-Pack component is managed by ARM CMSIS-Pack Eclipse Plug-in. This brings support for: components dependency. multiple component selection. automatically check dependencies in the new multiple component selection view. copy configuration and template files to project. Note. If a project was created with the previous version of Open-CMSIS-Pack support, you'll be asked to remove or to keep the added components. Choosing "keep" involves preserving sources only, not the links with Open-CMSIS-Pack Manager. If you need to have them managed by ARM CMSIS-Pack Eclipse Plug-in (for the above mentioned available features) please choose "remove" and add them back. Feature: Added support for selecting library type in SDK CLI. Now redlib, newlib, newlib_nano can be selected as options when generating a project. Check MCUXpresso_IDE_Command_Line_User_Guide.pdf for details. Improvement: [SDK Integration] Allow the possibility to switch a project from one MCU device to another. Improvement: [SDK Integration] Reduced time required to import examples from zipped SDKs. Improvement: [SDK Integration] Optimize initial SDK GitHub cloning time by deferring cloning of examples until actually needed. Improvement: [Debugger] Discover Probes dialog warns if using MCU-Link probes running firmware which is incompatible with the current IDE version. Improvement: [Debugger] Add possibility to disable auto-debug of secondary project based on target name in Debug Options preferences. Improvement: [RTOS] Add preferences to control enablement of RTOS TAD logging consoles. This prevents showing up unwanted or not used consoles. Go to Preferences -> MCUXpresso IDE -> RTOS TAD -> (Desired) RTOS -> Logging configuration and select or unselect "Create logging console and log messages from TAD plugin". Improvement: [SWO] Error caused by input in the ITM console now should also be displayed inside the console. Improvement: [IDE][Quickstart Panel] Added link to executable import wizard in Quickstart Panel. Improvement: [IDE] Add 'bash' shell executable in buildtools/bin folder on Windows. Improvement: [Installer] Support silent installation for Linux installers (deb.bin packages). This can be executed using: <install_package>.deb.bin -- --acceptLicense. Fixed: [SDK Integration] Unexpected disk space consumption at "Refresh" operation. Fixed: [SDK Integration] Error reported when creating a project from GitHub SDK with a board selection from a standalone SDK. Fixed: [SDK Integration] Include Paths list is duplicated after refreshing SDK components. Fixed: [SDK Integration] New Project Wizard incorrectly computes anyOf dependency for multi core component. Fixed: [SDK Integration] C startup file is incorrectly added in C++ project after refreshing SDK components. Fixed: [SDK Integration] App SW Packs fail to import on IDE starting with IDE v11.7.0 and SDK v2.12 and v2.13. Fixed: [SDK Integration] Exception error is displayed when user scrolls in component list from SDK Wizard window. Fixed: [SDK Integration] Cloning more than one GitHub SDK repository makes the second repository unusable. Fixed: [SDK Integration] Deselecting components with dependencies doesn't display warnings. Fixed: [SDK Integration] Unable to deactivate an already installed Git SDK repository from Installed SDKs view. Fixed: [SDK Integration] Build error is obtained when some specific components (serial_manager_*) are changed from SDK Management -> Manage SDK Components view. Fixed: [SDK Integration] Progress is incorrectly reported in NPW and SDK Import Wizard. Fixed: [SDK Integration] Importing projects may introduce wrong dependencies between SDK components which result in build failure. Fixed: [Toolchain integration] Building some projects may be shown as failed due to linker warnings misinterpreted as errors. Fixed: [Toolchain Integration] Project is always rebuilt after restarting the IDE. Fixed: [Executable Importer] Cannot use Binary Utilities with the imported ELF. Fixed: [Managed Linker Script] Sometimes .bss sections are unexpectedly part of the output bin/s19 images. These are now declared as NOLOAD in the linker scripts. Fixed: [Flash Programmer] KW45B41Z board should not have Resurrect locked Kinetis device option. Fixed: [Flash Programmer] Flash tool not writing .flash_config section from ELF. Fixed: [Debug][LPC55S36 A1] Restart does not work. Fixed: [Debug] Null pointer exception when creating new launch config for LinkServer. Fixed: [Debug] Broken SWO functionality on non LPC-Link2/MCULink probes (Arm ULINKplus). Fixed: [Debug][Multicore] "Step Return All Debug sessions" throws error while in source code. Fixed: [Debug][ARMv6-M] The default VECTRESET set for flash reset has no effect since it is not supported for ARMv6-M MCUs. Use SOFT reset instead. Fixed: [Debug][PEmicro & LinkServer] GUI Flash Tool fields are pre-filled with wrong information for PEmicro when a debug launch is previously created, or are not implemented when using LinkServer debug probes. Fixed: [Debug][PEmicro] TrustZone projects cannot be debugged because non-secure image is not programmed in flash. Fixed: [Debug][LinkServer] Semihosting operations fail while debugger is detached and may not recover when re-attaching. Fixed: [Debug][LinkServer] Various semihosting operations fail when using LinkServer debug probe. Fixed: [Debug][LinkServer][SWO] Support for SWO trace using CMSIS-DAP1.1 SWO probes is broken. Fixed: [Debug][LinkServer] Debug session launch is very slow on LinkServer compared to other probes on some Windows PCs. Fixed: [Debug][Linkserver] Cannot boot LPC-Link1 when a LPC-Link2 probe configured for DFU booting is also present. Fixed: [Energy Measurement] View should not allow attaching to debug session on targets with no measurement support. Fixed: [Enery Measurement] Error might be encountered when successively connecting various probes and using "Out of debug" mode. Fixed: [FreeRTOS] Exception occasionally encountered when resuming or pausing the debug session of a FreeRTOS project with non-stop GDB option disabled and Peripherals Window open. Fixed: [FreeRTOS] In 'freertos_hello' example application, 'hello' task is shown as "Running" even before having the scheduler running. Fixed: [SWO] When SWO Counters view is resumed, also the SWO Data view is resumed automatically. Fixed: [IDE] IDE Linker File Parser fails for question mark operator. Fixed: [IDE] Update icons to address some problems on dark theme and high DPI (macOS Retina) displays.   Known issues  Please follow the KnownIssues.txt file from installation layout for a detailed list. Note. Additional issues that will be found post-release will be added in an online version also aiming to describe workarounds when available

We are pleased to announce that MCUXpresso IDE v11.5.1 (build 7266) is now available. This is a maintenance release that builds upon the previous MCUXpresso IDE v11.5.0 release, and we recommend that all existing users download and install this new version.   Installer Downloads  To download the installers for all platforms, please login to our download site via:  https://www.nxp.com/mcuxpresso/ide/download   Documentation  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: https://www.nxp.com/mcuxpresso/ide/documentation   Notification of future releases  To receive notifications about future releases, please follow : MCUXpresso IDE - Release History    Summary of Changes - version 11.5.1 - April 2022 Upgraded: CDT from CDT 10.3.0 to CDT 10.3.3. This is intended to address: https://bugs.eclipse.org/bugs/show_bug.cgi?id=575903 issue. Upgraded: Newer SEGGER J-Link software (v7.62c). Upgraded: Newer PEmicro plugin (v5.2.0). Added: [NPI] RT1060X (RT1060 phantom) support. Feature: [Flash Programmer][RT1160/RT117x] Add flash driver for QSPI on FlexSPI2 Port A. Fixed: [Debugger] Notifications about new MCU-Link firmware releases may not be shown in the Probes Discovery dialog. Fixed: [Debugger] Debug operations are slow while Peripherals+ window is open on targets with lots of registers (like RT1160 or RT117x). Fixed: [Project Manager][RT1160/RT117x] Flood of the -D__MULTICORE_MASTER in the .cproject. Fixed: [Project Manager][RT1160/RT117x] M7 C++ project failed to load the M4 project (in the case of multicore configuration) on a particular application. Now exdata sections are placed before heap and stack sections in generated linker files (when using Managed Linker Script configuration) compared with previous version where exdata sections were placed before data sections. Fixed: [Peripherals+][LPC546xx] EMC register location/offset is incorrect in Peripherals+ window. Fixed: [Energy Measurement] Instability if Energy Measurement view is used together with SWO Profile Known issues Please follow the KnownIssues.txt file from installation layout for a detailed list. Note. Additional issues that will be found post-release will be added in an online version also aiming to describe workarounds when available.

We are pleased to announce that MCUXpresso IDE v11.3.1 (build 5262) is now available. This is a maintenance release that builds upon the previous MCUXpresso IDE v11.3.0 release, and we recommend that all existing users download and install this new version.   Installer Downloads  To download the installers for all platforms, please login to our download site via:  https://www.nxp.com/mcuxpresso/ide/download   Documentation  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: https://www.nxp.com/mcuxpresso/ide/documentation   Notification of future releases  To receive notifications about future releases, please follow : MCUXpresso IDE - Release History    Summary of Changes - version 11.3.1 - April 2021 Upgraded: Newer SEGGER J-Link software (v6.98a). Upgraded: Newer PEmicro plugin (v4.9.1). Added: 88MW320 support. Added: K32W041A support. Added: i.MX RT1160 support. Feature: Added MCU-Link firmware version check in MCUXpresso IDE: When connecting to target, "Probes discovered" will indicate if there are debugger probes that would require update; Each discovered probe will clearly indicate (by a warning icon) if a firmware update is available; Tooltip on the mentioned probes will indicate the firmware's download location and its version. Fixed: [RT1170] Can't download image to RT1170-EVK when SRAM_ITC_cm7 is located as the first item in RAM blocks in Memory configuration editor. Fixed: [RT1170][CM4 boot] Error programming flash in SDP or empty flash situations. Fixed: [RT5xx/RT6xx] wrong image type (at offset 0x24) in generated executable file. Fixed: [KW38] Instruction Trace window does not pull the assembler instructions. Fixed: [K32W041AM] SWO Trace not working. Fixed: SDK cannot set default launch config options for Segger. Fixed: Exception if the IDE is launched right after installation process, having all checkboxes for additional documentation selected. Fixed: Welcome page not appearing at startup. Fixed: Program and Erase Flash shortcuts from Quickstart Panel are also launching an unexpected debug session on the end of their normal operation. Fixed: LinkServer: Modifying from debugger 8-bit or 16-bit data residing at addresses not aligned to 32 bits may alter data beyond the intended range up to the next 32-bit address.

We are pleased to announce that MCUXpresso IDE v11.3.0 (build 5222) is now available. This is a major new version of the IDE and contains new features, enhancements and bug fixes over the previous versions, including latest announced MCUXpresso IDE v11.2.1.   Installer Downloads To download the installers for all platforms, please login to our download site via:  https://www.nxp.com/mcuxpresso/ide/download   Documentation 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: https://www.nxp.com/mcuxpresso/ide/documentation    Notification of future releases To receive notifications about future releases, please follow : MCUXpresso IDE - Release History    Summary of Changes - version 11.3.0 - January 2021 Upgraded: Eclipse version to 2020.06 (Eclipse Platform 4.16.0 /  CDT9.11.1). Upgraded: IDE now integrates with OpenJDK8. Upgraded: GNU ARM Embedded Toolchain to GCC9-2020-q2-update. Integrated: GNU test coverage (gcov) and performance analysis (gprof) tools and Eclipse plugins. Upgraded: Version v9 of MCUXpresso Config Tools. Upgraded: Newer SEGGER J-Link software (v6.88c). Upgraded: Newer PEmicro plugin (v4.8.5). Added: i.MX RT1170 B0 support. Added: i.MX RT1024 support. Added: RT500 B2 support. Added: K32W061 support. Added: K32W041AM support. Added: LPC55S06 support. Added: MCU-Link probe debug support. Feature: Added Energy Measurement view, aiming to replace the Power Measurement view. Main capabilities: The new view comes with the same feature-set as the old Power Measurement view; From a GUI perspective, it offers consistent look & feel with other views that display and controls graphs (e.g. Global Variables, SWO-related views); Compatible with existing LPCXpresso boards having on-board power measurement circuits; Power and energy estimation capability: in order to enable power/energy measurement/estimation the user should add a reference voltage in the Config tab section from Energy Measurement view. For convenience and more precise measurement, the user can press "Read from target" which will automatically generate a reference voltage computed as an average value (of the voltage) measured for the last 500msec. Energy and power will be displayed in the status line of the plot area, showing the min/max/average power values and the energy value for the measurements visible in the graph, or over a particular time range selection. Multiprobe and multiview support: the feature is capable to open multiple views, each view can be connected to a different probe (that is capable to measure analog). The probe can be selected from Probe Discovery feature available in the Energy Measurement view toolbar. Data collecting during an out-of-debug session and also during an active debug session; Data collecting with an active debug session while the core is in debug mode. Behavior is controlled via toolbar buttons; Configuration of the server-side (rltool) and of the IDE using the Config tab within the view; Import/Export data functionality for offline analysis: (buttons on the Energy view toolbar). The user is able to save (Export data, in a zip format) the data collected within the view, having the possibility to load the saved data (Import data) later, in the same view or another one. Loading saved data in the Energy Measurement is not requiring physical connection to the target; Extended LPC-Link2 support for all targets having onboard measurement circuit: LPCXpresso546x8/540xx/54S0xx, LPCXpresso54102, LPCXpresso51U68/54114, QN90x0/JN518x/K32W0x1. As a side note, if there is any other LPC-Link2 board having power measurement capability, the user can use an existing configuration (and change the resistor value if necessary); See MCUXpresso_IDE_Energy_Measurement.pdf (or Help -> Help Contents) for details. Feature: Auto-debug slave project(s) for multicore projects option becomes default option for multicore debug purpose (for LinkServer debug connection only). That means, in the case of multicore projects on which primary project refers one or several secondary projects, debug sessions will be automatically started for secondary projects after initiating debug with the primary project. Option is set by default on: Window -> references -> MCUXpresso IDE -> Debug Options -> LinkServer Options -> Miscellaneous -> Enable Auto-debug slave project(s) for multicore projects. If you don't want to have this feature enabled (so if you want to start debug sessions for each core independently), uncheck this option. Similar, Auto-debug slave project(s) for multicore projects option becomes default option for multicore debug purpose for PEmicro too. Option is set by default on: Window -> Preferences -> MCUXpresso IDE -> Debug Options -> PEMicro Options -> Enable Auto-debug slave project(s) for multicore projects. Improvement: Enhance SWO views: SWO Config: added new Tab for data traffic statistics, configuration for ITM Stimulus ports; SWO Profile: added samples and details tabs; SWO Data: added plot (similar to Global Variables); SWO Stats: moved inside SWO Config; ITM Console: added one tab for each stimulus port. Improvement: [RT600] Clean up on RT600 flash drivers: Add drivers for MXIC_OPI connected via FlexSPI_A port; Add drivers for QSPI drivers (SFDP) connected via FlexSPI_B port; Add drivers for QSPI drivers (SFDP) connected via FlexSPI_A port; Remove MIMXRT600_SFDP_* drivers generated by the old project (SDK now references the new drivers). Improvement: Drop-down boxes from several tables require two user operations for reaching the actual items from the list. Reduced now to a single operation (single click). Improvement: Extend CLI functionality - Add new command to list SDK info:   -filter=<string> : filters the available information based on regex expression string. e.g. -filter=K64 will display all data containing K64 string. See SDK command line documentation within the layout (MCUXpresso_SDK_Command_Line_User_Guide.pdf). Improvement: Merge c_include path section into cpp_include path section for cpp project in project settings. Improvement: New project wizard is now capable to handle HW with dual primary/secondary roles (i.e. RT1170). From SDK Wizard page, any core can be selected according with the secondary/primary SDK description, plus it can be selected as standalone (application). Improvement: Community forum accessible now from the main toolbar too (together with the older link from Help->MCUXpresso IDE support forum). The default selection will open the community web inside the IDE. If you want to set the default browser as external browser, use Window->Preferences->General->Web browser->"Use external web browser". Fixed: [RT500] QSPI flash drivers: driver was incorrectly using QSPI DDR instead of SDR. Fixed: [RT500][RT600] J-Link launch config default resets: Re-enable resets in J-Link launches for RT500/RT600 The most recent J-Link versions properly handle resets for RT500 & RT600 devices. Fixed: [RT500] Unable to Restart flash-based session on EVK RevC1 board. Fixed: [RT685] "Unsupported or unrecognized format error" dialog when using the installed SDK. Fixed: [LPC55S69] Implemented DWT (Data Watchpoint and Trace) component for ArmV8. This fixes the SWO Data trace not working issue. Fixed: [LPC55S06] SWO support. Fixed: [LPC55xx] LinkServer debug cannot recover LPC55xx from deep sleep. Fixed: [LPC845] Debug fails when SRAM is split into sub-blocks. Fixed: [LPC4337] Flash programming over JTAG not working on the M4 core. Fixed: [LPC54114] SWO Trace is not working with PEmicro. Fixed: [FRDM-K64] Removed unexpected warning reported in map file in a project. Fixed: [JN5189/QN9090/KW32W041AM] Improve OOB experience with (factory) erased devices. Fixed: IDE 'Utility' menu does not work for linked Folders. Fixed: Defined symbols are added prematurely (even when no component is selected in NPW). Fixed: Selection of a driver in NPW makes the Library Type and Floating Type to become empty. Fixed: "ERROR: fatal error: board.h: No such file or directory" error reported if build a new created project with no board support. Fixed: Library type is not changing correctly when using SDK Wizard. Fixed: SDKs for older LPCs failing to set CRP up correctly. Fixed: Outline view displays empty table header when selecting an SDK. Fixed: Issues when uninstalling a SDK plugin. Now "Installed SDKs" and "Install MCUXpresso SDK" views are in sync and report the right installation status of a SDK. Fixed: On explicit include paths in the project setting, the include paths are mixed between asm and c type. Fixed: Outline view displays empty table header when selecting an SDK. Fixed: Null pointer exception on generating example xml. Fixed: Build error when use MCUXpresso IDE command line with non-existing include. Fixed: SDK command line: pre and/or post build steps options not available in example.xml file. Fixed: J-Link scripts needed by SDK examples are not copied correctly when installing the SDK from a folder. Fixed: MCUXpresso linked projects compile errors on multicore platforms. Fixed: Compile errors reported on a project imported from a generate example.xml. Also fixed the CLI build failing on the same example.xml scenario. Fixed: Unexpected memory usage reported (over 100% occupied memory) by Image Info. Fixed: Programming empty pages for ERASE_WO devices when flash hashing is enabled. Fixed: 'debug interface type' identification shown in the "Debug messages" console. Fixed: "Terminate" operation does not kill the redlinkserv.exe process. Fixed: "Terminate" button appears disabled after the first "Suspend" for PEMicro and J-Link debug connection. Fixed: J-Link auto selection results in not working connection. Fixed: Flash programming using J-Link via JTAG. Fixed: The running environment (PC/SP) for RAM applications is now properly initialized by the debugger when using J-Link/PEmicro. Fixed: Debugger Console output stops working when debugging secure project. Fixed: Error reported when SWO clock speed dialogue cancelled. Fixed: FreeRTOS tasks list not populated correctly in some situations. Fixed: SVD viewer shows-up with empty peripherals list. Fixed: Live Variables: Unable to create expression with casts. Fixed: Global Variables: T0 will remain -0 while moving the Graph to the right. Fixed: [Dark Theme] highlighting makes text unreadable. Fixed: [Dark Theme] Text is not visible for Blocked jobs in FreeRTOS. Fixed: [Dark Theme] Peripherals view - some registers have yellow background making it hard to read. Fixed: [Dark Theme] Line highlighting in editor makes variables text unreadable. Fixed: [Dark Theme] Display issue for the "Probes discovered" window on Mac. Fixed: [Dark Theme] Low contrast on text vs. background when a word is high-lighted by having cursor selection on it. Fixed: [Dark Theme] Manage SDK Components window is not updated. Fixed: [Dark Theme] Various improvements on Disassembly, Memory, Peripherals, headers in views, editor, git plugin. Fixed: [Dark Theme] Install plugin SDKs window shows white rectangles around icons. Fixed: [Dark Theme] Line number background is too bright. Fixed: [Dark Theme] Install MCUXpresso SDK view shows white background while selecting table headers.

This video shows how to import any of the SDK example projects and use it as a starting point for you own project. Enjoy!

This video shows how to import MCUXpresso SDKs into the MCUXpresso IDE.

Checking disassemble code is often needed for programmers when developing a project. This article will introduce two methods of generating disassemble file with GNU utility objdump under MCUXpresso IDE 10.1.0. If user needs demo code, please send me community internal message.

As part of my university engagement, I have posted an overview article about the new MCUXpresso IDE: (external link): MCUXPresso IDE: Unified Eclipse IDE for NXPs ARM Cortex-M Microcontrollers | MCU on Eclipse  I hope you find it useful, Erich

This exercise demonstrates how to port a project using MCUXpresso IDE and SDK from one RT MCU to another.  The exercise starts with an SDK demo project for the MIMXRT1060-EVK board, and ports to the IMXRT1050-EVKB board.   The "MCUXpresso IDE User Guide" installed with the IDE gives this warning: changing a project’s associated MCU should not be undertaken unless you have a total grasp of the consequence of this change.  Therefore rather than changing a project’s associated MCU, it is strongly recommended that instead a new project is generated for the desired MCU and this new project is edited as required.  However, on occasion it may be expedient to reset a project’s MCU (and associated SDK)   I also recommend using a SDK project intended for the final MCU, and just port the application source files to it.  But here are the steps to port the project.  Also note, these two boards use different flash types by default.  In this example, the IMXRT1050-EVKB was reworked to use the QSPI flash on the board following Appnote AN12108.  Once the RT1050 EVK is modified to use the QSPI flash, it is the same flash used on the RT1060 EVK.   Resources used in this exercise: IMXRT1050-EVKB board RevA1 MIMXRT1060-EVK board RevA2 MCUXpresso IDE v11.2.0 MCUXpresso SDK from Welcome | MCUXpresso SDK Builder  EVKB-IMXRT1050_SDK_2.8.2 EVK-MIMXRT1060_SDK_2.8.2   Attached to this post are two projects: Starting_evkmimxrt1060_iled_blinky.zip was the original SDK example running on the RT1060 EVK evkbmimxrt1050_iled_blinky_ported.zip is the final ported project, running from QSPI and RT1050     Following the "MCUXpresso IDE User Guide" section "Changing the MCU (and associated SDK)", changed the MCU to MIMXRT1052xxxxB.  Also changed the flash driver to MIMXRT1050_SFDP_QSPI.cfx.  If using Segger JLink, see https://wiki.segger.com/i.MXRT1050 to change the flash algorithm to QSPI.   And then changed the package/part number to MIMXRT1052DVL6B.   Changed the project name to evkbmimxrt1050_iled_blinky_ported Changed the C Compiler Preprocessor definitions to the SDK device CPU_MIMXRT1052DVL6B   Replaced the files from the SDK package EVKB-IMXRT1050_SDK_2.8.2 (Note: MCUXpresso IDE supports "SDK Project Component Management", which could also be used for updating some of these files.  See section "SDK Project Component Management" of the IDE user guide.  But I replaced the files manually myself from the RT1050 SDK package): device folder with the SDK files from EVKB-IMXRT1050_SDK_2.8.2.zip\devices\MIMXRT1052.  startup file from \EVKB-IMXRT1050_SDK_2.8.2.zip\devices\MIMXRT1052\mcuxpresso\ drivers files from \EVKB-IMXRT1050_SDK_2.8.2.zip\devices\MIMXRT1052\drivers\ board files, can use an SDK example for the ported device, or generate the clock_config and pin_mux files from the MCUXpresso Config tools xip files would also need to be updated if flash configuration changes.  In this example, both boards are using the same QSPI flash, and these files are the same.   Delete the .launch debug configuration file in the project.  MCUXpresso IDE will regenerate it.   With these changes, the ported project runs on the RT1050 EVK.