You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently testing AOT in Zephyr, and I'm struggling to understand some things.
This readme states that AOT does not work on the ESP32C3. Can someone explain the reason why this is the case? What is the difference between the qemu_riscv32 and ESP32C3 platforms, so that AOT works on the former, but not on the latter?
Also, is there any kind of compatibility table, which shows what Zephyr platforms support each feature?
Thank you.
The text was updated successfully, but these errors were encountered:
Generally speaking, even though it's the same architecture, the toolchain for an embedded device will differ from a normal desktop
one(In your case, could be riscv32-esp-elf-gcc vs riscv32-unknown-elf-gcc).
The Memory layout and elf section will all be different, resulting in AOT works on one target, but not on the other.
I am not sure whether esp32c3 is still unsupported right now, you can try it out to see its current status.
Also, is there any kind of compatibility table, which shows what Zephyr platforms support each feature?
The Zephyr platform is a rather vague term that the actual support really depends on the board config, I would say most wasm language features are supported, but some runtime features like Zephry user mode, and threading depend on the actual hardware.
I'm currently testing AOT in Zephyr, and I'm struggling to understand some things.
This readme states that AOT does not work on the
ESP32C3
. Can someone explain the reason why this is the case? What is the difference between theqemu_riscv32
andESP32C3
platforms, so that AOT works on the former, but not on the latter?Also, is there any kind of compatibility table, which shows what Zephyr platforms support each feature?
Thank you.
The text was updated successfully, but these errors were encountered: