aboutsummaryrefslogtreecommitdiff
path: root/examples/stm32h7/src/bin/usart_split.rs
Commit message (Collapse)AuthorAgeFilesLines
* executor: return error when creating the spawntoken, not when spawning.Dario Nieuwenhuis2025-08-291-1/+1
|
* stm32/usart: remove instance generic paramsJan Špaček2024-05-231-2/+1
|
* stm32/usart: remove DMA generic params.Dario Nieuwenhuis2024-04-161-15/+3
|
* ci: use beta, add secondary nightly ci.Dario Nieuwenhuis2023-12-211-1/+0
|
* stm32/usart: return error instead of panicking on bad baudrate.Dario Nieuwenhuis2023-09-261-1/+1
|
* Deprecate *recv* in favor of *receive*Ruben De Smet2023-08-221-1/+1
|
* stm32: move to bind_interruptsxoviat2023-05-241-3/+6
| | | | disable lora functionality for now
* stm32: Add support for read_until_idle on UARTGuillaume MICHEL2022-10-261-1/+3
|
* sync: flatten module structure.Dario Nieuwenhuis2022-08-221-1/+1
|
* split `embassy-util` into `embassy-futures`, `embassy-sync`.Dario Nieuwenhuis2022-08-221-2/+2
|
* Split embassy-time from embassy-executor.Dario Nieuwenhuis2022-08-181-1/+1
|
* Remove HAL initialization from #[embassy::main] macro.Dario Nieuwenhuis2022-08-171-2/+2
|
* Split embassy crate into embassy-executor, embassy-util.Dario Nieuwenhuis2022-07-291-6/+6
|
* Run rustfmt.Dario Nieuwenhuis2022-06-121-7/+4
|
* Rename channel to mpmchuntc2022-06-121-1/+1
| | | | I've renamed the channel module for the MPMC as mpmc. There was a previous debate about this, but I feel that the strategy here avoids importing `channel::channel`. The change leaves `signal::Signal`, but I think that's ok. It is all a bit subjective of course. The bottom line for me is that I really like the term mpmc - it means something to me and aligns with broader naming e.g. in Tokio.
* Simpler Channel.Dario Nieuwenhuis2022-04-061-17/+9
| | | | | | | - Allow initializing in a static, without Forever. - Remove ability to close, since in embedded enviromnents channels usually live forever and don't get closed. - Remove MPSC restriction, it's MPMC now. Rename "mpsc" to "channel". - `Sender` and `Receiver` are still available if you want to enforce a piece of code only has send/receive access, but are optional: you can send/receive directly into the Channel if you want.
* Use embassy/defmt-timestamp-uptime in all examples.Dario Nieuwenhuis2022-04-021-3/+3
|
* Add support for splitting stm32 usart into TX and RXUlf Lilleengen2022-03-151-0/+67
* Keeps existing API for usart, but wraps it in Tx and Rx sub-types * Adds split() method similar to nRF for getting indepdendent TX and RX parts * Implements e-h traits for TX and RX types * Add stm32h7 example