| commit | e721be3c13c96299a9be17c13648efaf9baf6a04 | [log] [tgz] |
|---|---|---|
| author | Cocogoat <70917894+AyaseErii@users.noreply.github.com> | Sat Dec 03 19:57:07 2022 -0500 |
| committer | GitHub <noreply@github.com> | Sat Dec 03 19:57:07 2022 -0500 |
| tree | d75d53005e7f444d8ba2a2472202baefb928a17b | |
| parent | 1d798d1b540ed37fa58e6ad623c069b4acce342f [diff] |
Delete verilog/dv/la_test1 directory
| :exclamation: GF180mcuC shuttle MPW0 |
|---|
This is a simple design with five 4-bit up-counters. The ports of each counter are clock, reset, io_out.
The FiveGuys design (gdsii file) is located at here and the wrappered counter (gdsii file) is located at here.
Before running the design flow, please make sure the gf180 PDK was installed correctly. For the information about switching PDK from sky130 to gf180mcuC, you may refer to this video. (Great thanks to Matt)
Once you have done with PDK setups, you can simply follow the commands below after you changed the corresponding cntr_example.v, config.tcl file, all files in the includes directory, and the uprj_netlist.v of the counter:
git clone https://github.com/AyaseErii/gf180-FiveGuys.git cd gf180-FiveGuys make cntr_example
The command above will generate the digital counter design (gdsii) and all necessary files for the next step---wrapper the design in to user_project_wrapper.
Before running the flow of user_project_wrapper, please make sure you changed the user_project_wrapper.v, config.tcl for the user_project_wrapper design, and macro.cfg for macro placement.
Once you have done with the above commands, you need to go to gf180-demo-binary_counter directory again, and use the command below:
make user_project_wrapper
After the flow compeleted, you can repeat the Step 2 iteratively until you get a satisfied design.
Sample result of the FiveGuys wrapper: 
Jun (Jerry) Yin, Ceylan M. Morgul, Rahul Sreekumar, Xuanjia (Eric) Bi, and Mircea R. Stan.
ECE department of University of Virginia
Refer to README for a quickstart of how to use caravel_user_project
Refer to README for this sample project documentation.