-
Notifications
You must be signed in to change notification settings - Fork 47
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
images #1
Comments
Hi Kris, one quick question regarding the SPI. I am trying to get the SPI work and my sensor is responding but for some reason the MISO pin (pin #19) is not accepting any input. I tested the output of the sensor and it gives the expected output for the WHO_AM_I register but as soon as I connect the SDO of the sensor to MISO, the output goes down to zero and I don't see anything oscilloscope. Wondering if you have seen anything like this. Could not comment on your code so msging you here. |
No idea, I haven't tried to use SPI on the ESP32. This sounds like
something for the ESP forum maybe?
Which dev board are you using?
In any case, the SPI pins for VSPI are MOSI 23, MISO 19, CLK 18, and 5 for
nCS althout you could probably use any pin for chip select.GPIO5 is usually
pulled up though.
Not sure why this is not working for you.
…On Thu, Oct 26, 2017 at 6:05 PM, muktillc ***@***.***> wrote:
Hi Kris,
one quick question regarding the SPI. I am trying to get the SPI work and
my sensor is responding but for some reason the MISO pin (pin #19) is not
accepting any input. I tested the output of the sensor and it gives the
expected output for the WHO_AM_I register but as soon as I connect the SDO
of the sensor to MISO, the output goes down to zero and I don't see
anything oscilloscope. Wondering if you have seen anything like this.
Could not comment on your code so msging you here.
Thanks,
Bhaven.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGY1qgLf2JGPNCqw4BVQx9GEDAK7SXpBks5swSxUgaJpZM4LNQwf>
.
|
The text was updated successfully, but these errors were encountered: