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: 
Observer jsaxer
Observer
1,984 Views
Registered: ‎03-09-2015

New kernel build not getting included in image.ub

Using 2017.1, I added some messages to xilinx_uartps.c and ran petalinux-build. I see that the file is compiled, and a new kernel is made in

    ./build/tmp/work/plnx_aarch64-xilinx-linux/linux-xlnx/4.9-xilinx-v2017.1+gitAUTOINC+68e6869cfb-r0/linux-plnx_aarch64-standard-build/vmlinux

 

but this kernel is not copied to ./build/tmp/deploy/images/plnx_aarch64/vmlinux or to images/linux/vmlinux, and is not included in the image.ub.

 

How do I get the latest built kernel image with my driver changes into the bootable image? I have tried al the various combinations of yocto commands I can find, and have tried manually copying the correct kernel to the correct places, but it is always overwritten with this other, default kernel instead.

 

What am I doing wrong? There has to be a way to add, subtract or modify drivers and have them included in the bootable system.

0 Kudos
2 Replies
Observer kallensf
Observer
1,910 Views
Registered: ‎07-31-2017

Re: New kernel build not getting included in image.ub

What worked for me was to specify my own kernel.

- petalinux-config

- Linux components -> linux kernel -> ext-local-source

- External linux kernel source settings

0 Kudos
Observer hardik123
Observer
1,899 Views
Registered: ‎07-27-2017

Re: New kernel build not getting included in image.ub

you just create your Boot bin again then image.ub will be modified in that step

0 Kudos