Quick Start
Overview
The Ameba development platform provides an out-of-the-box development experience with complete SDK, rich sample code, and comprehensive development ecosystem, helping developers efficiently achieve product prototype implementation and mass production deployment.
This section introduces how to set up the software environment for Ameba hardware development, covering the complete development process including SDK acquisition, development environment setup, project compilation, firmware flashing, and serial log monitoring, helping developers quickly complete the process from environment preparation to firmware operation.
Prerequisites
Hardware Requirements
Before starting development, please prepare the following hardware devices:
PC Host: Supports Windows or Linux operating systems
Ameba Series Development Board: Target hardware platform for application development, firmware flashing, and functionality verification
USB Cable: Type-C interface for connecting PC to development board
Software Requirements
SDK: Ameba FreeRTOS Software Development Kit, providing peripheral drivers, library files, compilation scripts, and development assistance tools
Toolchain: Cross-compilation toolchain for code compilation
Text Editor: Code editors such as VS Code
Drivers: USB to serial port driver (if required)
SDK Quick Start Flow Chart
Hardware Setup Guide
For information on how to use the Ameba SoC development board (EVB), please watch the official tutorial video: Ameba SoC EVB Usage
For detailed user guides for specific board models, please visit: EVB User Guide
Environment Setup
Please refer to the corresponding environment configuration guide based on your chip model. Complete the toolchain installation and related settings accordingly.
The chip integrates an independent Cadence HiFi5 DSP core, designed for efficient handling of compute-intensive tasks such as audio algorithms, speech recognition, and AI inference.
SDK Development Environment Setup (Required) ： Regardless of whether DSP development is involved, the MCU development environment is always required. The MCU firmware handles system initialization, DSP firmware loading into memory, hardware resource management, and ultimately generates the complete firmware that can be flashed.
DSP Development Environment Setup (Optional) ： Used for developing signal processing algorithm firmware running on the DSP core, compiled and debugged based on Cadence Xtensa Xplorer IDE.
Note
Required：When developing or modifying DSP algorithm firmware.
Not Required：When using only MCU functionality, or when using pre-compiled DSP firmware libraries.
The chip integrates an independent Cadence HiFi5 DSP core, designed for efficient handling of compute-intensive tasks such as audio algorithms, speech recognition, and AI inference.
SDK Development Environment Setup (Required) ： Regardless of whether DSP development is involved, the MCU development environment is always required. The MCU firmware handles system initialization, DSP firmware loading into memory, hardware resource management, and ultimately generates the complete firmware that can be flashed.
DSP Development Environment Setup (Optional) ： Used for developing signal processing algorithm firmware running on the DSP core, compiled and debugged based on Cadence Xtensa Xplorer IDE.
Note
Required：When developing or modifying DSP algorithm firmware.
Not Required：When using only MCU functionality, or when using pre-compiled DSP firmware libraries.
The chip adopts a CA32 + KM4 + KM0 tri-core heterogeneous architecture and supports two development modes：
Mode One: FreeRTOS Development — All three cores run FreeRTOS system
Mode Two: Linux Development — CA32 runs Linux, KM4/KM0 run FreeRTOS
According to your chosen development mode, please refer to the corresponding environment setup guides：
FreeRTOS Development： Setup FreeRTOS SDK Development Environment
Linux Development： Setup Linux SDK Development Environment
SDK Acquisition
Before starting, please ensure that Git version management tool is installed for subsequent SDK acquisition and version management.
Note
DSP SDK Download is Optional: If your application involves Digital Signal Processing (DSP) functionality, you need to additionally download the DSP SDK.
Note
DSP SDK Download is Optional: If your application involves Digital Signal Processing (DSP) functionality, you need to additionally download the DSP SDK.
This chip supports two development platforms. Please download one of the SDKs according to your development scenario.
FreeRTOS Development: Download FreeRTOS SDK
Linux Development: Download Linux SDK
Project Compilation
After downloading the SDK, you can refer to Create External Project to start your application development.
Firmware Download
Depending on your development approach, Ameba provides different firmware flashing solutions.
Method 1: CLI Development
If you use command line tools for development, you can choose according to your flashing needs:
Single Device Flashing
Use Flash Flashing Tool to flash firmware to a single device, suitable for development and debugging stages, single device firmware updates and other scenarios.
Batch Flashing
Use Flash Batch Flashing Tool to flash multiple devices simultaneously, suitable for production environment batch flashing, firmware batch updates and other scenarios.
Method 2: VS Code Development
Use VS Code Firmware Download Feature to complete flashing with one click within the IDE.
Log Monitoring
Depending on your development approach, Ameba provides different serial debugging solutions.
Method 1: CLI Development
Use the Log tool for serial communication and log viewing.
Method 2: VS Code Development
Use VS Code Serial Monitor to complete serial debugging and log viewing within the IDE.
