Re: [yocto] Regarding Error occuring after changing configuration
you can use IMAGE_ROOTFS_SIZE ?= *"8192"* to increase Rootfs size. On Thu, Jul 5, 2018 at 12:16 AM Abhishek Kumar Rai < abhish...@eximiusdesign.com> wrote: > Hi Team, > > I am getting error while building yocto after changing the configuration. > > Please find set of below commands that i have used > $ bitbake virtual/kernel -c menuconfig > $ bitbake virtual/kernel > $ bitbake -k agl-demo-platform > > *| Disk > ~/build/tmp/work/nitrogen6x-agl-linux-gnueabi/agl-demo-platform/1.0-r0/deploy-agl-demo-platform-image-complete/agl-demo-platform-nitrogen6x-20180705063932.rootfs.sdcard: > 2185MB* > *| Sector size (logical/physical): 512B/512B* > *| Partition Table: msdos* > *| Disk Flags:* > *| * > *| Number Start End SizeType File system Flags* > *| 1 4194kB 12.6MB 8389kB primary lba* > *| 2 12.6MB 2181MB 2168MB primary* > *| * > *| mkfs.fat: warning - lowercase labels might not work properly with DOS > or Windows* > *| mkfs.fat 4.1 (2017-01-24)* > *| Disk full* > *| WARNING: exit code 1 from a shell command.* > *| ERROR: Function failed: do_image_sdcard (log file is located at > ~/build/tmp/work/nitrogen6x-agl-linux-gnueabi/agl-demo-platform/1.0-r0/temp/log.do_image_sdcard.6362)* > *ERROR: Task > (~/kapil/meta-agl-demo/recipes-platform/images/agl-demo-platform.bb:do_image_sdcard) > failed with exit code '1'* > > > *NOTE: Tasks Summary: Attempted 7063 tasks of which 7059 didn't need to be > rerun and 1 failed.*I think due to change in configuration rootfs size is > increased and the current rootfs size is small that is not able to > accommodate the thae changed size. > If it is so can anybody please provide steps to change the rootfs size . > > Can you please give your inputs regarding this. > > > *Regards,* > > *Abhishek Rai* > > The information contained in this e-mail message (including any > > attachments) may be confidential, proprietary, privileged, or otherwise > > exempt from disclosure under applicable laws. It is intended to be > > conveyed only to the designated recipient(s). Any use, dissemination, > > distribution, printing, retaining or copying of this e-mail (including its > > attachments) by unintended recipient(s) is strictly prohibited and may > > be unlawful. If you are not an intended recipient of this e-mail, or > believe > > that you have received this e-mail in error, please notify the sender > > immediately (by replying to this e-mail), delete any and all copies of > > this e-mail (including any attachments) from your system, and do not > > disclose the content of this e-mail to any other person. Thank you for > your cooperation. > > *This e-mail message (including any attachments) may be confidential, > proprietary, privileged, or otherwise exempt from disclosure under > applicable laws. If you are not an intended recipient, please delete this > message. Thank you.* > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- Thanks and Regards, Prakash K S +91 9620140303 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] struggling with initramfs
Try Adding
KERNEL_INITRAMFS = "-initramfs"
in platform specific .conf file
Thanks!
Prakash
On Tue, Jul 3, 2018 at 11:53 AM Tim Hammer wrote:
>
> Can anyone point me to a step-by-step tutorial or simple how-to on
> creating and using an initramfs with my kernel for ARM aarch64?
>
>
> I have tried creating my own:
> - boot-image.bb file with IMAGE_FSTYPES = "cpio.gz".
> - local.conf has INITRAMFS_IMAGE_BUNDLE = "1"
> - linux.bbappend has INITRAMFS_IMAGE = "boot-image"
>
> This all seems to be "correct" to the extent that bitbake linux tries to
> do the right thing.
>
> However, I get a failure in do_bundle_initramfs- "mv: cannot stat
> 'arch/arm64/boot/Image': No such file or directory".
>
> To the best of my (limited) debugging abilities with Yocto, it seems like
> the kernel image backup has already been run when it gets to this point and
> the Image file in that directory has already been moved to Image.bak. If I
> comment out the mv statement in kernel.bbclass causing the failure, the
> process continues, but the initramfs does not seem to get populated or
> perhaps installed into my kernel image as I get kernel panics that I have
> been unable to get past.
>
>
> I decided to take a different approach and try using the
> core-image-minimal-initramfs recipe as INITRAMFS_IMAGE. By commenting out
> the COMPATIBLE_HOST entry I am able to build a kernel for ARM aarch64. I
> can even seem to boot into this initramfs- it counts down waiting for
> removable media; seems to find my primary rootfs on sda3, but there is no
> rootfs.img file there so says it is dropping to a shell (although I never
> get a prompt...).
>
> Thinking I could start with that recipe and work to get rid of the live
> stuff and just get to a busybox prompt before trying to run my unique init
> commands, I copied core-image-minimal-initramfs.bb to my-
> core-image-minimal-initramfs.bb in my layer and changed INITRAMFS_IMAGE
> to "my- core-image-minimal-initramfs".
> However, I obviously missed something in the configuration as I get an
> error in go_bundle_initramfs again:
> kernel-source/scripts/gen_initramfs_list.sh:
> Cannot open
> '/.../linux-qoriq/4.14-r0/build/usr/my-core-image-minimal-initramfs-{machine}.cpio'
>
> Any help would be greatly appreciated.
> Thank you!
> --
>
> .Tim
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
Thanks and Regards,
Prakash K S
+91 9620140303
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Adding GCC to system root image
Try Removing line: IMAGE_INSTALL +="opkg" from poky/meta-qti-bsp/recipies-products/images/ BASE_IMAGE.inc Thanks! Prakash On Thu, Jun 21, 2018 at 6:59 PM Khem Raj wrote: > On Thu, Jun 21, 2018 at 4:02 PM Krishna Priya > wrote: > > > > Hello all, > > > > I am trying to add gcc to the system image by modifying the following > files. > > poky/meta-qti-bsp/recipies-products/images/ BASE_IMAGE.inc > > > > + IMAGE_INSTALL +="opkg" > > + IMAGE_INSTALL +="packagegroup-core-buildessential" > > > > poky/build/conf/local.conf > > + EXTRA_IMAGE_FEATURES = "tools-sdk dev-pkgs" > > > > When I build the whole image, I get the following errors : > > update-alternatives: Error: cannot register alternative cmp to /bin/cmp > since it is already registered to /usr/bin/cmp > > update-alternatives: Error: cannot register alternative diff to > /bin/diff since it is already registered to /usr/bin/diff > > update-alternatives: Error: cannot register alternative cmp to /bin/cmp > since it is already registered to /usr/bin/cmp > > update-alternatives: Error: cannot register alternative diff to > /bin/diff since it is already registered to /usr/bin/diff > > update-alternatives: Error: cannot register alternative ar to > /usr/bin/ar since it is already registered to /bin/ar > > update-alternatives: Error: cannot register alternative strings to > /usr/bin/strings since it is already registered to /bin/strings > > . > > . > > . > > . > > . > > ERROR: Multilib check error: duplicate files > poky/build/tmp-glibc/work/XXX80XX-oe-linux/machine-drone-image/1.0-r0/multilib/lib32/usr/include/fpu_control.h > poky/build/tmp-glibc/work/XXX80XX-oe-linux/machine-drone-image/1.0-r0/rootfs/usr/include/fpu_control.h > is not the same > > ERROR: Multilib check error: duplicate files > poky/build/tmp-glibc/work/XX80XX-oe-linux/machine-drone-image/1.0-r0/multilib/lib32/usr/include/fpu_control.h > poky/build/tmp-glibc/work/apq8096-oe-linux/machine-drone-image/1.0-r0/rootfs/usr/include/fpu_control.h > is not the same > > ERROR: Function failed: do_rootfs > > > > Please let me know the workaround to solve this error. Thanks. > > perhaps providing more information about which target arch and which > release etc. would be helpful. > If you post Build Configuration thats emitted by bitbake at beginning > of build, it provides good information on baseline. > > > Regards, > > -Priya. > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- Thanks and Regards, Prakash K S +91 9620140303 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Configuring speed of SD card read
Can you elaborate little more. On Thu, Apr 26, 2018 at 12:24 PM, Nishina A. Pervin < nishina.per...@nestgroup.net> wrote: > Hi > > > > > > I am using yocto Krogoth build for imx6q Sabreauto board. > > > > What is the rate at which data is read from SD card? Can we configure it > for higher speed from Uboot or Kernel > > > > Awaiting your favorable reply > > > > Regards, > > Nishina > -- > > *Confidentiality Statement / Disclaimer* : This message and any > attachments is intended for the sole use of the intended recipient. It may > contain confidential information. Any unauthorized use, dissemination or > modification is strictly prohibited. If you are not the intended recipient, > please notify the sender immediately then delete it from all your systems, > and do not copy, use or print. Internet communications are not secure and > it is the responsibility of the recipient to make sure that it is > virus/malicious code exempt. > > The company/sender cannot be responsible for any unauthorized alterations > or modifications made to the contents. If you require any form of > confirmation of the contents, please contact the company/sender. The > company/sender is not liable for any errors or omissions in the content of > this message. > -- > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- Thanks and Regards, Prakash K S +91 9620140303 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] where is useradd-example.bb
you can find in the oe-core openembedded-core/meta/classes/useradd.bbclass and openembedded-core/meta/classes/useradd_base.bbclass Thanks! Prakash On Tue, Apr 24, 2018 at 4:45 AM, Greg Wilson-Lindberg wrote: > I'm trying to understand adding a user in a recipe and in the > documentation it says to consult meta-skeleton/recipes-skeleton/useradd/u > seradd-example.bb. the meta-skeleton directory doesn't exist and I can't > find the file anywhere else. I've done a search on the net and I don't get > any hits on the file either, lots of references in the manuals, bot not the > file. > > > Can anyone tell me where to find it? > > > Regards, > > Greg > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- Thanks and Regards, Prakash K S +91 9620140303 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Encrypt Root FIle system as part of RPI sdcard image using cryptsetup.
Hi, I wanted to encrypt the Root file system parttition for the RPI3 SDcard image, it would be great if anybody have some suggestion on this. Note: Below are the steps i am using to encrypt, same kind of steps i want to do automate, when we issue dd command automatically it should create encrypted RFS partition. sudo cryptsetup -s 512 luksFormat /dev/sdb3 /home/tel/enc.key sudo cryptsetup luksOpen -d /home/tel/enc.key /dev/sdb3 example sudo mkfs.ext4 /dev/mapper/example sudo mount -t ext4 /dev/mapper/example /mnt/block3 sudo mount -t ext4 /dev/sdb2 /mnt/block2 sudo cp -ax /mnt/block2/* /mnt/block3/ sudo umount /mnt/block3 sudo umount /mnt/block2 sudo cryptsetup luksClose example Decryption part i have added as part of boot up process, working perfectly fine. I need help in encrypting using cryptsetup. Thanks! Prakash -- Thanks and Regards, Prakash K S +91 9620140303 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig file (or fragment files) not used
just create patch and run bitbake -c patch recipename, then check defconfig
file in your build folder, if your patch worked properly then the changes
will be available in your defconfig file.
Thanks!
Prakash
On Thu, Mar 29, 2018 at 4:12 PM, Vincent Daanen <
vincent.daa...@orthotaxy.com> wrote:
> Hi,
>
>
>
> What’s the difference between fragment and patch ?
>
> I can easily make a patch but how do I make sure the patch will be applied
> to the .config file ?
>
>
>
> Thanks for your help
>
>
>
> Vincent
>
>
>
> *De :* Prakash Ks
> *Envoyé :* jeudi 29 mars 2018 11:46
> *À :* Khem Raj
> *Cc :* Vincent Daanen ;
> yocto@yoctoproject.org
> *Objet :* Re: [yocto] defconfig file (or fragment files) not used
>
>
>
> Hi Vincent,
>
> Its better to create patch and apply from platform specific kernel recipes.
>
> if you need more info let me know.
>
> Thanks!
>
> Prakash
>
>
>
> On Thu, Mar 29, 2018 at 1:55 PM, Khem Raj wrote:
>
>
>
> On 3/28/18 11:00 PM, Vincent Daanen wrote:
>
> On 3/28/18 9:27 AM, Vincent Daanen wrote:
>
> Hi,
>
> I want to add CAN driver support to the kernel. Here is the procedure
> I
> followed:
>
> 1. Generate a .config file
> 2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
> 3. Update it: set at the end the config to enable CAN as follows
>
> # CAN Bus
>
> CONFIG_NET=y
>
> CONFIG_CAN=y
>
> CONFIG_CAN_RAW=y
>
> CONFIG_CAN_BCM=y
>
> CONFIG_CAN_GW=y
>
> #
>
> # CAN Device Drivers
>
> #
>
> CONFIG_CAN_VCAN=y
>
> # CONFIG_CAN_SLCAN is not set
>
> CONFIG_CAN_DEV=y
>
> # CONFIG_CAN_CALC_BITTIMING is not set
>
> # CONFIG_CAN_LEDS is not set
>
> # CONFIG_CAN_SJA1000 is not set
>
> 4. Update the linux-yocto_%.bbappend file as follows
>
> SUMMARY = "Recipe to configure kernel as required"
>
> LICENSE = "CLOSED"
>
> inherit kernel-yocto
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>
> SRC_URI += file://defconfig
>
> 5. Request rebuilt:
>
> bitbake linux-yocto-rt -c cleansstate
>
> bitbake -k linux-yocto-rt
>
> Once the image started (with qemu), I check if the CAN is enabled
> (using zcat /proc/config.gz | grep CAN) and I always get “CAN not set”
>
> I also tried using fragment and I got the same result ☹
>
> According the user manual, it seems to me I’m doing the right think!
>
> Does someone know why my defconfig file is not taken into account ?
>
>
> If you are using linux-yocto for your kernel provider then I wouldr
> recommend that you look into developer manual.
>
> you should look into using config fragments to modify the needed
> options e.g. see
> https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#cha
> nging-the-configuration
>
>
>
> I don't understand what you mean. That's what I'm doing. I followed the
> procedure described in the link you provide... Can u explain ?
>
>
> Create a file for config fragment say can.cfg and put all options you want
> to change in that file and then add that to SRC_URI
> you dont need to create full defconfig.
>
>
>
> Thanks
>
> Vincent
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>
> --
>
> Thanks and Regards,
>
> Prakash K S
>
> +91 9620140303
>
--
Thanks and Regards,
Prakash K S
+91 9620140303
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig file (or fragment files) not used
Hi Vincent,
Its better to create patch and apply from platform specific kernel recipes.
if you need more info let me know.
Thanks!
Prakash
On Thu, Mar 29, 2018 at 1:55 PM, Khem Raj wrote:
>
>
> On 3/28/18 11:00 PM, Vincent Daanen wrote:
>
>> On 3/28/18 9:27 AM, Vincent Daanen wrote:
>>>
Hi,
I want to add CAN driver support to the kernel. Here is the procedure
I
followed:
1. Generate a .config file
2. Copy it to meta-myWork/recipes-kernel/linux/files/defconfig
3. Update it: set at the end the config to enable CAN as follows
# CAN Bus
CONFIG_NET=y
CONFIG_CAN=y
CONFIG_CAN_RAW=y
CONFIG_CAN_BCM=y
CONFIG_CAN_GW=y
#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=y
# CONFIG_CAN_SLCAN is not set
CONFIG_CAN_DEV=y
# CONFIG_CAN_CALC_BITTIMING is not set
# CONFIG_CAN_LEDS is not set
# CONFIG_CAN_SJA1000 is not set
4. Update the linux-yocto_%.bbappend file as follows
SUMMARY = "Recipe to configure kernel as required"
LICENSE = "CLOSED"
inherit kernel-yocto
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI += file://defconfig
5. Request rebuilt:
bitbake linux-yocto-rt -c cleansstate
bitbake -k linux-yocto-rt
Once the image started (with qemu), I check if the CAN is enabled
(using zcat /proc/config.gz | grep CAN) and I always get “CAN not set”
I also tried using fragment and I got the same result ☹
According the user manual, it seems to me I’m doing the right think!
Does someone know why my defconfig file is not taken into account ?
>>> If you are using linux-yocto for your kernel provider then I wouldr
>>> recommend that you look into developer manual.
>>>
>>> you should look into using config fragments to modify the needed
>>> options e.g. see
>>> https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#cha
>>> nging-the-configuration
>>>
>>
>> I don't understand what you mean. That's what I'm doing. I followed the
>> procedure described in the link you provide... Can u explain ?
>>
>>
> Create a file for config fragment say can.cfg and put all options you want
> to change in that file and then add that to SRC_URI
> you dont need to create full defconfig.
>
>
> Thanks
>>
>> Vincent
>>
>> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
Thanks and Regards,
Prakash K S
+91 9620140303
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
