Move HBM CDC out of user DFX region
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- embedded-iot
Research direction
Start by tracing the user-to-HBM datapath and identifying the current CDC and DFX decoupler placement. Rework the design so the CDC is in the strip between HBM_NMUs and the DFX region, uses LUTRAM, and follows the decoupler; done means the entire DFX region is clocked from the scalable clock.
Written by the indexing model from the issue text.
Description
Currently CDC for user -> HBM datapath is in the DFX region which makes it possible for timing failures on the non-scalable HBM clock in the DFX region. To ensure timing failure is not possible for user designs in the DFX region, we must clock the entire DFX region from the scalable clock and therefore move the CDC out of the DFX and into the strip between HBM_NMUs and the DFX region. This requires
- rearchitecting the CDC to use LUTRAM
- swapping the order of DFX decoupler and CDC
- Dominant language
- Tcl
- Stars
- 48
- Forks
- 23
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Xilinx/SLASH
-
SMBus and DCMAC license requirement not in docsPossibly taken @mariodruiz claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Supporting asynchronous HBM clock crossing and AXI width conversionPossibly taken @hpc-aulmamei claimed this 5 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
device bring up issue (v80-smi write-static-shell)Possibly taken @quetric claimed this 8 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
tenstorrent/tt-umd#3605 ·
Maintainers usually reply within 4 days
-
Template: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
betaflight/betaflight#15807 · 3 comments ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
oresat/oresat-linux#90 ·
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
espressif/esp-iot-solution#794 ·