Hi Kent, I am using UUU to load and boot a stock U-Boot (built from an imx yocto repo for the imx8mmevk target) and then using FB to load and run the capdl. This is our normal dev setup.
I have found that U-Boot does seem to be the root cause of my problem. By using a U-Boot image that has been tailored to our own hardware rather than the EVK board I can get both the CI sel4test and a locally built version to run to completion on both the EVK board and our hardware. I'm not sure why the difference as our hardware is just a cut down of the EVK. I have been able to successfully remove the KernelAArch64SErrorIgnore workaround. Cheers, Zippy _______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
