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: How to resolve ccs warnings?

Part Number: TMS320F28335

The following warning appears in ccs10.1.0. How can I solve it?

1.“Description Resource Path Location Type
#10247-D creating output section ".cio" without a SECTIONS specification DSP2833x_mpu9250chuanjieya C/C++ Problem”

2.“Description Resource Path Location Type
This project was created using a version of compiler that is not currently installed - 6.2.0 [C2000]. Another version of the compiler will be used during build - 20.2.1.LTS. See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update. Visit <a href="liveaction:OpenAppCenter">CCS App Center</a> to get the latest compiler support. Or <a href="">software-dl.ti.com/.../a> and install the compiler, then register it with CCS through 'Preferences > CCS > Build > Compilers'. DSP2833x_mpu9250chuanjieya properties Problem”

  • 1.“Description Resource Path Location Type
    #10247-D creating output section ".cio" without a SECTIONS specification DSP2833x_mpu9250chuanjieya C/C++ Problem”

    The .cio section (buffer for stdio functions) for your program is not allocated to a memory range in the linker command file. So the linker placed it in a default location. This message is a warning and not really an erroor.

    For more information on sections, memory ranges, and linker command files, please see:

    https://dev.ti.com/tirex/explore/node?node=A__APJQ1q8Ox6tOF4TmB4THeg__ccs_devtools__FUz-xrs__LATEST

    There is also a Chinese version of the document: https://software-dl.ti.com/ccs/esd/documents/sdto_cgt_Linker-Command-File-Primer_cn.html

    2.“Description Resource Path Location Type
    This project was created using a version of compiler that is not currently installed - 6.2.0 [C2000]. Another version of the compiler will be used during build - 20.2.1.LTS. See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update. Visit <a href="liveaction:OpenAppCenter">CCS App Center</a> to get the latest compiler support. Or <a href="">software-dl.ti.com/.../a> and install the compiler, then register it with CCS through 'Preferences > CCS > Build > Compilers'. DSP2833x_mpu9250chuanjieya properties Problem”

    The project you are importing was created with an old version of the compiler that is not installed on your PC so CCS will use a version that is installed. Again, this message is a warning and not really an error. If you want to use the original old compiler version, see: 

    https://dev.ti.com/tirex/explore/node?node=A__AJRfIGmBSkp9naUDysxAFg__ccs_devtools__FUz-xrs__LATEST

    Thanks

    ki

  • HI Ki,

    Thank you very much for your answer!I have addressed the above two warning issues.

    However, solving this problem still does not solve the problem that the "sci" serial port print data is incomplete.

    I tried to change the main control from 28335 to 28035, but the problem was still not solved. I copied the complete code to another computer, but I could use the "sci" port to output data, which proves that there may be a problem in the configuration of ccs10.1.0 on my computer!

    So I want to uninstall ccs10.1.0 and replace it with ccs12.5. Do you think this might work?

    Can you provide TI's official "sci" usage code? Can you provide information about printf redirection?

    Also check out this link:CCS6中printf()的使用——TMS320F28335工程printf()的使用_ccs printf-CSDN博客

    As a dsp learner, I don't know where to put the nt fputc(int _c, register FILE *_fp) function.

    I really want your help. This problem is keeping me awake.

    God bless you

    Andy

  • However, solving this problem still does not solve the problem that the "sci" serial port print data is incomplete.

    This is a different question best handled by the device experts. You have an ongoing thread with them regarding this issue. It is best to continue discussion there.

  • Thank you very much for your patient reply