I have created sdcard images for imx6 with Yocto project. I try to create an image with "bitbake core-image-x11" command but I keep having these errores.I think the first proble is about disk partition and the other problem is about do_rootfs function. Please do help if you have solved this.errors
The error is shown in your screenshot.
/usr/IMX/fsl-community-bsp-new/build/tmp/deploy/images/imx6qsabresd/zImage-imx6qsabresd.bin: No such file or directory.
You need to ensure that this file exists in your deploy directory prior to executing the do_rootfs to create your sdcard image.
Please post your .bbclass or .bbappend file, or local.conf so we can obtain more information.
Related
I am trying to build a system (Yocto based project) using bitbake and one of the steps is that it needs to retrieve an archive.zip file with a hex file in it from a Jenkins instance somewhere and install that somewhere within the kernel.
The problem now is that I have get a bitbake error on the do_fetch step of this precise recipe.
File: '/cache/downloads/firmware-17.zip' has sha256 checksum 6b565bbe776e3eabd883af7d1660db6ac2c13f13f16fbb1dbf6b9af42e31e9c9 when 6b565bbe776e3eabd883af7d1660db6ac2c13f13f16fbb1dbf6b9af42e31e9c9 was expected If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe: SRC_URI[sha256sum] = "6b565bbe776e3eabd883af7d1660db6ac2c13f13f16fbb1dbf6b9af42e31e9c9"
As you can see the expected checksum is identical between what bitbake reads and expects so I don't really understand what to do at the moment.
What I have already tried is:
Ensure that bitbake does a full clean build.
Bump the repository where archive.zip originates from so that the hash isn't the problem.
What I haven't tried yet is:
Manually download the firmware and place it in the /downloads folder of bitbake and mark the recipe as 'fetched' but since it is running in docker that is not a viable solution really.
Has anybody come across something like this?
I suspect there is a stray space in the value set in your recipe. The message hints at that with "9c9 was" showing a double space.
I am new to Yocto and following starter tutorials : https://tutorialadda.com/yocto
When I do source oe-init-build-env , this creates a build directory and moves me into it. Then when I do bitbake core-image-minimal , this builds the minimal image for me. All good.
Now I have added my own layer and recipe and run bitbake core-image-minimal again and it works.
However, how do I stop overwriting the same image in tmp/deploy/images every time I make a change (adding recipes or changing code etc.). How do I tell it to create a new image alongside the older one /s ?
Sorry if this question is primitive, but I can't seem to find a clear answer. Thanks.
I am new to yocto world and i am trying to build a custom image for raspberrypi-cm3.
i have built the image with no errors and i have a generated image folder in the attached photo,enter image description here that contains multiple files that are confusing me such as
rpi-basic-image-raspberrypi-cm3.rootfs.tar.bz2
rpi-basic-image-raspberrypi-cm3.rootfs.ext3
image-kernelversion-machine.bin
rpi-basic-image-raspberrypi-cm3.rootfs.rpi-sdimg
bootcode.bin
and .dtb, .dtbo files
Now i am trying to understand what files are to be flashed to my emmc? how the boot partition will be created?
I have searched and found that i should create a .img where i copy all the files and flash it to the emmc.
But i am wondering how the emmc will be partionned.
As i knew there must be a boot partition and a rootfs partition.
i hope someone can explain to me how does the yocto images should be flashed on the emmc and what files should be considered.
Generated with meta-raspberrypi metadata layer binary file is - rpi-basic-image-raspberrypi-cm3.rootfs.rpi-sdimg, ready to install without any additional modification, so please try install it on Your eMMC:
sudo umount /dev/sdX
sudo dd if=tmp/deploy/images/rpi-basic-image-raspberrypi-cm3.rootfs.rpi-sdimg bs=4M of=/dev/sdX
sudo umount /dev/sdX
I'm currently trying to build poky-tiny for imx6ulevk (using the BSP Yocto Project Environment provided by NXP).
I first followed the Quick Start Guide, tested and everything worked just fine. I then went to the usual local.conf file (/build/conf/local.conf) and changed the DISTRO variable to poky-tiny.
In poky-tiny distro file (/sources/poky/meta-yocto/conf/distro/poky-tiny.conf), I changed the virtual/kernel in the variable PREFERRED_PROVIDER_virtual/kernel to linux-imx and the PREFERRED_VERSION_linux-imx to 3.14.38 which is compatible (I think).
I finally added to the local.conf the variable IMAGE_FSTYPES with the value tar.bz2 ext3 sdcard.
At this point I tried to build using:
bitbake core-image-minimal
this runs without any problems. But it doesn't generate sdcard image or any u-boot images as is expected. The only files generated are:
core-image-minimal-imx6ulevk-20160517152114.rootfs.cpio.gz
core-image-minimal-imx6ulevk-20160517152114.rootfs.manifest
core-image-minimal-imx6ulevk.cpio.gz
core-image-minimal-imx6ulevk.manifest
modules-imx6ulevk.tgz
zImage
zImage--3.14.38-r0-imx6ul-14x14-evk-20160517152114.dtb
zImage--3.14.38-r0-imx6ul-14x14-evk-csi-20160517152114.dtb
zImage--3.14.38-r0-imx6ulevk-20160517152114.bin
zImage-imx6ul-14x14-evk-csi.dtb
zImage-imx6ul-14x14-evk.dtb
zImage-imx6ulevk.bin
And I got stuck without knowing how to deploy to the imx6ulevk. What did I do wrong? Why is yocto not generating the usual sdcard image?
If anyone gets this what worked for me was the following:
Turns out poky-tiny for imx6ulevk does not create sdcard images normally. So what you need to do, once you build it with a proper kernel, is to manually create a bootable sdcard. This can be done by using gparted cleaning everything in it and adding 2 partitions, then proceed as follow:
1 - First you use gunzip in the file core-image-minimal-imx6ulevk-...-rootfs.cpio.gz.
2 - Call cpio on the generated file: cpio -i -vd < core-image-minimal...-.cpio
3 - You just generated the root file system copy everything into one of the partitions.
4 - the zImage...* files are the generated kernel for the poky-tiny distro. Copy all but the symbolic links to the second partition. You might need to rename the files (I had to) if you're not sure what to rename to, first build regular poky using sdcard image and check out the proper names.
That's pretty much it, you should be able to boot imx6ulevk using the provided files.
I'm doing android open source project and I'm new to aosp.
I am building gingerbread in Ubuntu 14.04 64-bit.
I have managed to successfully compile the source code without any error, and now when I run the command 'emulator', I get the following error and my emulator is not running at all
emulator: WARNING: ignoring locked user data image at /home/hari/Android/aosp/out/target/product/generic/userdata-qemu.img
emulator: WARNING: Another emulator is running. user data changes will *NOT* be saved
emulator: ERROR: There is no user data image in your build directory. Please make a full build
I searched over the internet and was not able to find a guy with the similar problem. So, anyone have any idea? What could be the possible solution ?
Edit:
My out directory and userdata-qemu.img is locked! Is this unusual ??
Thanks in advance.
I think your file is locked... may be you copied some files from another user. Make sure you give the all your files some permissions.
cd one step back from your aosp root directory and use this command
chmod -Rv 755 youraospdirectory/
I had similar issues, but in my case the whole directory was the problem.
So it would be better to chmod the whole directory.