[meta-xilinx] AMP using Yocto meta-xilinx

[Edward Wingate]

I created a fragment that configures the linux-xlnx kernel to allow AMP:
CONFIG_HIGHMEM=y
CONFIG_VMSPLIT_2G=y
CONFIG_ZYNQ_REMOTEPROC=m
CONFIG_RPMSG_OMX=m
CONFIG_RPMSG_FREERTOS_STAT=m
(These kernel config settings are based on the ug978 AMP guide.)

The bitbake command succeeded and after booting the new kernel, I
attempted to release the 2nd CPU from Linux with:
modprobe zynq_remoteproc

But this resulted in:
modprobe: module zynq_remoteproc not found in modules.dep

And when I looked at /lib/modules/3.14.2-xilinx/modules.dep, the file
is empty (zero length) and there are no modules in the directory
either.  I would think at least some modules would be present in the
distribution, if not the one I want.

In log.do_install for linux-xlnx, I do see the following (among many others):
INSTALL drivers/remoteproc/zynq_remoteproc.ko

And I do see the module in the poky build image directory:
./poky/build/tmp/work/<architecture>/linux-xlnx/3.14-xilinx+git2b48a8aeea7367359f9eebe55c4a09a05227f32b-r0/image/lib/modules/3.14.2-xilinx/kernel/drivers/remoteproc/zynq_remoteproc.ko

And zynq_remoteproc.ko is listed in
./poky/build/tmp/work/<architecture>/linux-xlnx/3.14-xilinx+git2b48a8aeea7367359f9eebe55c4a09a05227f32b-r0/image/lib/modules/3.14.2-xilinx/modules.order
as well.

Why didn't the module make it to the image?  I didn't see any obvious
errors in the log.do_deploy or log.do_package either.  Is there
another log I can check?

Thanks,
Edward


On Tue, Nov 25, 2014 at 10:03 AM, Joe MacDonald
<Joe_MacDonald at mentor.com> wrote:
> [Re: [meta-xilinx] AMP using Yocto meta-xilinx] On 14.11.25 (Tue 09:50) Edward Wingate wrote:
>
>> What is the difference between "virtual/kernel" and "linux-xlnx"?
>> Will they both build/make the same kernel?
>
> Sometimes.  :-)
>
> The information you're probably needing is right here:
>
> http://www.yoctoproject.org/docs/1.7/bitbake-user-manual/bitbake-user-manual.html#bb-bitbake-providers
>
> -J.
>
>>
>> Thanks,
>> Edward
>>
>>
>> On Sat, Nov 22, 2014 at 11:31 AM, Mike Looijmans
>> <mike.looijmans at topic.nl> wrote:
>> > On 11/21/2014 07:58 PM, Elvis Dowson wrote:
>> >>
>> >> Hi Edward,
>> >>
>> >> Type the following command to clean and reconfigure the kernel:
>> >>
>> >> bitbake linux-xilinx -c clean -f
>> >> bitbake linux-xilinx -c configure -f
>> >> bitbake linux-xilinx -c menuconfig -f
>> >> bitbake linux-xilinx -c compile -f
>> >> bitbake linux-xilinx -c deploy -f
>> >
>> >
>> > Use:
>> >
>> > bitbake virtual/kernel -c menuconfig
>> >
>> > Then from the menuconfig, save the configuration file to where your bitbake
>> > recipe will pick it up. Otherwise, your changes will be lost the next run of
>> > the kernel.
>> >
>> > And bitbake is smart enough to figure out the dependencies, so just running:
>> >
>> > bitbake virtual/kernel
>> >
>> > will install and deploy the new kernel after you've changed the
>> > configuration. All those "-f" (force) options aren't needed, and you also
>> > don't need to specify all the single steps. You can add a "-c deploy" if you
>> > like.
>> >
>> >
>> >
>> > --
>> > Mike Looijmans
>> > --
>> > _______________________________________________
>> > meta-xilinx mailing list
>> > meta-xilinx at yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/meta-xilinx
> --
> -Joe MacDonald.
> :wq