From: Chao Liu <chao.liu@yeah.net>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, bin.meng@windriver.com,
edgar.iglesias@gmail.com, alistair@alistair23.me,
Chao Liu <chao.liu@yeah.net>
Subject: [PATCH v3 0/2] Drop ignore_memory_transaction_failures for xilink_zynq
Date: Sun, 6 Oct 2024 00:06:04 +0800 [thread overview]
Message-ID: <cover.1728141040.git.chao.liu@yeah.net> (raw)
Hi all,
Following the Zynq-7000 SoC Data Sheet's "Memory Map" section (referenced at [1]),
We have identified the need to create placeholders for unimplemented devices
across the entire range of Zynq-7000 series boards.
This effort aims at ensuring maximum compatibility with different models
within the series.
The following table summarizes the relevant memory map addresses
for the Zynq-7000:
Start Address Size (MB) Description
0x0000_0000 1,024 DDR DRAM and on-chip memory (OCM)
0x4000_0000 1,024 PL AXI slave port #0
0x8000_0000 1,024 PL AXI slave port #1
0xE000_0000 256 IOP devices
0xF000_0000 128 Reserved
0xF800_0000 32 Programmable registers access via AMBA APB bus
0xFA00_0000 32 Reserved
0xFC00_0000 64 MB - 256 KB Quad-SPI linear address base address (except
to 256 KB which is in OCM), 64 MB reserved,
only 32 MB is currently supported
0xFFFC_0000 256 KB OCM when mapped to high address space
For the purposes of this patch, we will not be creating placeholders for
DRAM and any reserved regions of the address space.
A test script has been developed that covers the most common board types of
the Zynq-7000 series.
The test script obtained all linux binary images of the zynq-7000 series boards
from xilinx-wiki for script testing(referenced at [2]).
The steps to run the test are as follows:
a) Clone the repository.
git clone -b xilinx-zynq-test https://github.com/gevico/qemu-board.git
b) Apply the patch attached to this email and compile QEMU.
c) Set the environment variable for the path to your QEMU.
export QEMU_PATH=<your qemu path>
d) Execute the testing script.
./qemu-zynq-test
e) Check the results.
If successful, the output should resemble the following:
Test Project: <your path>/qemu-board/hw/arm/xilinx-zynq
Start 1: xilinx-zynq.zc702
1/3 Test #1: xilinx-zynq.zc702 ...................... Passed
Start 2: xilinx-zynq.zc706
2/3 Test #2: xilinx-zynq.zc706 ...................... Passed
Start 3: xilinx-zynq.zed
3/3 Test #3: xilinx-zynq.zed ...................... Passed
All tests passed
See:
[1]: https://www.amd.com/content/dam/xilinx/support/documents/data_sheets/ds190-Zynq-7000-Overview.pdf
[2]: http://www.wiki.xilinx.com/Zynq+2016.2+Release
Chao Liu (2):
xilink_zynq: Add various missing unimplemented devices
xilink-zynq-devcfg: Fix up for memory address range size not set
correctly
hw/arm/xilinx_zynq.c | 12 +++++++++++-
hw/dma/xlnx-zynq-devcfg.c | 2 +-
2 files changed, 12 insertions(+), 2 deletions(-)
--
2.46.1
next reply other threads:[~2024-10-05 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 16:06 Chao Liu [this message]
2024-10-05 16:06 ` [PATCH v3 1/2] xilink_zynq: Add various missing unimplemented devices Chao Liu
2024-10-06 14:13 ` Peter Maydell
2024-10-05 16:06 ` [PATCH v3 2/2] xilink-zynq-devcfg: Fix up for memory address range size not set correctly Chao Liu
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=cover.1728141040.git.chao.liu@yeah.net \
--to=chao.liu@yeah.net \
--cc=alistair@alistair23.me \
--cc=bin.meng@windriver.com \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).