-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated README #1
base: main
Are you sure you want to change the base?
Conversation
README.md
Outdated
@@ -1,4 +1,4 @@ | |||
# RISC-V-Eklavya'23 | |||
# RISC-V-CPU | |||
--- | |||
|
|||
#### The RISC-V CPU will be implemented with IMAF instruction extensions, and also verified using custom verification methods. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let’s not talk about future objectives, and try to describe the CPU in its current. State. The first thing in a README should be describing what we have in the repository.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, will do the changes
README.md
Outdated
@@ -10,14 +10,45 @@ RISC-V is an instruction set architecture like ARM based on RISC (Reduced Instr | |||
|
|||
Due to being open-source in nature, RISC-V provides a vital step in designing, building and testing new hardware without paying any license fees or royalties |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems unnecessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, will remove that section.
README.md
Outdated
--- | ||
### How to compile the CPU and view simulation | ||
|
||
First we need to write a C code for the operation we need to perform on our CPU(For example:- We have written a script that generates fibonacci series), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are you writing this para as “We”. Reword this paragraph simply as instructions.
“An example C program can be loaded on the CPU’s program memory for operations.”
“We provide an example code under sim/fibonacci.c
for testing purposes."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, will do the changes
README.md
Outdated
-[Verilator](https://verilator.org/guide/latest/install.html) | ||
-[Gtkwave](https://gtkwave.sourceforge.net/) | ||
|
||
All the necessary commands have been added to the Makefile |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Specify path of the makefile
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, will do the changes
@@ -48,20 +79,21 @@ Following is the block diagram and workflow in simple terms of our CPU:- | |||
![image.png](https://hackmd.io/_uploads/rJScfOEXT.png) | |||
|
|||
|
|||
![image.png](https://hackmd.io/_uploads/rk-YYoMXp.png) | |||
|
|||
--- | |||
|
|||
### Tech Stack | |||
|
|||
- Verilog | |||
- Quartus Prime IDE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove this as we no longer use it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, will do the changes
README.md
Outdated
- Lattice Framework | ||
--- | ||
### Future Work | ||
- [ ] Fix issues with Seven Segment Display | ||
- [ ] Verify CPU output with every cases, possible, edge and false cases. | ||
- [x] Verify CPU output with every cases, possible, edge and false cases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verification is not done. Ideally, there should be a script that will formally verify the CPU and display results.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, will do the changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add instructions or a list of software which are needed to run the CPU. Provide links with instructions to install/build.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added softwares in the Tech stack, should I bring it on top of the document?
Also links for installations are also given above in the form of hyperlinks
Pushed the suggested changes |
Changes made in README:-