v002 docs literalinclude migration to pccx-v002¶
The PCCX documentation site clones a sibling RTL repository at build
time into codes/v002/. After the v002 IP-core extraction (Phase H
of the May 2026 restructure), the reusable RTL moved from
pccxai/pccx-FPGA-NPU-LLM-kv260 (board integration repo) into the
new IP-core package
pccxai/pccx-v002.
This page records the migration so the file path drift is visible in the docs history rather than buried in workflow diffs.
Before¶
Item |
Value |
|---|---|
Source |
|
Ref |
|
Layout |
KV260 in-tree |
After¶
Item |
Value |
|---|---|
Source |
|
Ref |
|
Layout |
reusable IP-core package: |
Path mapping (subset relevant to docs/v002/)¶
The full kv260→pccx-v002 path mapping lives in
pccx-v002/SOURCE_MANIFEST.md. The mappings consumed by
docs/v002/RTL/ and docs/v002/Build/ literalincludes are:
Old path |
New path |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Items without a 1:1 counterpart in pccx-v002¶
hw/vivado/npu_core_wrapper.sv— the Vivado IP-packaging wrapper remains in the board integration repository (KV260) because it encodes board-side packaging concerns. The corresponding section indocs/v002/Build/index.mdwas rewritten to point at the board integration repo rather than embed the file literally.
Why a single PR¶
Flipping RTL_REPO_URL to pccx-v002/main while the docs still
reference kv260 paths breaks every Sphinx strict build immediately.
Flipping the docs paths first while the workflow still pins the old
kv260 SHA breaks every Sphinx strict build immediately. The two
changes ship together so there is no half-state.
Hard-rule confirmation¶
No
git push --forceor--force-with-lease.No tags pushed.
No staging push.
No PCCX™ claim, no trademark claim, no private trademark filings exposed.
No hardware/runtime/timing/bitstream claim is made by this PR; it is documentation-only.