Matchstiq-Z1 Getting Started Guide
ANGRYVIPER Team
Appendices
A
Intermittent Errors
Some tests have had “Segmentation Faults” or “Alignment Errors” in certain scenarios on the Z1. This seems to
happen when both USB ports are used to simultaneously transmit a large amount of data,
e.g.
high log-level output
to a USB serial console as well as NFS-mounted output files over a USB-to-Ethernet adapter. The default test setup
avoids triggering this by limiting output that is fed to the user, but users should be aware of this issue if non-default
test scenarios are attempted. If
ssh
is used to have all data routed through the USB-to-Ethernet adapter, this failure
mode is avoided.
B
Using ISE instead of Vivado with the Matchstiq-Z1
It is recommended that you use the default toolset (Xilinx Vivado) to build Matchstiq-Z1 bitstreams with OpenCPI.
However, if you wish to use ISE instead, reference the README file in
assets/hdl/platforms/matchstiq_z1/
ise_constraints/
, and perform the following steps:
1. Modify the target part in
assets/hdl/platforms/matchstiq_z1/matchstiq_z1.mk
to use the ISE alias:
HdlPart_matchstiq_z1=xc7z020_ise_alias-1-clg484
2. Export the ISE constraints files found in
<assets/>hdl/platforms/matchstiq_z1/ise_constraints/
by
modifying
ExportFiles
variable in
assets/hdl/platforms/matchstiq_z1/Makefile
:
ExportFiles=ise_constraints/matchstiq_z1.ucf ise_constraints/matchstiq_z1.ut matchstiq_z1.mk
C
Driver Notes
When available, the driver will attempt to make use of the CMA region for direct memory access. In use cases where
many memory allocations are made, the user may receive the following kernel message:
alloc_contig_range␣test_pages_isolated([memory␣start],␣[memory␣end])␣failed
This is a kernel warning, but does not indicate that a memory allocation failure occurred, only that the CMA engine
could not allocate memory in the first pass. Its default behavior is to make a second pass, and if that succeeded, the
end user should not see any more error messages. This message cannot be suppressed, but can be safely ignored. An
actual allocation failure will generate unambiguous error messages.
25
