-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs in FlashSafeDma<SpiDma> #1798
Comments
Two issues I noticed with current main (5d6354c) as of 2024.07.24 when communicating using async from embassy task on Firstly,
Secondly received buffer seems to contain only the first byte of the payload (the way I'm currently testing this is sending message from one board to another using LoRa P2P), but I don't know which side is responsible yet. |
Got any code to reproduce that? |
Well, repository of my LoRa code is currently here - https://github.com/plaes/rust-lilygo-ttgo-lora32 which uses lora-phy for communication with sx1276 which internally uses embedded-hal-1.0's transfer method: |
Discovered these while refactoring the DMA APIs. (I'm going to be removing them anyway for the new DMA Move API but I thought it'd be worth mentioning in case someone else runs into it)
Here the result of the transfer isn't copied back into user provided buffer.
esp-hal/esp-hal/src/spi/master.rs
Lines 1687 to 1700 in 7ea471c
esp-hal/esp-hal/src/spi/master.rs
Lines 1801 to 1811 in 7ea471c
Here the DMA buffer isn't being used.
esp-hal/esp-hal/src/spi/master.rs
Lines 1482 to 1491 in 7ea471c
esp-hal/esp-hal/src/spi/master.rs
Lines 1662 to 1664 in 7ea471c
esp-hal/esp-hal/src/spi/master.rs
Lines 1683 to 1685 in 7ea471c
The text was updated successfully, but these errors were encountered: