-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Feature/esp spi bitbang #14590
Feature/esp spi bitbang #14590
Conversation
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
364dff7
to
a068d34
Compare
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
a068d34
to
d4ad51d
Compare
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
d4ad51d
to
28e5e55
Compare
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
please fix the conflict, @eren-terzioglu |
28e5e55
to
85b0e7e
Compare
Thanks for informing, updated. |
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
85b0e7e
to
e3ac088
Compare
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
@lupyuen do you have some idea about this error:
|
e3ac088
to
28eca42
Compare
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
28eca42
to
90b4fb4
Compare
Thanks @lupyuen, updated |
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
Seems error is unrelated to this PR, we can fix it in other PR. |
@eren-terzioglu Yep let's wait for the Red Error Boxes below to disappear from nuttx-dashboard.org. Then we can rebase with master. Meanwhile I cloned your fork to my repo, enabled all the builds, to check if there are other errors: https://github.com/nuttxpr2/nuttx/actions/runs/11701148540 |
Summary
Bitbang device supports are added due to flexibility on device testing and other use cases especially the devices which has one related peripheral (e.g. There is one SPI peripheral for C3 or there is one I2C peripheral for C6). This feature adds another interface for related peripheral in cases of when number of peripherals are not enough.
One of the example use case is: Implementation used through working on
SPI Slave
on device testing on devices which has one SPI peripheral (e.g. esp32c3, esp32c6). With Bitbang support it became possible to test slave driver without needing other chip who acts as master.Impact
ESP32, ESP32S2, ESP32S3, ESP32C3, ESP32C6, ESP32H2
Testing
Configurations used with
ESPRESSIF_SPI_BITBANG
option enabled additionally:Default MOSI-MISO(GPIO3-GPIO2) pins connected with a wire and this command applied: