kromych / slstk3400a-blink-rs

Example application for SLSTK3400A

Example applications for SLSTK3400A

This example shows how to log via RTT and blink an LED on the SLSTK3400A starter kit board

Prepare

One-time tool installation:

cargo install flip-link
cargo install probe-rs --features="cli"

It is possible to process the compiled binary with objcopy and copy it over to the STK3400A disk that the board presensts when connected through the mini-USB port (the debug one). For that, can do

# One-time `objdump` and other tools installation
cargo install cargo-binutils
# Cross-platform copy; could use the platform-specific copy utility.
cargo install coreutils

# Every time to deploy
cargo objcopy --release -p blink -- -O binary blink.bin
# Adjust the path to the STK34400 for your system
coreutils cp ./blink.bin /Volumes/STK3400

Enjoy

Run with

cargo run --release blink

or (for multi-channel RTT logging)

cargo embed --release blink

Other demos:

Demo	Description
blink	SLSTK3400A blink in a loop
blink-pb	SLSTK3400A blink on push buttons
blink-systick	SLSTK3400A blink on SysTick interrupt
blink-rtc	SLSTK3400A blink on RTC interrupt

NOTE: if your code configures the clock to run at lower speeds, the speed of communication with the debug probe in .cargo/config.toml needs to be adjusted to be not greater than what the code sets for the board.

There is also a simple wrapper around cargo , ./x.py, that can be used like this:

./x.py flash blink --release

Look for other commands in ./x.json.

In the terminal, there should be something resembling this:

     Running `probe-rs run --chip EFM32HG322F64 target/thumbv6m-none-eabi/release/slstk3400a-blink-rs`
(HOST) INFO  flashing program (5 pages / 5.00 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
INFO  Hello, world!
└─ slstk3400a_blink_rs::__cortex_m_rt_main @ src/main.rs:21

To atach to the RTT logging after detaching:

./x.py attach blink --release

SVD packs

https://www.keil.arm.com/packs/

• EFM32HG

To create the Peripheral Access Crate (a.k.a PAC) from the SVD, you'll need these tools:

cargo install svd2rust
cargo install svdtools
cargo install form

and then run ./support/efm32hg322_pac/svd/gen.sh from its directory. Finally, cargo fmt will format the generated desciptions.

Thank you

It is speculated that if one wants to build something from scratch, they ought to start from creating the Universe itself :) That said, this project would not have been possible without many great folks on whose efforts this repo has relied.

1. The infrastructure parts of support/efm32hg322_hal borrow GPIO infra code from efm32hg-hal. Despite its name, it supports just one MCU of the EFM32HG family (EFM32HG309F64), and the means of extending weren't obvious to me. As the cleanest approach, I copied as much code as needed, complied with the licensing terms, and added support for EFM32322F64's GPIO. Support for the GPIO interrupts has been fixed.

2. The idea of generating the register description comes from efm32hg-pac. Again, the project supports just one MCU (EFM32HG309F64) so I procured the SVD file, patched it, and generated the definitions for EFM32HG322F64 myself.

3. Incredibly awesome folks who created probe-rs merged my pull request to support EFM32HG322F64.