All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Senior <russell@personaltelco.net>
To: Denys Dmytriyenko <denis@denix.org>
Cc: meta-ti@yoctoproject.org
Subject: Re: building meta-ti + poky HOWTO?
Date: Thu, 05 Apr 2012 13:43:46 -0700	[thread overview]
Message-ID: <86bon5nc3h.fsf@coulee.tdb.com> (raw)
In-Reply-To: <20120405191501.GB5144@denix.org> (Denys Dmytriyenko's message of "Thu\, 05 Apr 2012 15\:15\:01 -0400")

>>>>> "Denys" == Denys Dmytriyenko <denis@denix.org> writes:

Russell> I have been unable to get a booting image out of Angstrom in
Russell> about three weeks of trying and several unanswered queries to
Russell> the mailing list and elsewhere.  In my continuing effort to
Russell> get a build system that produces an image that boots on my
Russell> beaglebone, I'd like to try building meta-ti with poky, just
Russell> to see if that fails for me too.

Denys> As far as I remember, you are having problems with rootfs
Denys> images that generate an entire SD card disk image with multiple
Denys> partitions, e.g. Cloud9 image.  There are known issues with the
Denys> tools used to do that, like sometimes fdisk not making the
Denys> correct MBR and partition table that BootROM can boot from. So
Denys> far it seems to depend on the host distro and their tools. This
Denys> area still needs further investigation and probably the use of
Denys> different tools...

I am building on a Debian/unstable box with a core i7 cpu and 24 gig of RAM.

Denys> But you should not be stuck on this - why don't you use the
Denys> individual pieces, like kernel image, rootfs and load them on
Denys> SD card yourself, manually? Try working around the issue...

I have tried taking the pre-baked Angstrom image from here:

  http://www.angstrom-distribution.org/demo/beaglebone/Angstrom-Cloud9-IDE-eglibc-ipk-v2012.02-core-beaglebone-2012.02.14.img.xz

(which works for me), and replacing the uImage on the vfat partition
by copying over the existing one with one I built.  That boots, but the
rootfs isn't aligned (different kernel/module versions?).  

If I then try dropping in my rootfs, by reformatting the ext4fs and
untarring the rootfs tarball I built, I get 0.6 seconds into the boot
and then the boot stalls with some udevd messages, like so:

  U-Boot SPL 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03)
  Texas Instruments Revision detection unimplemented
  No AC power, disabling frequency switch
  OMAP SD/MMC: 0
  reading u-boot.img
  reading u-boot.img


  U-Boot 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03)

  I2C:   ready
  DRAM:  256 MiB
  No daughter card present
  NAND:  HW ECC Hamming Code selected
  nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x10, Chip ID: 0x10
  No NAND device found!!!
  0 MiB
  MMC:   OMAP SD/MMC: 0
  *** Warning - readenv() failed, using default environment

  Net:   cpsw
  Hit any key to stop autoboot:  0 
  SD/MMC found on device 0
  reading uEnv.txt

  33 bytes read
  Loaded environment from uEnv.txt
  Importing environment from mmc ...
  reading uImage

  3140320 bytes read
  ## Booting kernel from Legacy Image at 80007fc0 ...
     Image Name:   Angstrom/3.2/beaglebone
     Image Type:   ARM Linux Kernel Image (uncompressed)
     Data Size:    3140256 Bytes = 3 MiB
     Load Address: 80008000
     Entry Point:  80008000
     Verifying Checksum ... OK
     XIP Kernel Image ... OK
  OK

  Starting kernel ...

  Uncompressing Linux... done, booting the kernel.
  [    0.120087] cpuidle-am33xx cpuidle-am33xx.0: failed to register driver
  [    0.251953] _omap_mux_get_by_name: Could not find signal leds-gpio
  [    0.635798] omap2_set_init_voltage: unable to get clk dpll1_ck
  [    0.642040] omap2_set_init_voltage: unable to set vdd_mpu_iva
  [    0.648112] omap2_set_init_voltage: unable to get clk l3_ick
  [    0.654099] omap2_set_init_voltage: unable to set vdd_core
  udevd[56]: worker [79] did not accept message -1 (Connection refused), kill it
  ^M
  udevd[56]: worker [80] did not accept message -1 (Connection refused), kill it
  ^M
  udevd[56]: worker [81] did not accept message -1 (Connection refused), kill it
  ^M
  udevd[56]: worker [85] did not accept message -1 (Connection refused), kill it
  ^M
  udevd[56]: worker [86] did not accept message -1 (Connection refused), kill it
  ^M
  udevd[56]: worker [87] did not accept message -1 (Connection refused), kill it
  ^M

I don't know what that means, nor where to go from there.


-- 
Russell Senior, President
russell@personaltelco.net


  reply	other threads:[~2012-04-05 20:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 18:09 building meta-ti + poky HOWTO? Russell Senior
2012-04-05 18:36 ` Brian Hutchinson
2012-04-05 19:07   ` Denys Dmytriyenko
2012-04-05 19:15     ` Brian Hutchinson
2012-04-06 14:11   ` Gary Thomas
2012-04-12 14:42     ` Marco Monguzzi
2012-04-12 17:49       ` Denys Dmytriyenko
2012-04-05 19:15 ` Denys Dmytriyenko
2012-04-05 20:43   ` Russell Senior [this message]
2012-04-06  1:40     ` Russell Senior
2012-04-06 17:48       ` [Angstrom-devel] " Khem Raj
2012-04-09  1:40       ` Denys Dmytriyenko
2012-04-09  8:42         ` [PATCH] apply recommended kernel config for beaglebone Russell Senior
2012-04-09  9:08           ` Koen Kooi
2012-04-09 10:12             ` Russell Senior
2012-04-07 13:51     ` building meta-ti + poky HOWTO? Jack Mitchell
2012-04-07 19:35       ` Russell Senior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86bon5nc3h.fsf@coulee.tdb.com \
    --to=russell@personaltelco.net \
    --cc=denis@denix.org \
    --cc=meta-ti@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.