From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id ABA3CE00CB0; Thu, 10 Jan 2019 14:59:31 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [40.107.77.43 listed in list.dnswl.org] * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid X-Greylist: delayed 41925 seconds by postgrey-1.32 at yocto-www; Thu, 10 Jan 2019 14:59:25 PST Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-eopbgr770043.outbound.protection.outlook.com [40.107.77.43]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id EBED2E00C4E for ; Thu, 10 Jan 2019 14:59:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xilinx.onmicrosoft.com; s=selector1-xilinx-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=TmOJMlJQrIBHNe/xVRQnhKNfuFOJJ5R6YHKxQ3qQ5eE=; b=WsBOuy6A/vbQiGryr37w8z2Fd2ElBa2AV8XeaflEISms+hctdreU3sQ1C1rIZ+xMm+1psPFhZUz9ANMcDn3WqG+BcXJQIAlf8hryvDza+vl3YyXpEzLSq/XYYimUXu4ywJzvFLak+FfJI/WZOVljpt1MBINCYj/ZUcP8E7o8uZk= Received: from BYAPR02MB4888.namprd02.prod.outlook.com (52.135.234.202) by BYAPR02MB5557.namprd02.prod.outlook.com (20.177.230.79) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1495.6; Thu, 10 Jan 2019 19:26:30 +0000 Received: from BYAPR02MB4888.namprd02.prod.outlook.com ([fe80::5cb1:317e:a3ca:1399]) by BYAPR02MB4888.namprd02.prod.outlook.com ([fe80::5cb1:317e:a3ca:1399%5]) with mapi id 15.20.1516.016; Thu, 10 Jan 2019 19:26:30 +0000 From: Jiaying Liang To: "Pandey, Kamal" , "yocto@yoctoproject.org" Thread-Topic: bitbake openamp-image-minimal fails to create image Thread-Index: AdSmWDG603OeUfxeQYusuc4ZfFevdgACc8iwAA9BEDAABrMwsAB7TuiwAAJlgZAAGfqWEA== Date: Thu, 10 Jan 2019 19:26:30 +0000 Message-ID: References: <4d5f7a22db584df89e7e9f5404f845d2@ifm.com> <6f9664b4422a45dea24977f17e529033@ifm.com> <1855fa3943cd4ad69d41f6ffc5600597@ifm.com> In-Reply-To: <1855fa3943cd4ad69d41f6ffc5600597@ifm.com> Accept-Language: en-US X-MS-Has-Attach: X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=jliang@xilinx.com; x-originating-ip: [149.199.62.133] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BYAPR02MB5557; 6:EIe/vmYj22uMHw+jfgqDJnFckdsZgsfENtuwIkGcbRoYdeiCLgb+mregMc4GIa0XFAjUKv+382CFwb/ZgeqkNEdH+l6HIQfcrohscGPyRUGEbSEaX7QwsaRXucY61kSjJcut1HEnnBLzTBORFKg0pFt2eIZN3J6szYYjTEus1woviQ8KYES0fiG0Mge1lGK8oHTv1rHPpGSoFMPzL4wG4V+GDngAYMKM7vfgIqxj3XTM0MjbLUtdk41SFUjLD+v3XNPqT1JtfGarTXaemH0mRXVJ4rtBPK1iP80rHybbaXgcJIvWkFfBR6X/6i03xcBlTIWDzSF+jTKkGKBWJMTGJJmN859QJoGlbLfCT7g+XWmdSeWXL6Wsjj56WKdRAEPRxat2bZxyDD9HoWGlbqOKHQYlKs8u9+qX5TRBMc0oHulyJyTKy9WN9vhTpSrCxlJZ8BpwvmB1ALSOzW5qVuhocg==; 5:wPv9cHABuwOnjzL0cKIn7CElYV+QfQcPrG74gK4mrLTOU4HP9s2J+GM9Mtt3NpEMzkOzANNXI9kR2U9F4h4pFW2qgN5og39LB+oUZnVtJMtCmT8bhRTjxERs1knlpBWL1TmvCB9jrNkiTWstCAX1FCCwAjuOtMEf2bGwUmUpr9yuAatXC+tX5plztNHeMBgLLx9K5PXXUC5+HV6fH1NA/A==; 7:Tvdjt7dSGJYqcj5qO3bq+9w0iXiKXI9PVuC0K0tI8vApNsndGQXaPTC1KAnFguUOHvOxMPpLfeN12LSAtzY+sJv0OA06cpcrgtQTibZIyA+XbkymaOzd3qK66Bd+x1zRvmvn2dI332APumT6k2y+cQ== x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 076ac355-deac-4fae-fb53-08d67731861b x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600109)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:BYAPR02MB5557; x-ms-traffictypediagnostic: BYAPR02MB5557: x-microsoft-antispam-prvs: x-forefront-prvs: 0913EA1D60 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(39860400002)(136003)(366004)(396003)(51444003)(189003)(199004)(81166006)(93886005)(476003)(11346002)(81156014)(8676002)(53546011)(76176011)(2501003)(6436002)(7696005)(6506007)(105586002)(14444005)(110136005)(71200400001)(71190400001)(229853002)(33656002)(55016002)(567974002)(8936002)(446003)(25786009)(2906002)(316002)(256004)(86362001)(106356001)(74316002)(99286004)(478600001)(6306002)(54896002)(236005)(9686003)(53946003)(97736004)(6246003)(5660300001)(3846002)(790700001)(6116002)(186003)(26005)(102836004)(486006)(14454004)(7736002)(66066001)(53936002)(68736007); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR02MB5557; H:BYAPR02MB4888.namprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: xilinx.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: vKghxJi381nmhb1vpwBYBC82XGI3qYy1ni5fgrtVYp/6HAGAFkKFBQJXyQFgCAc3cnC9aucI/1pRgud2ugsDC1RfDwsvhYTzUZqm5D4IQb9eNmMOHZyKFqnEgulUUYhNqfFUzzzPglnb3xEUYVkRZxy2Rhlw6LG8J31WM2ULXFHiC9pnU3EYE/4lzkTKwrriw1NJf7nKHpda5tNX4+qsKdLf5ZbkeRUxNepOb9sfflJTLsXPG93Db4HyRAjStJGRxOROG642qAxd4kYOoM0pvu5Tt5kMNz5x6wU2MfHx7sifIC8C0AwURNTRQOEzAQP5 spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: xilinx.com X-MS-Exchange-CrossTenant-Network-Message-Id: 076ac355-deac-4fae-fb53-08d67731861b X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jan 2019 19:26:30.5024 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 657af505-d5df-48d0-8300-c31994686c5c X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR02MB5557 Subject: Re: bitbake openamp-image-minimal fails to create image X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2019 22:59:31 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_BYAPR02MB4888169BF6F2986ECD884429B0840BYAPR02MB4888namp_" --_000_BYAPR02MB4888169BF6F2986ECD884429B0840BYAPR02MB4888namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable From: Pandey, Kamal [mailto:Kamal.Pandey@ifm.com] Sent: Thursday, January 10, 2019 1:57 AM To: Jiaying Liang ; yocto@yoctoproject.org Subject: RE: bitbake openamp-image-minimal fails to create image Hi wendy, Thanks for replying. I have already enabled remoteproc, rpmsg and virtio in= the kernel configuration. I have also added CORE_IMAGE_EXTRA_INSTALL +=3D " \ kernel-modules \ " In my local.conf file. I generated BOOT.bin file from bootgen.bif file after adding the rpu firmwa= re: [destination_cpu=3Dr5-0] While booting the device I didn't see r5 code being booted. Now I am trying Building Linux Applications Using OpenAMP RPMsg in Linux Us= erspace Using meta-openamp layer. I found that there is a patch "Add Xilinx ZynqMP R5 remoteproc driver.patch= " to have a53 and r5 communication. Is this patch required for the purpose= of openamp in userspace? This patch was missing in meta-xilinx and I brought it to my custom layer, = but it failed to apply giving the following error: error: include/linux/firmware/xlnx-zynqmp.h: does not exist in index | error: include/linux/firmware/xlnx-zynqmp.h: does not exist in index | error: include/linux/firmware/xlnx-zynqmp.h: does not exist in index | error: drivers/firmware/xilinx/zynqmp.c: does not exist in index | error: include/linux/firmware/xlnx-zynqmp.h: does not exist in index | error: drivers/firmware/xilinx/zynqmp.c: does not exist in index | error: include/linux/firmware/xlnx-zynqmp.h: does not exist in index | [ERROR]: Application of .kernel-meta//patches//./0276-Add-Xilinx-ZynqMP-R= 5-remoteproc-driver.patch failed. | Patch needs to be refreshed. Sample resolution script: | .git/rebase-apply/resolve_rejects | ERROR: Could not apply patches for pdm3-rev-b-zynqmp. | ERROR: Patch failures can be resolved in the linux source directory /medi= a/iepl/iepl1/work/yocto_build/build_openamp/tmp/work-shared/pdm3-rev-b-zynq= mp/kernel-source) | WARNING: /media/iepl/iepl1/work/yocto_build/build_openamp/tmp/work/pdm3_r= ev_b_zynqmp-pdm3-linux/linux-yocto/4.14.79+gitAUTOINC+f1d93b219b-r0/temp/ru= n.do_patch.17384:1 exit 1 from 'exit 1' | ERROR: Function failed: do_patch (log file is located at /media/iepl/iepl= 1/work/yocto_build/build_openamp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/linu= x-yocto/4.14.79+gitAUTOINC+f1d93b219b-r0/temp/log.do_patch.17384) Now the Xilinx document UG1186 never mentioned about this patch or driver. = Also is this patch for the kernelspace implementation or userspace implemen= tation. [Wendy] the r5 remoteproc driver is to load RPU firmware from linux, and fo= r RPMsg in kernel space implementation. It is not required for userspace im= plementation. >From your error message, it looks like you don't have : include/linux/firmw= are/xlnx-zynqmp.h in your kernel. Did you use linux kernel from github.com/xilinx? And I am using tftp boot. I think that if r5 was able to boot it should sho= w me while booting as I am serially connected to the device. [Wendy] if you want to boot R5 from Linux, you will need to use r5 remotepr= oc driver to do so. By default, Linux will not auto boot R5. Best Regards, Wendy Please provide any pointers on this. Has anyone implemented this using meta= -openamp layer and no petalinux. Thanks From: Jiaying Liang > Sent: 10 January 2019 11:14 To: Manjukumar Harthikote Matha >; Pandey, Kamal >; = yocto@yoctoproject.org; meta-xilinx@yoctopro= ject.org Subject: RE: bitbake openamp-image-minimal fails to create image From: yocto-bounces@yoctoproject.org= [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Manjukumar Harthikote= Matha Sent: Monday, January 07, 2019 10:51 AM To: Pandey, Kamal >; yoct= o@yoctoproject.org; meta-xilinx@yoctoproject= .org Subject: Re: [yocto] bitbake openamp-image-minimal fails to create image +meta-xilinx mailing list From: Pandey, Kamal [mailto:Kamal.Pandey@ifm.com] Sent: Monday, January 07, 2019 8:59 AM To: yocto@yoctoproject.org; Manjukumar Harth= ikote Matha > Subject: RE: bitbake openamp-image-minimal fails to create image Hi, I solved the problem by using meta-openamp(branch should be similar to xili= nx version) layer in my yocto project and enabled "libmetal" and "open-amp"= packages in my image recipe. It compiled successfully. I also add rpmsg-e= cho-test, rpmsg-mat-mul , and rpmsg-proxy-app packages in the image and it= successfully compiled. I am building Linux Application that uses RPMsg in = user space. Now the executable generated from echo-test or mat-mul are in my host linux= master (a53-core). I have also created an r5-application using XSDK. What is the next step to have a communication between a53 and r5. How to us= e the generated elf file for r5 processor. Also I have enabled remoteproc, rpmsg, virtio in kernel configuration. But while using the command " $modprobe zynqmp_r5_remoteproc", I get the fo= llowing error: "modprobe: module zynqmp_r5_remoteproc not found in modules.dep" [Wendy] It doesn't look like the zynqmp_r5_remoteproc driver is compiled or= maybe it is compiled but not add into the system. Please check the following: * If your linux kernel has enabled in your kernel .config * If you have "kernel-modules" added to your image o E.g.: o CORE_IMAGE_EXTRA_INSTALL +=3D " \ o kernel-modules \ o " Best Regards, Wendy How can I boot the r5 processor and where to store the elf file generated. From: Manjukumar Harthikote Matha > Sent: 07 January 2019 13:53 To: Pandey, Kamal >; yoct= o@yoctoproject.org Subject: RE: bitbake openamp-image-minimal fails to create image Hi Kamal, Seems like the required kernel modules are missing causing the breakage. Enable them using kernel menuconfig (bitbake virtual/kernel -c menuconfig) = and then build the image Thanks, Manju From: yocto-bounces@yoctoproject.org= [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Pandey, Kamal Sent: Sunday, January 06, 2019 11:14 PM To: yocto@yoctoproject.org Subject: [yocto] bitbake openamp-image-minimal fails to create image Hello, I used the meta-openamp layer for r5-a53 communication. but when I simply ran $bitbake openamp-image-minimal, it gave me the follow= ing error: ERROR: openamp-image-minimal-1.0-r0 do_rootfs: Could not invoke dnf. Comman= d '/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zy= nqmp-pdm3-linux/openamp-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/= dnf -y -c /media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_r= ev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs/etc/dnf/dnf.conf= --setopt=3Dreposdir=3D/media/iepl/iepl1/work/yocto_build/build-open-amp/tm= p/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs/etc= /yum.repos.d --repofrompath=3Doe-repo,/media/iepl/iepl1/work/yocto_build/bu= ild-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.= 0-r0/oe-rootfs-repo --installroot=3D/media/iepl/iepl1/work/yocto_build/buil= d-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-= r0/rootfs --setopt=3Dlogdir=3D/media/iepl/iepl1/work/yocto_build/build-open= -amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/tem= p --nogpgcheck install kernel-module-virtio-ring kernel-module-virtio-rpmsg= -bus kernel-module-uio-pdrv-genirq kernel-module-virtio libopen-amp0 packag= egroup-base-extended kernel-image-fitimage-4.14.79-yocto-standard run-posti= nsts libmetal packagegroup-core-boot kernel-module-remoteproc' returned 1: Added oe-repo repo from /media/iepl/iepl1/work/yocto_build/build-open-amp/t= mp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/oe-rootfs= -repo Last metadata expiration check: 0:00:00 ago on Fri 04 Jan 2019 01:58:31 PM = UTC. No package kernel-module-virtio-ring available. No package available. No package kernel-module-virtio available. No package available. Error: Unable to find a match ERROR: openamp-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs ERROR: Logfile of failure stored in: /media/iepl/iepl1/work/yocto_build/bui= ld-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0= -r0/temp/log.do_rootfs.7153 ERROR: Task (/home/iepl/work/yocto_build/poky/../meta-openamp/recipes-opena= mp/images/openamp-image-minimal.bb:do_rootfs) failed with exit code '1' Can someone provide me a solution to this problem. Thanks --_000_BYAPR02MB4888169BF6F2986ECD884429B0840BYAPR02MB4888namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

 

From: Pandey, Kamal [mailto:Kamal.Pandey@ifm.= com]
Sent: Thursday, January 10, 2019 1:57 AM
To: Jiaying Liang <jliang@xilinx.com>; yocto@yoctoproject.org<= br> Subject: RE: bitbake openamp-image-minimal fails to create image

 

Hi wendy,

Thanks for replying. I have already enabled remoteproc,= rpmsg and virtio in the kernel configuration.

I have also added

CORE_IMAGE_EXTRA_INSTALL +=3D " \

kernel-= modules \

“=

In my local.conf file.

I generated BOOT.bin file from bootgen.bif file after a= dding the rpu firmware:

[destination_cpu=3Dr5-0] <path to RPU firmware>= ;

While booting the device I didn’t see r5 code bei= ng booted.

Now I am trying Building Linux Applications Using OpenA= MP RPMsg in Linux Userspace

Using meta-openamp layer.

I found that there is a patch “Add Xilinx ZynqMP R5 remoteproc driver.patch”  to = have a53 and r5 communication. Is this patch required for the purpose of&nb= sp; openamp in userspace?

This patch was missing in meta-xilinx and I brought it = to my custom layer, but it failed to apply giving the following error:=

 

error: include/linux/firmware/xlnx-zynqmp.h: does no= t exist in index

| error: include/linux/firmware/xlnx-zynqmp.h: does = not exist in index

| error: include/linux/firmware/xlnx-zynqmp.h: does = not exist in index

| error: drivers/firmware/xilinx/zynqmp.c: does not = exist in index

| error: include/linux/firmware/xlnx-zynqmp.h: does = not exist in index

| error: drivers/firmware/xilinx/zynqmp.c: does not = exist in index

| error: include/linux/firmware/xlnx-zynqmp.h: does = not exist in index

| [ERROR]: Application of .kernel-meta//patches//./0= 276-Add-Xilinx-ZynqMP-R5-remoteproc-driver.patch failed.<= /i>

|        &nb= sp; Patch needs to be refreshed. Sample resolution script:

|        &nb= sp;     .git/rebase-apply/resolve_rejects

| ERROR: Could not apply patches for pdm3-rev-b-zynq= mp.

| ERROR: Patch failures can be resolved in the linux= source directory /media/iepl/iepl1/work/yocto_build/build_openamp/tmp/work= -shared/pdm3-rev-b-zynqmp/kernel-source)

| WARNING: /media/iepl/iepl1/work/yocto_build/build_= openamp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/linux-yocto/4.14.79+gitAU= TOINC+f1d93b219b-r0/temp/run.do_patch.17384:1 exit 1 from 'exit 1'

| ERROR: Function failed: do_patch (log file is loca= ted at /media/iepl/iepl1/work/yocto_build/build_openamp/tmp/work/pdm3_rev_b= _zynqmp-pdm3-linux/linux-yocto/4.14.79+gitAUTOINC+f1d93b219b-r0/tem= p/log.do_patch.17384)

 

Now the Xilinx document UG1186 never mentioned about th= is patch or driver. Also is this patch for the kernelspace implementation o= r userspace implementation.

[Wendy] the r5 remoteproc driver is to load RPU firmware from l= inux, and for RPMsg in kernel space implementation. It is not required for = userspace implementation.

From your error message, it looks like you don’t have : include/linux/firmware/xlnx-zynqmp.h in your kernel.

Did you use linux kernel from github.com/xilinx?= =

 

And I am using tftp boot. I think that if r5 was able t= o boot it should show me while booting as I am serially connected to the de= vice.

[Wendy] if you want to boot R5 from Linux, you will need to use= r5 remoteproc driver to do so. By default, Linux will not auto boot R5.

 

Best Regards,

Wendy

 

Please provide any pointers on this. Has anyone impleme= nted this using meta-openamp layer and no petalinux.

Thanks

From: Jiaying Liang <jliang@xilinx.com>
Sent: 10 January 2019 11:14
To: Manjukumar Harthikote Matha <MANJUKUM@xilinx.com>; Pandey, Kamal <Kamal.Pandey@ifm.com>; yocto@yoctoproject.org; meta-xilinx@yoctoproject.org
Subject: RE: bitbake openamp-image-minimal fails to create image

 

 

 

From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Manjukumar Harthikote Matha
Sent: Monday, January 07, 2019 10:51 AM
To: Pandey, Kamal <Kamal.= Pandey@ifm.com>; yocto@yoctoproject.org; meta-xilinx@yoctoproject.org
Subject: Re: [yocto] bitbake openamp-image-minimal fails to create i= mage

 

+meta-xilinx maili= ng list

 

From: Pandey, Kamal [mailto:Kamal.Pandey@ifm.com]
Sent: Monday, January 07, 2019 8:59 AM
To: yocto@yoctoproject.org= ; Manjukumar Harthikote Matha <MANJUKUM@xilinx.com>
Subject: RE: bitbake openamp-image-minimal fails to create image

 

Hi,

I solve= d the problem by using meta-openamp(branch should be similar to xilinx vers= ion) layer in my yocto project and enabled “libmetal” and ̶= 0;open-amp” packages in my image recipe. It compiled successfully.  I also add rpmsg-echo-test,  rpmsg-mat-mul , and rpmsg-proxy-ap= p packages in the image and it successfully compiled. I am building Linux A= pplication that uses RPMsg in user space.

Now the= executable generated from echo-test or mat-mul are in my host linux master= (a53-core). I have also created an r5-application using XSDK.

What is= the next step to have a communication between a53 and r5. How to use the g= enerated elf file for r5 processor.

Also I = have enabled remoteproc, rpmsg, virtio  in kernel configuration.

But whi= le using the command “ $modprobe zynqmp_r5_remoteproc”, I get the following error:

&n= bsp;

“= modprobe: module zynqmp_r5_remoteproc not found in modules.dep”= ;

[= Wendy] It doesn’t look like the zynqmp_r5_remoteproc driver is compil= ed or maybe it is compiled but not add into the system.

<= o:p> 

P= lease check the following:

·       If your linux kernel has enabled in your kernel .config<= /p>

·       If you have “kernel-modules” added to your image

o   E.g.:

o   CORE_IMAGE_EXTRA_INSTALL +=3D " \

o       kernel-modules \

o   “

Best Re= gards,

W= endy=

How can= I boot the r5 processor and where to store the elf file generated.

From: Manjukumar Harthikote Matha <MANJUKUM@xilinx.com>
Sent: 07 January 2019 13:53
To: Pandey, Kamal <Kamal.= Pandey@ifm.com>; yocto@yoctoproject.org
Subject: RE: bitbake openamp-image-minimal fails to create image

 

Hi Kamal,

 

Seems like the require= d kernel modules are missing causing the breakage.

Enable them using kern= el menuconfig (bitbake virtual/kernel –c menuconfig) and then build t= he image

 

Thanks,

Manju

 

From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Pandey, Kamal
Sent: Sunday, January 06, 2019 11:14 PM
To: yocto@yoctoproject.org=
Subject: [yocto] bitbake openamp-image-minimal fails to create image=

 

Hello,

I us= ed the meta-openamp layer for r5-a53 communication.
but when I simply ran<= span lang=3D"EN-IN" style=3D"font-size:9.0pt;font-family:Consolas;color:#24= 292E"> $bitbake openamp-image-minimal, it gave me the following error:

 

ERROR: openamp-image-minimal-1.0-r0 do_rootfs: Cou= ld not invoke dnf. Command '/media/iepl/iepl1/work/yocto_build/build-open-a= mp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/recip= e-sysroot-native/usr/bin/dnf -y -c /media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_= b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs/etc/dnf/dnf.conf --= setopt=3Dreposdir=3D/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/w= ork/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs/etc/yu= m.repos.d --repofrompath=3Doe-repo,/media/iepl/iepl1/work/yocto_build/build-open-amp= /tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/oe-root= fs-repo --installroot=3D/media/iepl/iepl1/work/yocto_build/build-open-amp/t= mp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs --setopt=3Dlogdir=3D/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/= work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/temp --nogpg= check install kernel-module-virtio-ring kernel-module-virtio-rpmsg-bus kern= el-module-uio-pdrv-genirq kernel-module-virtio libopen-amp0 packagegroup-base-extended kernel-image-fitimage-4.14.79-yoct= o-standard run-postinsts libmetal packagegroup-core-boot kernel-module-remo= teproc' returned 1:

Added oe-repo repo from /media/iepl/iepl1/work/yoc= to_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image= -minimal/1.0-r0/oe-rootfs-repo

Last metadata expiration check: 0:00:00 ago on Fri= 04 Jan 2019 01:58:31 PM UTC.

No package kernel-module-virtio-ring available.

No package   available.=

No package kernel-module-virtio available.

No package   available.=

Error: Unable to find a match

 

ERROR: openamp-image-minimal-1.0-r0 do_rootfs: Fun= ction failed: do_rootfs

ERROR: Logfile of failure stored in: /media/iepl/i= epl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/= openamp-image-minimal/1.0-r0/temp/log.do_rootfs.7153

ERROR: Task (/home/iepl/work/yocto_build/poky/../m= eta-openamp/recipes-openamp/images/openamp-image-minimal.bb:do_rootfs) failed with exit code '1'

 

Can someone prov= ide me a solution to this problem.
Thanks

--_000_BYAPR02MB4888169BF6F2986ECD884429B0840BYAPR02MB4888namp_--