Simulink App Test Bench Architecture

1. Simulink App Test Bench Architecture WINLAB – Rutgers University Date : November 15 2011 Authors : Prasanthi Maddala, prasanthi.m@gmail.com Khanh Le, kle@winlab.rutgers.edu

2. Application Test Bench Model Simulink App TB MMU Driver, Pcore Driver and Simulation Manager are MATLAB/Simulink blocks that provide stimulus to the Application. Any signals between the Application and these blocks must be converted using Simulink Gateways.

3. MMU Driver Simulink App TB i_request – active high signal from the pcore driver requests for ‘i_cmd_cnt’ number of data commands to be sent to the App when ‘i_sent_all_pkts’ signal is low. When ‘i_send_all_pkts’ signal is high, all the data commands are sent on seeing ‘i_request’ high. MMU Driver (masked subsystem) mask Parameters – App Data Cmd file name , data folder App Data Cmd file contains a list of data command files. It should be noted that all files in that list are treated as data commands only, control commands (RMAP commands) are expected from Pcore driver. App Data Cmd file format Data Size (bytes) Data File *********************************************** 56 mod_data_1.txt 72 mod_data_2.txt

4. MMU Driver state machine Simulink App TB

5. Pcore Driver Simulink App TB PcoreCmd file format Cmd Param *********************************************** READ Addr WRITE Addr Data WAIT no.of clk cycles MMU_REQ_ALL MMU_REQ _CNT cmd_cnt

6. Pcore Driver state machine Simulink App TB Pcore driver sends an Mmu request and comes back to ST_PARSE_CMD. It continues to process commands until it sees another MMU_REQ command. It then checks if MMU driver is done with the previous request before sending a new request. If the MMU driver is still working on the previous request, then it waits in ST_WAIT_MMU_DRV_DONE.