Conversation

Jarkko Sakkinen

If most of firmware stack in RISC-V was rustified so that you could build compatible SBI implementation with cargo build, that would be the most effective embedded product creation platform that I could think of. You could move from product idea rapidly to a product PoC.

#riscv #rustlang
2
3
6

@jarkko that kinda works already, i just did a project with https://embassy.dev and it worked flawlessly

1
0
0
@laund AFAIK does not provide SBI implementation (could be wrong too) so not really what I was looking after.
1
0
0

@jarkko oh sorry, i must have somehow missed that part and just read the part about effective embedded in Rust. sorry.

1
0
0
@laund implement even a PoC quality version of SBI on top of Embassy. Then I'm super interested. Even just bare bones baseline for development an something is provably in working condition. There's some dead looking SBI crate but I would see more future in implementing one top of this more or less accepted framework called Embassy I suppose. Not that I'm too familiar with that either. I just hack CPU's, that what I do in the end....
0
0
0

@jarkko If you build your whole stack yourself you aren’t beholden to SBI conventions.

There is I think a Rust implementation of the SBI ABI.

1
0
0
@tommythorn not sure if embassy would be the tool of that decades taking job if i was into that. i can prove this to myself just by looking how much stuff in u-boot there is just to wake up dram controllers etc. :-) does not sound too productive work for me

I'll try that crate to see if it is working at all with my RISC-V board...
1
0
0
@tommythorn probably few years from now and RISC-V is also EFI/ACPI across the spectrum, which higher-level payload already. standards, despite being complex, are stable and they continue to exist. so they are in many ways better than Rust crates to some degree. Nobody gets never bored maintaining them and their reference implementations.
0
0
0