The Blinky project can be easily used to verify the basic tool setup. It is available for two different targets:

• Arm Cortstone-300 (Cortex-M55)
• NXP K32L3A60VPJ1A (dual-core Cortex-M0+/Cortex-M4)

It is compliant to the Cortex Microcontroller Software Interface Standard (CMSIS) and uses the CMSIS-RTOS v2 API for RTOS functionality. The CMSIS-RTOS v2 API is supported by various real-time operating systems, for example Keil RTX5 or FreeRTOS.

You have two options to flash the hardware target with Keil Studio:

1. Use the embedded debugger: when pressing the Run or Debug button, the embedded debugger is called to flash the application onto the target.
2. Use the Arm Debugger: in the tasks.json file, there is an entry for the new Arm Debugger. If you want to flash the target with this debugger, go to "Terminal --> Run Task..." and select "Flash K32 with Arm Debugger".

In both cases, use the "cm4" target in the selection pop-up:

You have two options to debug the hardware target with Keil Studio:

1. Use the embedded debugger: when pressing the Debug button, the embedded debugger is called to debug the application onto the target.

2. Use the Arm Debugger: in the launch.json file, there is an entry for the new Arm Debugger. If you want to debug the target with this debugger, go to the debug view (1), select the launch configuration in the drop-down at the top ("Arm Debug")(2), and press the debug button(3):

   

In both cases, use the "cm4" target in the selection pop-up:

• In the beginning, vioLED0 blinks in 1 sec interval.
• Pressing vioBUTTON0 changes the blink frequency and start/stops vioLED1.
• printf messages are shown on the serial console.

The board hardware mapping of vioLED0, vioLED1, and vioBUTTON0 depends on the configuration of the CMSIS-Driver VIO.

The output of the serial console can be observed in a Terminal window on VS Code.

The real-time operating system Keil RTX5 implements the resource management.

It is configured with the following settings:

• Global Dynamic Memory size: 24000 bytes
• Default Thread Stack size: 3072 bytes
• Event Recorder Configuration
  • Global Initialization: 1
    • Start Recording: 1

Refer to Configure RTX v5 for a detailed description of all configuration options.

MPS3 platform for Corstone-300 simulated by Arm Virtual Hardware (AVH).

The heap/stack setup and the CMSIS-Driver assignment is in configuration files of related software components.

STDIO is routed to USART0

Note: On AVH, the LEDs and the button are simulated in a graphical window.

The tables below list the device configuration for this board. The board layer for the NXP FRDM-K32L3A6 is using the software component ::Board Support: SDK Project Template: project_template (Variant: frdmk32l3a6) from NXP.FRDM-K32L3A6_BSP.13.0.0 pack.

The heap/stack setup and the CMSIS-Driver assignment is in configuration files of related software components.

The example project can be re-configured to work on custom hardware. Refer to "Configuring Example Projects with MCUXpresso Config Tools" for information.

Note: configured with Functional Group: BOARD_BootClockRUN

STDIO is routed to a debug console through Virtual COM port (DAP-Link, peripheral = LPUART0, baudrate = 115200)