From: Roland Hieber <rhi@pengutronix.de>
To: "Joshi, Pranay" <Pranay.Joshi@bakerhughes.com>
Cc: "ptxdist@pengutronix.de distrokit@pengutronix.de"
<distrokit@pengutronix.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
Marco Felsch <m.felsch@pengutronix.de>
Subject: Re: [DistroKit] [ptxdist] Prepare Image for Raspberry Pi 4
Date: Tue, 15 Nov 2022 11:16:26 +0100 [thread overview]
Message-ID: <20221115101626.t3tofvn56vrupw7t@pengutronix.de> (raw)
In-Reply-To: <20221115094115.rxiaepnmabnkmeav@pengutronix.de>
On Tue, Nov 15, 2022 at 10:41:15AM +0100, Marco Felsch wrote:
> Hi,
>
> On 22-11-15, Joshi, Pranay wrote:
> > Hi Marco,
> >
> > Thanks for response.
> >
> > Please find attached error logs for more detail.
>
> Thanks for the error log.
>
> > Read start_cd.elf bytes 685540 hnd 0x00000000
> > Read fixup_cd.dat bytes 2657 hnd 0x00000000
> > Firmware: 679ebca20dc08ca3f5392e02d772fed727debdae Sep 9 2019 18:51:29
> > 0x00d03114 0x00000000 0x00000000
> > start_cd.elf: is not compatible
> > This board requires newer software
> > Get the latest software from https://www.raspberrypi.com/software/
>
> The version of the start_cd.elf seems a bit old since Ahmad updated it
> to v1.20220331 and the loader says it is from 2019.
>
> To sum up a few things since I just stepped in into this conversation:
Let me just step into this conversation too… 🙂 I'm not very experienced
with RPi 4 either, but you can try using the newer firmware files from
https://github.com/raspberrypi/firmware/tree/master/boot and put them
into /rpi-firmware in your DistroKit tree. I'm not sure if barebox will
work, but it's worth a try.
- Roland
--
Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-11-15 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PH0PR08MB801478F4321D6EC7F26475AB82329@PH0PR08MB8014.namprd08.prod.outlook.com>
2022-10-31 8:01 ` Ahmad Fatoum
[not found] ` <PH0PR08MB80142B5E46E08F7A38197224823C9@PH0PR08MB8014.namprd08.prod.outlook.com>
[not found] ` <SN4PR0801MB8017A9D758C4B6BB3D006FAD82059@SN4PR0801MB8017.namprd08.prod.outlook.com>
2022-11-14 10:58 ` Marco Felsch
2022-11-15 6:05 ` Joshi, Pranay
2022-11-15 9:41 ` Marco Felsch
2022-11-15 9:47 ` Joshi, Pranay
2022-11-15 10:04 ` Marco Felsch
2022-11-15 10:16 ` Roland Hieber [this message]
2022-11-15 10:30 ` Joshi, Pranay
2022-11-15 11:00 ` Marco Felsch
2022-11-15 11:27 ` Joshi, Pranay
2022-12-01 12:09 ` Ahmad Fatoum
2022-12-02 5:39 ` Joshi, Pranay
2022-12-02 6:14 ` Ahmad Fatoum
2022-12-05 6:00 ` Joshi, Pranay
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=20221115101626.t3tofvn56vrupw7t@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=Pranay.Joshi@bakerhughes.com \
--cc=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=m.felsch@pengutronix.de \
/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