matthew1kalasky3/a2o: The A2O core was a follow-on to A2I, written in Verilog, and supported a lower thread count than A2I, but higher performance per thread, using out-of-order execution (register renaming, reservation stations, completion buffer) and a store queue - a2o

The A2O core was a follow-on to A2I, written in Verilog, and supported a lower thread count than A2I, but higher performance per thread, using out-of-order execution (register renaming, reservation stations, completion buffer) and a store queue

You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Go to file

wtf 3f6663020c init		3 years ago
rel/doc	init	3 years ago
.gitattributes	init	3 years ago
LICENSE	init	3 years ago
README.md	init	3 years ago
readme.md	init	3 years ago

readme.md

Directory Structure

src/verilog/trilib
src/verilog/work
src/vhdl

build
   bd (project)
   ip_cache (empty until project built)
   ip_repo (empty until IP built/copied)
   ip_user (IP macros to be built)
   tcl (build scripts)

fpga
   tcl

doc
   core user guide, etc.

Build Process

IP

IP is created in ip_user and copied to ip_repo for use in top level bd.

See build/ip_user/xxx/readme.md.

Core:

a2o_core

Core-AXI:

a2l2_axi

Simple card components:

a2o_axi_reg 
a2o_dbug

Help Vivado attach to VIO correctly:

reverserator_3
reverserator_4
reverserator_64

Project

See build/bd/readme.md.

create project
synth/implement