Hi Bryan,
We have seen this problem before [http://sel4.systems/pipermail/devel/2015-March/000291.html].
The theory is that an asynchronous abort that is caused by the bootloader is propagating through to the kernel.
Asynchronous aborts are masked globally when building in release mode, but it was thought that they would be a valuable debug feature when building in debug mode.
A work around to your problem is to disable the abort in all build configurations by changing #ifdef DEBUG to #if 0 on this line of the kernel source:
https://github.com/seL4/seL4/blob/master/include/arch/arm/arch/machine/regis...
- Alex Kroh
________________________________________
From: Bryan Ching [bryanching7373@gmail.com]
Sent: Wednesday, 28 October 2015 08:49
To: Alexander Kroh
Cc: devel@sel4.systems
Subject: Re: [seL4] Running CAmkES Sample Application on Sabre Lite Board
So I tried running the sample application on my Sabre Lite board again but with the settings in menuconfig changed to "Cortex-A9" and "iMX6". However, when I run the "bootelf" command in minicom, I am getting an error. Any suggestions?
Here is what is on my console screen:
U-Boot > bootelf
## Starting application at 0x20000000 ...
ELF-loader started on CPU: ARM Ltd. Cortex-A9 r2p10
paddr=[20000000..2010c01f]
ELF-loading image 'kernel'
paddr=[10000000..10031fff]
vaddr=[e0000000..e0031fff]
virt_entry=e0000000
ELF-loading image 'capdl-loader-experimental'
paddr=[10032000..10215fff]
vaddr=[8000..1ebfff]
virt_entry=f460
Enabling MMU and paging
Jumping to kernel-image entry point...
Bootstrapping kernel
Caught cap fault in send phase at address 0x0
while trying to handle:
vm fault on data at address 0xda1c1556 with status 0x1c06
in thread 0xffefd500 "rootserver" at address 0xf460
On Tue, Oct 27, 2015 at 1:37 AM, Bryan Ching