Nuvoton NuMicro Cortex-M Pack

Description

Nuvoton NuMicro Cortex-M Pack is a complete development toolkit for Nuvoton’s NuMicro Cortex-M microcontrollers in Visual Studio Code.

Outline

• Features
• Requirements
• Getting Started
  • NuMicro Cortex-M Pack Environment Setup Guide
  • (Optional) Zephyr Project Setup Guide for Nuvoton NuMicro Cortex-M

Features

The extension pack integrates essential components to simplify embedded development, including:

• Essential extensions for VS Code.
• Configuration files.
• SVD (System View Description) support.
• OpenOCD setup for debugging.
• The PinView and LCDView help you with debugging.
• Template projects to help you get started.
• Extension version control prevents automatic extension upgrades from causing usage issues.
  • Caveat: You might be forced to use specific, fixed versions of the relevant extensions. For details, please see the sub-extension: Nuvoton Extension Version Manager.

Requirements

• Visual Studio Code: Version 1.95.0 or higher.
• Nu-Link_USB_Driver: Version 1.11 or higher. Nu-Link_USB_Driver download link

Getting Started

NuMicro Cortex-M Pack Environment Setup Guide

This guide walks you through setting up a NuMicro Cortex-M Pack project.

1. Install Required Extension Packs

   • Nuvoton NuMicro Cortex-M Pack

     

   • Fix Arm CMSIS Solution version at 1.56.0
   • Fix Arm Debugger version at 1.4.4

2. Prepare NuMicro BSP project

   • Go to Nuvoton Technology Corp, and download NuMicro BSP project.

3. Open VSCode folder in your project

   • Launch Visual Studio Code
   • Choose "Open Folder..." and select the VSCode folder in your project.

   

4. Add Nuvoton Debug configuration

   • Open .vscode/launch.json file, and insert the debug configuration in configurations
   • insert the debug configuration in configurations

   {
       "name": "Nuvoton Debug",
       "type": "cortex-debug-nuvoton",
       "request": "launch",
       "cwd": "${workspaceFolder}",
       "executable": "${command:embedded-debug.getApplicationFile}",
       "servertype": "openocd",
       "serverpath": "${command:openocd-helper.getOpenOcdPath}",
       "svdFile": "${command:openocd-helper.getSvdPath}",
       "configFiles": [
           "interface/cmsis-dap.cfg",
           "${command:openocd-helper.getOpenOcdConfigPath}"
       ],
       "runToEntryPoint": "main",
       "overrideLaunchCommands": [
           "monitor reset halt"
       ]
   }
   

   

5. Ensure your settings in "Manage Solution" are properly configured

   • Click on CMSIS in the active bar and then click on Manage Solution to set a context for your solution.
   • configure the Run & Debug settings.
   • Debug Configuration: Nuvoton Debug

     

6. Check Device Status

   • Make sure the device is recognized in Device Manager.
   • If a new VS Code instance is opened, the device in the Device Manager may be taken over by the newly opened VS Code. Close all instances of VS Code and restart to ensure proper device recognition.

     

7. Execute Build, Run and Debug

   • Build

     

   • Run

     

   • Debug

     

(Optional) Zephyr Project Setup Guide for Nuvoton NuMicro Cortex-M

1. Install Required Extension Packs

   Install the following extension packs:

   • Nuvoton NuMicro Cortex-M Pack
   • Zephyr IDE Extension Pack

   

   

   Use the Zephyr IDE buttons in the following steps to create the environment.

   

2. Creating a Zephyr Project from Sample Code

   Create a new project using sample code. Choose a project template provided by the Zephyr IDE.

   

3. Add a build configuration and choose your target board, e.g., NuMaker-PFM-M467.

   

4. Add Runner Configuration (OpenOCD) Configure the project runner to use OpenOCD.

   

5. Update Zephyr Project Runner Settings

   Go to View → Command Palette and run Update Zephyr Project Runner. Select the project to update the runner settings and refresh the settings.

   

   

   

   

6. Build Project and Flash to Target Use the build button to build and flash the firmware to your target board.

   

7. Create launch.json Create the launch.json file used for debugging.

   

8. Set the runToEntryPoint (optional) If you don’t want execution to stop at the main function when running in debug mode, set the runToEntryPoint parameter and specify the symbol function where you want it to stop (for example, Zephyr’s execution entry point z_arm_reset; for Nuvoton BSP projects, the entry point is Reset_Handler).

   

9. Set the target type Please choose the target type for debugging according to the project.

   

10. Select Debug Settings Select Nuvoton Debug Zephyr.

    

11. Enter Debug Mode and Start Monitor for Output Launch the debugger and open the monitor or terminal to view runtime output.