Both issues concern the same hardware (ESP32-S2 Saola-1 WROVER with PSRAM) and the problem of getting MicroPython running on it. However, the query (#5958) is asking how to compile/build firmware for the board, while the candidate (#7299) is a distinct runtime bug — continuous resets after deployment when using mismatched board configs (GENERIC_S2/UM_TINYS2 instead of SAOLA_1_WROVER). The candidate does not answer the query's compilation question; it represents a downstream problem that can arise once the user attempts deployment. Neither resolves the other.
Suggested action
No closure action needed. These can be cross-referenced as context: #7299 illustrates a pitfall (wrong board config causing reset loops) that directly follows the situation described in #5958. Both issues may already be addressed by the addition of the SAOLA_1_WROVER board definition to the esp32 port.