All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maciej Borzecki <maciej.borzecki@open-rnd.pl>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-ti mailing list <meta-ti@yoctoproject.org>
Subject: Re: BeagleBone Black , u-boot, and zImage
Date: Mon, 18 Aug 2014 16:45:16 +0200	[thread overview]
Message-ID: <5823428.XaY5WDaLTE@localhost.localdomain> (raw)
In-Reply-To: <20140818141613.GI23523@edge>

On Monday 18 of August 2014 10:16:14 Denys Dmytriyenko wrote:
> On Mon, Aug 18, 2014 at 09:34:58AM -0300, Diego Sueiro wrote:
> > On Mon, Aug 18, 2014 at 9:28 AM, Maciej Borzecki <
> > 
> > maciej.borzecki@open-rnd.pl> wrote:
> > > Rough guess, but it looks like a default u-boot from eMMC. Try following
> > > official instruction to make it boot off SD card:
> > > https://www.yoctoproject.org/downloads/bsps/daisy16/beaglebone
> > 
> > This should do the trick:
> > "Pressing the USER/BOOT button when powering on will temporarily change
> > the
> > boot order".
> 
> The USER button may sometimes be tricky, as it preserves the state across
> reboots. So, if you already booted off of eMMC, holding the button and
> rebooting won't work - you'd have to unplug the power to completely turn it
> down and then power it up, while pressing the USER button. Making eMMC
> non-bootable is more reliable in many cases...

Silly question, is there any requirement that partition block count must be 
even for boot partition?

For instance, I'm not able to boot using this partition layout, keep getting 
CCC on serial console:

Device         Boot     Start       End Blocks  Id System
/dev/mmcblk0p1 *         2048     22526  10239+  c W95 FAT32 (LBA)
/dev/mmcblk0p2          22528    116735  47104  83 Linux

This one, almost works (u-boot runs, init fails mounting rootfs):
evice         Boot     Start       End Blocks  Id System
/dev/mmcblk0p1 *         2048     22527  10240   c W95 FAT32 (LBA)
/dev/mmcblk0p2          22528    116735  47104  83 Linux



-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you.


  parent reply	other threads:[~2014-08-18 14:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 19:53 BeagleBone Black , u-boot, and zImage Carlos Rafael Giani
2014-08-14 20:04 ` Denys Dmytriyenko
2014-08-14 20:09   ` Carlos Rafael Giani
2014-08-14 20:20     ` Maciej Borzecki
2014-08-18  9:10       ` Carlos Rafael Giani
2014-08-18 10:31         ` Diego Sueiro
2014-08-18 12:28         ` Maciej Borzecki
2014-08-18 12:34           ` Diego Sueiro
2014-08-18 14:16             ` Denys Dmytriyenko
2014-08-18 14:18               ` Carlos Rafael Giani
2014-08-18 14:45               ` Maciej Borzecki [this message]
2014-08-23  3:24                 ` Denys Dmytriyenko
2014-08-23  8:36                   ` Maciej Borzecki
2014-08-14 20:20     ` Denys Dmytriyenko
2014-08-15  9:47       ` Diego Sueiro
2014-08-15 14:10         ` Denys Dmytriyenko

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=5823428.XaY5WDaLTE@localhost.localdomain \
    --to=maciej.borzecki@open-rnd.pl \
    --cc=denys@ti.com \
    --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.