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.
It probably won’t support the ESP32-P4, but we have an update the the mm-iot-esp32 going out tonight which will add support for the ESP32-C6 and ESP32-C3. If either of these use the same compiler and same march and mabi flags as the ESP32-P4 then you may be able to get away with those. Otherwise you will need to wait until we open source libmorse. Which is progressing!
I just got my hands on a P4 board in a Pi5-ish form factor, so this just got a lot easier to test. I’ll report back when I can spend some time firing it up.
Support for the ESP32-P4 as well as libmorse source will be in the 2.10 release. I don’t have a firm release date, but it’s Soon™, on the order of a couple of weeks. We’re looking forward to this as it will make porting to other architectures much easier.
+1 for this request. I’m looking to integrate several RISC-V ESP32 targets that are critical to our project roadmap (I’ve been in parallel discussions with the Morse Micro sales team regarding this requirement as well).
I’m very interested in the open-sourcing of libmorse and would be happy to contribute to the porting process or maintain these specific board definitions to help accelerate the release for the community.
