Team Slytherin

Team Members

• Kevin Townsend
• Bhavani Satyanarayana Rao
• Chidvila Gaddam

Assignment1

---

Running the sample application with script files

• The runcp script located in the SampleAppVadd can be used to run the application in HW which sets the appropriate environment variables and runs the UserApp.exe
export CNY_PDK_PROJ = ~/pdk_sample/cae_pers_vadd ./runcp
• The run script located in the SampleAppVadd can be used to run the application in SW
• The scripts above can be used to run the application on Simulator using the "-vsim" option which sets the environment variable CNY_CAE_EMULATOR to ./run_simulation
./runcp -vsim or ./run -vsim

Environment Variables	Software	ModelSim	Hardware
CNY_SIM_THREAD	libcpSimLib2.so	libcpSimLib2.so	unset
CNY_CAE_EMULATOR	<location for CaeSimPers>	./run_simulation	unset

Changes made to run the application on ModelSim

• Setup as explained in here [[1]]
• Set the CNY_PDK_PROJ environment variable to the location of cae_pers_vadd
export CNY_PDK_PROJ = ~/pdk_sample/cae_pers_vadd
• Copied Jones' my_makefile from the temp dir and replaced the makefile in CY_PDK_PROJ/testbench
• Add line to the makefile in testbench dir
CNY_PDK_MODELSIM_USER_SIM_OPTIONS= -i -do "run -all"
• Modify the values of LIB_DIR and LDFLAGS from 32-bit to 64-bit as given below
LIB_DIR = lib64 LDFLAGS = -m64

Extra Credit: Invoking gdb

• We can invoke gdb using the gdb <programname> command or by using the run/runcp script files in with "-gdb" option
gdb UserApp.exe or ./run -gdb
• One can find different command classes on gdb by typing help.To get details on a particular command class/command, type help on gdb followed by the name of the command class/command
• We explored some commands like run, start (to begin execution), stepi (for single instruction stepping into a file), kill (kill a running program) and quit on gdb