conneroisu/processsor-proj-1 issues and pull requests

#87 - Enhanced Header Program

Issue - State: open - Opened by conneroisu 29 days ago

#87 - Enhanced Header Program

Issue - State: open - Opened by conneroisu 29 days ago

#86 - Changes by create-pull-request action

Pull Request - State: open - Opened by github-actions[bot] about 1 month ago

#86 - Changes by create-pull-request action

Pull Request - State: open - Opened by github-actions[bot] about 1 month ago

#85 - new ALU tests with all operations for part 2cVIII

Pull Request - State: closed - Opened by DanielMauricio13 about 1 month ago

#85 - new ALU tests with all operations for part 2cVIII

Pull Request - State: closed - Opened by DanielMauricio13 about 1 month ago

#84 - [Part 3] In your writeup, show the Modelsim output for each of the following tests, and provide a discussion of result correctness. It may be helpful to also annotate the waveforms directly.

Issue - State: closed - Opened by aidanfoss about 1 month ago

#84 - [Part 3] In your writeup, show the Modelsim output for each of the following tests, and provide a discussion of result correctness. It may be helpful to also annotate the waveforms directly.

Issue - State: closed - Opened by aidanfoss about 1 month ago

#83 - fix control unit

Issue - State: closed - Opened by aidanfoss about 1 month ago

#83 - fix control unit

Issue - State: closed - Opened by aidanfoss about 1 month ago

#82 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#82 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#81 - modified ALU working fine now

Pull Request - State: closed - Opened by DanielMauricio13 about 1 month ago

#81 - modified ALU working fine now

Pull Request - State: closed - Opened by DanielMauricio13 about 1 month ago

#80 - ALU

Pull Request - State: closed - Opened by DanielMauricio13 about 1 month ago - 1 comment

#80 - ALU

Pull Request - State: closed - Opened by DanielMauricio13 about 1 month ago - 1 comment

#79 - Update tb_barrelShifter.vhd

Pull Request - State: closed - Opened by aidanfoss about 1 month ago

#79 - Update tb_barrelShifter.vhd

Pull Request - State: closed - Opened by aidanfoss about 1 month ago

#78 - testing barrelshifter, final fix

Pull Request - State: closed - Opened by aidanfoss about 1 month ago - 1 comment

#78 - testing barrelshifter, final fix

Pull Request - State: closed - Opened by aidanfoss about 1 month ago - 1 comment

#77 - should really just gitignore this file

Pull Request - State: closed - Opened by aidanfoss about 1 month ago

#77 - should really just gitignore this file

Pull Request - State: closed - Opened by aidanfoss about 1 month ago

#76 - 70 merge damage

Pull Request - State: closed - Opened by aidanfoss about 1 month ago - 1 comment

#76 - 70 merge damage

Pull Request - State: closed - Opened by aidanfoss about 1 month ago - 1 comment

#75 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#75 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#74 - [Part 2 (b.i)] What are the control flow possibilities that your instruction fetch logic must support? Describe these possibilities as a function of the different control flow-related instructions you are required to implement.

Issue - State: closed - Opened by conneroisu about 1 month ago

#74 - [Part 2 (b.i)] What are the control flow possibilities that your instruction fetch logic must support? Describe these possibilities as a function of the different control flow-related instructions you are required to implement.

Issue - State: closed - Opened by conneroisu about 1 month ago

#73 - assembly report files

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#73 - assembly report files

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#72 - assembly report files

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#72 - assembly report files

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#71 - assembly report files

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#71 - assembly report files

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#70 - remove contract and update workflow

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#70 - remove contract and update workflow

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#69 - rebase awfoss to aidanfoss

Issue - State: open - Opened by aidanfoss about 1 month ago - 4 comments

#69 - rebase awfoss to aidanfoss

Issue - State: open - Opened by aidanfoss about 1 month ago - 4 comments

#68 - Project Report

Issue - State: open - Opened by aidanfoss about 1 month ago - 4 comments
Labels: documentation, Report

#68 - Project Report

Issue - State: open - Opened by aidanfoss about 1 month ago - 4 comments
Labels: documentation, Report

#67 - 44 project report and barrel shifter fix

Pull Request - State: closed - Opened by aidanfoss about 1 month ago

#67 - 44 project report and barrel shifter fix

Pull Request - State: closed - Opened by aidanfoss about 1 month ago

#66 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#66 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#65 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#65 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#64 - 8 barrel shifter

Pull Request - State: closed - Opened by aidanfoss about 1 month ago

#64 - 8 barrel shifter

Pull Request - State: closed - Opened by aidanfoss about 1 month ago

#63 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#63 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#62 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#62 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#61 - adder subtractor

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: components

#61 - adder subtractor

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: components

#60 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#60 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#59 - component/addersub

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#59 - component/addersub

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#58 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#58 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#57 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#57 - Changes by create-pull-request action

Pull Request - State: closed - Opened by github-actions[bot] about 1 month ago

#56 - test/branch

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#56 - test/branch

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#55 - fix header program to get all commits for the file not just the branch

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#55 - fix header program to get all commits for the file not just the branch

Pull Request - State: closed - Opened by conneroisu about 1 month ago

#54 - [Part 2 (c.viii)] justify why your test plan is comprehensive. Include waveforms that demonstrate your test programs functioning.

Issue - State: closed - Opened by conneroisu about 1 month ago - 4 comments
Labels: Report

#54 - [Part 2 (c.viii)] justify why your test plan is comprehensive. Include waveforms that demonstrate your test programs functioning.

Issue - State: closed - Opened by conneroisu about 1 month ago - 4 comments
Labels: Report

#53 - [Part 4] report the maximum frequency your processor can run at and determine what your critical path is. Draw this critical path on top of your top-level schematics. What components would you focus on to improve the frequency?

Issue - State: closed - Opened by conneroisu about 1 month ago - 1 comment
Labels: Report

#53 - [Part 4] report the maximum frequency your processor can run at and determine what your critical path is. Draw this critical path on top of your top-level schematics. What components would you focus on to improve the frequency?

Issue - State: closed - Opened by conneroisu about 1 month ago - 1 comment
Labels: Report

#52 - [Part 3] In your writeup, show the Modelsim output for each of the following tests, and provide a discussion of result correctness. It may be helpful to also annotate the waveforms directly.

Issue - State: closed - Opened by conneroisu about 1 month ago - 3 comments
Labels: Report

#52 - [Part 3] In your writeup, show the Modelsim output for each of the following tests, and provide a discussion of result correctness. It may be helpful to also annotate the waveforms directly.

Issue - State: closed - Opened by conneroisu about 1 month ago - 3 comments
Labels: Report

#51 - Synthesize Processor and commit results to the repo

Issue - State: closed - Opened by conneroisu about 1 month ago - 3 comments

#51 - Synthesize Processor and commit results to the repo

Issue - State: closed - Opened by conneroisu about 1 month ago - 3 comments

#50 - [Part 3 (c)] Create and test an application that sorts an array with N elements using the BubbleSort algorithm (link). Name this file Proj1_bubblesort.s.

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: Report

#50 - [Part 3 (c)] Create and test an application that sorts an array with N elements using the BubbleSort algorithm (link). Name this file Proj1_bubblesort.s.

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: Report

#49 - [Part 3 (a)] Create a test application that makes use of every required arithmetic/logical instruction at least once. The application need not perform any particularly useful task, but it should demonstrate the full functionality of the processor (e.g., sequences of many instructions executed sequentially, 1 per cycle while data written into registers can be effectively retrieved and used by later instructions). Name this file Proj1_base_test.s.

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: Report

#49 - [Part 3 (a)] Create a test application that makes use of every required arithmetic/logical instruction at least once. The application need not perform any particularly useful task, but it should demonstrate the full functionality of the processor (e.g., sequences of many instructions executed sequentially, 1 per cycle while data written into registers can be effectively retrieved and used by later instructions). Name this file Proj1_base_test.s.

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: Report

#48 - [Part 3 (b)] Create and test an application which uses each of the required control-flow instructions and has a call depth of at least 5 (i.e., the number of activation records on the stack is at least 4). Name this file Proj1_cf_test.s.

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: Report

#48 - [Part 3 (b)] Create and test an application which uses each of the required control-flow instructions and has a call depth of at least 5 (i.e., the number of activation records on the stack is at least 4). Name this file Proj1_cf_test.s.

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: Report

#47 - [Part 2 (c.iii)] Draw a simplified, high-level schematic for the 32-bit ALU. Consider the following questions: how is Overflow calculated? How is Zero calculated? How is slt implemented?

Issue - State: closed - Opened by conneroisu about 1 month ago - 1 comment
Labels: Report

#47 - [Part 2 (c.iii)] Draw a simplified, high-level schematic for the 32-bit ALU. Consider the following questions: how is Overflow calculated? How is Zero calculated? How is slt implemented?

Issue - State: closed - Opened by conneroisu about 1 month ago - 1 comment
Labels: Report

#46 - In your writeup, briefly describe your design approach, including any resources you used to choose or implement the design. Include at least one design decision you had to make.

Issue - State: closed - Opened by conneroisu about 1 month ago - 2 comments
Labels: Report

#46 - In your writeup, briefly describe your design approach, including any resources you used to choose or implement the design. Include at least one design decision you had to make.

Issue - State: closed - Opened by conneroisu about 1 month ago - 2 comments
Labels: Report

#45 - [Part 2 (c.i.2)] In your writeup, briefly describe how your VHDL code implements both the arithmetic and logical shifting operations.

Issue - State: closed - Opened by conneroisu about 1 month ago - 2 comments
Labels: Report

#45 - [Part 2 (c.i.2)] In your writeup, briefly describe how your VHDL code implements both the arithmetic and logical shifting operations.

Issue - State: closed - Opened by conneroisu about 1 month ago - 2 comments
Labels: Report

#44 - [Part 2 (c.i.1)] Describe the difference between logical (srl) and arithmetic (sra) shifts. Why does MIPS not have a sla instruction?

Issue - State: closed - Opened by conneroisu about 1 month ago - 1 comment
Labels: Report

#44 - [Part 2 (c.i.1)] Describe the difference between logical (srl) and arithmetic (sra) shifts. Why does MIPS not have a sla instruction?

Issue - State: closed - Opened by conneroisu about 1 month ago - 1 comment
Labels: Report

#43 - Draw a schematic for the instruction fetch logic and any other datapath modifications needed for control flow instructions. What additional control signals are needed?

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: Report

#43 - Draw a schematic for the instruction fetch logic and any other datapath modifications needed for control flow instructions. What additional control signals are needed?

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: Report

#42 - Include your final MIPS processor schematic in your lab report.

Issue - State: closed - Opened by conneroisu about 1 month ago - 1 comment
Labels: Report

#42 - Include your final MIPS processor schematic in your lab report.

Issue - State: closed - Opened by conneroisu about 1 month ago - 1 comment
Labels: Report

#41 - Implement the control logic module using whatever method and coding style you prefer. Create a testbench to test this module individually, and show that your output matches the expected control signals from problem 1(a).

Issue - State: closed - Opened by conneroisu about 1 month ago - 4 comments
Labels: Report

#41 - Implement the control logic module using whatever method and coding style you prefer. Create a testbench to test this module individually, and show that your output matches the expected control signals from problem 1(a).

Issue - State: closed - Opened by conneroisu about 1 month ago - 4 comments
Labels: Report

#40 - What are the control flow possibilities that your instruction fetch logic must support? Describe these possibilities as a function of the different control flow-related instructions you are required to implement.

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: Report

#40 - What are the control flow possibilities that your instruction fetch logic must support? Describe these possibilities as a function of the different control flow-related instructions you are required to implement.

Issue - State: closed - Opened by conneroisu about 1 month ago
Labels: Report

#39 - Implement your new instruction fetch logic using VHDL. Use Modelsim to test your design thoroughly to make sure it is working as expected. Describe how the execution of the control flow possibilities corresponds to the Modelsim waveforms in your writeup.

Issue - State: closed - Opened by conneroisu about 1 month ago - 9 comments
Labels: Report

#39 - Implement your new instruction fetch logic using VHDL. Use Modelsim to test your design thoroughly to make sure it is working as expected. Describe how the execution of the control flow possibilities corresponds to the Modelsim waveforms in your writeup.

Issue - State: closed - Opened by conneroisu about 1 month ago - 9 comments
Labels: Report

#38 - [Part 2 (c.i.4)] Describe how the execution of the different shifting operations corresponds to the Modelsim waveforms in your writeup.

Issue - State: closed - Opened by conneroisu about 1 month ago - 1 comment
Labels: Report

#38 - [Part 2 (c.i.4)] Describe how the execution of the different shifting operations corresponds to the Modelsim waveforms in your writeup.

Issue - State: closed - Opened by conneroisu about 1 month ago - 1 comment
Labels: Report

GitHub / conneroisu/processsor-proj-1 issues and pull requests