rcsim opened a new pull request, #16274: URL: https://github.com/apache/nuttx/pull/16274
## Summary This commit introduces initial support for the Seeed Studio XIAO ESP32C3 board. Five configurations are available: - nsh: Basic NuttShell support over UART0 - usbnsh: Basic NuttShell support over USB - gpio: NuttShell over USB + GPIO - wifi: NuttShell over USB + Wifi support - ble: NuttShell over SUB + Bluetooth support ## Impact * Is new feature added? Is existing feature changed? Yes, new board support XIAO ESP32C3. * Impact on user (will user need to adapt to change)? Yes, users can use XIAO ESP32C3 * Impact on build (will build process change)? No * Impact on hardware (will arch(s) / board(s) / driver(s) change)? Yes, new board added * Impact on documentation (is update required / provided)? Yes, PR https://github.com/apache/nuttx/pull/16273 * Impact on security (any sort of implications)? No * Impact on compatibility (backward/forward/interoperability)? No * Anything else to consider or add? No ## Testing Build Host(s): OS: Ubuntu 24.04, CPU: Intel i7-8850H, Compiler: GCC 13.3.0 Target(s): arch: risc-v, board: esp32c3-xiao, configs:nsh, usbnsh, gpio, wifi and able ``` Memory region Used Size Region Size %age Used ROM: 212728 B 4 MB 5.07% iram0_0_seg: 13328 B 321296 B 4.15% irom0_0_seg: 82642 B 4 MB 1.97% dram0_0_seg: 20768 B 321296 B 6.46% drom0_0_seg: 147192 B 4 MB 3.51% rtc_iram_seg: 16 B 8168 B 0.20% rtc_reserved_seg: 0 GB 24 B 0.00% CP: nuttx.hex MKIMAGE: NuttX binary esptool.py -c esp32c3 elf2image --ram-only-header -fs 4MB -fm dio -ff "80m" -o nuttx.bin nuttx esptool.py v4.8.1 Creating esp32c3 image... Image has only RAM segments visible. ROM segments are hidden and SHA256 digest is not appended. Merged 1 ELF section Successfully created esp32c3 image. Generated: nuttx.bin ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org