From: Jens Maus <mail@jens-maus.de>
To: barebox@lists.infradead.org
Subject: barebox on RaspberryPi2 and Pi3
Date: Sat, 9 Dec 2017 23:32:13 +0100 [thread overview]
Message-ID: <C315E0B1-4F4E-4814-9106-85C7E1363C2D@jens-maus.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1233 bytes --]
Hello Barebox developers,
I am currently trying to use barebox for one of my embedded linux projects which is mainly targeted for the RaspberryPi hardware platform. I was already able to compile barebox (v2017.11 using rpi_defconfig) and successfully run it on an old RaspberryPi1 Model B version using the „barebox-raspberry-pi-1.img“ file as a kernel image. It shows up on my serial console using 115200/8N1 and I am able to play around with the console commands.
However, when I use the „barebox-raspberry-pi-2.img“ file together with a RaspberryPi2 nothing shows up on the serial console. Also using an old version (v2017.09) doesn’t show up anything and the green LED on the Pi2 just flashes in a 1 second interval. The same happens with a Pi3 and nothing shows up on the serial console or the HDMI connection.
As the changelog states that at least the Pi2 should be supported I wonder what could be the reason why I am only able to get barebox running on the old RaspberryPi1 Model B hardware but not on newer RaspberryPi models.
Any help would be appreciated.
Best Regards,
Jens
--
Jens Maus, Dresden/Germany
http://jens-maus.de/
*** Content is authentic only with digital signature ***
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3745 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-12-09 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 22:32 Jens Maus [this message]
2017-12-12 6:37 ` Sascha Hauer
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=C315E0B1-4F4E-4814-9106-85C7E1363C2D@jens-maus.de \
--to=mail@jens-maus.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox