Has anyone else managed to build the ESP32 software on anything other than the Seeed Xiao S3 which uses Xtensa architecture? I attempted to build it for the RISC5 boards but no luck.
Also attempted to connect the Halow Module (FHG100M-H) up to a ESP32-S3 dev module and use the same pins as used on the Seeed Xiao ESP32-S3. It appears to communicate with the module and read the version but won’t connect to the wireless network. So, if the host (ESP) can communicate with the chip I am wondering why it doesn’t go all the way and connect.
At the moment we don’t have a publicly available RISCV port of our driver library (libmorse.a). Instead of maintaining support for custom builds, we’re currently working through open sourcing that library so you can target whichever host platform you require. The nature of that library means that this is currently a bit of a slow process of review and refactoring.
Without seeing logs (on the ESP32, but also on the AP side), it’s hard to say why the FGH100M-H isn’t connecting. What does logread on the AP show? Does the ESP32 output anything to the console?
We were able to bring up the ESP32S3 XIAO from Seeed using their fork of the mm-iot-esp32 SDK. Available at GitHub - Seeed-Studio/mm-iot-esp32, and also with Zephyr.
Some things to check without logs:
Have you configured the ESP32 for the same region as the AP?
Have you used the correct BCF? See the Seeed mm-iot-esp32, it has the correct BCF.
