Challenge3_Project_Report - kashyapp1/github_exp GitHub Wiki
Block Level UVMF TB Description:
- The below diagram shows the block level structure of different blocks present in the project.
Fig.1 Block level representation of blocks
-
As shown in the diagram there are three blocks present in the project and different blocks has different different interfaces connected to it to transfer of the data.
-
block 1 has apb, axi and spi interfaces connected to it and apb and axi are acts as an master interface for the block whereas spi is slave interface.
-
Associated interface.yaml files with block 1:
1. apb_master.yaml
2. axi_master.yaml
3. spi_slave.yaml -
Associated environmets and utils files with block 1:
1. block_1_env.yaml
2. block_2_utils.yaml -
Associated bench files with block 1:
1. block_1_bench.yaml -
block 2 has spi and wishbone interfaces connected to it and spi is acts as an master interface for the block whereas wishbone is slave interface.
-
Associated interface.yaml files with block 2:
1. spi_master.yaml
2. wishbone_slave.yaml -
Associated environments and utils files with block 2:
1. block_2_env.yaml
2. block_2_utils.yaml -
Associated bench files with block 1:
1. block_2_bench.yaml -
block 3 has axi and wishbone interfaces connected to it and wishbone is acts as master interface for the block whereas axi is slave interface.
-
Associated interface.yaml files with block 3:
1. wishbone_master.yaml
2. axi_slave.yaml -
Associated environments and utils files with block 3:
1. block_3_env.yaml
2. block_3_utils.yaml -
Associated bench files with block 1:
1. block_3_bench.yaml
Subsystem Level UVMF TB Description:
- The below diagram shows the subsystem level structure consists of blocks present in the project.
Fig.2 Subsystem of different two blocks
- As shown in the diagram there are two blocks present in the subsystem level architechure and different blocks has different different interfaces connected to it to transfer of the data.
- For the given subsystem apb, axi are acts as a master interfaces and wishbone is acts as slave interface.
- Associated files with it:
1. subsystem.yaml
2. subsystem_utils.yaml
System Level UVMF TB Description:
- The below diagram shows the system level structure consists of 3 blocks present in the project with subsystem.
Fig.3 System level diagram
- As shown in the diagram there are one subsystem with two blocks and one another block 3 making the whole system.
- this is the final system level diagram and it has all the blocks interfaces which can be made by reusing the subsystem environment and block 3 environment.
- Associated files with it:
1. system.yaml
2. system_utils.yaml