Write a MIPS simulator that consists of assembler and virtual machine.
The assembler is able to take an assembly program written in a subset of MIPS-32 instruction set and translate it into machine language. The assembler should be able to do the following:
- Provide a GUI interface and allow the user to load a program:
1.1. By typing in the instructions directly.
1.2. Or by copying and pasting. - Support the following instructions:
2.1. The basic functions without pseudo-instructions and without function calls.
2.2. ALU operations: add, addi, sub, and, or, andi, ori, sll, slt, slti, lui
2.3. Branches/jumps: jr, j, beq, bne and labels. Assembler must decide jump destination. - The assembler will take as input the text of the assembly program and will output a list of machine language instructions. (See the assumptions in MIPS Virtual Machine section below)
- Note: Your assembler does not work like QTSPIM. So no need to support data declarations, data types, data and text sections, etc. You will get input programs in pure MIPS assembly.
The virtual machine simulates the structure of MIPS-32 processor and can run the machine language program produced by the assembler. Your machine should be able to do the following:
1. Provide a GUI to allow the user to see the status of the Program Counter, MIPS registers (or at least the important ones), the relevant part of the memory (were used variables are stored) and the currently executing instructions and its type (R, I, J), parts like opcode, registers, etc.
2. The machine will have buttons to execute the next instruction or the entire program.
3. Make the following assumptions:
• Memory has only two segments: Text (Program) segment and Data segment.
• The program is always loaded starting from memory location 0. (Start of text segment)
• Data is stored starting from memory location 0x00001000. (Start of Data segment)
- Develop the program in JAVA. Take advantage of JAVA Swing GUI components.
- Write file headers with date, author, version, etc. and which Java version / tools you used.
- Use object-oriented design properly.
3.1. First think of the classes your system should have in this system.
3.2. Next, think of the responsibility of each class and its attributes and methods to do its job.
3.3. Next, think of the external API (public methods) that other classes can use in this class.
3.4. Finally, think of how these classes cooperate to achieve the task of the program.
3.5. (Advanced - Optional) Consider using the Command Design Pattern.
- MinaFarid - mina faried
- Mariam Makram - mariammakram
- Fatma Ashraf - fatmaashraframadan