MCUXpresso IDE Knowledge Base

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MCUXpresso IDE Knowledge Base

Labels

Discussions

Sort by:
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.
View full article
  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.
View full article
This video shows how to create, build and debug a new SDK project with MCUXpresso IDE. Enjoy!
View full article
This video shows how to import any of the SDK example projects and use it as a starting point for you own project. Enjoy!
View full article
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!
View full article
Attached MCUXpresso IDE fact sheet gives an overview about the IDE and its capabilities. More information is available on MCUXpresso IDE|NXP .
View full article
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
View full article
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.
View full article
[中文翻译版] 见附件 原文链接: https://community.nxp.com/community/mcuxpresso/mcuxpresso-ide/blog/2019/06/12/using-lpc55s69-sdk-trustzone-examples-with-mcuxpresso-ide-v1100
View full article
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
View full article
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.
View full article
This tip will show you how to re-trigger a full probe discovery.  The feature is very useful for the customer who may use multiple debug probes. The first time you debug a project, MCUXpresso IDE will perform a probe discovery operation and display the discovered Debug Probes for selection. This will show all Supported Probes that are attached to your computer. (Here you can see the default P&E Micro OpenSDA of FRDM-KL25Z board was found.) For any future debug sessions, the stored probe selection will be automatically used to match the project being debugged with the previously used debug probe. This greatly simplifies the case where multiple debug probes are being used. However, if a debug operation is performed and the previously remembered debug probe cannot be found, then a debug probe discovery operation will be performed from within the same family e.g. MCUXpresso IDE LinkServer, P&E Micro or SEGGER J-Link. (Here you can see there are two Probe search options: Search for PEMicroDBB97E74 again and Search for other attached PE Micro probes.) But if you want to use a different debug probe(for example: debug FRDM-KL25Z board with SEGGER JLink), click this blue debug icon will meet problem. Supported Probes dialog only show P&E Micro probes, it will not search other family of debug probes e.g. MCUXpresso IDE LinkServer or SEGGER J-Link.   Once a launch configuration file has been created, it will be used for the projects future debug operations. If you wish to use the project with a different debug probe, then simply delete the existing launch configuration and allow a new one to be automatically used on the next debug operation. Now click blue debug icon re-trigger a full probe discovery, and it show all Supported Probes that are attached to your computer again.
View full article
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. 
View full article