Wasm2Mpy: Compiling WASM to MicroPython so it can run on Raspberrys

Post by vshymanskyy » Wed, Sep 25, 2024, 6:04 AM UTC

westurner wrote: post #15

HALtheWise wrote: post #9

Earlier quoted context omitted.

In this case, the modules contain native code compiled for the target architecture. Micropython has something approximating a dynamic linker to load them. https://docs.micropython.org/en/latest/develop/natmod.html

tools/mpy_ld.py: https://github.com/micropython/micropython/blob/master/tools... tools/mpy-tool.py lists opcodes: https://github.com/micropython/micropython/blob/master/tools... Can the same be done with .pyc files; what are the advantages of MicroPython native modules? Why does it need wasm2c?

Post by 0points » Wed, Sep 25, 2024, 8:24 AM UTC

vshymanskyy wrote: post #20

bragr wrote: post #2

I feel like this project is a classic example of the README missing a "Why?" section. Not to justify the project, it just makes it hard to evaluate without understanding why they choose implementing a transpiler rather than an embedded WASM VM. Or why not transpile to native assembly? I'm sure they have good reasons but they aren't listed here.

Thanks for the feedback. I'll improve the README based on your inputs. I was focused on the actual research. Overall, this allows writing code in statically compiled languages and running it (fast) on embedded systems with MicroPython. MicroPython itself is comparatively slow, and this provides tools to deliver more demanding software (AI, signal processing, etc).

Post by oulipo » Wed, Sep 25, 2024, 8:49 AM UTC

vshymanskyy wrote: post #22

oulipo wrote: post #11

What would be the recommendation to run on ESP32? https://github.com/wasm3/wasm3 ? https://github.com/espressif/esp-wasmachine ? https://github.com/bytecodealliance/wasm-micro-runtime/tree/... ? https://github.com/TOPLLab/WARDuino ?

For esp32 I'd recommend https://github.com/wasm3/embedded-wasm-apps It obviously depends on your needs/goals. P.S. I'm also the author of wasm3

Post by vshymanskyy » Wed, Sep 25, 2024, 10:27 AM UTC

oulipo wrote: post #25

vshymanskyy wrote: post #22

Earlier quoted context omitted.

For esp32 I'd recommend https://github.com/wasm3/embedded-wasm-apps It obviously depends on your needs/goals. P.S. I'm also the author of wasm3

Actually in my case I need a VM, because I want users to be able to upload "extension plugins" in real-time, without reuploading firmware In that case which approach / library would you recommend to embedd a WASM VM?

Post by kragen » Wed, Sep 25, 2024, 11:15 AM UTC

15155 wrote: post #16

kragen wrote: post #7

Earlier quoted context omitted.

i think your questions are implicitly answered in the top page of the readme, but by showing rather than telling esp32 and stm32 run three different native assembly instruction sets (though this only supports two of them, the others listed in the first line of the readme are all arm) the coremark results seem like an adequate answer to why you'd use a compiler rather than an interpreter i do think it would be clearer…

There's no scenario where a bespoke WASM interpreter is slower than MicroPython - though this isn't really Python. WASM is an almost "ideal" bytecode target for embedded AOT native compilation as well, though yeah, you'd have to implement all of the backend targets.