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.

The project that import from controlSUITE can not burn-in TMS320F28035

Other Parts Discussed in Thread: CONTROLSUITE, TMS320F28035

I import the example project(ADC SOC(C28x)) into CCSv6.1.0 from controlSUITE, and the project can build successfully.

But when I want to burn-in TMS320F28035, the project can not build. I have added DSP2803x_Memcopy.c file to the project, defined extern variables above main() function and replaced 28035_RAM_lnk.cmd with  F28035.cmd.

I also want to consult why DSP2803x_Memcopy.c file is not found in C:\ti\controlSUITE\device_support\f2803x\v130\DSP2803x_common\source. 

so I used the DSP2803x_Memcopy.c file in v125. Is it a problem that cause the compilation failure?

Could you please give me some advice about that?

Thanks a lot.

  • I also want to consult why DSP2803x_Memcopy.c file is not found in \ti\controlSUITE\device_support\f2803x\v130\DSP2803x_common\source .
    It is in \ti\controlSUITE\device_support\f2803x\v125\DSP2803x_common\source. The imported project's other source files like DSP2803x_Adc.c, DSP2803x_PieCtrl.c, and etc. are in v130. Is it a problem that cause the compilation failure?
  • Hi,

    Hong Wu said:
    so I used the DSP2803x_Memcopy.c file in v125. Is it a problem that cause the compilation failure?

    That shouldn't be a problem!

    Hong Wu said:
    Could you please give me some advice about that?

    You seem to be missing some more include paths with required header files. Check example project include paths and compare.

    Regards,

    Gautam

  • Hello,

    The DSP2803x_Memcopy.c was removed because it is no longer needed. The C28 compiler has a built-in intrinsic function called "memcpy" that performs the same functionality. Within F2803x v130, look at the "flash_f28035" example which utilizes this intrinsic to copy RAM funcs.

    Best Regards,
    Chris
  • Thank you very much!