Hello, Any and all help will be appreciated. With Angstrom the linux-omap_3.1.0-r1a is built. This uses meta-ti/receipes-kernel/linux/linux-omap4_3.1.0.bb which has
SRC_URI = "git://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git;protocol=git;branch=ti-ubuntu-3.1-1282 \ Angstrom is using bitbake 1.15.2 OE Build Configuration: BB_VERSION = "1.15.2" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "pandaboard" DISTRO = "angstrom" DISTRO_VERSION = "v2012.05" TUNE_FEATURES = "armv7a vfp neon cortexa9" TARGET_FPU = "vfp-neon" meta-angstrom = "angstrom-v2012.05-yocto1.2:6a2febed13f179c042c2371b2e86286c 80c0df5e" meta-oe toolchain-layer meta-efl meta-gpe meta-gnome meta-xfce meta-initramfs = "denzil:a6f56d7eabe50dc55198aa8b8b349dbbb40757b1" meta-opie = "master:efa3892b20a4ef80274e56e5633ebd62c16f9731" meta-java = "master:3386ea6c96096f107f43f282f654e5afa456109e" meta-browser = "master:c47f59df2e723495679c751cbdf6a8c6adec4b6a" meta-mono = "master:83f8233b0498aadb18bf7605c3ba6c71d9e13a3a" meta-kde = "master:5b0882d951cfd71886d423c190faaa7c7f932333" meta-ti = "angstrom-staging-yocto1.2:edfd9649cbd16b2cdb5385954c0441c7b With meta-ti and yocto the linux-omap_3.1.0-r0 would hang up do a do_fetch. This uses meta-ti/receipes-kernel/linux/linux-omap4_3.1.0.bbwhich has SRC_URI = "git://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git;protocol=git;branch=ti-ubuntu-3.1-1282 \ Yocto is using bitbake 1.17.0 Build Configuration: BB_VERSION = "1.17.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Unknown" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "pandaboard" DISTRO = "poky" DISTRO_VERSION = "1.3+snapshot-20121230" TUNE_FEATURES = "armv7a vfp neon" TARGET_FPU = "vfp-neon" meta meta-yocto = "master:4a36a32567ecfbc7ce7b967803e6e23314953ef5" meta-ti = "master:d3ff5630a74640f46ca2ceaef1aa1baa86b9b795" I found the following at http://www.mail-archive.com/yocto@yoctoproject.org/msg09315.html and https://lists.yoctoproject.org/pipermail/yocto/2012-October/012023.html Both of these sites have deferences to changing protocol=git to protocol=http I just changed my recipe meta-ti/receipes-kernel/linux/linux-omap4_3.1.0.bb which has SRC_URI = "git://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git;protocol=git;branch=ti-ubuntu-3.1-1282 \ to meta-ti/receipes-kernel/linux/linux-omap4_3.1.0.bb which has SRC_URI = "git://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git;protocol=http;branch=ti-ubuntu-3.1-1282 \ and the fetch worked. Is this a bitbake problem or a meta-ti problem. Thanks Ed vidal On Fri, Jan 4, 2013 at 11:09 AM, Edward Vidal <vidal.devel...@gmail.com>wrote: > Hello, > I am still trying to get the pandaboard to boot with meta-ti and yocto. > I built the kernel on a Fedora17 pandaboard, This took appoximately 9 hrs. > The following are the steps that I have taken. What needs to set to have > the kernel display the process as it is booting? > This is far as get with Angstrom and meta-ti with Yocto. > Basic steps > fetch the kernel > checkout ti-ubuntu-3.1.0-1282.11 > configure the kernel > make > change zImage to uImage with mkimage > copy files to SD card > > As always any and all help will be appreciated. > regards Ed Vidal > > On Thu, Jan 3, 2013 at 1:25 PM, Edward Vidal <vidal.devel...@gmail.com>wrote: > >> Hello, >> the Angstrom build just finished. >> I get the same as meta-ti and yocto >> >> Texas Instruments OMAP4460 ES1.1 >> OMAP SD/MMC: 0 >> reading u-boot.img >> reading u-boot.img >> >> >> U-Boot 2011.12-dirty (Jan 03 2013 - 12:29:15) >> >> >> CPU : OMAP4460 ES1.1 >> Board: OMAP4 Panda >> I2C: ready >> DRAM: 1 GiB >> MMC: OMAP SD/MMC: 0 >> Using default environment >> >> In: serial >> Out: serial >> Err: serial >> Hit any key to stop autoboot: 0 >> reading boot.scr >> >> 342 bytes read >> >> Running bootscript from mmc0 ... >> ## Executing script at 82000000 >> Booting from mmc0 >> Device: OMAP SD/MMC >> Manufacturer ID: 2 >> OEM: 544d >> Name: SA16G >> Tran Speed: 25000000 >> Rd Block Len: 512 >> SD version 2.0 >> High Capacity: Yes >> Capacity: 14.6 GiB >> Bus Width: 4-bit >> reading uImage >> >> 4164360 bytes read >> ## Booting kernel from Legacy Image at 80300000 ... >> Image Name: Angstrom/3.1.0/pandaboard >> >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 4164296 Bytes = 4 MiB >> >> Load Address: 80008000 >> Entry Point: 80008000 >> Verifying Checksum ... OK >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Uncompressing Linux... done, booting the kernel. >> As always any and all help will be appreciated. >> regards Ed Vidal >> >> On Thu, Jan 3, 2013 at 1:09 PM, Edward Vidal <vidal.devel...@gmail.com>wrote: >> >>> Hello All from Ed Vidal >>> I have not changed any recipes. >>> >>> I have been trying with a current version of angstrom which downloads >>> linux-omap_3.1.0-r1a. cd >>> ~/angstrom/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/deploy/images/pandaboard/ >>> This creates the following files >>> ls >>> MLO >>> MLO-pandaboard >>> MLO-pandaboard-2011.12 >>> modules-3.1.0-r1a-pandaboard.tgz >>> README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt >>> u-boot.img >>> u-boot-pandaboard-2011.12-r8.img >>> u-boot-pandaboard.img >>> uImage >>> uImage-3.1.0-r1a-pandaboard-20130103162548.bin >>> uImage-pandaboard.bin >>> I also have tried using meta-ti with yocto which creates the following >>> files >>> >>> u-boot-pandaboard-2011.12-r8.img >>> u-boot-pandaboard.img >>> uImage >>> uImage-3.1.0-r1a-pandaboard-20130103162548.bin >>> uImage-pandaboard.bin >>> [vidal@ws009 pandaboard]$ cd >>> ~/POKY/build122912_panda/poky/build/tmp/deploy/images/ >>> [vidal@ws009 images]$ ls >>> core-image-sato-sdk-pandaboard-20121230164443.rootfs.tar.bz2 >>> core-image-sato-sdk-pandaboard-20130101172231.rootfs.tar.bz2 >>> core-image-sato-sdk-pandaboard.tar.bz2 >>> MLO >>> MLO-pandaboard >>> MLO-pandaboard-2011.12 >>> modules--3.1.0-r0-pandaboard-20121230164443.tgz >>> modules--3.1.0-r0-pandaboard-20130101172231.tgz >>> README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt >>> u-boot.img >>> u-boot-pandaboard-2011.12-r8.img >>> u-boot-pandaboard.img >>> uImage >>> uImage-3.1.0-r0-pandaboard-20121230164443.bin >>> uImage-3.1.0-r0-pandaboard-20130101172231.bin >>> The difference between uImage-3.1.0-r0-pandaboard-20121230164443.bin and >>> uImage-3.1.0-r0-pandaboard-20130101172231.bin is I added to local.conf >>> CMDLINE_DEBUG ?= "debug" to see if I could be some debug out of the boot >>> process. All >>> I get is Starting kernel ... >>> >>> >>> Uncompressing Linux... done, booting the kernel. >>> My angstrom build should be done shortly. May this will give a tar.vz2 >>> file so I can test the kernel that I get above in >>> ~/angstrom/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/deploy/images/pandaboard/ >>> As always any and all help will be appreciated. >>> regards Ed Vidal >>> >>> On Thu, Jan 3, 2013 at 11:50 AM, Gary Thomas <g...@mlbassoc.com> wrote: >>> >>>> On 2013-01-03 11:40, Alan DuBoff wrote: >>>> >>>>> On Tue, 25 Dec 2012, Gary Thomas wrote: >>>>> >>>>> Please try to answer the question that was asked: what did you change >>>>>> in the *recipe*?? >>>>>> >>>>> >>>>> I *DID* answer, please go back and read my messages, here it is again >>>>> for your convenience: >>>>> >>>>> setup-scripts/sources/meta-ti/**recipes-kernel/linux/linux-** >>>>> ti33x-psp_3.2.bb <http://linux-ti33x-psp_3.2.bb> >>>>> >>>>> If you change the kernel version on that recipe it will build the >>>>> image with that kernel, AFAICT. >>>>> >>>> >>>> Exactly what do you mean? Did you actually change the recipe (i.e. >>>> edit the file >>>> mentioned above)? Or did you try to select that kernel via some other >>>> means? If >>>> so, how? >>>> >>>> If you'll be more explicit about how you are trying to get this >>>> alternate >>>> kernel to be used, we can help figure out why it's not working for you. >>>> >>>> >>>> >>>>> The kernel and the modules [package] have to match or else you'll >>>>>> have problems. >>>>>> >>>>> >>>>> They do. I've included the kernel-modules in my recipes. >>>>> >>>> >>>> query: why isn't this discussion on the meta-ti list where the >>>> supporters >>>> of this recipe (and layer) hang out? >>>> >>>> >>>> -- >>>> ------------------------------**------------------------------ >>>> Gary Thomas | Consulting for the >>>> MLB Associates | Embedded world >>>> ------------------------------**------------------------------ >>>> >>>> ______________________________**_________________ >>>> Angstrom-distro-devel mailing list >>>> Angstrom-distro-devel@**linuxtogo.org<Angstrom-distro-devel@linuxtogo.org> >>>> http://lists.linuxtogo.org/**cgi-bin/mailman/listinfo/** >>>> angstrom-distro-devel<http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel> >>>> >>> >>> >> > _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
