Intermittent HardFault_Handler on ESP32-S2

[anecdata]

CircuitPython version

Adafruit CircuitPython 7.0.0-rc.2 on 2021-09-15; FeatherS2 with ESP32S2
Adafruit CircuitPython 7.0.0-rc.2 on 2021-09-15; Adafruit MagTag with ESP32S2
Adafruit CircuitPython 7.0.0-rc.2 on 2021-09-15; LILYGO TTGO T8 ESP32-S2 w/Display with ESP32S2

Code/REPL

No minimum reproducible example at this time.

Behavior

This is more of a placeholder issue since it's not reproducible on demand.

These are intermittent hardfaults that occur during code.py run, but not obviously correlated to any particular operations within the code. Have not seen this on PyPortal (the only SAMD I have on rc.2 at the moment).

In the 48 or so hours since installing rc.2, have seen this:
(5) times on a specific FeatherS2 with an I2C PCF8523 RTC and a 2C EPD FeatherWing
(5) times on a specific MagTag with an I2C DS3231 RTC and an I2C SHT31D
(1) time on a specific LILYGO (built-in TFT) with no external devices attached
(0) times since rc.2 install on 5 other ESP32-S2 devices, some with external I2C devices and / or external SPI TFT displays (one of these has 10 external I2C devices and an external SPI TFT)

Prior to rc.2, I would mainly see intermittent hardfaults on FunHouse, but it had the I2C PCF8523 RTC at the time. I moved it to the FeatherS2 above to see if the hardfaults would move.

I don't see hardfaults on another half dozen or so 6.2.0 FeatherS2s, though of course they do not use the full arsenal of newer features.

I'll continue to track, and upgrade to rc.3 (or release) on all of these devices at some point, starting from erase_flash. I'll also try to put DEBUG builds on a couple devices to get better info.

Description

No response

Additional information

No response

[anecdata]

I did a clean install of 7.0.0 on the MagTag and the FeatherS2 yesterday. Install sequence: command line erase_flash, command line install TinyUF2, install (drag) CircuitPython UF2, install libraries and .py files, ctrl-C & return in console to enter REPL, EJECT Volume, hard reset, then let it run.

Saw 1st hardfault on one of these devices (the FeatherS2) this morning (Sep 21).

Addendum: 7.0.0 hardfaults on MagTag and FeatherS2 on Sep22.

[anecdata]

All of my ESP32-S2 devices hardfaulted last night within a second or two of recognizing the time change. I periodically check for internet time and update the MCU clock with:
rtc.RTC().datetime = time.localtime(s)
All of my ESP32-S2 devices need reset after hardfault sporadically (I check every morning and typically 1 or 2 out of the 5 continuously running devices will have hardfaulted), but time change is not always the pattern. Hardfaults occur in other areas of code unrelated to a time change, but this is the closest thing to a pattern I've found for at least some of the hardfaults. I'll try to come up with a minimal example.

[anecdata]

I haven't seen a hardfault in the five days since the watchdog issue was fixed (#5562), so I'm closing this. Will open a specific issue if any new hardfaults arise.