On 4/13/2023 2:57 AM, Mike Looijmans via lists.yoctoproject.org wrote:
Problem in this particular case turned out to be the SD card interface.
The board has a 1v8/3v3 switch for the UHS modes, but needs to control
that through a driver. So in FSBL, this probably means that the code
should limit itself to 3v3 operation only (boot default). The problem
is that the FSBL cannot access the SD card to read the rest of the
image, probably because it thinks that it can use the UHS modes...
Boot from QSPI or EMMC does work fine though.
AFAIK By FSBL has UHS mode disabled
https://github.com/Xilinx/embeddedsw/blob/xlnx_rel_v2022.2/XilinxProcessorIPLib/drivers/sdps/src/xsdps_card.c#L273,
For more support on boot issues you can post in
https://support.xilinx.com/s/topic/0TO2E000000YKXWWA4/boot-and-configuration?language=en_US
For u-boot this could simply be communicated through devicetree, for
FSBL I'll have to create (another) custom code patch.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: [email protected]
W: www.topic.nl
Please consider the environment before printing this e-mail
On 07-04-2023 16:49, Gundlupet Raju, Sandeep wrote:
Hi Mike,
Can you share your xsa we can take a look. Looks like something is
missing. Is this on QEMU or real HW? Also are you using Xilinx
evaluation board or custom board?
Thanks,
Sandeep
On 4/7/2023 1:40 AM, Mike Looijmans via lists.yoctoproject.org wrote:
Hmm, the build succeeds, but the resulting FSBL doesn't boot. It
gets stuck after displaying this banner:
Xilinx Zynq MP First Stage Boot Loader
Release 2022.2 Oct 7 2022 - 04:56:16
Note that feeding the same XSA to petalinux works fine.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: [email protected]
W: www.topic.nl
Please consider the environment before printing this e-mail
On 07-04-2023 09:34, Mike Looijmans via lists.yoctoproject.org wrote:
As, as it turns out, this is what you get when the HDF_* variables
aren't set. I set them in the machine conf, and now at least the
build succeeds.
I assume that HDF_PATH can also point to a https server or so. Have
it pointing to a file for now.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: [email protected]
W: www.topic.nl
Please consider the environment before printing this e-mail
On 07-04-2023 07:42, Mike Looijmans via lists.yoctoproject.org wrote:
This is where I get stuck with meta-xilinx-tools:
NOTE: Fetching xsct binary tarball from
http://petalinux.xilinx.com/sswreleases/rel-v2022/xsct-trim/xsct-2022-2.tar.xz;sha256sum=8a3272036ca61f017f357bf6ad9dfbdec6aebb39f43c3ca0cee7ec86ea4c066f;downloadfilename=xsct_2022.2.tar.xz
NOTE: Extracting external xsct-tarball to sysroots
Initialising tasks: 100%
|################################################################################################|
Time: 0:02:14
Sstate summary: Wanted 1273 Local 1206 Mirrors 20 Missed 47
Current 0 (96% match, 0% complete)
NOTE: Executing Tasks
WARNING: pmufw-1.0-r0 do_package_qa: QA Issue: File
/boot/pmufw.elf in package pmufw contains reference to TMPDIR
[buildpaths]
ERROR: xilinx-bootbin-1.0-r0 do_configure: Expected file
//.../build/tmp-glibc/work/tdpzu9-oe-linux/xilinx-bootbin/1.0-r0/recipe-sysroot/boot/devicetree/tdpzu9.dtb,
specified from the bif file does not exists!
ERROR: Logfile of failure stored in:
//.../build/tmp-glibc/work/tdpzu9-oe-linux/xilinx-bootbin/1.0-r0/temp/log.do_configure.25424
ERROR: Task
(//.../meta-xilinx/meta-xilinx-core/recipes-bsp/bootbin/xilinx-bootbin_1.0.bb:do_configure)
failed with exit code '1'
WARNING: fsbl-1.0-r0 do_package_qa: QA Issue: File /boot/fsbl.elf
in package fsbl contains reference to TMPDIR [buildpaths]
NOTE: Tasks Summary: Attempted 3339 tasks of which 3011 didn't
need to be rerun and 1 failed.
Summary: 1 task failed:
/home/mike/projects/topic-platform-langdale/meta-xilinx/meta-xilinx-core/recipes-bsp/bootbin/xilinx-bootbin_1.0.bb:do_configure
Summary: There were 2 WARNING messages.
Summary: There was 1 ERROR message, returning a non-zero exit code.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: [email protected]
W: www.topic.nl
Please consider the environment before printing this e-mail
On 06-04-2023 17:06, Mark Hatle via lists.yoctoproject.org wrote:
On 4/6/23 6:53 AM, Mike Looijmans wrote:
Ah, andmeta-xilinx-tools is not part of meta-xilinx, but in a
separate repo: https://github.com/Xilinx/meta-xilinx-tools.git
Okay, this seems to build, but that can't be the case. It
appears to be using some random defaults for DDR timing and
such... So next is to figure out where to put that information...
You need to provide your XSA to the build.
This is handled via the external-hdf recipe in meta-xilinx-tools:
https://github.com/Xilinx/meta-xilinx-tools/blob/master/recipes-bsp/hdf/external-hdf.bb
# HDF_BASE - file protocol
# HDF_PATH - Path to git repository, or file in question
# HDF_NAME - Path to the XSA file once downloaded (must be inside
WORKDIR) (See anon python)
HDF_BASE ??= "git://"
HDF_PATH ??= "github.com/Xilinx/hdf-examples.git"
HDF_NAME ??= ""
The above is the method we currently recommend for setting
things. If your XSA is in a git repository you can mimic the
above. If you do use a git repository, then the XSA is expected
to be in a subdirectory that uses the name in the "HDF_MACHINE"
variable.
Otherwise if you just do:
HDF_BASE = "file://"
HDF_PATH = "/home/my_dir/my_project/my_board.xsa"
--Mark
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5222):
https://lists.yoctoproject.org/g/meta-xilinx/message/5222
Mute This Topic: https://lists.yoctoproject.org/mt/98101406/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
