I designed a board and got my first prototype from an assembler. The board has an ESP32-WROOM-32U connected via I2C (module pins 26 (IO4) and 29 (IO5)) to an MCP23017 GPIO expander module. This is the only I2C device on this bus, which has 1K pullup resistors to VCC (3.3V). All three address pins on the expander are pulled high for an address of 0x27. There is a 10k resistor on the expander reset pin to pull it high.
I am able to upload apps using both Arduino and Mongoose OS to the ESP3 module and it runs nicely, but I wrote a test app with Arduino and I can not get the I2C bus to work. I tested the app with a known good ESP32-WROOM-32U dev board and also checked the bus with my scope. On my new board I can't get anything resembling a square waveform, or anything that looks like there is anything happening.
I verified that all aspects of the schematic were properly assembled, including 3.3V on the expander, that the GND is connected, that the address pins are pulled up, that there is a good connection between the module pins and the expander pins and so on.
I'm stumped. I'm wondering, do I have to do anything to configure the ESP32-WROOM-32U module fresh from the factory? What else can I check?
Thanks very much...
New board design with ESP32-WROOM-32U has I2C problem
Re: New board design with ESP32-WROOM-32U has I2C problem
Well, What I would do next is to create a simple app that toggles module pins 26 (IO4) and 29 (IO5).
When you toggle them make sure they are always opposite level from one another. That will help verify a short on the PCB.
Verify with a scope that each pin is toggleing and you can move onto the next idea to find the cause.
When you toggle them make sure they are always opposite level from one another. That will help verify a short on the PCB.
Verify with a scope that each pin is toggleing and you can move onto the next idea to find the cause.
Re: New board design with ESP32-WROOM-32U has I2C problem
Great idea thanks, I'll do that and report back!
Re: New board design with ESP32-WROOM-32U has I2C problem
Thanks @MikeMoy, this problem is resolved. I has SCA and SDL backwards in the test app. Killed lots of time but that's what happens sometimes. Thanks for your suggestion, I'll keep that in mind for next time.
Who is online
Users browsing this forum: Baidu [Spider], s.allasia and 90 guests