stm32wlxx-hal icon indicating copy to clipboard operation
stm32wlxx-hal copied to clipboard

Support for STM32WL33

Open hgaiser opened this issue 1 month ago • 2 comments

I'm trying to get my MCU (STM32WL33CC) supported through Rust. Does it make sense for this project to support that board, since it is in the same family?

I worry that there are quite some changes w.r.t. memory layout. As an example I see the addresses for GPIOA, GPIOB and GPIOC are 0x4800_0000, 0x4800_0400 and 0x4800_0800 respectively, while for the STM32WL33 it's 0x4800_0000 and 0x4810_0000 (there is no GPIOC).

What is the best way to approach the development of a HAL for this board?

ps. I am also trying to add support for STM32WL33 to stm32-rs.

hgaiser avatar Oct 28 '25 20:10 hgaiser

It does make sense in this project, but I direct most people to embassy for STM32WL support these days because it is better maintained. Their code to drive the radio was actually taken (with permission) from this repo, though it has probably diverged since then.

newAM avatar Nov 01 '25 19:11 newAM

It does make sense in this project, but I direct most people to embassy for STM32WL support these days because it is better maintained. Their code to drive the radio was actually taken (with permission) from this repo, though it has probably diverged since then.

Ahh interesting, thanks for your reply 👍

Would you advise to use embassy for any new embedded Rust project?

I'm new to embedded Rust, so I'm trying to get my bearing :).

hgaiser avatar Nov 01 '25 19:11 hgaiser

Welcome to embedded rust! Generally embassy is more actively maintained, and has a longer history of active maintenance.

I still use this crate for an existing project, but if I ever start another I will be using embassy myself.

newAM avatar Nov 09 '25 23:11 newAM