Has anyone had issues with serial when running the test suite on a Raspberry Pi 3b?
Currently I am following the blog post:
https://research.csiro.au/tsblog/sel4-raspberry-pi-3/
In the seL4test project I have successfully compiled sel4test-driver-image-arm-bcm2837 from rpi3_debug_xml_defconfig. Along with this I have the following files: bootcode.bin, start.elf, u-boot.bin, and config.txt.
Bootcode.bin and start.elf are from the current Raspian firmware. Config.txt just contains a line to enable UART ("enable_uart=1") and one to point and u-boot.bin ("kernel=u-boot.bin"). And per the comment section of the seL4 post I downgraded the version of u-boot to before March 2017 (currently using Jan 2017).
I am not deviating from the blog posting but I am experiencing an issue not mentioned. I have no serial output (I do have a u-boot terminal prompt through HDMI, so I can load/boot the binary). When I boot seL4 I receive the misaligned cache messages (through HDMI) and then it hangs. Without serial I have no eyes to see if the seL4 tests are running.
Other than wiring into the RPI3 UART (GND/TX/RX on pins 6/8/10) and enabling UART in config.txt is there another step I'm missing?
Thanks for any direction you can point me in, Steve