From: Jorge Ramirez-Ortiz, Foundries <jorge@foundries.io>
To: u-boot@lists.denx.de
Subject: Zynq MPSoC Dynamic DDR DIMM Configuration support
Date: Wed, 12 May 2021 23:21:21 +0200 [thread overview]
Message-ID: <20210512212121.GA6242@trex> (raw)
Hi Michal
We are doing some work on an MPSoC UZ3EG platform part of which
requires us to replace FSBL with SPL.
It seems the actual boot process is becoming an issue on these SoCs;
currently, 1) we embed the PMU firmware on SPL so the bootrom can
extract it and program it; 2) then SPL configures the PMU using a
platform specific binary that gets built also with SPL; and finally,
3) SPL sets up the DDR using its psu_init_gpl.c settings (also board
specific, part of the XSA).
It is this final step in the boot sequence that is being broken by the
Dynamic DDR DIMM configuration feature [1]
[1] https://www.xilinx.com/support/answers/75768.html
Are you aware of any work in progress to support this? Any thoughts on
how to work around it and train the DDR? will the functionality
required to implmenet Dynamic DDR DIMM configuration be added as a
separate file to the XSA tarball or will we need to do some native
implementation in SPL?
Becase without a change in the last link in the process chain
described earlier (calls to psu_init()), DDR just wont be accessible
to U-BOOT or OP-TEE.
In our case, we were able to boot from QSPI, boot SPL (in OCM), have
SPL unpack and validate the FIT image, execute TF-A(in OCM), but then
any jumps to OP-TEE or U-BOOT would obviously not progress since the
DDR wasnt properly trained/initialized.
so, any thoughts or plans you can share?
TIA!
jorge
next reply other threads:[~2021-05-12 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 21:21 Jorge [this message]
2021-05-13 6:38 ` Zynq MPSoC Dynamic DDR DIMM Configuration support Michal Simek
2021-05-13 7:24 ` Jorge
2021-05-13 7:36 ` Jorge
2021-05-13 10:01 ` Michal Simek
2021-05-14 7:38 ` Jorge
2021-05-14 7:47 ` Michal Simek
2021-05-14 9:08 ` Jorge
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=20210512212121.GA6242@trex \
--to=u-boot@lists.denx.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