stm32f4xx-hal
rfcs
stm32f4xx-hal | rfcs | |
---|---|---|
11 | 666 | |
506 | 5,711 | |
2.8% | 0.9% | |
8.4 | 9.8 | |
7 days ago | 2 days ago | |
Rust | Markdown | |
BSD Zero Clause License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stm32f4xx-hal
- Rust newcomers are 70x less likely to create vulnerabilities than C++ newcomers [pdf]
-
1.5st project: Rusty Stopwatch
I would personally use the abstractions provided by the stm32f4xx-hal crate more. See https://github.com/stm32-rs/stm32f4xx-hal/tree/master/examples/ for examples.
-
[Media] To get familiar with embedded Rust, I wrote a Tetris clone! It's running on an STM32. I repurposed a board I designed for another project
For this project, the audio ended up being the biggest challenge. I spent a few days on-and-off working on it because it would stop working as I modified the PWM frequency. I was eventually able to track it down to a bug in the HAL and opened a PR accordingly: https://github.com/stm32-rs/stm32f4xx-hal/pull/555
-
Hey Rustaceans! Got a question? Ask here! (30/2022)!
For my specific issue, I'm using the stm32f4xx-hal library to control a bunch of RGB leds, each with a pwm output. Since I have to get pins and timers where I can find them, each component of the led is made by something like
-
STM32F4 Embedded Rust at the HAL: PWM Buzzer
At the time of writing this post, I noticed that if going with option 1 stated earlier that returns a PWMChannel can prove to be quite problematic. In navigating the documentation, the PWMChannel implementations do not include methods that allow to get and set the period of the peripheral. There is an issue that I submitted here for that.
-
blink sketch for stm32f411?
Maybe check out this example from the stm324xx-hal repo?
- How to setup CLion for programming AVR microcontrollers?
-
can u reccommend a microcontroller for my protorypes needs?
Here is an example for stm32f407 (trivial to change to stm32f411) that gets random numbers from the rng peripheral and displays them on an ssd1306 display: https://github.com/stm32-rs/stm32f4xx-hal/blob/master/examples/rng-display.rs although this uses Rust, which you may or may not like. Arduino will have you covered as well, obviously.
- Huge binary size when using usbd_device SerialPort on stm32
-
Learn a new language after C. Rust or C++?
A major benefit of Rust in embedded is how easy it is to use libraries. This example implements USB serial communication on an STM32 in under 80 lines. You add some libs and if it compiles it works.
rfcs
-
Ask HN: What April Fools jokes have you noticed this year?
RFC: Add large language models to Rust
https://github.com/rust-lang/rfcs/pull/3603
- Rust to add large language models to the standard library
-
Why does Rust choose not to provide `for` comprehensions?
Man, SO and family has really gone downhill. That top answer is absolutely terrible. In fact, if you care, you can literally look at the RFC discussion here to see the actual debate: https://github.com/rust-lang/rfcs/pull/582
Basically, `for x in y` is kind of redundant, already sorta-kinda supported by itertools, and there's also a ton of macros that sorta-kinda do it already. It would just be language bloat at this point.
Literally has nothing to do with memory management.
- Coroutines in C
-
Uv: Python Packaging in Rust
Congrats!
> Similarly, uv does not yet generate a platform-agnostic lockfile. This matches pip-tools, but differs from Poetry and PDM, making uv a better fit for projects built around the pip and pip-tools workflows.
Do you expect to make the higher level workflow independent of requirements.txt / support a platform-agnostic lockfile? Being attached to Rye makes me think "no".
Without being platform agnostic, to me this is dead-on-arrival and unable to meet the "Cargo for Python" aim.
> uv supports alternate resolution strategies. By default, uv follows the standard Python dependency resolution strategy of preferring the latest compatible version of each package. But by passing --resolution=lowest, library authors can test their packages against the lowest-compatible version of their dependencies. (This is similar to Go's Minimal version selection.)
> uv allows for resolutions against arbitrary target Python versions. While pip and pip-tools always resolve against the currently-installed Python version (generating, e.g., a Python 3.12-compatible resolution when running under Python 3.12), uv accepts a --python-version parameter, enabling you to generate, e.g., Python 3.7-compatible resolutions even when running under newer versions.
This is great to see though!
I can understand it being a flag on these lower level, directly invoked dependency resolution operations.
While you aren't onto the higher level operations yet, I think it'd be useful to see if there is any cross-ecosystem learning we can do for my MSRV RFC: https://github.com/rust-lang/rfcs/pull/3537
How are you handling pre-releases in you resolution? Unsure how much of that is specified in PEPs. Its something that Cargo is weak in today but we're slowly improving.
- RFC: Rust Has Provenance
-
The bane of my existence: Supporting both async and sync code in Rust
In the early days of Rust there was a debate about whether to support "green threads" and in doing that require runtime support. It was actually implemented and included for a time but it creates problems when trying to do library or embedded code. At the time Go for example chose to go that route, and it was both nice (goroutines are nice to write and well supported) and expensive (effectively requires GC etc). I don't remember the details but there is a Rust RFC from when they removed green threads:
https://github.com/rust-lang/rfcs/blob/0806be4f282144cfcd55b...
-
Why stdout is faster than stderr?
I did some more digging. By RFC 899, I believe Alex Crichton meant PR 899 in this repo:
https://github.com/rust-lang/rfcs/pull/899
Still, no real discussion of why unbuffered stderr.
- Go: What We Got Right, What We Got Wrong
-
Ask HN: What's the fastest programming language with a large standard library?
Rust has had a stable SIMD vector API[1] for a long time. But, it's architecture specific. The portable API[2] isn't stable yet, but you probably can't use the portable API for some of the more exotic uses of SIMD anyway. Indeed, that's true in .NET's case too[3].
Rust does all this SIMD too. It just isn't in the standard library. But the regex crate does it. Indeed, this is where .NET got its SIMD approach for multiple substring search from in the first place[4]. ;-)
You're right that Rust's standard library is conservatively vectorized though[5]. The main thing blocking this isn't the lack of SIMD availability. It's more about how the standard library is internally structured, and the fact that things like substring search are not actually defined in `std` directly, but rather, in `core`. There are plans to fix this[6].
[1]: https://doc.rust-lang.org/std/arch/index.html
[2]: https://doc.rust-lang.org/std/simd/index.html
[3]: https://github.com/dotnet/runtime/blob/72fae0073b35a404f03c3...
[4]: https://github.com/dotnet/runtime/pull/88394#issuecomment-16...
[5]: https://github.com/BurntSushi/memchr#why-is-the-standard-lib...
[6]: https://github.com/rust-lang/rfcs/pull/3469
What are some alternatives?
stm32-rs - Embedded Rust device crates for STM32 microcontrollers
rust - Empowering everyone to build reliable and efficient software.
meta-raspberrypi - Yocto/OE BSP layer for the Raspberry Pi boards
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
embassy - Modern embedded framework, using Rust and async.
crates.io - The Rust package registry
cargo-binutils - Cargo subcommands to invoke the LLVM tools shipped with the Rust toolchain
polonius - Defines the Rust borrow checker.
bare-metal-stopwatch-rust - Bare-metal interrupt-driven stopwatch on STM32F439ZI, written in Rust
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
hubris - A lightweight, memory-protected, message-passing kernel for deeply embedded systems.
rust-gc - Simple tracing (mark and sweep) garbage collector for Rust