Kent.Mcleod@data61.csiro.au writes:
Hi Daniel, Two things to try:
First is to confirm that CONFIG_PRINTING is enabled to distinguish if the kernel is successfully starting its init process.
Also, please try resyncing your tree. The default manifest was updated yesterday; I tried it on the TK1-SOM this afternoon and it all worked.
I used the default manifest from https://github.com/SEL4PROJ/camkes-arm-vm-manifest.git
did make tk1_vm_defconfig
loaded the resulting image at 0x80408000 and started it with bootelf
The result hung for a little while at Jumping to kernel-image entry point...
then I see: Bootstrapping kernel Total 28 IOASID set up Region [c to 28) for SMMU caps Booting all finished, dropped to user space
and then Linux boots.