# Generated by Code Composer Studio # Makefile for C:\Users\kvallabhaneni\Desktop\HDL2_VF9_cat-hallfailtest-release\HDL2-June2708.pjt # This makefile is intended to be compatible with any version of make. # # USAGE # Step 1: Set up proper environment variables, by running DosRun.bat # (Windows platform) or set them up by yourself. # Step 2: Change directory to the directory of this makefile, which is stored # in the macro MAKEFILE_DIR # Step 3: In the makefile directory, you can perform one of these operations: # To build the configuration , type make # To clean the configuration , type make clean # To rebuild the configuration , type make rebuild # If is not specified, the operations apply to the active # configuration, which is stored in the macro ACTIVE_CONFIG. # For CCS gmake users: In the makefile directory, you can perform one of these operations: # To build the configuration , type gmake projectName.mak # To clean the configuration , type gmake clean # To rebuild the configuration , type gmake rebuild # If is not specified, the operations apply to the active # configuration, which is stored in the macro ACTIVE_CONFIG. # # DETAILS # Step 1: # In order for this makefile to work, you must have the environment variables # set properly. Specifically, the paths to build programs and the system-wide # header files and library files must be set. # In Windows, a batch file "DosRun.bat", located at the root directory of # the Code Composer Studio installation, is provided to set up these variables. # In UNIX, you can set up these environment variables yourself. The "PATH" # variable must include the paths to the build programs, and the "C_DIR" and # "A_DIR" variables must include the paths to the system-wide header files and # library files. # # Step 2: # System files referenced by this project are specified in full path names, # while other files in this project are specified in path names relative to the # directory of this makefile. These directory names are stored in DIR_x macros. # You can modify them to reflect the locations of the files on this system. # It is important that the command to make this makefile is issued from the # directory of this makefile, which is stored in the macro MAKEFILE_DIR. # # Step 3: # There are three operations that can be performed on a build configuration: # make, clean, and rebuild. A rebuild forces all files in the configuration to # be rebuilt. # To build the configuration , type make # To clean the configuration , type make clean # To rebuild the configuration , type make rebuild # If is not specified, the operations apply to the active # configuration. The active configuration can be any valid build configuration # (including "all") and is specified in the macro ACTIVE_CONFIG. # To build the active configuration, type make # To clean the active configuration, type make clean # To rebuild the active configuration, type make rebuild # # For CCS gmake users: # There are three operations that can be performed on a build configuration: # make, clean, and rebuild. A rebuild forces all files in the configuration to # be rebuilt. # To build the configuration , type gmake projectName.mak # To clean the configuration , type gmake clean # To rebuild the configuration , type gmake rebuild # If is not specified, the operations apply to the active # configuration. The active configuration can be any valid build configuration # (including "all") and is specified in the macro ACTIVE_CONFIG. # To build the active configuration, type gmake # To clean the active configuration, type gmake clean # To rebuild the active configuration, type gmake rebuild # The MKFLAGS macro takes the place of the MFLAGS or MAKEFLAGS macro. If it # gives you any trouble, just delete the macro. It is used when recursively # calling make (i.e. when rebuilding) MKFLAGS= $(MFLAGS)$(MAKEFLAGS) MAKEFILE_DIR= C:/Users/kvallabhaneni/Desktop/HDL2_VF9_cat-hallfailtest-release # The active configuration can be one of these valid build configurations: # all, Debug ACTIVE_CONFIG= Debug # These DIR_x macros store the directories of the files used in this project. # There must be no trailing spaces after these macros. DIR_1= C:/CCStudio_v3.3PLA/C6000/cgtools/bin DIR_2= Debug SOURCE=ClearRegs.asm SOURCE=CRC-iniFordt.sa SOURCE=EtherRecieve.asm SOURCE=EtherRESET.asm SOURCE=Ethersetuphdl.asm SOURCE=LDLASER8xR2.sa SOURCE=MainDualA-DR3.asm SOURCE=MotorR3.sa SOURCE=Read120Mwtimestamp.sa SOURCE=SerialIn.sa SOURCE=SETADCr2.sa SOURCE=StoreEprom11-02.asm SOURCE=SyncDMA.sa SOURCE=Time01.sa SOURCE=EpromBoot11-02.cmd active_config: $(ACTIVE_CONFIG) norecurse: $(ACTIVE_CONFIG)_norecurse clean: $(ACTIVE_CONFIG)clean clean_norecurse: $(ACTIVE_CONFIG)clean_norecurse rebuild: $(ACTIVE_CONFIG)rebuild force_rebuild: all: Debug allclean: Debugclean allrebuild: Debugrebuild Debugclean: Debugclean_norecurse Debugclean_norecurse: -@rm -f ClearRegs.obj -@rm -f CRC-iniFordt.obj -@rm -f EtherRecieve.obj -@rm -f EtherRESET.obj -@rm -f Ethersetuphdl.obj -@rm -f LDLASER8xR2.obj -@rm -f MainDualA-DR3.obj -@rm -f MotorR3.obj -@rm -f Read120Mwtimestamp.obj -@rm -f SerialIn.obj -@rm -f SETADCr2.obj -@rm -f StoreEprom11-02.obj -@rm -f SyncDMA.obj -@rm -f Time01.obj -@rm -f $(DIR_2)/HDL64.out Debugrebuild: $(MAKE) $(MFLAGS) -f HDL2-June2708.mak Debug FRC=force_rebuild Debug: Debug_norecurse Debug_norecurse: $(DIR_2)/HDL64.out ClearRegs.obj \ CRC-iniFordt.obj \ EtherRecieve.obj \ EtherRESET.obj \ Ethersetuphdl.obj \ LDLASER8xR2.obj \ MainDualA-DR3.obj \ MotorR3.obj \ Read120Mwtimestamp.obj \ SerialIn.obj \ SETADCr2.obj \ StoreEprom11-02.obj \ SyncDMA.obj \ Time01.obj: $(FRC) ClearRegs.asm CRC-iniFordt.sa EtherRecieve.asm EtherRESET.asm Ethersetuphdl.asm LDLASER8xR2.sa MainDualA-DR3.asm MotorR3.sa Read120Mwtimestamp.sa SerialIn.sa SETADCr2.sa StoreEprom11-02.asm SyncDMA.sa Time01.sa Macros.h Tms6416.h Caltable.h -@echo -k -pm -al -op2 -o2 -mt -mh -mi -ms0 -mv6400 --mem_model:data=near> HDL2-June2708.Debug.lkf -@echo "ClearRegs.asm">> HDL2-June2708.Debug.lkf -@echo "CRC-iniFordt.sa">> HDL2-June2708.Debug.lkf -@echo "EtherRecieve.asm">> HDL2-June2708.Debug.lkf -@echo "EtherRESET.asm">> HDL2-June2708.Debug.lkf -@echo "Ethersetuphdl.asm">> HDL2-June2708.Debug.lkf -@echo "LDLASER8xR2.sa">> HDL2-June2708.Debug.lkf -@echo "MainDualA-DR3.asm">> HDL2-June2708.Debug.lkf -@echo "MotorR3.sa">> HDL2-June2708.Debug.lkf -@echo "Read120Mwtimestamp.sa">> HDL2-June2708.Debug.lkf -@echo "SerialIn.sa">> HDL2-June2708.Debug.lkf -@echo "SETADCr2.sa">> HDL2-June2708.Debug.lkf -@echo "StoreEprom11-02.asm">> HDL2-June2708.Debug.lkf -@echo "SyncDMA.sa">> HDL2-June2708.Debug.lkf -@echo "Time01.sa">> HDL2-June2708.Debug.lkf "$(DIR_1)/cl6x" -k -pm -al -op2 -o2 -mt -mh -mi -ms0 -mv6400 --mem_model:data=near -@"HDL2-June2708.Debug.lkf" -@rm -f HDL2-June2708.Debug.lkf $(DIR_2)/HDL64.out: ClearRegs.obj CRC-iniFordt.obj EtherRecieve.obj EtherRESET.obj Ethersetuphdl.obj LDLASER8xR2.obj MainDualA-DR3.obj MotorR3.obj Read120Mwtimestamp.obj SerialIn.obj SETADCr2.obj StoreEprom11-02.obj SyncDMA.obj Time01.obj EpromBoot11-02.cmd -@echo -z -q -h -m"./Debug/HDL64.map" -o"./Debug/HDL64.out"> HDL2-June2708.Debug.lkf -@echo "ClearRegs.obj">> HDL2-June2708.Debug.lkf -@echo "CRC-iniFordt.obj">> HDL2-June2708.Debug.lkf -@echo "EtherRecieve.obj">> HDL2-June2708.Debug.lkf -@echo "EtherRESET.obj">> HDL2-June2708.Debug.lkf -@echo "Ethersetuphdl.obj">> HDL2-June2708.Debug.lkf -@echo "LDLASER8xR2.obj">> HDL2-June2708.Debug.lkf -@echo "MainDualA-DR3.obj">> HDL2-June2708.Debug.lkf -@echo "MotorR3.obj">> HDL2-June2708.Debug.lkf -@echo "Read120Mwtimestamp.obj">> HDL2-June2708.Debug.lkf -@echo "SerialIn.obj">> HDL2-June2708.Debug.lkf -@echo "SETADCr2.obj">> HDL2-June2708.Debug.lkf -@echo "StoreEprom11-02.obj">> HDL2-June2708.Debug.lkf -@echo "SyncDMA.obj">> HDL2-June2708.Debug.lkf -@echo "Time01.obj">> HDL2-June2708.Debug.lkf -@echo "EpromBoot11-02.cmd">> HDL2-June2708.Debug.lkf "$(DIR_1)/cl6x" -@"HDL2-June2708.Debug.lkf" -@rm -f HDL2-June2708.Debug.lkf