Hi all,
I'd like to propose temporarily reverting commit 7cc6707a76b
("boards/esp32s3-xiao: switch defconfigs to nxinit entrypoint", by
wangjianyu3) while we investigate further.
On real esp32s3-xiao hardware (Seeed XIAO ESP32-S3 Sense, chip rev v0.2),
this commit hangs the board during boot before any console output is
produced. It affects both defconfigs the commit touches (usbnsh and combo)
identically. The board never enumerates on USB during a normal reset — it
only responds when forced into ROM download mode via the BOOT strap pin,
i.e. the app image never actually runs.
The commit's own message notes it wasn't boot-tested on this board ("this
board has no hardware attached for a flash/boot pass in this session"),
only build-verified here and boot-verified on a different board
(lckfb-szpi-esp32s3).
Evidence: attaching over the ESP32-S3's built-in JTAG (OpenOCD + GDB) shows
the core statically stuck at the same PC and call stack across independent
halts, on both defconfigs:
pc 0x40041a79
#0 0x40041a79 (rsr.ccount-based busy-wait, ROM address range)
#1 0x40047b51
#2 0x4004397f
#3 0x40043c36
#4 0x40034c48
All five frames are in the 0x40034000-0x40048000 ROM range — nx_start
itself lives at 0x42011068 (.flash.text) in this build, a completely
different region. So the hang happens inside the chip's boot ROM, before
NuttX's own init code ever runs. Reverting just this commit's two defconfig
changes on top of current master fixes it: the board boots normally to an
interactive nsh prompt.
*I can help to solve and / or test solutions in real hardware later, but
for now I want to propose a temporary PR revert.*
*--Felipe Moura de Oliveira*
Linkedin <https://www.linkedin.com/in/felipe-oliveira-75a651a0>
