• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 1782 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28335 Experimenter Kit - Flashing LED Build Problem

Dean Koucoulas
Prodigy 40 points
Other Parts Discussed in Thread: CONTROLSUITE, TMS320F28335

Hi all,


I have recently downloaded CCS Version 6 as well as ControlSuite, and am trying to set up the introductory Flashing LEDs project on the F28335 Experimenter Kit. I don't yet have access to the Experimenter Kit to try out the code, but I'm just trying to see if the files compile properly.

This is probably a really dumb question, but how much of me not having the actual board connected would this affect building the project? The reason I ask is because the only way I avoid Build Project errors is to select as my Target Device : Generic C28xx Device. If I specify anything more specific for the target like the Experimenter's Kit - Delfino 28335 or TMS320F28335, I get about 42 errors as seen below:


**** Build of configuration F2833x_RAM for project FlashingLeds-F28335 ****

"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all
'Building target: FlashingLeds.out'
'Invoking: C2000 Linker'
"C:/ti/ccsv6/tools/compiler/ti-cgt-c2000_6.4.4/bin/cl2000" -v28 -ml -mt --float_support=fpu32 -g --define="_DEBUG" --define="LARGE_MODEL" --diag_warning=225 -z -m"FlashingLeds.map" --stack_size=0x400 --warn_sections -i"C:/ti/ccsv6/tools/compiler/ti-cgt-c2000_6.4.4/lib" -i"C:/ti/ccsv6/tools/compiler/ti-cgt-c2000_6.4.4/include" -i"C:/ti/controlSUITE/development_kits/TemplateProjects/FlashingLeds-F28335_v1.0" --reread_libs --xml_link_info="FlashingLeds_linkInfo.xml" --no_sym_merge --rom_model -o "FlashingLeds.out" "C:/ti/controlSUITE/device_support/f2833x/v132/DSP2833x_headers/cmd/DSP2833x_Headers_nonBIOS.cmd" "./DSP2833x_CodeStartBranch.obj" "./DSP2833x_GlobalVariableDefs.obj" "./FlashingLeds-DevInit_F2833x.obj" "./FlashingLeds-Main.obj" "./SciCommsGui.obj" "../28335_RAM_lnk.cmd" "../F28335_RAM_FlashingLeds.CMD"  -l"libc.a"
<Linking>
"../F28335_RAM_FlashingLeds.CMD", line 89: error: BEGIN memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 89: error: BEGIN memory range overlaps
   existing memory range BEGIN
"../F28335_RAM_FlashingLeds.CMD", line 91: error: RAMM0 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 91: error: RAMM0 memory range overlaps
   existing memory range RAMM0
"../F28335_RAM_FlashingLeds.CMD", line 93: error: RAML0 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 93: error: RAML0 memory range overlaps
   existing memory range RAML0
"../F28335_RAM_FlashingLeds.CMD", line 94: error: RAML1 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 94: error: RAML1 memory range overlaps
   existing memory range RAML1
"../F28335_RAM_FlashingLeds.CMD", line 94: error: RAML1 memory range overlaps
   existing memory range RAML2
"../F28335_RAM_FlashingLeds.CMD", line 95: error: RAML2 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 95: error: RAML2 memory range overlaps
   existing memory range RAML3
"../F28335_RAM_FlashingLeds.CMD", line 96: error: RAML3 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 97: error: ZONE7A memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 97: error: ZONE7A memory range overlaps
   existing memory range ZONE7A
"../F28335_RAM_FlashingLeds.CMD", line 98: error: CSM_RSVD memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 98: error: CSM_RSVD memory range
   overlaps existing memory range CSM_RSVD
"../F28335_RAM_FlashingLeds.CMD", line 99: error: CSM_PWL memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 99: error: CSM_PWL memory range overlaps
   existing memory range CSM_PWL
"../F28335_RAM_FlashingLeds.CMD", line 100: error: ADC_CAL memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 100: error: ADC_CAL memory range
   overlaps existing memory range ADC_CAL
"../F28335_RAM_FlashingLeds.CMD", line 101: error: RESET memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 101: error: RESET memory range overlaps
   existing memory range RESET
"../F28335_RAM_FlashingLeds.CMD", line 102: error: IQTABLES memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 102: error: IQTABLES memory range
   overlaps existing memory range IQTABLES
"../F28335_RAM_FlashingLeds.CMD", line 103: error: IQTABLES2 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 103: error: IQTABLES2 memory range
   overlaps existing memory range IQTABLES2
"../F28335_RAM_FlashingLeds.CMD", line 104: error: FPUTABLES memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 104: error: FPUTABLES memory range
   overlaps existing memory range FPUTABLES
"../F28335_RAM_FlashingLeds.CMD", line 105: error: BOOTROM memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 105: error: BOOTROM memory range
   overlaps existing memory range BOOTROM
"../F28335_RAM_FlashingLeds.CMD", line 109: error: RAMM1 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 109: error: RAMM1 memory range overlaps
   existing memory range RAMM1
"../F28335_RAM_FlashingLeds.CMD", line 110: error: RAML4 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 110: error: RAML4 memory range overlaps
   existing memory range RAML4
"../F28335_RAM_FlashingLeds.CMD", line 111: error: RAML5 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 111: error: RAML5 memory range overlaps
   existing memory range RAML5
"../F28335_RAM_FlashingLeds.CMD", line 112: error: RAML6 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 112: error: RAML6 memory range overlaps
   existing memory range RAML6
"../F28335_RAM_FlashingLeds.CMD", line 113: error: RAML7 memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 113: error: RAML7 memory range overlaps
   existing memory range RAML7
"../F28335_RAM_FlashingLeds.CMD", line 114: error: ZONE7B memory range has
   already been specified
"../F28335_RAM_FlashingLeds.CMD", line 114: error: ZONE7B memory range overlaps
   existing memory range ZONE7B
error: errors encountered during linking; "FlashingLeds.out" not built

>> Compilation failure
gmake: *** [FlashingLeds.out] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

Again, this all makes sense if connection to the board was required for Building the project, but I have not run into such an issue when using some other platforms.

Likely not relevant since there is no target connection, but I get same above results when my Target Configuration is specified as either the Experimenter's Kit, or the actual TMS320F28335 device.


I'd appreciate any insight into this. Thanks

 

 

  • 0
    TI__Mastermind 30255 points

    Dean,

    No connection to the board is required for building the project. The error you are seeing is because the project is including two linker command files so that's why CCS is saying the memory has already been specified.

    The project itself is included with a linker command file (circled below):

    When you go under the project properties->General and change the variant from generic to something else, another linker command file is linked to the project. This can be seen below:

    In order to fix the error, use the drop down menu from the window (above) to deselect that linker command file and select "none" so that only 1 linker command file is included in your project.

    Best Regards,

    Chris

  • 0 in reply to Christopher Chiarella
    Prodigy 40 points
    Hi Chris,

    Thank you very much for your input. Deselecting the linker command to <none> did the trick, and the LED is flashing as it should!

    Thanks again.