Rust on RTEMS

Frank Kühndel frank.kuehndel at
Tue Jan 30 15:38:35 UTC 2024

On 1/30/24 14:08, Jan.Sommer at wrote:
>> -----Ursprüngliche Nachricht-----
>> Von: Frank Kühndel<frank.kuehndel at>
>> Gesendet: Dienstag, 30. Januar 2024 11:03
>> An: Sommer, Jan<Jan.Sommer at>;joel at
>> Cc:dwaine.s.molock at;users at
>> Betreff: Re: AW: Rust on RTEMS
>> Hello Jan,
>> thanks for the info and all your efforts.
>> Are you planing to add a short "How to use Rust with RTEMS?" section to the
>> RTEMS user manual?
>> I am asking because I was thinking of writing a description on how to use Rust
>> with `#![no_std]` and `#![no_main]` into the user manual.
>> Basically the same text which I already attached to
>> Yet, because you are much ahead of me, does it still make sense for me to
>> put such a text into the manual (would it not be outdated by your approach
>> soon)?
> Good question. I think your explanations are more general, while the things I am working on will only be relevant for the Xilinx BSPs (until other architectures are ported). So, I think it would still be good to have this in the manual.

OK. I'll do.

What surprises me is that the porting of Rust libraries (i.e. std), Rust 
test framework and the ability to have a Rust main() function does 
depend so much on the particular BSP. I was thinking that these items 
must be adapted once to RTEMS and are then - at least mostly - 
independent of a particular processor and board.

How much effort is (very roughly) the porting to another BSP?
Or what needs to be done to adapt Rust to another BSP?


embedded brains GmbH & Co. KG
Herr Frank KÜHNDEL
Dornierstr. 4
82178 Puchheim
email: frank.kuehndel at
phone:  +49-89-18 94 741 - 23
mobile: +49-176-15 22 06 - 11

Registergericht: Amtsgericht München
Registernummer: HRA 117265
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:

More information about the users mailing list