embassy
CC65-Advanced-Optimizations
Our great sponsors
embassy | CC65-Advanced-Optimizations | |
---|---|---|
70 | 2 | |
4,286 | 115 | |
7.6% | - | |
9.9 | 0.6 | |
7 days ago | about 1 year ago | |
Rust | C | |
Apache License 2.0 | MIT License |
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.
embassy
- Embassy 在 Blue Pill 上的点灯案例
-
Why choose async/await over threads?
thanks. looked that up. for the curious: https://embassy.dev/
-
Accessing the Pinecil UART with Picoprobe
Running the Embassy RP2040 USB CDC ACM serial example takes about 5 seconds on a Pico.
https://github.com/embassy-rs/embassy/blob/main/examples/rp/...
-
Avoid Async Rust at All Cost
Async solves different problems, you can, for instance, have just a single-threaded CPU and still have a nice API if you have async-await. It might not be so cool at a higher level as Go's approach of channels and threads, but it's cool in embedded, read this:
https://github.com/embassy-rs/embassy?tab=readme-ov-file#rus...
"Rust's async/await allows for unprecedently easy and efficient multitasking in embedded systems. Tasks get transformed at compile time into state machines that get run cooperatively. It requires no dynamic memory allocation, and runs on a single stack, so no per-task stack size tuning is required. It obsoletes the need for a traditional RTOS with kernel context switching, and is faster and smaller than one!"
I'm just toying with Raspberry Pi Pico and it's pretty nice.
Go and Rust have different use cases, the async-await is nice at a low level.
-
Is anyone using coroutines seriously?
I have not yet dipped by toes in the Rust waters, but reading about the embassy project is actually what piqued my curiosity about using C++ coroutines in embedded. Are you familiar with the project or have you found it lacking?
-
The state of BLE and Rust (no_std)
I think I get the basics (shoutout to the Rust Embedded Working Group!), and I've started looking for the stack I'd be using. I think Embassy is really amazing, as well as the work of the ESP team -- hats off.
-
Rust newcomers are 70x less likely to create vulnerabilities than C++ newcomers [pdf]
> }
And this is how to do it using embassy, which is an async framework for embedded in rust:
https://github.com/embassy-rs/embassy/blob/main/examples/rp/...
-
The State of Async Rust
> not good for embedded
embassy begs to differ
async/await is really just a syntax for building state machines in a way that resembles regular code. It's compiled down to the same code that you would write by hand anyway (early on it had some bloat in state size but I think it's all fixed now).
And embedded has a lot of state machines!
-
Asynchronous Rust on Cortex-M Microcontrollers
You can run multiple executors at different interrupt priority levels (with multiple tasks per executor), which allows tasks on the higher priority executor to interrupt other tasks. Here's an example https://github.com/embassy-rs/embassy/blob/main/examples/nrf...
- Espressif advances with Rust – 30-06-2023
CC65-Advanced-Optimizations
-
Assembly programming on the Commodore 64
I'd like to suggest trying C, using cc65. Assembly knowledge is useful, but working in C is much easier and fast enough most of the time. Here's a nice guide on how to write C code that runs fast on a C64: https://github.com/ilmenit/CC65-Advanced-Optimizations
-
Rust on the MOS 6502: Beyond Fibonacci
The cool thing about LLVM-MOS specifically it that by using the zero page as virtual registers you sort-of get the same output with 'regular' code as opposed to this 'global variables' style of programming.
I recall a tutorial for 'cc65 optimizations'[0] which basically destroys a well-structured C program in order to do all of these optimizations (like making everything global) and it was absolutely terrible, code-wise. Well, the end result was probably fine, but it's just a shame these 'optimizations' were needed.
[0] I think it was this one: https://github.com/ilmenit/CC65-Advanced-Optimizations
What are some alternatives?
rtic - Real-Time Interrupt-driven Concurrency (RTIC) framework for ARM Cortex-M microcontrollers
llvm-mos-ferris-demo
rusty-clock - An alarm clock with environment stats in pure bare metal embedded rust
rust-mos - Empowering everyone to build reliable and efficient software.
smoltcp - a smol tcp/ip stack
nrf-hal - A Rust HAL for the nRF family of devices
nrf-softdevice
a800-rust-test
async-std - Async version of the Rust standard library
chirp8-engine