Tasks Use the provided template to implement your custom register…

/in /by

Question Answered step-by-step Tasks Use the provided template to implement your custom register… TasksUse the provided template to implement your custom register file and ALU.Register FileThe register file must fulfill the following requirements and functions:• The register file must be able to store four different 4-bit numbers.• With every rising edge of the clock, the register file will store the current inputvalue into the selected register. The write select input is used to determine wherethis value will be stored. For each possible input value of write select, a differentregister is being selected.• This custom register file has two 4-bit outputs: number 1 and number 2. Usingthe num 1 select and num 2 select inputs, the user can select two of the four storedvalues that will be used as output value (separately for each of the two outputs).It is possible to select the same value for both outputs.Notes:• You are allowed to (and should) use the built-in logic components provided by Lo-gisim. Think about the storing and retrieving part separately, review the functionof all logic components we covered, and find the component(s) that allows you toimplement the required function of the register file. You do not have to createa circuit on your own and can implement the entire register file by utilizing thecorrect logic components with the provided inputs and outputs.• The clear input of the register should not be used (do not connect anything to it).However, the enable input is a very important input for this assignment: It allowsyou to disable the register (enable input = 0 ), so it will keep the currently storedvalue and ignores rising edges. Only if the register is enabled (enable input = 1 )it will store the current input with the next rising edge.• Remember to generate rising edges (toggle the clock input) for testing. Otherwisethe registers will not store anything. Engineering & Technology Electrical Engineering SER 232 Share QuestionEmailCopy link Comments (0)