Search found 9 matches
- Fri Nov 09, 2018 10:40 pm
- Forum: Hardware
- Topic: WROOM-32 ground pin connections and EMI/EMC
- Replies: 1
- Views: 7341
WROOM-32 ground pin connections and EMI/EMC
Hello, We are encountering some issues with clock noise emissions on our WROOM-32 mounted on a PCB and were wondering if all ground pins need to be connected? Given the size of the module, having multiple grounds connected creates ground loops which we think might be causing some of the emission pro...
- Sat Feb 10, 2018 5:41 am
- Forum: ESP32 Arduino
- Topic: EEPROM library not reading or writing correctly
- Replies: 0
- Views: 3633
EEPROM library not reading or writing correctly
We recently received a shipment of manufactured boards that use the ESP-WROOM-32 module. The packaging of this module is different from the previous ESP-WROOM-32 that we had been using during development with markings for CE and FCC certifications now present. We are able write code to this module a...
- Thu Dec 07, 2017 11:11 pm
- Forum: ESP-IDF
- Topic: Suggestions for finding stack/program counter corruption
- Replies: 3
- Views: 7314
Re: Suggestions for finding stack/program counter corruption
Thanks for the response. I have stack smashing detection/protection enabled and that worked as expected when I overwrote the end of a char array while logging so I know that that works. Unfortunately, that is never triggered in this situation. I also have checking of the stack size but it is not a s...
- Thu Dec 07, 2017 10:17 pm
- Forum: ESP-IDF
- Topic: Suggestions for finding stack/program counter corruption
- Replies: 3
- Views: 7314
Suggestions for finding stack/program counter corruption
Hello, I am hitting an infrequent problem that occurs once or twice per day and causes the system to reboot. I get a back trace but the addresses are nonsensical and random, indicating that the program counter is corrupted. I was looking for method/tools to debug the problem but have been unable to ...
- Mon Oct 02, 2017 12:46 pm
- Forum: General Discussion
- Topic: I2C Command operation
- Replies: 0
- Views: 2485
I2C Command operation
Another question on I2C and the Command buffer structure... If no END or STOP operation operation is provided within the 16 COMMAND items, does the state machine keep running from the beginning or terminate after executing the 16th command?
- Sat Sep 30, 2017 3:48 pm
- Forum: General Discussion
- Topic: I2C Command sequence structure and done flag on END
- Replies: 0
- Views: 2812
I2C Command sequence structure and done flag on END
Hi, I have a situation where I am attempting to read from the I2C in chunks for larger messages, but am encountering a hanging/timeout problem when doing so. According to the I2C write section (page 216, 10.3.6) of the reference manual (http://espressif.com/sites/default/files/documentation/esp32_te...
- Sat Sep 30, 2017 6:53 am
- Forum: Report Bugs
- Topic: I2C bus_busy set on startup/reboot and no recovery option
- Replies: 8
- Views: 12876
Re: I2C bus_busy set on startup/reboot and no recovery option
A reset method is now available in the Arduino master for the Wire library. You can use it as a part of recovery of the I2C under your own control.
- Thu Sep 28, 2017 7:22 pm
- Forum: Report Bugs
- Topic: I2C bus_busy set on startup/reboot and no recovery option
- Replies: 8
- Views: 12876
Re: I2C bus_busy set on startup/reboot and no recovery option
Thank you, that worked once I did these steps and reinitialized the I2C configuration. I did not see that specific information in the documentation or the forum search. It would be helpful to have it explicitly defined in the documentation here: http://espressif.com/sites/default/files/documentation...
- Wed Sep 27, 2017 3:39 pm
- Forum: Report Bugs
- Topic: I2C bus_busy set on startup/reboot and no recovery option
- Replies: 8
- Views: 12876
I2C bus_busy set on startup/reboot and no recovery option
Hi, I have been fighting with a repeatable problem in the I2C subsystem that happens on startup and reboot. In a number of cases, the system will start with the I2C hardware state machine in an indeterminate state manifesting itself with the bus_busy flag of the i2c_dev_t structure already set prior...