Repository boundaries¶
The model and the board consume the IP core. The IP core never references
a specific model name or board name in rtl/ or compatibility/.
Repository roles¶
Repository |
Role |
|---|---|
|
Canonical specification, documentation, and project index. |
|
v002 IP-core package for LLM, Vision, Voice, and common reusable sources. |
|
Future v003 IP-core package. |
|
KV260 + LLM application integration; consumes |
Placement rule¶
Content |
Owner |
|---|---|
Architecture contracts, register maps, memory maps, and top interfaces |
Versioned IP-core package, mirrored here for documentation. |
Reusable RTL, packages, interfaces, wrappers, testbenches, and formal harnesses |
|
Board constraints, Vivado project files, board top wrappers, and PS/PL wiring |
Board integration repository. |
Model manifests, application runtime code, driver HALs, and board run evidence |
Application integration repository. |
Naming red flags¶
These names are not allowed inside IP-core rtl/ or compatibility/
paths, except in README files or compatibility documentation that clearly
describes a consumer.
gemma gemma3n gemma4 llama qwen mistral e4b
kv260 kria zcu104 alveo versal