Thank you Michael, this is a very nice explanation.
I tock a short look at the two emulators,
> https://github.com/takahirox/riscv-rust
> https://github.com/d0iasm/rvemu
they seem to be target towards emulating bigger systems (able to run Linux) than RIOT targets. Afaik RIOT is aiming at
microcontrollers.
I found https://github.com/renode/renode as a MCU emulator but it is written in C# (which i don't know much about) and i
found no WASM Version.
Maybe someone know about a WASM MCU emulator or the two from above maybe configurable or stripdownable to be MCU
emulators. If one wants to emulate MCU it would also be nice to emulate some peripherals integrated and external.
On 28/10/2020 11:51, Michael Richardson wrote:
Philipp Blum <[email protected]> wrote:
> That is actually a quite interesting option to evaluate. There are
already a
> couple of projects for that:
> https://github.com/takahirox/riscv-rust
> https://github.com/d0iasm/rvemu
> Of course this will be very inefficient, but this wouldn't be a
productive
> dev environment. Just for people playing with RIOT OS. For that purpose
it
> should be good enough.
>>
>> btw.: I am currently working on running WASM inside RIOT.
> I don't get why you should want to run wasm inside RIOT, when you can
just
> compile the source code for the desired architecture. What is the
use-case
> for this?
It means that we can have a sensor/device with all sorts of nice onboarding,
security, and sane stack, which is upgraded/patched on a long-cycle.
But the actual application code can be downloaded on a much shorter cycle,
and can be authored by far less capable (and far less trusted) people.
[See RUST talk at last summit]
Could also have a different license.
Whether this will really work given the battery optimization concerns is
something we'll have to learn.
_______________________________________________
users mailing list
[email protected]
https://lists.riot-os.org/mailman/listinfo/users
