Repository navigation
Which pins on the ESP32-S3 N16R8 are excluded from use #3258
|
After installing version 3.9.0, I can't get the EMS bus. I have my own design with ESP32-S3 N16R8 + my own interface. Probably the pins I use are excluded. I use Rx on pin 5 and Tx on pin 17. |
Replies: 4 comments 20 replies
|
if there are GPIO conflicts, it will show in the log - what does it say? |
|
Do you mean in the System log? I'll reinstall 3.9.0 dev 15 and export it to log.txt. There were only yellow entries in the log from the program start, but I didn't notice them because I was looking for communication on the EMS bus. |
|
going into the Console and typing 'show' will list the GPIOs too, and which ones are free to use. I assume you have setup a custom config for the Rx/Tx pins? |
|
I can't do it today, I'll try tomorrow. |
|
Since you didn't tell me which version to use (which you edited), I tried from proddy/EMS-ESP32 dev 16. Unfortunately, nothing changed, no communication on the EMS bus. |
|
since you haven't given any log reports, I'm stuck what to do next |
|
Records from what. From the dev 16 exam? |
|
Thanks. I think I traced the cause. The Rx (gpio 5) needs a pull-up resistor to stop the pin from floating and setting it 3.3V with nothing is driving it low. BBQKees gateways have this, which is why no one else has reported this issue with ESP32-S3 chips. It worked in v3.8.4 because the espressif core silently turned on its own internal pull-up on the UART Rx, and v3.9.0 uses a newer core (ESP_IDF 5) which doesn't by default. Instead of soldering, I'll make a change in the code to enforce it. |
|
OK. I'll wait. |
|
try the S3 build from https://github.com/proddy/EMS-ESP32/releases/tag/latest |
|
So you solved it, it works like a Swiss watch. |
try the S3 build from https://github.com/proddy/EMS-ESP32/releases/tag/latest