This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Problem in compilation in CCSv3.3

Other Parts Discussed in Thread: CCSTUDIO

Hi all

i am having problem in compilation of given example ..

As i compiled it with given project it gives warning 

[Linking...] "D:\CCStudio_v3.3\C2000\cgtools\bin\cl2000" -@"Debug.lkf"

 

<Linking>

>> D:\DOCUME~1\CHINTA~1\LOCALS~1\Temp\TI9323, line 24:   error:can't find input file 'C:/tidcs/c28/DSP2833x/v120/DSP2833x_headers/cmd'

>> 28335_RAM_lnk.cmd:   error: system error, can't open file 'DSP2833x_Headers_nonBIOS.cmd' for input: No such file or directory       

>> Compilation failure

Build Complete,

  3 Errors, 0 Warnings, 0 Remarks.

 

  • The error means that the project is looking for the linker command file DSP2833x_Headers_nonBIOS.cmd in the default install directory for the Peripheral Header Files/Examples, in this case, C:\tidcs\c28\DSP2833x\v120\DSP2833x_headers\cmd, but is not able to find it. Do you have the examples/peripheral header files installed in a different path? If so, you may need to modify your project options in CCS to point to the correct directory.

    Which example project are you trying to build?

  • hi Aarti,

    Thanks for reply i have successfully compiled that example of initiallization of GPIO.

    Now i m waiting for my board to come and by the time i m trying to make a code for my board..

    I have some doubts related to command file for the examples according to that command file if i use that command file for my board the program will execute in RAM so if i want to load my program on the flash so can I use different command file name "F28335.cmd" in place of "28335_RAM_lnk.cmd" or i need to change something else

    because i want to run my board without JTAG.

    regards,

    Chintan

     

  • Yes you would need to use the F28335.cmd if you want to program to Flash. The key thing to look for in the linker command file is where the initialized sections (such as .text, .cinit etc) are being placed (under SECTIONS directive). In the RAM versions, they are loaded to RAM memory while in the Flash version, they are loaded to FLASH.

  • go through this.

    http://focus.ti.com/lit/an/spra958h/spra958h.pdf

     

    before executing any flash related example check for CSM and Password sections. it will be better if you disable them during code development phase. else you will end  locking up your device and thus rendering its secured memory useless if you dont know the password.. (refer CSM  guide for detailed desciption.)

    the above link gives an URl from which example code can be downloaded. Better go through the code, cmd and asm files before executing it.

    ( http://www-s.ti.com/sc/techlit/spra958.zip.) the code given in this zip file uses CSM. Be careful.

     

  • Hi Pankaj,

    Thanks for reply,

    I want to ask one thing that if i am using the same code which is given in the examples from TI, than also i required to take care of this CSM. I will be using that sample code with little modification according to GPIO and and along with that i will be using that F28335.cmd file to use serial flash programmer. so my code can run without j-tag.

    So is there any requirement to take care of CSM because I have seen that .cmd,  it is like this

       CSM_RSVD    : origin = 0x33FF80, length = 0x000076     /* Part of FLASHA.  Program with all 0x0000 when CSM is in use. */

       BEGIN       : origin = 0x33FFF6, length = 0x000002     /* Part of FLASHA.  Used for "boot to Flash" bootloader mode. */

       CSM_PWL     : origin = 0x33FFF8, length = 0x000008     /* Part of FLASHA.  CSM password locations in FLASHA */

    What is the meaning of When CSM is in use.........,   if i m not changing anyithing in the command file than also i required to take care of CSM


     

  • Chintan,

    "CSM in use" means that there is a password programmed in the password locations (CSM_PWL) shown above because you want the device to be secure.

    During development you will most likely leave the password locations erased (all 0xFFFF) so the device can easily be unlocked (this is also called unsecure because you can unlock the device by simply reading the password locations).  In the header file examples TI supplies the password is not programmed.

    For more info on the CSM refer to the System Control and Interrupts guide for the particular device.

    Cheers

    Lori