Hi Hari Hara Naveen,

That's neat.

>From the looks of it, you've only implemented the PingPong MicroROS example? 
>Or do the other ones work as well somehow?
A minor nit with your blogpost: seL4 does not impose init/notified/protected, 
this is part of the seL4 microkit runtime, one could run other software on seL4 
if you so desired.

I see that you used CMake as a build system, and seemingly integrated our 
libVMM/sDDF work.
Do you have any comments to us for how easy/well it was to integrate your 
system & work with
sDDF and our (make) build systems/tooling? We're always interested in external 
feedback.

Julia

________________________________________
From: HHN via Devel <[email protected]>
Sent: Sunday, 21 June 2026 01:22
To: [email protected]
Subject: [seL4] RFC: Enabling uROS on seL4

Hi Everyone,

I have recently been experimenting with porting uROS to seL4.

uROS (micro-ROS) is a very minimal version of ROS (Robot Operating System)
- a well known robotics middleware suite.
I have implemented the micro-ROS examples
<https://github.com/micro-ROS/micro-ROS-demos/tree/kilted/rclc> and the
necessary system to run them on seL4 over here
<https://github.com/Johan511/sel4_uros>.
A high level explanation of the work can be found here
<https://johan511.github.io/posts/2025-01-19-uros-on-sel4/>.

I do not have any prior experience with Operating system development or
with ROS, so any critiques are much appreciated.

Thank you
--
Hari Hara Naveen
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

This email and any files transmitted with it may contain confidential 
information. If you believe you have received this email or any of its contents 
in error, please notify me immediately by return email and destroy this email. 
Do not use, disseminate, forward, print or copy any contents of an email 
received in error.

_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to