All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9226] Firefly boot fails with: "failed to find part:boot"
Date: Sat, 17 Sep 2016 13:59:47 +0000	[thread overview]
Message-ID: <bug-9226-163-0M067if1R8@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9226-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9226

--- Comment #2 from Ciro Santilli <ciro.santilli@gmail.com> ---
I have managed to boot from TTL as follows:

- enter recovery mode (hold recovery and restart board by resetting)
- download upgrade tool, and official Ubuntu image, and run:

     sudo ./Linux_Upgrade_Tool_v1.2/upgrade_tool uf
Firefly-RK3288_Ubuntu14.04_201607222032.img

   This burns the image to the eMMC.

-  that image works. From inside of it, clear eMMC to ensure that it will not
be used instead of the SD: sudo dd if=/dev/zero of=/dev/mmblk0

-  try again

However I can't get HDMI / VGA output to my screen, only TTL access.

I also tried to insert the cable after boot, but it did not help.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2016-09-17 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11 15:19 [Buildroot] [Bug 9226] New: Firefly boot fails with: "failed to find part:boot" bugzilla at busybox.net
2016-09-11 19:29 ` Thomas Petazzoni
2016-09-12 14:13   ` Ezequiel Garcia
2016-09-12 14:29     ` Thomas Petazzoni
2016-09-12 14:25 ` [Buildroot] [Bug 9226] " bugzilla at busybox.net
2016-09-17 13:59 ` bugzilla at busybox.net [this message]

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=bug-9226-163-0M067if1R8@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.