conneroisu/sfhw-proj2 issues and pull requests

#59 - Updates to IF/ID

Pull Request - State: closed - Opened by Kariniux 3 months ago

#59 - Updates to IF/ID

Pull Request - State: closed - Opened by Kariniux 3 months ago

#58 - Changes by create-pull-request action

Pull Request - State: open - Opened by github-actions[bot] 3 months ago

#58 - Changes by create-pull-request action

Pull Request - State: open - Opened by github-actions[bot] 3 months ago

#57 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#57 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#56 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#56 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#55 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#55 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#54 - component/forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#54 - component/forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#53 - updates to the IF/ID stage.. still not complete

Pull Request - State: closed - Opened by Kariniux 3 months ago

#53 - updates to the IF/ID stage.. still not complete

Pull Request - State: closed - Opened by Kariniux 3 months ago

#52 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#52 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#51 - IF_ID stage component created

Pull Request - State: closed - Opened by Kariniux 3 months ago

#51 - IF_ID stage component created

Pull Request - State: closed - Opened by Kariniux 3 months ago

#50 - component/forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#50 - component/forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#49 - component/forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#49 - component/forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#48 - adding pipeline Reg Ex/Mem implementation as well as test bench

Pull Request - State: closed - Opened by DanielMauricio13 3 months ago

#48 - adding pipeline Reg Ex/Mem implementation as well as test bench

Pull Request - State: closed - Opened by DanielMauricio13 3 months ago

#47 - component/forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#47 - component/forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#46 - made initial structure and basic logic for forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#46 - made initial structure and basic logic for forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#45 - feature/tooling

Pull Request - State: closed - Opened by conneroisu 3 months ago

#44 - removed unused vhdl_ls.toml (put it in $HOME) and further simplified the stage_idex.vhd file by removing the unnecessary signals and signals that were not being used (specifically the signals that were being used in the future stages)

Pull Request - State: closed - Opened by conneroisu 3 months ago
Labels: component

#44 - removed unused vhdl_ls.toml (put it in $HOME) and further simplified the stage_idex.vhd file by removing the unnecessary signals and signals that were not being used (specifically the signals that were being used in the future stages)

Pull Request - State: closed - Opened by conneroisu 3 months ago
Labels: component

#43 - added do file examples and start of testbench for stage_idex

Pull Request - State: closed - Opened by conneroisu 3 months ago

#43 - added do file examples and start of testbench for stage_idex

Pull Request - State: closed - Opened by conneroisu 3 months ago

#42 - feature/tooling

Pull Request - State: closed - Opened by conneroisu 3 months ago

#42 - feature/tooling

Pull Request - State: closed - Opened by conneroisu 3 months ago

#41 - feature/tooling

Pull Request - State: closed - Opened by conneroisu 3 months ago

#41 - feature/tooling

Pull Request - State: closed - Opened by conneroisu 3 months ago

#40 - feature/tooling

Pull Request - State: closed - Opened by conneroisu 3 months ago

#39 - feature/tooling

Pull Request - State: closed - Opened by conneroisu 3 months ago

#39 - feature/tooling

Pull Request - State: closed - Opened by conneroisu 3 months ago

#38 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#38 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#37 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#37 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#36 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#36 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] 3 months ago

#35 - component/forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#35 - component/forward unit

Pull Request - State: closed - Opened by conneroisu 3 months ago

#34 - fix

Pull Request - State: closed - Opened by aidanfoss 4 months ago

#34 - fix

Pull Request - State: closed - Opened by aidanfoss 4 months ago

#33 - create exmem stage

Pull Request - State: closed - Opened by aidanfoss 4 months ago

#33 - create exmem stage

Pull Request - State: closed - Opened by aidanfoss 4 months ago

#32 - Stages

Issue - State: open - Opened by conneroisu 4 months ago - 8 comments
Labels: component

#32 - Stages

Issue - State: open - Opened by conneroisu 4 months ago - 8 comments
Labels: component

#31 - Stage 2

Issue - State: open - Opened by conneroisu 4 months ago - 3 comments
Labels: component

#31 - Stage 2

Issue - State: open - Opened by conneroisu 4 months ago - 3 comments
Labels: component

#30 - Stage 1 (IF/ID)

Issue - State: open - Opened by Kariniux 4 months ago

#30 - Stage 1 (IF/ID)

Issue - State: open - Opened by Kariniux 4 months ago

#29 - Stage4 (MEM/WB)

Issue - State: open - Opened by aidanfoss 4 months ago - 1 comment

#29 - Stage4 (MEM/WB)

Issue - State: open - Opened by aidanfoss 4 months ago - 1 comment

#28 - Stage3 (EX/MEM)

Issue - State: open - Opened by aidanfoss 4 months ago

#28 - Stage3 (EX/MEM)

Issue - State: open - Opened by aidanfoss 4 months ago

#27 - Forwarding Unit

Issue - State: open - Opened by conneroisu 4 months ago
Labels: component

#27 - Forwarding Unit

Issue - State: open - Opened by conneroisu 4 months ago
Labels: component

#26 - Hardware / Software Creation

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: meta

#26 - Hardware / Software Creation

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: meta

#25 - Create a set of assembly programs that exhaustively tests control hazard avoidance. Minimally include one test program per control flow instruction. Then you should create a set of test programs that activates combinations of these instructions in the pipeline. Create a spreadsheet to track these cases and justify the coverage of your testing approach. Include this spreadsheet in your report as a table

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: assembly

#25 - Create a set of assembly programs that exhaustively tests control hazard avoidance. Minimally include one test program per control flow instruction. Then you should create a set of test programs that activates combinations of these instructions in the pipeline. Create a spreadsheet to track these cases and justify the coverage of your testing approach. Include this spreadsheet in your report as a table

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: assembly

#24 - Create a set of assembly programs that exhaustively tests the data forwarding and hazard detection capabilities of your pipeline. Minimally you should create one assembly program for each of your hazard detection and forwarding cases. Then you should create a set of test programs that activates combinations of your data hazard detection and forwarding cases that can occur simultaneously within your pipeline. Create a spreadsheet to track these cases and justify the coverage of your testing approach. Include this spreadsheet in your report as a table.

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: meta

#24 - Create a set of assembly programs that exhaustively tests the data forwarding and hazard detection capabilities of your pipeline. Minimally you should create one assembly program for each of your hazard detection and forwarding cases. Then you should create a set of test programs that activates combinations of your data hazard detection and forwarding cases that can occur simultaneously within your pipeline. Create a spreadsheet to track these cases and justify the coverage of your testing approach. Include this spreadsheet in your report as a table.

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: meta

#23 - Spreadsheet

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: report, spreadsheet

#23 - Spreadsheet

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: report, spreadsheet

#22 - Fill out When2Meet

Issue - State: closed - Opened by aidanfoss 4 months ago - 3 comments
Labels: meta

#22 - Fill out When2Meet

Issue - State: closed - Opened by aidanfoss 4 months ago - 3 comments
Labels: meta

#21 - Assign some shit to milestones

Issue - State: closed - Opened by aidanfoss 4 months ago

#21 - Assign some shit to milestones

Issue - State: closed - Opened by aidanfoss 4 months ago

#20 - new contract

Pull Request - State: closed - Opened by conneroisu 4 months ago

#20 - new contract

Pull Request - State: closed - Opened by conneroisu 4 months ago

#19 - added team contract work

Pull Request - State: closed - Opened by conneroisu 4 months ago

#19 - added team contract work

Pull Request - State: closed - Opened by conneroisu 4 months ago

#18 - [2.c.ii] For these instructions, list which stages need to be stalled and which stages need to be squashed/flushed relative to the stage each of these instructions is in.

Issue - State: open - Opened by aidanfoss 4 months ago - 3 comments
Labels: report

#17 - [2.c.i] list all instructions that may result in a non-sequential PC update and in which pipeline stage that update occurs.

Issue - State: open - Opened by aidanfoss 4 months ago - 1 comment
Labels: report

#16 - [2.b.iv] global list of the datapath values and control signals that are required during each pipeline stage

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: report

#15 - [2.b.iii] generalized list of potential data dependencies. From this generalized list, select those dependencies that can be forwarded (write down the corresponding pipeline stages that will be forwarding and receiving the data), and those dependencies that will require hazard stalls.

Issue - State: open - Opened by aidanfoss 4 months ago - 1 comment
Labels: report

#14 - [2.b.ii] List which of these same instructions consume values, and what signals in the pipeline these correspond to.

Issue - State: open - Opened by aidanfoss 4 months ago - 1 comment
Labels: report

#13 - e. Testing: Spreadsheet Testing of forwarding/detection and avoidance

Issue - State: open - Opened by conneroisu 4 months ago - 4 comments
Labels: hardware-pipeline, software-pipeline, assembly

#12 - [2.b.i] list which instructions produce values, and what signals (i.e., bus names) in the pipeline these correspond to.

Issue - State: open - Opened by aidanfoss 4 months ago - 2 comments
Labels: report

#11 - [2.a.iii] Create a testbench that instantiates all four of the registers in a single design. Show that values that are stored in the initial IF/ID register are available as expected four cycles later, and that new values can be inserted into the pipeline every single cycle. Most importantly, this testbench should also test that each pipeline register can be individually stalled or flushed.

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: report, wave-diagram, testbench

#10 - [2.a.ii] Draw a simple schematic showing how you could implement stalling and flushing operations given an ideal N-bit register.

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: report

#9 - [1.d] report the maximum frequency your software-scheduled pipelined processor can run at and determine what your critical path is (specify each module/entity/component that this path goes through).

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: report

#8 - [1.c.iii] Include an annotated waveform in your writeup of two iterations or recursions of these programs executing correctly and provide a short discussion of result correctness. In your waveform and annotation, provide 3 different examples (at least one data-flow and one control-flow) of where you did not have to use the maximum number of NOPs.

Issue - State: open - Opened by aidanfoss 4 months ago - 1 comment
Labels: report

#7 - [1.c.ii] Include an annotated waveform in your writeup of two iterations or recursions of these programs executing correctly and provide a short discussion of result correctness. In your waveform and annotation, provide 3 different examples (at least one data-flow and one control-flow) of where you did not have to use the maximum number of NOPs.

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: report

#6 - [1.c.i] include an annotated waveform in your writeup and provide a short discussion of result correctness.

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: report

#5 - [1.b.ii] high-level schematic drawing of the interconnection between components.

Issue - State: open - Opened by aidanfoss 4 months ago - 1 comment
Labels: report

#4 - [1.a] Come up with a global list of the datapath values and control signals that are required during each pipeline stage.

Issue - State: open - Opened by aidanfoss 4 months ago - 3 comments
Labels: report

#3 - Finalize Spreadsheet

Issue - State: open - Opened by aidanfoss 4 months ago
Labels: report, spreadsheet

#2 - Project Report

Issue - State: open - Opened by aidanfoss 4 months ago - 1 comment
Labels: meta

#1 - Google Doc Report

Issue - State: closed - Opened by conneroisu 4 months ago
Labels: report

GitHub / conneroisu/sfhw-proj2 issues and pull requests