492: Adjust the config.toml for U5. r=Dirbaio a=bobmcwhirter
- Correct ISA
- Remove commented-out cruft.
Co-authored-by: Bob McWhirter <bmcwhirt@redhat.com>
484: Fix lifetime of pwmsequence buffer argument and clarity cleanups r=Dirbaio a=jacobrosenthal
Im not sure its UB to write to the sequence values struct after having started a pwm sequence.. but its against the ethos of the api I had in mind to monkey with it while its in motion.
~Use const generics to consume any size input instead of a borrow of slice~
cc https://github.com/embassy-rs/embassy/pull/483
Co-authored-by: Jacob Rosenthal <jacobrosenthal@gmail.com>
It is basically impossible to directly convert that example to a sequence for various reasons. You cant have multiple channels on same buffer with one sequence instance for starters, also at that clock rate and max_duty 1 period is far longer than the 3ms it was using, which would require using a new max_duty and thus require regenerating the sine table which makes it not representitive of the original example anymore
455: simple_playback api from nrf sdk r=Dirbaio a=jacobrosenthal
Port of the nrf_drv_pwm_simple_playback call from the nordic sdk that allows you to set up a sequence to play across leds with no interaction necessary using the 'shorts' registers to trigger looping sequences
Co-authored-by: Jacob Rosenthal <jacobrosenthal@gmail.com>
482: Add MCO peripheral. r=Dirbaio a=matoushybl
This PR adds an abstraction over STM32 RCC feature called MCO (Microcontroller Clock Output). The clock output can bind to several clock sources and then can be scaled using a prescaler.
Given that from the embassy ecosystem the RCC is generaly invisible to the user, the MCO was implemented as a separate peripheral bound to the pin where the clock should appear.
Co-authored-by: Matous Hybl <hyblmatous@gmail.com>
