Anyone else running into this issue with the latest clone? I had this all working just fine previously (maybe 6 months ago), but something must have been updated that breaks this. Not sure why.

Mike

On Tue, Jun 12, 2018 at 8:45 AM, Mike Clark <undefinedspace@gmail.com> wrote:
Adrian,

I am doing `make menuconfig`, then going to "Applications" and checking the box that says "Insecure: Give all devices to VM component". That is the only change I do, then recompile, copy the new image to my SD card, and boot.

Mike

On Mon, Jun 11, 2018 at 9:20 PM, <Adrian.Danis@data61.csiro.au> wrote:
Hi Mike,

In order to be acting as a hypervisor in the default configuration that you say booted fine seL4 will already be setup to run in nonsecure hypervisor mode. Given this can you elaborate on what 'the unsecure mode' is and how you are switching to it?

Adrian

On Sun 10-Jun-2018 10:08 PM, Mike Clark wrote:
> I just checked out a fresh copy of https://github.com/
> SEL4PROJ/camkes-arm-vm-manifest and built an image for the TK1 using the
> docker build environment. I copied the resulting image to an SD card and it
> boots fine.
>
> If I switch to the unsecure mode, I get an error on boot.
>
> SMMU Address translation error:
> ID: 98 address: 0xae5be000 type: 6 direction: 0x0
> IOPT permission: read 0x0 write 0x0 nonsecure 0x0
> [   10.204777] mmc1: ADMA error
>
>
> I have not made any changes, so my vm.smmu settings are all default.
>
> Any thoughts or help?
>
> Mike
>
>
>
> _______________________________________________
> Devel mailing list
> Devel@sel4.systems
> https://sel4.systems/lists/listinfo/devel
>