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.

Two .cmd files

Other Parts Discussed in Thread: TMS320F28335

I'm developing on a TMS320F28335, utilizing two .cmd files that were purloined from example code:  DSP2833x_Headers_nonBIOS.cmd and F28335_nonBIOS_flash.cmd.  DSP2833x_Headers_nonBIOS.cmd seems to be defining the locations of registers while F28335_nonBIOS_flash.cmd defines RAM usage.  If memory serves, this one was added when I moved the code to flash. 

DSP2833x_Headers_nonBIOS.cmd is specified in the project Properties -> General -> Linker command file.  I have not found how F28335_nonBIOS_flash.cmd is invoked, but both are needed to build.  I don't fully understand why two .cmd files are needed. I further don't understand how the latter one is invoked.  Is it simply because it resides in the project directory?  Or have I just not discovered where it gets called out?

  • Sadly, I don't have any beers for you ;-)  but I do have answers to your questions!

    DSP2833x_Header_nonBios.cmd is used to define the locations of the peripherals in the memory map.  The source file GlobalVariableDefs.c declares variables for each of the peripherals and uses a pragma to create a section for each variable which gets linked onto memory using this linker command file.

    The F28335x_flash.cmd file is used to actually define the physical memories of the device and where the application will be linked.

    Any file that CCS recognizes the extension of that is in the project directory will automatically be pulled in to the project (which is probably how that one linker file is being pulled in).

    Regards,

    Trey