Hey All,
First, thank you for your responses so far. This message board has been helpful with learning seL4.
While we have been working to benchmark the seL4 system on bare metal we have run into some trouble trying to figure out how to get output to the console instead of serial. For our tests we are using the existing seL4test-manifest files and defining custom tests within the apps/sel4test-tests/src/tests/ipc.c file. We noticed that the test output will only go to serial. We have tested with and without the debug configuration.
We would like to see all output go to console. We have tried to remove debug defines on the system call path for __arch_putchar() which seems to only affect the serial output. These system calls don't seem to affect the direction of the output, but only what is being output to serial.
Is there a driver missing from the test libraries that defines the console output? Is there a specific way to output to console when working with tests.
To test these settings we are working with a 32-bit build and are using syslinux to create a bootable USB to test on bare metal.
Regards,
Matthew Scaperoth
Jr. Programmer Analyst
The George Washington University
Academic Technologies
Tel: 202-994-6907
"Matthew" == Matthew Scaperoth mscapero@gwu.edu writes:
Matthew> First, thank you for your responses so far. This message Matthew> board has been helpful with learning seL4.
Matthew> While we have been working to benchmark the seL4 system on Matthew> bare metal we have run into some trouble trying to figure out Matthew> how to get output to the console instead of serial. For our Matthew> tests we are using the existing seL4test-manifest files and Matthew> defining custom tests within the Matthew> apps/sel4test-tests/src/tests/ipc.c file. We noticed that the Matthew> test output will only go to serial. We have tested with and Matthew> without the debug configuration.
seL4 test supports only a serial console. It's easy to capture serial output for automatic testing, so our scripts tend to autoreboot (which loads the test suite over tftp), then capture the serial output using an expect script, to log errors. This works for all the platforms we support --- although the X86 ones are harder to script rebooting for, as it needs IPMI or similar.
AFAIK, noone has yet written any other console driver.
Peter C
-
Matthew Scaperoth -
Peter Chubb