[yocto] How to enable the LTP in “core-image-basic”
Hi,
How to enable the LTP in “core-image-basic”
I have tried to enable the LTP for “core-image-basic” for that i have edit
“core-image-basic.bb” --> IMAGE_FEATURES += "ssh-server-openssh ltp" but the
final executable image does not contains the ltp utiltiy.
Than i tried the add the “tools-testapp” but in that case also in final image
no ltp.
Also tried to add the RDEPEND_${PN} += "ltp" in the image recipe file but still
in am not able to see the ltp image in my final running image on qemu.
In all the cases during the bitbake build the ltp packages has been build but
the image is not yet added in final running image.
Could you please suggest me what setp is missing, why it's not get added in my
final image?
Thanks & Regards
Amit K
The contents of this e-mail and any attachment(s) may contain confidential or
privileged information for the intended recipient(s). Unintended recipients are
prohibited from taking action on the basis of information in this e-mail and
using or disseminating the information, and must notify the sender and delete
it from their system. L&T Infotech will not accept responsibility or liability
for the accuracy or completeness of, or the presence of any virus or disabling
code in this e-mail"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] uimage instead of zImage
Edward, Your zImage is booting fine. The kernel starts and then tries to mount the root file system. But it cannot find it. It's looking for a UBIFS but cannot find it: . > VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0): error -19 > Please append a correct "root=" boot option; here are the available > partitions: > VFS: Unable to mount root fs on unknown-block(0,0) > User configuration error - no valid root filesystem found > Kernel panic - not syncing: Invalid configuration from end user prevents > continu > ing > You may have had additional error messages before the ones above that you copied into your e-mail such as: UBIFS error (pid 1): ubifs_check_node: bad CRC: calculated 0xdfca80ed, read 0x7b7c0f6b UBIFS error (pid 1): ubifs_check_node: bad node at LEB 0:0 UBIFS error (pid 1): ubifs_read_node: expected node type 6 That would be an indicator that the UBIFS root file system was not created correctly on your flash device. How did you create it? Rudi ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] uimage instead of zImage
Hello all, I made some changes to my uEnv.txt mpurate=auto bootcmd="mmc rescan 0; fatload mmc 0:1 0x8030 uImage; bootm 0x8030" dvimode="hd720 omapfb.vram=0:8M,1:4M,2:4M" vram=16M optargs="consoleblank=0" console="ttyO2 console=tty0,115200n8" chgs uImage to zImage in the bootcmd line above. Still would not boot? setenv bootcmd "mmc rescan 0; fatload mmc 0:1 0x8020 zImage; bootz 0x8020" setenv vram "16M" setenv bootfile "zImage" printenv echo $vram echo $bootfile echo $bootcmd run bootcmd If I make the above setenv at the u-boot prompt I get the kernel to boot, but get a kernel panic. VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0): error -19 Please append a correct "root=" boot option; here are the available partitions: VFS: Unable to mount root fs on unknown-block(0,0) User configuration error - no valid root filesystem found Kernel panic - not syncing: Invalid configuration from end user prevents continu ing CPU: 0 PID: 1 Comm: swapper Not tainted 3.10.11-yocto-standard #1 [] (unwind_backtrace+0x0/0xec) from [] (show_stack+0x20/0x24 ) [] (show_stack+0x20/0x24) from [] (dump_stack+0x20/0x28) [] (dump_stack+0x20/0x28) from [] (panic+0x84/0x1c0) [] (panic+0x84/0x1c0) from [] (mount_block_root+0x1fc/0x244) [] (mount_block_root+0x1fc/0x244) from [] (prepare_namespace +0x94/0x1c4) [] (prepare_namespace+0x94/0x1c4) from [] (kernel_init_freea ble+0x1e8/0x238) [] (kernel_init_freeable+0x1e8/0x238) from [] (kernel_init+0 x1c/0xf4) [] (kernel_init+0x1c/0xf4) from [] (ret_from_fork+0x14/0x20) zImage-omap3-beagle.dtb is the name of my dtb file. This is a new file that I had seen before in my beagleboard until dora build. I had seen in my zedboard build. Any and all help will be appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] threads set in local.conf
Hello all, Is this loading what others on a similar system are experiencing (see below)? I first was setting my threads to 6 on a AMD 6 core system. In the mega-manual i found 5.4. Configuring the local.conf File Briefly, set BB_NUMBER_THREADS and PARALLEL_MAKE to twice your host processor's number of cores. I am creating an image with 8017 tasks for the beagleboard. I set threads to 12 and now the build is proceeding much more rapid than when threads were set to 6. In 30 minutes the build has completed 2435 tasks or about 25%. I am seeing a fairly high load 35. 30. 24 and the fan is been at high speed since the build started. The system has 8G of memory and now it is using and it was using about 13800 of swap space. Any and all help will be appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] missing reference to "-ptest" packages for packagegroups in dev manual?
section 5.2.2 in current yocto dev manual reads: "inherit packagegroup sets appropriate default values and automatically adds -dev and -dbg complementary packages for every package specified in PACKAGES." but oe core's packagegroup.bbclass contains the snippet: for postfix in ['-dbg', '-dev', '-ptest']: genpackages.append(pkg+postfix) so should that explanation also not mention the "-ptest" complementary package being added as well? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
