On 2013-01-05 09:00, Edward Vidal wrote:
Hello,
I notice that meta-ti for me is
commit d3ff5630a74640f46ca2ceaef1aa1baa86b9b795
Author: Andreas Müller <schnitzelt...@googlemail.com>
Date:   Mon Jul 9 14:35:36 2012 +0200

     netbase: follow oe-core to v5.0

     Signed-off-by: Andreas Müller <schnitzelt...@googlemail.com>
     Signed-off-by: Denys Dmytriyenko <de...@ti.com>

your version is meta-ti           = "master:7bc112911d856962d2f477

a6ba60e08907141433"

What command did you use to get meta-ti?
I used

git clone *https://github.com/Angstrom-distribution/meta-ti.git*

This tree is probably very out of date.  Use git://git.yoctoproject.org/meta-ti


Did you have to use an initrd file?

No - Yocto boot does not normally use such a setup

Do you have the text you used for your boot.scr?

I used nothing - the U-Boot defaults work fine.

Did you use ext3 or ext4 for you linux partition?

ext3 but ext4 should work as well

I build my SD card using the attached scripts (locally honed) on both
Fedora 16 & Ubuntu 12.10

What does
/home/vidal/POKY/build122912_panda/poky/meta-ti/recipes-kernel/linux/
linux-ti33x-psp_3.2.bb have do with the build?
I thought
/home/vidal/POKY/build122912_panda/poky/meta-ti/recipes-kernel/linux/
linux-omap4_3.1.0.bb was being used.
   As always any and all help will be appreciated.

Those are out of date.  The current tree will use 
meta-ti/recipes-kernel/linux/linux-omap4_3.4.bb

regards Ed Vidal


On Sat, Jan 5, 2013 at 8:18 AM, Gary Thomas <g...@mlbassoc.com> wrote:

On 2013-01-04 11:09, Edward Vidal 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


I'm a bit confused here as to the problem.  I just built Poky/Yocto for the
PandaBoard using meta-ti (which is what you claim to want).  This used this
configuration:

Build Configuration:
BB_VERSION        = "1.17.0"
BUILD_SYS         = "i686-linux"
NATIVELSBSTRING   = "Unknown"
TARGET_SYS        = "arm-amltd-linux-gnueabi"
MACHINE           = "pandaboard"
DISTRO            = "yocto"
DISTRO_VERSION    = "1.3+snapshot-20130104"
TUNE_FEATURES     = "armv7a vfp neon"
TARGET_FPU        = "vfp-neon"
meta-yocto
meta              = "master:**09359e6ec00901abfe49157f1f9730**117b4d284b"
meta-ti           = "master:**7bc112911d856962d2f477a6ba60e0**8907141433"

The result built a Linux 3.4.11 kernel which booted to a console prompt
(I only built a console based image).  Note: the only thing special in
my local.conf was
   MACHINE="pandaboard"
   BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/**formfactor|graphics/mesa)/"

Why are your results different?


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@**linuxt**ogo.org <http://linuxtogo.org><
Angstrom-distro-devel@**linuxtogo.org<Angstrom-distro-devel@linuxtogo.org>

http://lists.linuxtogo.org/****cgi-bin/mailman/listinfo/**<http://lists.linuxtogo.org/**cgi-bin/mailman/listinfo/**>
angstrom-distro-devel<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<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>


--
------------------------------**------------------------------
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


--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#! /bin/bash

# Evaluate arguments so variables can be easily overridden
for i in $*; do
  if echo $i | grep -q '='; then
    eval $i
  fi
done

if [ $# -lt 3 ]; then
  echo "usage: make_sd <dev> <uImage> <rootfs> [MLO=mlo] [UBOOT=uboot]"
  exit 1
fi

DEV=$1
UIMAGE=`readlink -e $2`
ROOTFS=`readlink -e $3`
MLO=${MLO:-""}
UBOOT=${UBOOT:-""}
UBOOT_IMG=${UBOOT_IMG:-""}
UENV=${UENV:=""}

MDEV=`basename ${DEV}`
if ! fgrep -q ${MDEV} /proc/partitions; then
  echo "*** Are you sure?  ${DEV} is not in partition list"
  exit 1
fi

echo "========================================"
echo ""
echo "About to create SD:"
echo "  SD device = ${DEV}"
echo "  uImage file = ${UIMAGE}"
echo "  root file system = ${ROOTFS}"
if [ "x$MLO" != "x" ]; then
MLO=`readlink -e $MLO`
echo "  MLO = ${MLO}"
fi
if [ "x$UBOOT" != "x" ]; then
UBOOT=`readlink -e $UBOOT`
echo "  UBOOT = ${UBOOT}"
fi
if [ "x$UBOOT_IMG" != "x" ]; then
UBOOT_IMG=`readlink -e $UBOOT_IMG`
echo "  UBOOT_IMG = ${UBOOT_IMG}"
fi
if [ "x$UENV" != "x" ]; then
UENV=`readlink -e $UENV`
echo "  UENV = ${UENV}"
fi
echo ""
echo "========================================"

read -p "Continue? " OK

if [ "${OK}" == "yes" ]; then
  echo "****************************************"
  echo "Format SD card"
  mkcard.sh ${DEV} >/tmp/mkcard.log 2>&1
  echo "****************************************"
  mkdir -p /tmp/media
  mount ${DEV}1 /tmp/media
  if [ "x$MLO" != "x" ]; then
    echo "Install MLO"
    cp ${MLO} /tmp/media/MLO
  fi
  if [ "x$UBOOT" != "x" ]; then
    echo "Install U-Boot"
    cp ${UBOOT} /tmp/media/u-boot.bin
  fi
  if [ "x$UBOOT_IMG" != "x" ]; then
    echo "Install U-Boot [img]"
    cp ${UBOOT_IMG} /tmp/media/u-boot.img
  fi
  if [ "x$UENV" != "x" ]; then
    echo "Install U-Boot environment"
    cp ${UENV} /tmp/media/uEnv.txt
  fi
  echo "Copy kernel"
  cp ${UIMAGE} /tmp/media/uImage
  cp ${UIMAGE} /tmp/media/uImage.bin
  umount /tmp/media
  echo "****************************************"
  echo "Install root file system"
  mount ${DEV}2 /tmp/media
  if `echo ${ROOTFS} | fgrep -q bz2`; then
    tar -jxpf ${ROOTFS} -C /tmp/media
  else
    tar -zxpf ${ROOTFS} -C /tmp/media
  fi
  mkdir -p /tmp/media/boot
  cp ${UIMAGE} /tmp/media/boot/uImage
  umount /tmp/media
  sync
fi


Attachment: mkcard.sh
Description: application/shellscript

_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Reply via email to