Hi Ihor, I've run sel4test and CAmkES samples on the Jetson TK1. They are OK. Only ARM VM can't work.
Yao On Tue, Feb 14, 2017 at 3:50 PM, <[email protected]> wrote: > I’ve seen this behaviour (stopped after loading the kernel in HYP mode) > before on what I suspect was malfunctioning hardware. > > Have you tried running a simple, non-VM, system on this hardware (is this > what your monitor-mode image was)? > > Ihor > > > > On 15 Feb 2017, at 10:28 am, [email protected] wrote: > > > > It works on our jetson. > > The uboot commands that we use are: > > `setenv autoload no && dhcp && tftpboot 0x81000000 jetson1/sel4-image` > > and then `bootelf 0x81000000` > > > > What compiler versions are you using? > > > > Kent. > > From: Devel <[email protected]> on behalf of SHI, Yao < > [email protected]> > > Sent: Wednesday, February 15, 2017 8:11 AM > > To: John Backes > > Cc: [email protected] > > Subject: Re: [seL4] CAmkES ARM VM boot on TK1 > > > > Yes, I think so. Can I do any change for the configure/code? > > > > Thanks, > > Yao > > > > On Tue, Feb 14, 2017 at 12:44 PM, John Backes <[email protected]> > wrote: > > We have been using this image for the TK1-SOM not the Jetson. Perhaps > that is the issue? > > > > - John > > > > On Tue, Feb 14, 2017 at 1:57 PM, SHI, Yao <[email protected]> wrote: > > Thanks John. I checked the bootm_boot_mode and it's already nonsec. > > > > Yao > > > > On Tue, Feb 14, 2017 at 11:51 AM, John Backes <[email protected]> > wrote: > > Hi Yao, > > > > I'm not sure if this is the issue, but did you change the environment > variable in uboot so that the tegra will boot in nonsecure hyp mode?: > > > > setenv bootm_boot_mode nonsec > > > > saveenv > > more details here: > > > > https://wiki.sel4.systems/Hardware/jetsontk1 > > > > - John > > > > > > On Tue, Feb 14, 2017 at 1:43 PM, SHI, Yao <[email protected]> wrote: > > Hi, > > > > I am trying to run CAmkES ARM VM on TK1. I downloaded built the image > using: > > > > repo init -u https://github.com/SEL4PROJ/camkes-arm-vm-manifest > > repo sync > > make tk1_vm_defconfig > > make > > > > And then ran the image on the hardware. It stopped after loading seL4 in > nonsecure HYP mode, > > Tegra124 (Jetson TK1) # bootelf > > CACHE: Misaligned operation at range [90000000, 90007408] > > CACHE: Misaligned operation at range [90007408, 9134c900] > > CACHE: Misaligned operation at range [9134c900, 9134c908] > > CACHE: Misaligned operation at range [91350000, 91360820] > > ## Starting application at 0x90000000 ... > > ELF loader: monitor mode init done > > Copy monitor mode vector from 90001000 to a7f00000 size 50 > > Number of IRQs: 192 > > Load seL4 in nonsecure HYP mode 600001da > > > > Then I tried to build a monitor mode image and got this, > > > > Tegra124 (Jetson TK1) # bootelf > > CACHE: Misaligned operation at range [90000000, 90007250] > > CACHE: Misaligned operation at range [90007250, 9134c710] > > CACHE: Misaligned operation at range [91350000, 91360820] > > ## Starting application at 0x90000000 ... > > ELF loader: monitor mode init done > > Copy monitor mode vector from 90001000 to a7f00000 size 50 > > ELF-loader started on CPU: ARM Ltd. Cortex-A15 r3p3 > > paddr=[90000000..9136081f] > > ELF-loading image 'kernel' > > paddr=[80000000..80031fff] > > vaddr=[e0000000..e0031fff] > > virt_entry=e0000000 > > ELF-loading image 'capdl-loader-experimental' > > paddr=[80032000..8155bfff] > > vaddr=[10000..1539fff] > > virt_entry=17580 > > Enabling MMU and paging > > Jumping to kernel-image entry point... > > abort() called. > > > > Anyone may tell me the possible problem? Thank you very much. > > > > Yao > > > > _______________________________________________ > > Devel mailing list > > [email protected] > > https://sel4.systems/lists/listinfo/devel > > > > > > > > > > > > _______________________________________________ > > Devel mailing list > > [email protected] > > https://sel4.systems/lists/listinfo/devel > >
_______________________________________________ Devel mailing list [email protected] https://sel4.systems/lists/listinfo/devel
