Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] RPi B+ update
Date: Tue, 16 May 2017 23:46:28 +0200	[thread overview]
Message-ID: <87vap079vv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <38b2ad6e-f9bd-c0f7-e5be-c0531fd22f2a@gmail.com> (Marco Trapanese's message of "Tue, 16 May 2017 21:32:26 +0200")

>>>>> "Marco" == Marco Trapanese <marcotrapanese@gmail.com> writes:

 > Hi!
 > A couple of years ago (it was in 2015) I built a buildroot environment
 > for RPi B+. We ended up with an sd-card image that was cloned for
 > every installation.
 > This months we've bought some other RPi B+ but with this batch the
 > system refuses to boot: it hangs with black screen and the raspberry
 > icon at the top-left corner.

 > We're aware they have changed the RAM chips (from Samsung to Elpida)
 > and likely we should update the drivers with the new ones.

 > Here the buildroot related question: is it possible to change
 > something in the current sd-card image instead of updating and
 > rebuilding the whole system?

 > This is because if we need to go with the second option we're going to
 > deeply upgrade the application and this is not affordable right now.

If it doesn't boot at all (E.G. no output on the serial port), then the
problem is most likely in the rpi-firmware and/or Linux kernel, so you
could try updating those and leaving the rootfs as is.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2017-05-16 21:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 19:32 [Buildroot] RPi B+ update Marco Trapanese
2017-05-16 21:23 ` Peter Seiderer
2017-05-17  6:05   ` Marco Trapanese
2017-05-17 15:28     ` Marco Trapanese
2017-05-17 17:36       ` Waldemar Brodkorb
2017-05-17 20:49         ` Marco Trapanese
2017-05-17 19:29       ` Peter Korsgaard
2017-05-16 21:46 ` Peter Korsgaard [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=87vap079vv.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox