This is the documentation for the latest (main) development branch of mcuxpresso sdk. If you are looking for the documentation of previous releases, use the drop-down menu on the left and select the desired version.

Locating example application source files

When opening an example application in any of the supported IDEs, a variety of source files are referenced. The MCUXpresso SDK devices folder is the central component to all example applications. It means the examples reference the same source files and, if one of these files is modified, it could potentially impact the behavior of other examples.

The main areas of the MCUXpresso SDK tree used in all example applications are:

  • devices/<device_name>: The device’s CMSIS header file, MCUXpresso SDK feature file and a few other files

  • devices/<device_name>/drivers: All of the peripheral drivers for your specific MCU

  • devices/<device_name>/<tool_name>: Toolchain-specific startup code, including vector table definitions

  • devices/<device_name>/utilities: Items such as the debug console that are used by many of the example applications

For examples containing an RTOS, there are references to the appropriate source code. RTOSes are in the rtos folder. The core files of each of these are shared, so modifying one could have potential impacts on other projects that depend on that file.

What is the plain load image?

The plain load image is linked to SRAMX. When building, it needs to be programmed to the external onboard flash. After reset, the bootloader starts to run. Then, it checks the image type (which is set in the image header, which resides in the startup code). If the type is plain load image, the bootloader copies the image to SRAMX, then jumps to SRAMX to run.

Parent topic:Locating example application source files

What is the XIP image?

When an XIP (Execute-in-Place) image is used, the MCU executes instructions and uses data directly from external (quad) SPI flash. When building, it needs to be programmed to the external onboard flash. After reset, the bootloader starts to run. Then, it checks the image type (which is set in the image header, which resides in the startup code). If the type is XIP image, the device executes in the external flash.

Parent topic:Locating example application source files

What is the SRAM target image?

The SRAM target image is linked to the SRAM address when building. When debugging, the SRAM target, the IDE just loads the image into SRAM to run.

Parent topic:Locating example application source files

Parent topic:MCUXpresso SDK board support package folders