From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: "Yazdani, Reyhaneh" <RYazdani@data-modul.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: signed HDMI firmware in imx8mq image
Date: Wed, 16 Jan 2019 12:30:54 -0800 [thread overview]
Message-ID: <CAHQ1cqGzMcgUGYXn5uq_86kHb_QSb2ZeQCrG-5jc1wS4rvC5aA@mail.gmail.com> (raw)
In-Reply-To: <1547631290.4339.26.camel@pengutronix.de>
On Wed, Jan 16, 2019 at 1:34 AM Lucas Stach <l.stach@pengutronix.de> wrote:
>
> Hi Reyhaneh,
>
> Am Mittwoch, den 16.01.2019, 08:48 +0000 schrieb Yazdani, Reyhaneh:
> > Every one,
> >
> > In order to build a Barebox image to boot imx8mq-evk with HDMI, I have tried to
> > tell Barebox about the embedded signed HDMI firmware, which is necessary for
> > provided kernel image by NXP.
> >
> > for this matter, I added the below line into the
> > arch/arm/boards/nxp-imx8mq-evk/flash-header-imx8mq-evk.imxcfg
> >
> > soc imx8mq
> > loadaddr 0x007E1000
> > dcdofs 0x400
> > + signed_hdmi_firmware firmware/imx/signed_hdmi_imx8m.bin
> >
> > And placed the firmware into the build-directory/firmware/imx
> >
> >
> > By checking kernel boot message, it seems the HDMI FW is running, but no access
> > to the HDMI:
> > [drm:hdmi_phy_init_t28hpc] *ERROR* HDMI mailbox access failed
> >
> > What should I do more in Barebox to make HDMI accessible by kernel?
>
> I don't think there is anything more needed from the Barebox side. At
> least the same change works for me and gets me a working HDMI display
> on the EVK board.
>
FWIW, I don't see anything missing either.
> I don't use the NXP kernel through, but running a 4.20 based kernel
> with lot of downstream bits ported. This might be a incompatibility of
> your kernel with the imx8 ATF version shipped with Barebox.
>
I was using vendor kernel when I was working on
implementing/validating initial support of that and it worked alright.
However, that has been over 5 month ago, so it is entirely possible
that newer version of various components might have become
problematic.
It is probably not a problem in your case, but do keep in mind, that
i.MX8MQ mask ROM code uses SD2 as a "backup" boot option, so if it
doesn't find anything bootable on the selected (via pins or fuses)
medium it will revert to that. If that happens, HDMI firmware present
on SD card will _not_ be loaded into HDMI IP block. I've been bitten
by this when I was working with a board that I forgot was configured
to boot from eMMC and was booting from SD card by coincidence.
Thanks,
Andrey Smirnov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-01-16 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 8:48 Yazdani, Reyhaneh
2019-01-16 9:34 ` Lucas Stach
2019-01-16 20:30 ` Andrey Smirnov [this message]
2019-01-17 10:04 ` Yazdani, Reyhaneh
2019-01-23 10:43 ` Yazdani, Reyhaneh
2019-01-17 8:19 ` Yazdani, Reyhaneh
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=CAHQ1cqGzMcgUGYXn5uq_86kHb_QSb2ZeQCrG-5jc1wS4rvC5aA@mail.gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=RYazdani@data-modul.com \
--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