MCUXpresso SDK Documentation

Version: 26.09.00 26.06.00-lts 26.03.00 25.12.00 latest

Open on Repo Open an Issue

Source (.md/.rst) Page PDF (.pdf)

Getting Started with Repository-Layout SDK Package

Table of Contents

• Development Tools Installation
  • Quick Start: Automated Installation (Recommended)
  • Manual Installation
    • Essential Tools
      • Git - Version Control
      • Python - Scripting Environment
      • West - SDK Management Tool
    • Build System Tools
      • CMake - Build Configuration
      • Ninja - Fast Build System
      • Ruby - IDE Project Generation (Optional)
    • Compiler Toolchains
      • Setting Up Environment Variables
  • Verify Your Installation
    • Troubleshooting Installation Issues
• Workspace Structure
  • Top-Level Organization
  • SDK Component Layout
  • Example Organization
    • Common Example Files
    • Board-Specific Files
  • Device Support Structure
  • Middleware Organization
  • Documentation Structure
  • Understanding Example Structure
    • 1. General README: examples/demo_apps/hello_world/readme.md
    • 2. Board-Specific README: examples/_boards/{board_name}/demo_apps/hello_world/example_board_readme.md
• Installing 3rd Party Patch
  • What’s in the zip
  • Upgrade J-Link to V8.88 or later
  • Install the J-Link part (JLink.zip)
    • Verify the J-Link part
  • Install the IAR part (arm.zip)
    • Verify the IAR part
• RT2660 Debug Guide
  • The New Debugging Mechanism
  • Debug patch install
    • What’s in the zip
    • Install the J-Link part (JLink.zip)
      • Upgrade J-Link to V8.88 or later
      • Verify the J-Link part
    • Install the IAR part (arm.zip)
      • Verify the IAR part
  • Build Targets
    • Quick reference
    • Unified Linkage targets
    • RAM ONLY targets
  • Unified Linkage Targets
    • What is Unified Linkage?
    • Comparison with the legacy RT1xxx RAM-target flow
      • Side-by-side comparison
      • The key mental shift
    • Trade-offs
    • Common misconceptions
  • RAM ONLY Targets
    • Debug
      • ram_only
      • psram_only
    • Creating a bootable image
      • Option A: west build
      • Option A: IAR EWARM
  • eMMC Boot
    • Hardware adaptation
    • Boot mode setting
      • Fuse programming (production)
      • Auxiliary image workaround (development)
    • Downloading an image to eMMC
  • blhost
    • Prerequisites
    • Configuring BOOT_CFG0 for eMMC boot
    • eMMC operations
      • Writing an image to eMMC
      • Reading from eMMC
      • Erasing eMMC
  • Setup – IAR EWARM
    • Build
    • Debug inside IAR EWARM (C-SPY)
      • Using a CMSIS-DAP probe (default)
      • Using a J-Link probe
  • Setup – armgcc + J-Link
    • Build
    • Debug in Ozone with an armgcc ELF
  • Setup – SEGGER Ozone
    • RAM ONLY targets
    • Unified Linkage targets
      • Step 1: PC / SP configuration
      • Step 2: Save the project, then hand-edit .jdebug
      • Step 3: Debug and Attach
      • Known issues
  • Flow – Unified Linkage Debug
    • Unified Linkage Debug
  • Flow – ram_only Debug
    • ram_only Debug
  • Flow – psram_only Debug (XSPI NOR + PSRAM system)
    • psram_only Debug – XSPI NOR + PSRAM system
  • Flow – psram_only Debug (eMMC + PSRAM system)
    • psram_only Debug – eMMC + PSRAM, shadow fuse via xspi_nor auxiliary (recommended)
    • psram_only Debug – eMMC + PSRAM, shadow fuse via ram_only auxiliary
    • psram_only Debug – eMMC + PSRAM, fuse (production)
  • FAQ / Known Issues
    • A. Install and environment
      • A1. Device picker doesn’t show MIMXRT2663xxxxx_M85
      • A2. jlinkscript reports “Cortex-M85 not recognized”
      • A3. How do I know which version of the J-Link patch is actually loaded?
    • B. Debug behavior and source-level issues
      • B1. Ozone downloads OK but the target doesn’t run correctly
      • B2. Ozone stops on the right instruction but source view is wrong (IAR ELF)
      • B3. Editing PSRAM (0x80000000–0xAFFFFFFF) from the IDE memory window doesn’t stick
    • C. Bricking and recovery
      • C1. J-Link connect shows ROM Ver = 0xFFFFFFFF (or the debugger can’t attach)
      • C2. Prevention: manual “brake” to avoid bricking during clock / power setup
    • Getting help
  • eMMC Hardware Rework
    • MIMXRT2660-EVK
  • MIMXRT2660-EVK PSRAM Configuration
    • PSRAM on the MIMXRT2660-EVK
    • PSRAM Selection Macro
    • Where to set the macro
      • SDK repository (CMake build)
      • IAR Embedded Workbench
• Building Your First Project
  • Prerequisites
  • Understanding Board Support
  • Basic Build Process
    • Simple Build
    • Specifying Configuration
    • Alternative Toolchains
  • Multicore Applications
  • Flash an Application
  • Debug
  • Common Build Options
    • Clean Build
    • Dry Run
    • Device Variants
  • Project Configuration
    • CMake Configuration Only
    • Interactive Configuration
  • Troubleshooting
    • Build Failures
    • Getting Help
    • Check Supported Configurations
  • Next Steps
• Run a Demo Using IAR
  • Prerequisite: Ruby
  • 1. Generate the IAR project
    • Generate into a custom folder
  • 2. Open the project in IAR Embedded Workbench
  • 3. Build the demo application
  • 4. Run the demo application
  • Next steps