-
Notifications
You must be signed in to change notification settings - Fork 889
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
Add an example of using using DMA with PIO #468
Conversation
988bccc
to
47053b4
Compare
47053b4
to
9232a3a
Compare
9232a3a
to
3fd5556
Compare
3fd5556
to
77461c7
Compare
77461c7
to
67e3171
Compare
4e3dc9e
to
9ba2c96
Compare
Currently it just sends a small buffer. To make it more realistic it might be nice to send more data and maybe send and receive on different cores? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is good as is - it shows what to do
907191a
to
5c461c0
Compare
This is already handled by add_shared_irq_handler() and i think it is more confusing to have it here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good - I can't approve my own PR!
#define USE_DMA_FOR_TX 1 | ||
|
||
#define SERIAL_BAUD 921600 | ||
#define HARD_UART_INST uart1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity I just did some quick local compile-tests, and this code all still compiles if you replace
#define HARD_UART_INST uart1
with
#if !USE_PIO_FOR_RX || !USE_PIO_FOR_TX
#define HARD_UART_INST uart1
#endif
😉 (which perhaps makes it clearer that the "hard UART" isn't used at all when PIO is being used for both RX and TX?)
Fixes #467