• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 576 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Inconsistency between the original CCS 3.3 and the CCS3.3 with the new SP12 and CGT

Renaissance
Intellectual 925 points
Other Parts Discussed in Thread: CCSTUDIO

Recently, I update my CCS3.3 with the SP12 and CGT (6.1.5) for my C6455 development. However, I just found out that using this update CCS is generating different .out file, which will output incorrect results. 

Previously, I used the CCS3.3 without these update, and the running results were the same as I expected. However, when I use the updated CCS3.3, the running results were with big error. So I thought it is maybe the different setting of the building option, especially for the compiler. So, I distable all the optimization and re-compile my code. I run the program and there is an error displayed in the stdout window as following:

The CIO command cmd:(0) in the CIO buffer at address (0x9e8d80) was not recognized. Please check the device and program memory maps.

Then, I only got a portion of all the outputs. However, based on these incomplete outputs, I can see these results are correct. This really makes me feel that the previous inconsistent results is due to the setting for the build option.

So, Can any one give me some hints: (1)what is the reason for above error in the stdout window (2)what should I do to make this update CCS generate the same results as I got using the original CCS (without these updates)

Here are some information about my project

- My project is NOT a DSP/BIOS one

- Under the Libararies branch in the File View window of my project, there is no other libs inside. In the .cmd file of my project, there is following script

-l csl_c6455.lib (I have edited the "-l rts64plus.lib" line as in "-l C:\CCStudio_v3.3\C6000\cgt_6.1.5\lib\rts64plus.lib", and then rebuild the project. I am using the correct path for my installation of the CGT files. )
-l rts64plus.lib

Thank you so much,

I have posted this message in the TMS320C6000™ High Performance DSPs forum, here is the previous thread

http://e2e.ti.com/forums/p/9792/38298.aspx#38298

Renaissance

  • 0
    TI__Guru**** 463451 points

    Hi,

    Could you try switching back to the CGT version you were using prior to the update? That way we can see if it the problem was introduced from the CCS SR or the CGT.

    Information on how you can point CCS to your older CGT can be found in: http://tiexpressdsp.com/index.php/Compiler_Installation_and_Selection#CCStudio_3.x

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 925 points

    In fact, when I use the CCS3.3 without any update ( CGT and SR12), also, when I disable the optimization option in build dialog, the generated program will have the same error in the std output window.  However, when I enable the optimization option, the generate program does not have the error when I run it.

    Now, let me clarify the output. When I run the program built by CCS3.3 without any update and with optimization option, the running result (output) is the same as we expected. When I use the CCS with new update (CGT and SR12) and with optimization. , the running result (output) is wrong. This is how I called it “incorrect results”and this is what I call inconsistency between the original CCS 3.3 and the CCS3.3 with the new SP12 and CGT .

    Thank you, Ki

    Renaissance

  • 0 in reply to Renaissance
    TI__Guru**** 463451 points

    regarding the error: The CIO command cmd:(0) in the CIO buffer at address (0x9e8d80) was not recognized. Please check the device and program memory maps.

    This can occur when the CIO buffer is allocated in memory that is not valid. Is the address 0x9e8d80 a valid address? Which optimization setting are you using? Could you explain exactly what are the "incorrect results" are between the pre and post updates?