Hi Sid,
Just to add on to what the others have said. For booting an seL4CP image,
tftpboot or other U-Boot methods will also work and we have been doing that
internally at Trustworthy Systems. Just to note that some sel4test
images are
a different format compared to seL4CP images. All seL4CP images are raw
binaries which means you need to use the `go` command with U-Boot. Some
sel4test images are ELFs or other formats so other commands (e.g `bootelf`)
are used.
In general for getting another AArch64 board supported by seL4CP there
should
only be two files you need to change, `build_sdk.py` to add the board
support/config
to the SDK and `loader.c` needs a simple UART put char implementation so
that
it can output debug info/logging.
Lastly, like Indan has said, seL4CP does not make use of the existing
seL4_libs,
util_libs, etc libraries. However, if you would like to run virtual
machines on top
of seL4CP, you may be interested in the VMM we have been building:
https://github.com/Ivan-Velickovic/sel4cp_vmm. Note that it is still
experimental
and not quite ready for production use, however it should become more stable
and production ready in the next couple of months.
Ivan
On 5/8/23 10:47, Sid Agrawal wrote:
Hi,
I would like to setup a working example on sel4 with picoTCP and an eth
driver. I came across this [1] from one of the seL4CP/sDDF demos and [2]
from the camkes examples. However, I do not have access to those particular
boards.
I have a rspi4 and a Toradex Colibri iMX8X module with the aster carrier
board. This Toradex has the same SoC ( iMX8X) as the tqma8xqp-1gb mentioned
on the sel4cp website. Do you folks have any thoughts on how much effort it
is getting seL4 working on "Toradex Colibri iMX8X" given it is supported on
"tqma8xqp-1gb" which has the same SoC? I do not mind buying a
specific development board as long as I know that I can use it for a while
:)
For folks who are working on sel4cp, what kind of dev setup do you have? I
am looking for basic conveniences like flashing the image via USB (so I do
not have to add/remove an SD card), TFTPboot, and some simple device
drivers. I did see the instructions on TFTPbootat [3]. However, does it
matter if the image was built via the sel4test of sel4cp? I think not, but
I just wanted to double-check.
And lastly, a higher-order question about seL4cp. How does sel4cp tie into
the example in seL4_Libs [3], which has barebones libc and a VMM? Which is
what I have used so far with sel4test. I understand that both sel4cp and
camkes are for static systems, but I thought that I could use sel4cp to
start some initial processes, such as a driver, a memory server, and some
management processes. And later use process_spawn from seL4 libs to start
additional PDs.
Best,
Sid
[1]https://github.com/lucypa/sDDF
[2]
https://github.com/seL4/global-components/tree/master/components/Ethdriver/include/plat
[3]https://docs.sel4.systems/Hardware/GeneralARM
_______________________________________________
Devel mailing list [email protected]
To unsubscribe send an email [email protected]
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
