Contents 24 files in 7 folders · listed 14 November 2026
This lists the whole project folder, 84-phantasmphi-cpu, which 13 products on this site draw on. What this product delivers is stated on this page under What you get.
- animate/
- make_phantomcore_3d.py 14 KB
- make_phantomcore_voxel.py 11 KB
- phantomcore-3d.svg 228 KB
- phantomcore-voxel.svg 71 KB
- README.md 2 KB
- build/
- phantom_soc_sky130.v 11.5 MB
- phantom_soc_tb.vvp 106 KB
- phantom_soc_v2_tb.vvp 119 KB
- phc01_sky130.log 766 KB
- phc02_sky130.v 17 KB
- phc02_yosys.log 190 KB
- rtl/
- phc02/
- tb/ 1 file
- phantom_core_cpu_v2.v 9 KB
- phantom_soc_v2.v 7 KB
- seq_divider.v 3 KB
- sram_1rw.v 2 KB
- sw/
- tb/
- phantom_core_cpu.v 9 KB
- phantom_soc.v 6 KB
- CONTACT_INFO.txt 1 KB
- phantomcore-cpu-deploy.zip 6 KB
- README.md 4 KB
- STATUS-PHC02.md 5 KB
For the Curious
A chip should earn its place in a rack the way a person earns a seat at a table: by doing the work, not by being talked about. This edition is PhantomCore at rack scale. The name says PHC03 at 14 nm, a 64-core 1U server node; the description says sixty-four PhantasmPhi cores at 1 GHz in a one-rack-unit box. It is RTL-proven, so the logic has been exercised and holds, and it is SKY130-mapped, so it has been carried onto a named open process rather than left as a drawing.
One rack unit is the thinnest slice a datacenter hands out, and sixty-four cores in that slice at a gigahertz is a part built for the hall, not the bench. It is for the datacenter operator who buys servers by the row and wants a CPU with a blueprint behind it before it goes in, for the engineering buyer specifying the next node, and for the licensee who wants a server-class core they do not have to take on trust. The figures behind it are laid out in the full calculator on the site; this is product number 10329, the rack-scale edition.
What you walk away with is the use of the blueprint for this 64-core 1U edition. The PhantomCore design stays with the inventor, CRI-ONE; the right to fill a rack with it is yours.