Getting Started with FRDM-IMX93 and MCU-LINK Pro for M Core Debugging

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

Getting Started with FRDM-IMX93 and MCU-LINK Pro for M Core Debugging

Getting Started with FRDM-IMX93 and MCU-LINK Pro for M Core Debugging

This guide walks you through the required steps to prepare your development environment and hardware for debugging the M core on the FRDM-IMX93 board using the MCU-LINK Pro. You’ll install the necessary firmware, perform minor hardware modifications, compile and flash a binary, and finally, initiate a debug session using MCUXpresso for VS Code.

Requirements:

  • FRDM-IMX93 Board

  • MCU-LINK Pro Debug Probe

  • Soldering Station (for minor rework)

  • PC Host with MCUXpresso for VS Code installed

  • Adapter Cables

 

Install Segger Firmware on MCU-LINK Pro

By default, the MCU-LINK Pro does not support i.MX processors. Installing the Segger firmware is essential for proper debugging.

Follow the firmware update guide to update your MCU-LINK Pro.

 

Rework the FRDM-IMX93 Board

The FRDM-IMX93 uses UART5 (shared with the BT module) for debug pins, which causes conflicts. To enable reliable debugging, remove the following resistors:

  • R3017

  • R3018

Note: After this modification, the Bluetooth module will no longer function under Linux.

Schematic:

Chavira_0-1748616335462.png

FRDM BOARD:

Chavira_2-1748616835371.png

 

Note: After this rework we can't use the Bluetooth module in Linux

 

Compile the Binary for the M Core

Ensure MCUXpresso for VS Code is properly installed.

 

Import the iMX93-EVK SDK

Chavira_0-1748619933509.jpeg

 

Import "hello world" example


Chavira_2-1748619983886.jpeg

Ensure that we are compiling a debug binary

Chavira_3-1748620017855.jpeg

 


Build Project

Chavira_4-1748620044672.jpeg

 

Flash the Binary using UUU Tool

Connect the FRDM Board to your Host PC via USB

Chavira_2-1749228564082.png

 


Enter Fastboot Mode in U-Boot Terminal

=> fastboot 0

 

On your Host PC, navigate to the binary location and flash it using the next commands:

$ cd <project_location>/armgcc/debug/

$ uuu -b fat_write sdk20-app.bin mmc X:1 hello_world.bin

Note: replace the X with 0 if you are booting from eMMC or 1 if you are booting from SD Card

Chavira_0-1749230229321.png

 

Connect MCU-LINK Pro to the Target

To set up debugging, connect the FRDM-IMX93 board to your host computer using the MCU-LINK Pro and the J-LINK Adapter for Cortex-M.



Chavira_0-1750689254774.png



FRDM-IMX93 Debug connector:

Chavira_1-1750689677035.png

 

Required Connections
Use the following pin mapping between the J-LINK Adapter and the FRDM-IMX93 debug connector:

 

J-LINK ADAPTER        -->         FRMD-IMX93

 V REF        -->      3.3v(RPI Connector pin 1 )

 SWDIO        -->      SWDIO (P14 pin 2)

 SWCLK        -->      SWCLK (P14 pin 1)

 GND        -->      GND (P14 pin 3)

 

Make sure all connections are secure before powering on the board.

 

Launch the M Core from U-Boot Terminal

Use the following commands in the U-Boot terminal:
=> fatload mmc X:1 80000000 hello_world.bin; cp.b 0x80000000 0x201e0000 0x10000;
=> bootaux 0x1ffe0000 0

Note: replace the X with 0 if you are booting from eMMC or 1 if you are booting from SD Card

Chavira_2-1749230331330.png

 

Start the Debug Session

Once the M core is launched, you can start your debug session in VS Code using MCUXpresso:

Chavira_0-1749230744360.png

 

Chavira_0-1750700999360.png

 

  
With the MCU-LINK Pro configured, the FRDM-IMX93 reworked, and the binary successfully flashed and executed, you are now ready to debug applications on the M core using MCUXpresso and VS Code. This setup enables a reliable development workflow for i.MX93-based projects.

No ratings
Version history
Last update:
‎06-23-2025 10:50 AM
Updated by: