From: Cheng Yang <cyang999@apple.com>
To: openbmc@lists.ozlabs.org
Subject: Difficulty booting on Raspberry Pi 4.
Date: Wed, 23 Sep 2020 10:36:03 -0700 [thread overview]
Message-ID: <CDC90A55-957D-47BB-9B42-4283BB6706AF@apple.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
Hi, I’m openbmc noob here.
I follow the instruction of https://github.com/openbmc/openbmc/blob/master/meta-raspberrypi/README.md <https://github.com/openbmc/openbmc/blob/master/meta-raspberrypi/README.md>
After 2.5 hours everything built, (I used either x86 ubuntu 18.04 or 20.04 same result)
However after I copied to the image to micro SD, raspberry Pi 4 won’t boot.
No video output, no serial output at all. (The board works fine with ubuntu 18.04.)
Any tip/cheat sheet to get openbmc running on Raspberry Pi 4?
The steps I did, anything I missed? Is the recipe correct?
git clone the openbmc code.
source poky/oe-init-build-env rpi-build <== yes I did this.
Add this layer to bblayers.conf and the dependencies above <== yes I added /var/openbmc/openbmc/meta-raspberrypi (where I’m using /var/openbmc as the source code dir.)
Set MACHINE in local.conf to one of the supported boards <== I added MACHINE ??= “raspberrypi4” (replacing the original qemu line)
bitbake core-image-base <== went through, only 5 warnings, no error, everything successful.
Use bmaptool to copy the generated .wic.bz2 file to the SD card <== with “sudo ~/bmap-tools/bmaptool copy core-image-base-raspberrypi4.wic.bz2 /dev/sdc1” no error copied successfully.
Boot your RPI <== nothing happen, no VGA, can’t be ping’ed, no console serial output either (no uboot messages).
Any tip/pointer will be greatly appreciated.
Cheng
[-- Attachment #2: Type: text/html, Size: 2907 bytes --]
next reply other threads:[~2020-09-23 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 17:36 Cheng Yang [this message]
2020-09-24 0:10 ` Difficulty booting on Raspberry Pi 4 Patrick Williams
2020-09-24 0:34 ` Cheng Yang
[not found] ` <CACWQX831sTH1Mp5nZEo+_bs2pCgz9ovspXD9onqiHCgAs=vciw@mail.gmail.com>
2020-09-24 1:05 ` Ed Tanous
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=CDC90A55-957D-47BB-9B42-4283BB6706AF@apple.com \
--to=cyang999@apple.com \
--cc=openbmc@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).