From: Trevor Woerner <twoerner@gmail.com>
To: David Weisgerber <david.weisgerber@ms-gmbh.de>
Cc: Yocto list discussion <yocto@yoctoproject.org>
Subject: Re: [meta-raspberry] Raspberry Pi 3
Date: Thu, 31 Mar 2016 11:26:04 -0400 [thread overview]
Message-ID: <20160331152604.GA23623@linux-yxv0> (raw)
In-Reply-To: <1704123.nFWplM32RM@valkyrie>
On Fri 2016-03-18 @ 10:15:39 AM, David Weisgerber wrote:
> Hi,
> did anyone succeed in building an image that runs on Raspberry Pi 3? I set my
> conf/local.conf to
>
> MACHINE ??= "raspberrypi3"
> GPU_MEM = "128"
> DISABLE_OVERSCAN = "1"
>
> and built rpi-basic-image but when booting the Pi 3 up I only see 4
> raspberries in the top right but nothing else happens. The image works
> perfectly on a Pi 2 though.
I'm able to get a raspi3 image running on my Raspberry Pi 3, but my console is
messed up. Everything works fine via the usb+hdmi ports, but plugging a
console cable into the GPIO header is messed up.
It looks like what happens when the baud rate is set incorrectly, but I've
tried every baud rate in my terminal emulator and it all looks the same
(messed up).
Anyone got their console working? The same cable/setup works fine on the
raspi2 (ttyAMA0) but doesn't work on my raspi3 (ttyS0).
next prev parent reply other threads:[~2016-03-31 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 9:15 [meta-raspberry] Raspberry Pi 3 David Weisgerber
2016-03-31 15:26 ` Trevor Woerner [this message]
2016-03-31 15:29 ` Josep Puigdemont
2016-03-31 16:36 ` Khem Raj
2016-04-01 19:17 ` Trevor Woerner
2016-04-01 22:46 ` Trevor Woerner
2016-04-01 22:55 ` Khem Raj
2016-04-02 4:03 ` Trevor Woerner
2016-04-02 4:56 ` Michael Dumont
2016-04-02 14:49 ` Tom Doehring
2016-04-04 1:38 ` Trevor Woerner
2016-04-04 2:29 ` Khem Raj
2016-04-04 15:08 ` Trevor Woerner
2016-07-08 13:12 ` Andrei Gherzan
2016-07-08 14:15 ` Khem Raj
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=20160331152604.GA23623@linux-yxv0 \
--to=twoerner@gmail.com \
--cc=david.weisgerber@ms-gmbh.de \
--cc=yocto@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.