UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Visitor jesuslazaro
Visitor
1,013 Views
Registered: ‎02-25-2013

XEN and OpenAMP

Hi,

 

I have followed both the XEN and OpenAMP tutorials for Petalinux 2017.2:

Both Petalinux system work separately but when I tried to mix them there is an error when trying to launch a firmware in R5_0:

[  172.820418] Unhandled fault: ttbr address size fault (0x96000000) at 0xffffff8009300000
[  172.828485] Internal error: : 96000000 [#2] SMP
[  172.833040] Modules linked in: virtio_rpmsg_bus(+) rpmsg_user_dev_driver(O) rpmsg_core xen_netback xen_blkback xen_gntalloc xen_gntdev zynqmp_r5_remoteproc remoteproc virtio virtio_ring uio_pdrv_genirq
[  172.850948] CPU: 0 PID: 2117 Comm: udevd Tainted: G      D    O    4.9.0-xilinx-v2017.2 #1
[  172.859249] Hardware name: xlnx,zynqmp (DT)

Is there a way to use both systems at the same time?

0 Kudos
2 Replies
Observer bstahlman
Observer
949 Views
Registered: ‎01-31-2017

Re: XEN and OpenAMP


@jesuslazaro wrote:

Hi,

 

I have followed both the XEN and OpenAMP tutorials for Petalinux 2017.2:

Both Petalinux system work separately but when I tried to mix them there is an error when trying to launch a firmware in R5_0:

[  172.820418] Unhandled fault: ttbr address size fault (0x96000000) at 0xffffff8009300000
[  172.828485] Internal error: : 96000000 [#2] SMP
[  172.833040] Modules linked in: virtio_rpmsg_bus(+) rpmsg_user_dev_driver(O) rpmsg_core xen_netback xen_blkback xen_gntalloc xen_gntdev zynqmp_r5_remoteproc remoteproc virtio virtio_ring uio_pdrv_genirq
[  172.850948] CPU: 0 PID: 2117 Comm: udevd Tainted: G      D    O    4.9.0-xilinx-v2017.2 #1
[  172.859249] Hardware name: xlnx,zynqmp (DT)

Is there a way to use both systems at the same time?


Any luck root causing this? I think I may be seeing something similar. For me, the fault comes when I try to access a buffer allocated by mmap() from dom0. I'm using a Xen kernel built by Petalinux, and a dom0 built by buildroot.

Thanks,

Brett S.

0 Kudos
Highlighted
Visitor jesuslazaro
Visitor
935 Views
Registered: ‎02-25-2013

Re: XEN and OpenAMP

Hi,

 

No new clues. I think that Xen protects accesses to memory and it does not allow to mess with it.

 

In your case it may be useful to pass the memory region to Dom0 as a passthrough area. I have issues with that and I2C, but no luck for know. In my case the error may come from the driver, but since you are doing it by hand, you may try it.

 

You could try to follow the net passthrough demo (I cannot make it work, out of luck with XEN and OpenAMP). You could launch the DomU with the iomem line in the config. For example, if your mapped memory is in 0xff030000, something like:

 

name = "mmap test"
kernel = "/boot/Image"
extra = "console=hvc0 rdinit=/sbin/init"
iomem = [ "0xff030,1" ]
memory = 256
vcpus = 1

You may need to modify the Dom0 devicetree so that the area of memory is known, possibly with:

 

status = "disabled";
xen,passthrough = "1";

 

 

All of this if you do not need DMA. If you need it, there is extra work to do.

 

Regards,

 

Jesús

 

Tags (3)
0 Kudos