I’ve been working with a VM and docker container created by the good folks at DornerWorks. I had a compile time error with the camkes-arm-vm-manafest tree called out in their "Getting Started” lab. However, I was able to successfully compile an image using the instructions and files in their single_vm_lab. I am loading that image onto an SD card with their pre-built boot.bin. At the U-boot prompt I load that image to 0x10000000 and subsequently type “go 0x10000000”. The image seems to start the initial boot just fine but I get an exception when it tries to jump to the kernel. image entry point. Looking at the value of esr_eli1 it appears that something is trying to write to a protected register. Wondering if there is some sort of switch setting on the board or special flags that need to be sent to u-boot to keep this from happening.
Here is the console output:
ZynqMP> fatload mmc 0 0x10000000 dorner 22183936 bytes read in 1472 ms (14.4 MiB/s) ZynqMP> go 0x10000000 ## Starting application at 0x10000000 ...
ELF-loader started on CPU: ARM Ltd. Cortex-A53 r0p4 paddr=[10000000..1152e06f] No DTB passed in from boot loader. Looking for DTB in CPIO archive...found at 100f4058. Loaded DTB from 100f4058. paddr=[237000..23bfff] ELF-loading image 'kernel' paddr=[0..236fff] vaddr=[ff8000000000..ff8000236fff] virt_entry=ff8000000000 ELF-loading image 'capdl-loader' paddr=[23c000..1854fff] vaddr=[400000..1a18fff] virt_entry=4088d0 ELF loader relocated, continuing boot... Enabling MMU and paging Jumping to kernel-image entry point...
ELF-LOADER: Synchronous exception received: esr_el1: 86000004 elr_el1: ff8000000000 spsr_el1: 600003c5 far_el1: ff8000000000 abort() called.