Rust async and the ARM generic timer
The article discusses the implementation of timers in Rust for the Arm architecture, focusing on the Arm SYSTICK and CMSDK timers. It highlights the limitations of the SYSTICK timer for long-duration events and introduces the CMSDK timer as a more capable alternative. The article aims to provide insights into running concurrent tasks on Arm processors using these timers.
- ▪The Arm SYSTICK timer is a standard feature in all Arm Cortex-M devices, designed primarily for generating regular interrupts.
- ▪The SYSTICK timer has a 24-bit counter, limiting its maximum wait time to approximately 34.95 ms with a 480 MHz system clock.
- ▪The Arm CMSDK timer offers a 32-bit counter and is more suitable for setting alarms for variable future events.
Lobsters files mainly under programming. We currently carry 187 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | JP's Website |
| Canonical URL | https://thejpster.org.uk/blog/blog-2026-05-17/ |
| Publication time | Sun, 17 May 2026 19:28:51 -0500 |
| Retrieval time | 2026-05-18T00:33:21.159Z |
| Last seen | 2026-05-18T00:33:21.159Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | T-jJ-hCLEQrm |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
JP's Website Scroll through the blog: ‹ Newer | List All | Older › Finding the Time Part 2 - Rust Async and the Arm Generic Timer Posted on 2026-05-17 Contents Intro Timers Arm SYSTICK Arm CMSDK Timer Arm Generic Timer Embassy RTIC Intro In the last article, I set out the various versions of the Arm Architecture, and ones I've been focussed on whilst developing the aarch32-rt and aarch32-cpu libraries. Building an example that gets into fn main() and perhaps fires a few interrupts is fine and all that, but most people using these big processors are going to want a bit more - some sort of framework that lets them run multiple tasks concurrently (whether using pre-emptive task switching, or co-operative scheduling) and manage a list of upcoming events (like timeouts, or when the LED next…
Excerpt limited to ~120 words for fair-use compliance. The full article is at JP's Website.
Discussion
0 commentsMore from JP's Website
