Albin Hedman
Albin Hedman
One of my main reasons fo wanting to use MCPWM is for syncing multiple timers with a phase offset. How should that best be exposed? Something like a new type...
~~Is this perhaps to be considered blocked on some sort of ESP/ESP-S3 CI?~~ - #96 merged
No worries :)
Just found a [problem](https://gist.github.com/usbalbin/27bda42687df365b3029b2a28ad606e6) in release mode in the mcpwm-simple example
The same thing in debug mode works fine
Oh right sorry. I'll push when I get home. I believe I reduced the step size to something like 0.1% and sleep time to 10ms, only printing on integer values...
I am currently at: ```rust #[cfg(any(esp32, esp32s3))] fn main() -> anyhow::Result { use embedded_hal::delay::blocking::DelayUs; use esp_idf_hal::delay::FreeRtos; esp_idf_sys::link_patches(); let v = f32::from(159_u16) * 0.1; println!("159 to float is={v}"); // 159 to...
This also works fine: ```rust #[cfg(any(esp32, esp32s3))] fn main() -> anyhow::Result { use embedded_hal::delay::blocking::DelayUs; use esp_idf_hal::delay::FreeRtos; esp_idf_sys::link_patches(); let v = f32::from(159_u16) * 0.1; println!("159 to float is={v}"); let v =...
```rust #[cfg(any(esp32, esp32s3))] fn main() -> anyhow::Result { esp_idf_sys::link_patches(); let v = 16.0; println!("f32 literal is={v}"); let v = f32::from(16_u16); println!("Converting the number seems to work"); println!("from u16 to f32...
Created #112 since I think the problem might be unrelated to this PR