-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow openamp_gs.pdf and meet build error. #8
Comments
which petalinux version do you use? if you are using petalinux 2014.4 or above, and if you are using Linux as master, please do not using the zynq_remoteproc driver from this openamp git, but use the zynq_remoteproc directly from the kernel. You can run "petalinux-config -c kernel" from petalinux, go to remoteproc submenu, and select the driver. The Zynq remoteproc in this repo hasn't been updated for the newer kernel. Prefer to remove it from here, and update the document to use the one directly from Xilinx kernel |
@wjliang i am using petalinux 2013.10 and using linux master. i believe that i found the root cause of the build error, as blow. but i have no ider why my kernel miss this header file(inux/irqchip/arm-gic.h)? kinreven@ubuntu:~/openamp/zynq-amp-linux/build/linux/rootfs/modules/zynq_remoteproc_driver$ make make[1]: Entering directory |
@wjliang , i found the linux kernel of petalinux 2013.10 is 3.8. In this kernel version, we should include "asm/hardware/gic.h", and not "linux/irqchip/arm-gic. h". so i guess this remoteproc driver is for linux 3.10 or above. as what you commented, the open-AMP framework could work with petalinux 2014.4 or above. and could you update the getting started documents for betalinux 2015.2? BTW, if you add a section how to run this AMP system on qemu, i believe that more and more people can get started with the project. |
I just checked the driver inside the open-amp, the last commit shows it works with kernel 3.17, which is matches the one with petalinux v2014.4. If you want to use 3.8 kernel, you can use this HEAD: 211f8ad Sure, we will add AMP system on QEMU later. Just last time when I tested it, it runs very very slow in QEMU, |
@wjliang, i have work well with petalinux 2013.10 by QEMU. Thank you very much. |
@wjliang Is there a version of OpenAMP that works with Peatlilnux 2014.2 (kernel version 3.14)? I tried using both the current version and the commit you posted above but both are not working for me. If I use the 3.8 version, I get the same error kinreven got during petalinux-build. If I use the current version, I get this error during modprobe: i have also changed the ipino from 6 to 8 as has been suggested for the newer kernels. Thanks, |
Hi Josh, I haven't tried OpenAMP with 3.14.2 kernel. but I have tried with 3.17 about the IPINO, have you check /proc/interrupts to see if 6 and 8 are Best Regards, On Fri, Oct 9, 2015 at 4:26 AM, joshkern notifications@github.com wrote:
|
I'm going through the same steps on 2014.4 just for debugging purposes, but ultimately I want to use 2014.2 since I'm using that version for all my other tools (Vivado, SDK, etc.). I have checked /proc/interrupts, and before adding the remoteproc node on the device tree, the only IPIs that are occupied are IPI1 through IPI7. And after adding the remoteproc node to the device tree, I see "Firmware kick" appear as whatever IPI I set ipino to. |
@wjliang About the original comment you made on this thread. You said if using Petalinux 2014.4+ we should use the "zynq_remoteproc" that's built into the kernel. Isn't that the same driver as "zynq_remoteproc_driver" found in /components/modules/ ? The only other remoteproc driver is the generic one, just "remoteproc". Is this the one that you meant? |
Hi Josh, Since it is very confusing to have the remoteproc driver in multiple However, the zynq_remotepro_driver in github is obsolete, and it will be Best Regards, On Sat, Oct 10, 2015 at 5:56 AM, joshkern notifications@github.com wrote:
|
Hi Josh, Since it is very confusing to have the remoteproc driver in multiple However, the zynq_remotepro_driver in github is obsolete, and it will be Best Regards, On Sat, Oct 10, 2015 at 5:56 AM, joshkern notifications@github.com wrote:
|
@wjliang I'm still confused. If those two drivers are the same, how is one obsolete and the other is valid? |
Hi Josh, the zyqn remoteproc driver in the github will not be maintained or updated I should have said the zynq_remoteproc_driver in openamp github repo will Best Regards, On Mon, Oct 12, 2015 at 11:43 PM, joshkern notifications@github.com wrote:
|
For anyone trying to follow the OpenAMP Framework Getting Started Guide using Petalinux 2014.4, make sure to use: modprobe zynq_remoteproc firmware="/zc702evk/baremetal/matrix_multiply/firmware" instead of modprobe zynq_remoteproc firmware="/lib/firmware/zc702evk/baremetal/matrix_multiply/firmware" Took me a couple days of experimentation/kernel debugging to figure out the simple change |
openamp_gs.pdf:
5. Build PetaLinux
a. Change into the <master_root>
$ cd <master_root>
b. Execute the following command:
$ petalinux-build
kinreven@ubuntu:~/openamp/xilinx-zynq-linux$ petalinux-build
INFO: Checking component...
INFO: Generating make files and build linux
INFO: Generating make files for the subcomponents of linux
INFO: Building linux
[INFO ] pre-build linux/rootfs/rpmsg_echo_test_kern_app
[INFO ] pre-build linux/rootfs/rpmsg_mat_mul_kern_app
[INFO ] pre-build linux/rootfs/rpmsg_proxy_dev_driver
[INFO ] pre-build linux/rootfs/rpmsg_user_dev_driver
[INFO ] pre-build linux/rootfs/zynq_remoteproc_driver
[INFO ] pre-build linux/rootfs/echo_test
[INFO ] pre-build linux/rootfs/echo_test_baremetal_fw
[INFO ] pre-build linux/rootfs/fwupgrade
[INFO ] pre-build linux/rootfs/mat_mul_baremetal_fw
[INFO ] pre-build linux/rootfs/mat_mul_demo
[INFO ] pre-build linux/rootfs/peekpoke
[INFO ] pre-build linux/rootfs/proxy_app
[INFO ] pre-build linux/rootfs/rpc_demo_baremetal_fw
[INFO ] pre-build linux/rootfs/uWeb
[INFO ] build system.dtb
[INFO ] build linux/kernel
[INFO ] update linux/u-boot source
[INFO ] generate linux/u-boot configuration files
[INFO ] build linux/u-boot
[INFO ] Setting up stage config
[INFO ] Setting up rootfs config
[INFO ] Updating for armv7a-vfp-neon
[INFO ] Updating package manager
[INFO ] Expanding stagefs
[INFO ] build kernel in-tree modules
[INFO ] modules linux/kernel
[INFO ] build linux/rootfs/rpmsg_echo_test_kern_app
[INFO ] modules linux/kernel
[INFO ] build linux/rootfs/rpmsg_mat_mul_kern_app
[INFO ] modules linux/kernel
[INFO ] build linux/rootfs/rpmsg_proxy_dev_driver
[INFO ] modules linux/kernel
[INFO ] build linux/rootfs/rpmsg_user_dev_driver
[INFO ] modules linux/kernel
[INFO ] build linux/rootfs/zynq_remoteproc_driver
[INFO ] modules linux/kernel
[ERROR] make[6]: *** [/home/kinreven/openamp/xilinx-zynq-linux/build/linux/rootfs/modules/zynq_remoteproc_driver/zynq_remoteproc_driver.o] Error 1
[ERROR] make[5]: *** [module/home/kinreven/openamp/xilinx-zynq-linux/build/linux/rootfs/modules/zynq_remoteproc_driver] Error 2
[ERROR] make[4]: *** [sub-make] Error 2
[ERROR] make[3]: *** [modules_only] Error 2
[ERROR] make[2]: *** [modules] Error 2
[ERROR] make[1]: *** [sub_build_component_/none/modules/multi/zynq_remoteproc_driver] Error 2
ERROR: Failed to build linux
The text was updated successfully, but these errors were encountered: