Re: [yocto] Error while adding a new recipe
I did the mentioned modification and it worked..
Thanks a lot..
On Thu, Jul 12, 2012 at 7:33 AM, Khem Raj raj.k...@gmail.com wrote:
On Thu, Jul 12, 2012 at 1:03 AM, Navani Srivastava
navani.srivast...@gmail.com wrote:
Sorry, but it didn't worked for me..
.bb file is something like-
PACKAGES = colorado
SRC_URI = file://colorado_gui_bk
do_install () {
#
# Create directories and install device independent scripts
#
install -d ${D}/{homedir}/Test
install -d ${D}${homedir}/Test/Bin
# install -m 0755 ${WORKDIR}/colorado_gui_bk
${D}${homedir}/Test/Bin
cp ${WORKDIR}/colorado_gui_bk
${D}${homedir}/Test/Bin
}
#FILES_${PN}-dbg += \
# ${homedir}/Test/Bin/.debug/colorado_gui_bk \
#
INHIBIT_PACKAGE_STRIP = 1
add
INSANE_SKIP_${PN} = arch
as well
Please review if anything else need to be added..
On Thu, Jul 12, 2012 at 1:08 PM, Khem Raj raj.k...@gmail.com wrote:
On Wed, Jul 11, 2012 at 9:03 PM, Navani Srivastava
navani.srivast...@gmail.com wrote:
Thanks for your reply..
It is a pre-built-binary which I am trying to put in a specific path
of
rootfs.
I didn't get what does it mean by packaging it seperately..
is this the only file in this package ? you might add
INHIBIT_PACKAGE_STRIP = 1 to the recipe then
but be aware this will disable stripping the binaries and if you have
other legit binaries that this
recipe is generating then they wont be stripped as well.
On Wed, Jul 11, 2012 at 8:04 PM, Khem Raj raj.k...@gmail.com wrote:
On Wed, Jul 11, 2012 at 5:28 AM, Navani Srivastava
navani.srivast...@gmail.com wrote:
ERROR: QA Issue: Architecture did not match (40 to 3) on
/work/armv6-vfp-poky-linux-gnueabi/colorado-1.0-r0/packages-split/colorado/home/Leica/Bin/colorado_gui_bk
what is this file ?
is it some precompiled binary or some firmware blob ?
you need to package is separately and then may be skip stripping just
that one package
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: QA Issue: Architecture did not match (20 to 62) on /work/virtex5-poky-linux
Hi Khem, On Jul 14, 2012, at 10:26 PM, Khem Raj wrote: On Fri, Jul 13, 2012 at 10:17 PM, Elvis Dowson elvis.dow...@gmail.com wrote: ERROR: QA Issue: Architecture did not match (20 to 62) on /work/virtex5-poky-linux/linux-xilinx-2.6.38-r00/packages-split/kernel-dev/usr/src/kernel/scripts/kconfig/kxgettext.o ERROR: QA run found fatal errors. Please consider fixing them. This is because kernel is trying to package tools which are built for your build host. Try this patch http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/miscid=e061aca8a9ad2e4342927b3d2ca4216ef3874936 The patch that you sent me works! Thank you very much for this! I've built both linux-2.6.38 and linux-3.0.0 for the PowerPC440 processor on the Xilinx Virtex-5 processor, against the latest updates to the yocto repos, as of today. Do you think you could apply your patch to oe-core, so that it's available mainstream? Best regards, Elvis ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto and Qt embedded
Hi Khem, I have to use Yocto Denzil branch (not the latest snapshot) because I'm developing for Freescale iMX53 QSB and fsl-arm branch is aligned with Denzil. From a fresh Denzil installation I edited local.conf and bblayer.conf files and run bitbake meta-toolchain-qte. The command ends successfully. So I tried to find g++ compiler using find command, into: /opt/poky/1.2.1/sysroots/i686-pokysdk-linux/ with no success. I found qmake command (into /opt/poky/1.2.1/sysroots/i686-pokysdk-linux/usr/bin) but when I set this Qt version in Qt creator the ABI detection fails, so I can't configure the right toolchain inside Qt creator and I can't build my application. Do I have to rerun the bitbake command? Am I missing any configuration? Thanks Giovanni -- Dott. Ing. Giovanni Foiani Cell:+39-349-3577515 Phone:+39-0532-97-4106 mail:giovanni.foi...@unife.it CenTec - Corso Guercino, 47 - 44042 Cento (FE) On Fri, Jul 13, 2012 at 9:04 PM, Khem Raj raj.k...@gmail.com wrote: On Wed, Jul 11, 2012 at 11:45 PM, Giovanni Foiani fno...@unife.it wrote: Where is the compiler located inside Poky SDK built from meta-toolchain-qte? somewhere like below is mine for x86_64 /opt/poky/1.2+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] linux-xilinx: uImage.dtb files not being generated anymore
Hi Khem, On Jun 30, 2012, at 7:41 PM, Khem Raj wrote: On Sat, Jun 30, 2012 at 4:07 AM, Elvis Dowson elvis.dow...@gmail.com wrote: Hi, On Jun 30, 2012, at 10:17 AM, Elvis Dowson wrote: About a week ago, my linux-xilinx builds used to correctly generate the *.dtb files, required for the PowerPC440 processor on my Xilinx ML-507 development board. After having recently updated poky, I find that the required *.dtb files are not generated anymore. Would someone be able to tell me which file I should take a look at to restore this functionality? My build configuration is as follows: Build Configuration: BB_VERSION= 1.15.2 TARGET_ARCH = powerpc TARGET_OS = linux MACHINE = virtex5 DISTRO= poky DISTRO_VERSION= 1.2+snapshot-20120630 TUNE_FEATURES = m32 fpu-soft ppc440 TARGET_FPU= soft meta meta-yocto= master:4d48398798c898c5db08294ba64d9bfc7daca19c meta-oe = master:3eb5f6eecf6faf7b2701f94b12cf779350d31acc meta-xilinx = master:c977270d6f0608cc5fa83f57254202713af37be0 I traced the reason for the dtb file not build due to the following commit: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=8c904eb643ad8ca1bc29cb2d870a80b355dcb341 Should I specify DTS_FILE in order to get my recipe to build the *.dtb? you need to define KERNEL_DEVICETREE = yourdtbfile I tried various combinations, but all of them did not yield a dtb file. KERNEL_DEVICETREE = virtex440-ml507.dtb (as you suggested in your original email, but I guess it might have been a typo? should be .dts?) KERNEL_DEVICETREE = virtex440-ml507.dts KERNEL_DEVICETREE = arch/powerpc/boot/dts/virtex440-ml507.dts How exactly should I specify the .dts to get yocto to generate the .dtb file? Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] linux-xilinx: uImage.dtb files not being generated anymore
Hi,
On Jul 15, 2012, at 9:23 PM, Elvis Dowson wrote:
I tried various combinations, but all of them did not yield a dtb file.
KERNEL_DEVICETREE = virtex440-ml507.dtb (as you suggested in your original
email, but I guess it might have been a typo? should be .dts?)
KERNEL_DEVICETREE = virtex440-ml507.dts
KERNEL_DEVICETREE = arch/powerpc/boot/dts/virtex440-ml507.dts
How exactly should I specify the .dts to get yocto to generate the .dtb file?
I found the solution, I had to ensure that the KERNEL_DEVICE tree variable
evaluate to the following
KERNEL_DEVICETREE = ${S}/arch/powerpc/boot/dts/virtex440-ml507.dts
i.e. it was missing the ${S} prefix.
Elvis Dowson
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] beagleboard not booting
On 12-07-14 9:23 AM, Edward Vidal wrote: Hello, git clone git://git.yoctoproject.org/poky.git http://git.yoctoproject.org/poky.git cd poky . oe-init-build-env MACHINE=beagleboard bitbake -v core-image-sato Hmmm. And here I was just thinking that things had been quiet on this front and it was time to get supported move to the 3.4 kernel tree. Created 2 partitions on /dev/sdb fdisk /dev/sdb Welcome to fdisk (util-linux 2.21.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/sdb: 7960 MB, 7960788992 bytes 255 heads, 63 sectors/track, 967 cylinders, total 15548416 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/sdb1 * 63 144584 72261 c W95 FAT32 (LBA) /dev/sdb2 144585 7132859 3494137+ 83 Linux format 2 partitions. mkfs.vfat -F 16 -n boot /dev/sdb1 mke2fs -j -L rootfs /dev/sdb2 remove the mmc /dev/sdb1 72098 0 72098 0% /run/media/vidal/boot /dev/sdb2 3441720 74096 3192920 3% /run/media/vidal/rootfs cd /home/vidal/poky/build/tmp/deploy/images cp MLO-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0 /run/media/vidal/boot/MLO cp u-boot-beagleboard-v2011.06+git5+b1af6f532e0d348b153d5c148369229d24af361a-r1.bin /run/media/vidal/boot/u-boot.bin cp uImage-3.0.32+git1+d282029891bba5440630a885b940dea5e34e3e2c_1+3ab688a78cac7b2e32afc83376a53370f2bd13b7-r4.0-beagleboard-20120712003552.bin /run/media/vidal/boot/uImage cd /run/media/vidal/rootfs tar jvxf /home/vidal/poky/build/tmp/deploy/images/core-image-sato-beagleboard-20120712003552.rootfs.tar.bz2 cp /home/vidal/uEnv.txt /run/media/vidal/boot cat /run/media/vidal/boot/uEnv.txt mpurate=auto dvimode=hd720 omapfb.vram=0:8M,1:4M,2:4M vram=16M optargs=consoleblank=0 console=tty0 console=ttyO2,115200n8 umount /run/media/vidal/boot umount /run/media/vidal/rootfs sync * - * Qodem 0.1.2 Capture Generated Fri, 13 Jul 2012 10:51:17 -0600 BEGIN * - * Texas Instruments X-Loader 1.5.0 (Jul 11 2012 - 21:01:18) Beagle xM Reading boot sector Loading u-boot.bin from mmc U-Boot 2011.06 (Jul 11 2012 - 21:01:18) OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Beagle unknown 0x02 No EEPROM on expansion board Die ID #15829ff80160a7450b02602d Hit any key to stop autoboot: 10 9 8 7 6 5 4 3 2 1 0 SD/MMC found on device 0 reading uEnv.txt 130 bytes read Importing environment from mmc ... reading uImage 3043164 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 8200 ... Image Name: Linux-3.0.32-yocto-standard Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3043100 Bytes = 2.9 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 3.0.32-yocto-standard (vi...@ws009.swbell.net http://us.mc1814.mail.yahoo.com/mc/compose?to=vi...@ws009.swbell.net) (gcc version 4.7.2 20120615 (prerelease) (GCC) ) #1 Wed Jul 11 20:38:46 MDT 2012 CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine: OMAP3 Beagle Board Reserving 16777216 bytes SDRAM for VRAM Memory policy: ECC disabled, Data cache writeback OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk ) SRAM: Mapped pa 0x4020 to va 0xfe40 size: 0x1 Clocking rate (Crystal/Core/MPU): 26.0/332/600 MHz Reprogramming SDRC clock to 33200 Hz Built 1 zonelists in Zone order, mobility grouping on. Total pages: 125952 Kernel command line: console=tty0 console=ttyO2,115200n8 mpurate=auto vram=16M o mapfb.mode=dvi:hd720 omapfb.vram=0:8M,1:4M,2:4M omapfb.debug=y omapdss.def_disp= dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) allocated 2097152 bytes of page_cgroup please try 'cgroup_disable=memory' option if you don't want memory cgroups Memory: 496MB = 496MB total Memory: 494448k/494448k available, 29840k reserved, 0K highmem Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xfff0 - 0xfffe ( 896 kB) DMA : 0xffc0 - 0xffe0 ( 2 MB) vmalloc : 0xe080 - 0xf800 ( 376 MB) lowmem : 0xc000 - 0xe000 ( 512 MB) modules : 0xbf00 - 0xc000 ( 16 MB) .init : 0xc0008000 - 0xc0058000 ( 320 kB) .text : 0xc0058000 - 0xc0613b0c (5871 kB) .data : 0xc0614000 - 0xc0671438 ( 374 kB) .bss : 0xc067145c
