jamesmunns

7 ms·

1.
by jamesmunns 3mo ago
My materials probably took 4-6 hours to write the first draft (I did most of it over two evenings, maybe one more just skimming the questions to figure out what things to talk about for each question), probably 2-3 hours or so to edit, then
2.
by jamesmunns 3mo ago
There's no single "embassy" crate, but all the components (HALs, executor, usb, net, etc.) are all on crates io and have been for a long time.
3.
by jamesmunns 4mo ago
It's worth noting that the support for ESP32 in Rust is official [0], and there are multiple full time engineers at Espressif working on developing and maintaining it. [0]: https://github.com/esp-rs/esp-hal/
4.
by jamesmunns 6mo ago
It's really not so different! In embassy, DMA transfers and interrupts become things that you can .await on, the process is basically: * The software starts a transaction, or triggers some event (like putting data in the fifo) *
5.
by jamesmunns 8mo ago
Speaking as someone familiar with C and Rust (not so much Go!), although there's a parallel here to Rust's Traits, this actually is much closer to dyn Trait in Rust, which uses vtables and runtime polymorphism, rather than &quot
6.
by jamesmunns 8mo ago
As others have mentioned, ~all of the embassy HALs support nearly 1:1 parity of blocking interfaces for drivers next to the async ones. You really can avoid async entirely while still using embassy hals. The ecosystem is not tightly integra
7.
Esp-hal 1.0.0 release announcement(developer.espressif.com)
7 points by jamesmunns 11mo ago|0 comments
8.
by jamesmunns 1y ago
If you haven't seen it, Mara Bos' "Rust Atomics and Locks"[0] is an excellent book on this topic, even if you aren't particularly interested in Rust. [0]: https://marabos.nl/atomics/
9.
by jamesmunns 1y ago
In safety industries, particularly aviation, "alarm fatigue" is a really big deal. You recognize that pilots have limited situational bandwidth, and you REALLY don't want to be bugging them about things you can avoid. I worke
10.
by jamesmunns 1y ago
Nordic's nRF family is the major other vendor I've seen doing this, almost all peripheral can be on any pin. It's definitely a big help for designing boards.
11.
by jamesmunns 1y ago
SEEKING WORK | Remote | Rust and Embedded Systems Location: Berlin, DE Remote: Yes Willing to relocate: No Technologies and tools: Rust, Embedded Systems (Cortex-M, RISC-V), Desktop/server apps/tools, async/await Website: ht
12.
by jamesmunns 1y ago
Kobzol is an absolutely wonderful person to work with. I also work in the Rust project, and any time I've interacted with him, he's been great.
13.
by jamesmunns 1y ago
You definitely can, I designed a 206x85cm standing banner for my last trade show as one of the first "production" things I built in Typst: https://typst.app/project/r1YNDcKpoF1sVXHf5n4VKB Plus you can share t
14.
by jamesmunns 1y ago
Thank you for sharing, I'd never seen this before. It's an incredibly good read (and relevant for me) so far.
15.
by jamesmunns 2y ago
Thanks for Sublime Text! It's been my daily driver for over 15 years :). 10 of those developing Rust, and making heavy use of the Rust Analyzer/LSP plugin infra. I also want to thank you for having such a reasonable licensing mode
16.
by jamesmunns 2y ago
For 3, if you haven't seen snapshot tests, like those using the insta crate, it makes it very easy to detect when values change like this in tests/ci.
17.
by jamesmunns 2y ago
This is entirely incorrect, Ferrocene manages a specification of a subset of the language here: https://public-docs.ferrocene.dev/main/specification/index.h... , including things like a traceability matrix that lin
18.
by jamesmunns 2y ago
I bridged my bluesky account, if you're on mastodon and want to talk to me here, you're welcome to. Not sure if you need to opt-in on the mastodon side to be bridged to bluesky. @jamesmunns.com@bsky.brid.gy I think you can opt-in
19.
by jamesmunns 2y ago
You don't generally need to license Arm chips unless you are designing your own chips for sale, like STM32 or Raspberry Pi do. This is something very few companies do, relative to those who just build things from existing chips. If you
20.
by jamesmunns 2y ago
In general in Rust, lifetimes enforce that references to a thing do not outlive the thing itself. Even in unsafe code, it is possible to tie the lifetime of the allocations to the lifetime of the thing handing out the allocations, meaning t
21.
by jamesmunns 2y ago
Tock-OS, Oxid-OS (the safety version of Tock-OS, like freertos/safertos), and Hubris (from Oxide Computers) are the main three RTOSs, Embassy and RTIC are common frameworks (but not classic RTOSs) used for scheduling and resource manag
22.
by jamesmunns 2y ago
Phil's writing on OS development is always a wonderful read.
23.
Rust Embedded Working Group Community Micro Survey(blog.rust-lang.org)
6 points by jamesmunns 2y ago|0 comments
24.
by jamesmunns 2y ago
Additionally, recursion and function pointers (including dynamic dispatch) are the other two "normal" language features that can defeat static stack analysis. There are techniques for working around this (bounded annotations, lang
25.
by jamesmunns 2y ago
> Embassy has it's own HALs which makes it better at async and has also nicer ergonomic IMO Worth noting, you don't HAVE to use the embassy HALs with the embassy executor. However, AFAIK, the only mainstream non-embassy HALs th
26.
by jamesmunns 2y ago
The usual solution, including in safety critical systems, is to give the judge of the halting problem a stopwatch and a gun. For example in an embedded system: a watchdog timer that you don't service during the execution of some contex
27.
by jamesmunns 2y ago
Yep. Sometimes it's "known issues are avoidable issues", and other times it's "hey I wish we didn't spend xx% of our time avoiding (incl. spending time auditing syntax) or doing mitigations for the same limitat
28.
by jamesmunns 2y ago
Having worked in both kinds personally, it's different . You spend more time on less topics: the variety of work is much lower, which some people love, and some people are frustrated by. There is often much less "drastic innovati
29.
by jamesmunns 2y ago
Having worked in a couple of safety critical companies, there are things you definitely HAVE to do, but some companies do it better than others. Some companies have process and development practices down pat: things go smoothly, and meeting
30.
by jamesmunns 2y ago
Do all of your platforms have the same word width? The same -fshort-enums settings? Do you know that none of your data structures include pointers? Do all of your systems use the same compiler? Compiler version? I agree it will usually wo

More ›