1. 前言
瑞萨 RA4M2 系列微控制器以其强大的硬件安全特性(TrustZone 与 SCE)和高性能的 Cortex-M33 内核成为工业级应用的优选。为了在软件层面进一步提升系统的安全性与开发体验,本项目选择了 Rust 这一内存安全语言作为开发主体。
然而,嵌入式开发往往离不开原厂成熟的 C 语言 SDK(如瑞萨灵活配置软件包 FSP)。本报告记录了如何利用 rust / Bindge 技术,在 ATfE (Arm Toolchain for Embed) 这一高性能 LLVM 工具链的支持下,搭建一套 Rust 与 FSP 深度融合的开发环境。通过这种混合编程模式,
我们既能保留 FSP 对底层硬件配置的便利性,又能享受 Rust 语言带来的现代化开发体验。
2. 实现细节
2.1 工具链与环境配置
wget https://github.com/llvm/llvm-project/releases/download/llvmorg-22.1.0/LLVM-22.1.0-win64.exe
wget https://github.com/arm/arm-toolchain/releases/download/release-22.1.0-ATfE/ATfE-22.1.0-Windows-x86_64.zip
- ATfE 路径配置:通过设置环境变量
LIBCLANG_PATH指向 LLVM 动态库,并把 ATfE 的bin目录加入PATH,确保 Rust 的构建引擎(cc和bindgen)能够调用特定的 Clang 进行头文件解析与编译。
# libclang.dll
$Env:LIBCLANG_PATH="D:\Projects\workspace\llvm-22.1.0\lib"
# clang
$Env:Path += ";D:\Projects\workspace\ATfE-22.1.0-Windows-x86_64\bin"
- 调试器安装:既然使用rust,当然得试试 probe-rs 工具链。probe-rs是rust实现的嵌入式debug工具,它原生支持 DAPLink,能够跳过复杂的 GDB 配置,通过简单的命令行实现秒级的烧录与 RTT 实时日志打印。
irm https://github.com/probe-rs/probe-rs/releases/latest/download/probe-rs-tools-installer.ps1 | iex
- fsp配置
由于仅仅为了测试rust的集成点亮LED,不涉及很复杂的外设驱动,我们简单的在fsp配置一下引脚和时钟




注意:RA4M2-Sensor搭载的晶振为12MHz,需要将FSP默认的24MHz改为12MHz,PLL Div设置为 /1,PLL MUL设置为 x16.5
2.2 自动化构建
编写build.rs利用 cc crate,指定 ATfE 路径下的 clang.exe 作为编译器,并注入 -mcpu=cortex-m33 等核心参数,将 FSP 所有的 .c 源文件(排除应用入口 hal_entry.c)静态链接到 Rust 产物中。使用 bindgen 扫描 hal_data.h。通过注入 ATfE 的内置 Clang 头文件路径(lib/clang/22/include),解决 string.h 等标准库依赖问题,将 C 接口转化为 Rust 可直接调用的模块。
参考FSP生成的CMake工程可以很轻松的编写build.rs
use std::env;
use std::path::PathBuf;
use glob::glob;
fn main() {
let out_dir = env::var("OUT_DIR").unwrap();
let out_path = PathBuf::from(out_dir);
let toolchain_root = PathBuf::from(r"D:\Projects\workspace\ATfE-22.1.0-Windows-x86_64");
let toolchain_bin = toolchain_root.join("bin");
let clang_exe = toolchain_bin.join("clang.exe");
let llvm_ar_exe = toolchain_bin.join("llvm-ar.exe");
println!("cargo:rerun-if-changed=fsp_c/");
let mut build = cc::Build::new();
build.compiler(&clang_exe);
build.archiver(&llvm_ar_exe);
build.target("arm-none-eabi");
build.define("_RA_CORE", "CM33");
build.define("_RA_ORDINAL", "1");
build.define("_RENESAS_RA_", None);
build.flag("-mcpu=cortex-m33");
build.flag("-mfpu=fpv5-sp-d16");
build.flag("-mfloat-abi=hard");
build.flag("-mthumb");
build.flag("-g");
build.flag("-fshort-enums");
build.flag("-ffunction-sections");
build.flag("-fdata-sections");
build.flag("-Os");
let includes = [
"fsp_c/ra/arm/CMSIS_6/CMSIS/Core/Include",
"fsp_c/ra/fsp/inc",
"fsp_c/ra/fsp/inc/api",
"fsp_c/ra/fsp/inc/instances",
"fsp_c/ra_cfg/fsp_cfg",
"fsp_c/ra_cfg/fsp_cfg/bsp",
"fsp_c/ra_gen",
"fsp_c/src",
"fsp_c",
];
for inc in &includes {
build.include(inc);
}
let search_patterns = [
"fsp_c/ra/**/*.c", "fsp_c/ra/**/*.S",
"fsp_c/ra_gen/**/*.c", "fsp_c/ra_gen/**/*.S",
"fsp_c/src/**/*.c", "fsp_c/src/**/*.S",
];
for pattern in search_patterns.iter() {
for entry in glob(pattern).expect("Failed to read glob pattern") {
if let Ok(path) = entry {
if path.file_name().unwrap() == "hal_entry.c" {
continue;
}
build.file(path);
}
}
}
build.compile("fsp");
let manifest_dir = env::var("CARGO_MANIFEST_DIR").unwrap();
println!("cargo:rustc-link-search=native={}/fsp_c/script", manifest_dir);
println!("cargo:rustc-link-search=native={}/fsp_c", manifest_dir);
println!("cargo:rustc-link-arg=-Tfsp.lld");
let mut bindgen_builder = bindgen::Builder::default()
.use_core()
.header("fsp_c/ra_gen/hal_data.h")
.clang_arg("--target=arm-none-eabi")
.clang_arg("-mcpu=cortex-m33")
.clang_arg("-mfloat-abi=hard")
.clang_arg("-fshort-enums")
.clang_arg("-D_RA_CORE=CM33")
.clang_arg("-D_RENESAS_RA_");
let clang_builtin_inc = toolchain_root.join("lib").join("clang").join("22").join("include");
if clang_builtin_inc.exists() {
bindgen_builder = bindgen_builder.clang_arg(format!("-I{}", clang_builtin_inc.display()));
} else {
println!("cargo:warning=找不到 Clang 内置头文件路径: {}", clang_builtin_inc.display());
}
let libc_inc = toolchain_root.join("lib").join("clang-runtimes").join("arm-none-eabi").join("include");
if libc_inc.exists() {
bindgen_builder = bindgen_builder.clang_arg(format!("-I{}", libc_inc.display()));
} else {
println!("cargo:warning=找不到 C 标准库头文件路径: {}", libc_inc.display());
}
for inc in &includes {
bindgen_builder = bindgen_builder.clang_arg(format!("-I{}", inc));
}
let bindings = bindgen_builder
.generate()
.expect("Unable to generate bindings! (Did you set LIBCLANG_PATH?)");
bindings
.write_to_file(out_path.join("bindings.rs"))
.expect("Couldn't write bindings!");
}
2.3 rust应用
在 Rust 端,我们已经定义了名为 fsp 的模块来承载自动生成的绑定。由于fsp生成应用入口为hal_entry,在切换到rust后,需要通过 no_mangle 导出 hal_entry 函数,确保链接器能正确对接 FSP 的启动流程。
在 Rust 逻辑中,通过 unsafe 块封装对 FSP 原始 API(如 R_IOPORT_Open 和 R_IOPORT_PinWrite)的调用。最后集成 rtt-target 库,利用 probe-rs 的高速通道在不占用硬件串口的情况下直接在控制台输出调试日志。
#![no_std]
#![no_main]
use panic_probe as _;
use rtt_target::{rprintln, rtt_init_print};
#[allow(warnings)]
#[allow(unsafe_extern_blocks)]
pub mod fsp {
include!(concat!(env!("OUT_DIR"), "/bindings.rs"));
}
use fsp::*;
#[no_mangle]
pub extern "C" fn _init_tls() {}
#[no_mangle]
pub extern "C" fn _set_tls() {}
fn delay(count: u32) {
for _ in 0..count {
cortex_m::asm::nop();
}
}
#[no_mangle]
pub extern "C" fn hal_entry() {
const FERRIS: &str = r#"
_~^~^~_
\) / o o \ (/
'_ - _'
/ '-----' \
"#;
rtt_init_print!(); // 初始化 RTT 打印
rprintln!("RA4M2 Rust 系统已启动!");
rprintln!("{}", FERRIS);
unsafe {
R_IOPORT_Open(&raw mut g_ioport_ctrl as *mut _ as *mut _, &g_bsp_pin_cfg);
}
loop {
rprintln!("LED 翻转...");
unsafe {
R_IOPORT_PinWrite(
&raw mut g_ioport_ctrl as *mut _ as *mut _,
e_bsp_io_port_pin_t_BSP_IO_PORT_01_PIN_03 as u16,
e_bsp_io_level_BSP_IO_LEVEL_HIGH as u8,
);
R_IOPORT_PinWrite(
&raw mut g_ioport_ctrl as *mut _ as *mut _,
e_bsp_io_port_pin_t_BSP_IO_PORT_00_PIN_02 as u16,
e_bsp_io_level_BSP_IO_LEVEL_HIGH as u8,
);
R_IOPORT_PinWrite(
&raw mut g_ioport_ctrl as *mut _ as *mut _,
e_bsp_io_port_pin_t_BSP_IO_PORT_01_PIN_04 as u16,
e_bsp_io_level_BSP_IO_LEVEL_HIGH as u8,
);
}
delay(2_000_000);
unsafe {
R_IOPORT_PinWrite(
&raw mut g_ioport_ctrl as *mut _ as *mut _,
e_bsp_io_port_pin_t_BSP_IO_PORT_01_PIN_03 as u16,
e_bsp_io_level_BSP_IO_LEVEL_LOW as u8,
);
R_IOPORT_PinWrite(
&raw mut g_ioport_ctrl as *mut _ as *mut _,
e_bsp_io_port_pin_t_BSP_IO_PORT_00_PIN_02 as u16,
e_bsp_io_level_BSP_IO_LEVEL_LOW as u8,
);
R_IOPORT_PinWrite(
&raw mut g_ioport_ctrl as *mut _ as *mut _,
e_bsp_io_port_pin_t_BSP_IO_PORT_01_PIN_04 as u16,
e_bsp_io_level_BSP_IO_LEVEL_LOW as u8,
);
}
delay(2_000_000);
}
}
添加配置
[package]
name = "ra4m2-blink"
version = "0.1.0"
edition = "2021"
[dependencies]
cortex-m = { version = "0.7", features = ["critical-section-single-core"] }
cortex-m-rt = "0.7"
panic-halt = "0.2"
rtt-target = "0.5"
panic-probe = { version = "0.3", features = ["print-rtt"] }
[build-dependencies]
cc = "1.0"
bindgen = "0.69"
glob = "0.3"
[[bin]]
name = "ra4m2-blink"
path = "src/main.rs"
test = false
bench = false
[build]
target = "thumbv8m.main-none-eabihf"
[target.thumbv8m.main-none-eabihf]
runner = "probe-rs run --chip R7FA4M2AD"
rustflags = [
"-C", "linker=rust-lld",
"-C", "link-arg=--Map=target/output.map",
]
3. 效果
查看占用情况
$ llvm-size --format=berkeley target/thumbv8m.main-none-eabihf/release/ra4m2-blink
text data bss dec hex filename
8646 0 2228 10874 2a7a target/thumbv8m.main-none-eabihf/release/ra4m2-blink
环境跑通后,在 VS Code 终端输入 cargo run --release,


$ cargo run --release
Finished `release` profile [optimized + debuginfo] target(s) in 0.13s
Running `probe-rs run --chip R7FA4M2AD target\thumbv8m.main-none-eabihf\release\ra4m2-blink`
Erasing ✔ 100% [####################] 8.00 KiB @ 9.40 KiB/s (took 1s)
Programming ✔ 100% [####################] 6.88 KiB @ 2.25 KiB/s (took 3s)
Erasing 2 ✔ 100% [####################] 48 B @ 57 B/s (took 1s)
Programming 2 ✔ 100% [####################] 48 B @ 195 B/s (took 0s) Finished in 5.11s
RA4M2 Rust 系统已启动!
11:23:16.943:
11:23:16.943: _~^~^~_
11:23:16.943: \) / o o \ (/
11:23:16.943: '_ - _'
11:23:16.943: / '-----' \
11:23:16.943:
11:23:16.943: LED 翻转...
11:23:17.171: LED 翻转...
11:23:17.508: LED 翻转...
11:23:17.845: LED 翻转...
11:23:18.181: LED 翻转...
11:23:18.518: LED 翻转...
11:23:18.855: LED 翻转...
11:23:19.191: LED 翻转...
11:23:19.420: LED 翻转...
11:23:19.756: LED 翻转...
11:23:20.093: LED 翻转...
Received Ctrl+C, exiting
probe-rs成功使用RTT打印信息,欢迎进入rust的世界!
4. 总结
这一套折腾下来,最大的感触就是:只要胆子大,RA4M2 也能玩出花。我们通过 Bindgen 成功让fsp也能有“新体验”,无需额外的设置,daplink也能直接使用RTT,同时rust的安全也可以实现成功编译,即可安全运行。

全部评论