Xilinx / Xilinx/XRT

Errors when checking memory bank index using "xbutil examine --report memory" command

Open
#7,638 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
686
Forks
549
Avg merge
2d 4h
Merged PRs (30d)
70

Description

The XRT native API documentation says we can use xbutil examine --report memory command to check the memory bank index. But I always got errors.

First I was asked to use --device to specify device. This is easy to solve. So the command now becomes

xbutil examine --report memory -d 0000:3b:00.1

But when I run this command, the first problem I encountered is that there is no information related to memory bank index. Only platform name was returned:

-------------------------------------------------
[0000:3b:00.1] : xilinx_u280_gen3x16_xdma_base_1
-------------------------------------------------

I have no idea how to fix these errors and I want to get the memory bank index using xbutil examine --report memory command as the document suggests, especially those related to HBM. Can you please lend me a hand? Thank you.

I am using Alveo U280 accelerator card on Ubuntu 22.04. The XRT version is 2.15.228 (released on 2023-06-13).

Contributor guide

Open the contributing guide

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.

Research direction

Start with the linked XRT native API documentation and reproduce xbutil examine --report memory -d 0000:3b:00.1 on the reported U280, Ubuntu 22.04, and XRT 2.15 setup. Compare the documented behavior with the command output, then determine whether the documentation or the command needs correction and verify the expected HBM memory-bank information.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, ubuntu
Domain
cli, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.