Is there any documentation on how the VMM works? If I wanted to start
hacking on the VMM and extend its capability, where should I start
looking to learn how it works, etc?
That might be a pretty broad topic, because there are lots of ways the
VMM can be extended, I'm sure. Broad is fine, until I
ther you are asking about the arm or x86 VMM.
>
> Adrian
>
>
> On Fri 09-Jun-2017 2:26 AM, Mike Clark wrote:
>
> Is there any documentation on how the VMM works? If I wanted to start
> hacking on the VMM and extend its capability, where should I start
> looking to learn h
they
> are structured differently.
>
> Anna.
>
>
> ____
> From: Devel on behalf of Mike Clark
>
> Sent: Friday, 9 June 2017 10:56 PM
> To: Danis, Adrian (Data61, Kensington NSW)
> Cc: devel@sel4.systems
> Subject: Re: [seL4] vmm docum
ng HSTR to trap, where should that be handled? Also
in the seL4_Fault_VCPUFault case?
On Wed, Jun 14, 2017 at 1:17 PM, Mike Clark wrote:
> Thanks Anna. That is great. Is there a quick and easy way to get up
> and running with hypercalls on ARM?
>
> On Mon, Jun 12, 2017 at 8:17 PM, wrote
ed by HSTR should end up being sent to the VMM by seL4 as a
> seL4_Fault_VCPUFault (You can look in kernel/src/arch/arm/32/hyp_traps.S
> under "Traps taken to HYP mode" to see where the trap enters the kernel).
>
> Kind regards,
> Kent McLeod.
>
nd
> kernel/include/arch/arm/arch/object/vcpu.h) where you would have to add the
> assembly to read and write to the registers yourself.
>
> Kind regards,
> Kent McLeod
>
> From: Mike Clark
> Sent: Thursday, June 22, 2017 12:04
m_get_vcpu(fault->vm), reg,
> fault_emulate(fault, res.value));
> if (error) {
> ZF_LOGF("Write registers failed");
> return -1;
> }
>
> Let me know if this answers your question.
>
> Kind regards,
> Ke
ormation
> should be stored).
>
> I'd be interested to hear more about what is causing the fault.
>
> Kind regards,
> Kent
>
>
> From: Mike Clark
> Sent: Saturday, June 24, 2017 5:04 AM
> To: Mcleod, Kent (Data61, Kensin
Something else I just realized. I'm calling a print_fault on these new
traps I added. All of the ones that handle just fine have an FSR value
that looks like 0x03800047 or 0x03870007. The one that results in the
failed assertion has FSR of 0x47.
On Mon, Jun 26, 2017 at 8:31 AM, Mike Clark
bits of an entry in the first or second level
translation table to be b00, then there will be a page fault any time
that page is accessed. How would I do this in seL4 from the VMM? Is
that currently possible to do?
Thanks!
On Thu, Jun 8, 2017 at 12:26 PM, Mike Clark wrote:
> Is there
Yes, it appears to be down.
Mike
On Oct 2, 2017 12:39 PM, wrote:
Is it just me or is everyone having trouble accessing the seL4 website?
I’m getting the following:
MOD_PYTHON ERROR
ProcessId: 29222
Interpreter:'sel4.systems.keg.ertos.in.nicta.com.au'
ServerName: 'sel4.sy
It does not support the TX2 currently. Only the TK1 from the jetson
line is supported.
Mike
On Thu, Oct 5, 2017 at 8:23 AM, wrote:
> Hi ,
>
> I am newbie to sel4 and currently working on one hobby project.I want to
> bring sel4 kernel on TX2 board.
> Can you guide me that is there any support a
I don't believe raspberry pi is supported for virtualization. I followed
the instructions on https://github.com/SEL4PROJ/camkes-arm-vm/blob/
master/README.md to get it working on the TK1. Wasn't too hard.
On Jan 26, 2018 4:48 AM, "Joel Svensson" wrote:
> Hello,
>
> I'm trying to form an underst
Daniel,
In theory yes. I don't know if there are any build scripts or instructions
however. Note that you have to have an armel kernel. I think Ubuntu only
ships armhf. Not sure about the others.
On Mar 5, 2018 12:02 PM, "Daniel Wang" wrote:
> Hi all,
>
> I was able to compile the camkes-arm-vm
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 translatio
o 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
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
wrote:
> Adrian,
>
> I am doing `make m
-( )
>
> [1]
>
> https://github.com/seL4/seL4/commit/80d32b160989c55f9fdc33fce1bf60
> 5ac1b42f1e
>
> https://github.com/SEL4PROJ/camkes-arm-vm/commit/
> f3948cf41978bee33179ac7a814eefc4fe30b5c2
>
>
> [2] https://developer.nvidia.com/embedded/tegra-k1-reference
> -
t;
> cmake -DTk1Insecure=True . && ninja
>
> Kent.
> --
> *From:* Mike Clark
> *Sent:* Friday, June 22, 2018 12:01 AM
> *To:* Mcleod, Kent (Data61, Kensington NSW)
> *Cc:* Danis, Adrian (Data61, Kensington NSW); devel@sel4.systems
>
> *Subject:* Re: [seL4]
kes#L278
>
> Kent.
>
>
>
> ------
> *From:* Mike Clark
> *Sent:* Tuesday, June 26, 2018 6:00 AM
>
> *To:* Mcleod, Kent (Data61, Kensington NSW)
> *Cc:* Danis, Adrian (Data61, Kensington NSW); devel@sel4.systems
> *Subject:* Re: [seL4] P
Is it currently possible to boot the camkes-vm-example applications using
qemu?
I followed the directions here (https://github.com/seL4/camkes-vm-examples)
to get a build of the minimal application.
I then tried to follow the directions here (
https://docs.sel4.systems/Hardware/Qemu/#running-qemu
I've been doing
# ../init-build.sh -DAARCH32=TRUE -DTk1Insecure=TRUE -DCAMKES_VM_APP=tk1_vm
# ninja
If that doesn't work can you post logs?
On Thu, Oct 4, 2018 at 1:39 PM Daniel Wang wrote:
> Hi all,
>
> It seems CAmkES-arm-vmm has been immigrated to cmake, How can I build it?
> I tried to bui
or can work in ARM? It would be good to have the
> communication between VM and native seL4 process.
>
> Thanks again!
>
>
> Best Regards
> -Daniel Wang
>
>
>
> On Oct 4, 2018, at 2:36 PM, Mike Clark wrote:
>
> I've been doing
>
> # ../init-b
To anyone who has followed the stackexchange proposed seL4 site, make sure
you go and vote on questions. As of right now, for the site to move on to
the next phase it must get 10 more followers and have 34 more questions
with a score of +10 or better.
On Wed, Nov 14, 2018 at 5:11 PM wrote:
> Hi
Any reason you aren't using the Docker image to build everything?
https://github.com/SEL4PROJ/seL4-CAmkES-L4v-dockerfiles
On Tue, Dec 4, 2018, 8:26 PM Dave Richards I thought I got all of the host dependencies installed, but evidently I am
> doing something wrong. I am building on Debian 9 (x8
I'm using the docker image to build the CAmkES ARM VMM project using
roughly the instructions here:
https://docs.sel4.systems/VM/CAmkESARMVM.html (they are slightly out of
date).
I do:
../init-build.sh -DAARCH32=TRUE -DCAMKES_VM_APP=vm_minimal -DPLATFORM=tk1
ninja
Then I copy the resulting image
t;
> Thanks,
>
> Chris Guikema
>
>
>
> DornerWorks
>
>
>
> *From:* Devel *On Behalf Of *Mike Clark
> *Sent:* Friday, January 10, 2020 3:22 PM
> *To:* devel@sel4.systems
> *Subject:* [seL4] Problem booting camkes arm vmm on TK1 from SD Card
>
>
> C
fine with bootelf. Any
thoughts?
Mike
On Fri, Jan 10, 2020 at 3:46 PM Mike Clark wrote:
> That did the trick Chris. Thanks!
>
> On Fri, Jan 10, 2020 at 3:30 PM Chris Guikema <
> chris.guik...@dornerworks.com> wrote:
>
>> Mike,
>>
>>
>>
>> Can you d
gt; Regards,
> Yanyan
>
> On Fri, 2020-01-24 at 15:24 -0500, Mike Clark wrote:
> > Chris,
> >
> > Looks like I might have spoken too soon. When I use go instead of
> > bootelf, the board actually resets. Here are the log messages:
> >
> > Tegra124 (Jetson TK1
k1 to be efi. You can remove the
> “tk1” from the “efi_list” and running “ccmake .” should allow you to choose
> the output setting as an elf. I’ve seen some issues where efi images don’t
> boot properly, but not with u-boot, so I can’t be sure your exact problem.
>
>
>
> Thanks,
ck to make sure I had done this. I am still not able to
boot the ARM VMM.
setenv bootm_boot_mode nonsec
saveenv
On Mon, Jan 27, 2020 at 10:41 AM Mike Clark
wrote:
> Hi Chris,
>
> Thank you for the suggestion. I removed tk1 from the efi_list (so now it
> is the empty string). I rebuil
boot.
Mike
On Mon, Jan 27, 2020 at 11:27 AM Mike Clark
wrote:
> One update on this. I pulled the sel4test-manifest project and built that
> for the TK1. When it built the efi image, I wasn't able to get it to work
> on my TK1 device. When I made the changes to the settings and got it
Thanks Kent for looking at this.
I downloaded the image you sent and it gets stuck after I issue the bootefi
command. I let it sit for a few minutes and it never goes anywhere (console
output is pasted below)
You mentioned that "A reason why ELF works for seL4test and not for
camkes-arm-vm is pot
Hi Kent,
Thanks for the suggestions. My loadaddr was set to 0x8100. I tried
using 0x8400 and it booted just fine in secure mode. This is on the
Nvidia TK1.
If I build with -DTk1Insecure=TRUE, I do have some issues. I get:
Undelivered IRQ: 85
Loading Linux: 'linux' dtb: 'linux-dtb'
instal
Did you try anything from my thread from January?
http://sel4.systems/pipermail/devel/2020-January/002595.html
On Thu, Mar 5, 2020, 5:03 PM Travis Wheatley <
travis.wheat...@emergentspace.com> wrote:
> Hello all,
>
> I am spinning up on sel4 and having difficulty booting a kernel on a
> Jetson T
see nothing at all on the serial port (aka, stdout).
>
> At this point I completely stumped. Is there some tweak I need to make to
> the serial port code before building?
>
> Other suggestions?
>
> On Mar 5, 2020, at 4:11 PM, Mike Clark wrote:
>
> Did you try anything
The camkes-vm-examples readme mentions that the Nvidia TX2 should support
multiple VMs but it is untested. If you try to build the vm_multi app for
TX2 you just get an error that the platform is unsupported.
Has anyone tried vm_multi on TX2? Do you have a working devices.camkes that
you can share?
I have seL4 running on a TK1 using linux-tk1-initrd. I'd like to get
the linux-tk1-debian version running to load the userspace off of the
emmc drive of the TK1. FWIW, I did flash the TK1 to the latest
verison, R21.5.
The default DTS has root=/dev/mmcblk0p2 in the bootargs. When booting
with this,
econfigure tzdata
> # Update everything
> apt-get update
>
> # Cleanup and leave
> apt-get clean
> rm /etc/resolv.conf
> exit
>
> # At this stage you can create a cpio archive to then extract out onto the SD
> partition of the TK1
> # Assuming your partion is mounted
39 matches
Mail list logo
