All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Morris <morris@buinea.com>
To: buildroot@busybox.net
Subject: [Buildroot] Trouble bringing up Raspberry Pi
Date: Sat, 19 Dec 2015 12:11:26 -0800	[thread overview]
Message-ID: <20151219201126.GA9718@buinea.com> (raw)

Hi All,

I'm having some trouble bringing up a Raspberry Pi B+ and was hoping
someone could point me in the right direction. I have successfully used
buildroot on x86 machines in the past and managed to get them to run.

I'm using a Raspberry Pi B+,with a USB keyboard, ethernet and HDMI
output. The system works properly using a Raspbian image.

I'm just trying to bring up a minimal system and then go from there.

I'm using buildroot-2015.11.1 and followed the readme.txt under
board/raspberrypi. I've tried both the volatile and persistent rootfs
and find the instruction insufficient to get a working system.

After the first failed attempt, I set 
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
which allowed me to boot the machine  and I'm now able to log in via
SSH/dropbear, but I don't always get a login prompt, and the keyboard
has no effect even though it's found by the system and I
 get a message when I unplug it or plug it back in again.

I've tried adding items to cmdline.txt from various websites, 
but still don't have any keyboard input.

Are there other missing notes like the one about enabling MDEV which
will allow me to log in to the console?

Perhaps a working .config for the Pi B+ would set me in the right
direction.

Thanks,

Steve Morris

             reply	other threads:[~2015-12-19 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 20:11 Steve Morris [this message]
2015-12-20  9:27 ` [Buildroot] Trouble bringing up Raspberry Pi Thomas Petazzoni
2015-12-20 13:36   ` Steve Morris
2015-12-20 13:40     ` Thomas Petazzoni
2015-12-20 20:12       ` Steve Morris
2015-12-20 21:48         ` Thomas Petazzoni

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=20151219201126.GA9718@buinea.com \
    --to=morris@buinea.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 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.