Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`pr_verify` failures in several exampeles

Open
  • Is something wrong?
#228 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Domain
build-system, embedded-iot

Research direction

Start by comparing the reference checkpoint static_shell_compute/static_shell_slash.dcp with the routed checkpoints under examples/04_freq, examples/05_perf, and examples/06_dcmac. Run the reported pr_verify -full_check comparisons and inspect the NOC-Validation-16 address-size differences. Done means documenting whether the RP rebuild flow causes the mismatch and whether pr_verify is required before partial PDI generation.

Written by the indexing model from the issue text.

Description

We observed a similar failure on our Alveo V80 with Vivado 2025.1. We also found a separate DFX compatibility issue through offline pr_verify.
Our setup uses a custom SLASH shell modified from the original PCIe Gen5 x8 configuration to PCIe Gen4 x16. The observations therefore come from a modified shell. Our V80 board failed while loading the 05_perf partial PDI, accroding to dmesg:

[Fri Sep 25 11:04:06 2026] ami: CRITICAL WARNING: cmd id: 234 timed out(timeout), hot reset is required
[Fri Sep 25 11:04:06 2026] ami 0000:25:00.0: ERROR           : Submitted command timed out
[Fri Sep 25 11:04:06 2026] ami: ERROR           : Failed to get the heartbeat msg!
[Fri Sep 25 11:04:06 2026] ami: ERROR           : AMC Heartbeat expired event received
[Fri Sep 25 11:04:07 2026] ami 0000:25:00.0: ERROR           : Logging thread error - invalid PCI data read!
[Fri Sep 25 11:04:08 2026] ami: CRITICAL WARNING: cmd id: 237 timed out(timeout), hot reset is required
[Fri Sep 25 11:04:08 2026] ami 0000:25:00.0: ERROR           : Submitted command timed out
[Fri Sep 25 11:04:08 2026] ami: ERROR           : Failed to get the heartbeat msg!
[Fri Sep 25 11:04:08 2026] ami: ERROR           : AMC Heartbeat expired event received
[Fri Sep 25 11:04:08 2026] slash_qdma 0000:25:00.1: QDMA PCI access lost; stopping error polling and hardware cleanup
[Fri Sep 25 11:04:09 2026] ami: ERROR           : FW_IF write request failed; 28
[Fri Sep 25 11:04:09 2026] ami 0000:25:00.0: ERROR           : Submitted command killed, abort.
[Fri Sep 25 11:04:09 2026] ami: ERROR           : Failed to get the heartbeat msg!
[Fri Sep 25 11:04:09 2026] ami: ERROR           : AMC Heartbeat expired event received
[Fri Sep 25 11:04:09 2026] ami: ERROR           : Heartbeat fail count above threshold! Raising fatal event...
[Fri Sep 25 11:04:09 2026] ami: ERROR           : AMC Heartbeat fatal event received, stopping GCQ...
[Fri Sep 25 11:04:23 2026] ami: ERROR           : No matching cid 234 found, unexpected response
[Fri Sep 25 11:04:31 2026] ami: ERROR           : No matching cid 237 found, unexpected response
  • 11:04:05: PDI download started, size 32,221,056 bytes.
  • 11:04:06–08: AMI reported heartbeat timeouts, QDMA reported PCI access lost, and the download failed with No such device.
  • 11:04:47: A subsequent reset failed at AMI_IOC_DEVICE_BOOT with Operation not permitted.
  • VRTD subsequently reported that the device did not exist.
pr_verify failures

We ran pr_verify -full_check between each region’s reference abstract shell DCP and its corresponding routed implementation DCP:

Example RP checked Reference NoC address size Implemented address size Result
04_freq slash 128 MiB 64 KiB Not compatible
05_perf slash 128 MiB 8 MiB Not compatible
06_dcmac slash 128 MiB 256 KiB Not compatible

All three slash checks failed with NOC-Validation-16.

ERROR: [Constraints 18-6214] NOC-Validation-16: Reconfigurable NOC instance top_i/slash/S_AXILITE_INI in checkpoint ~/SLASH/linker/slashkit/resources/static_shell_compute/static_shell_slash.dcp has address size 134217728, while the equivalent reconfigurable NOC instance top_i/slash/axi_noc_0/inst/M00_AXI_nsu/bd_2beb_M00_AXI_nsu_0_top_INST/NOC_NSU512_INST in checkpoint ~/SLASH/examples/05_perf/build/perf_hw.vbin.prj/slash_rm/slash_perf_hw.runs/impl_1/top_wrapper_routed.dcp has a different address size 8388608. In Dynamic Function Exchange flow, the equivalent reconfigurable NOC instance must have the same address size across configurations.

Is this NoC address-size change a known issue in the RP rebuild flow, or is a different verification procedure required? It would also be useful to clarify whether pr_verify should be enforced before partial PDI generation.

Originally posted by @ZhangMZh in #225

Dominant language
Tcl
Stars
48
Forks
23
Avg merge
1d 1h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Xilinx/SLASH

All issues in Xilinx/SLASH

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.