TMS320F280039C: CIO Error message when the CCS is updated.

Hello,

SY Yoon said:

Customer has been using the code in CCS version 12.1.0. 

Customer built the same code in CCS version 12.4.0. It compiled perfectly and did not show any errors, but when he tried to run it displayed this error.

To clarify, the error appears in both CCS versions? This issue is typically thrown for console I/O functions like printf, and any problems regarding this issue should have been fixed in version 12 of CCS.

Please review the following posts and let me know whether or not they apply to the customer's project:

• https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/738482/ccs-invalid-cio-command-8-in-the-cio-buffer-at-address-0x20002000-was-not-recognized-please-check-the-device-and-program-memory-maps
• https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/76336/invalid-cio-command-8-in-the-cio-buffer-at-address-0x20002000-was-not-recognized-please-check-the-device-and-program-memory-maps
• https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/168606/nvalid-cio-command-38-in-the-cio-buffer-at-address-0x800ded88-was-not-recognized

Best regards,

Omer Amir

Hello,

Omer Amir said:

To clarify, the error appears in both CCS versions? This issue is typically thrown for console I/O functions like printf, and any problems regarding this issue should have been fixed in version 12 of CCS.

The error appears only in the CCS v12.4.

And when I disabled the option 'Enable CIO function use' in debug properties, error disappears but C2000 doesn't work normally. 

Hello,

SY Yoon said:

And when I disabled the option 'Enable CIO function use' in debug properties, error disappears but C2000 doesn't work normally. 

Can you clarify what you mean by this? How does CCS not work normally? Does the device not run as expected?

Best regards,

Omer Amir

Hello,

I am sorry that I am not good at English.

"C2000 doesn't work normally" means device not run as expected.

Hello,

Unfortunately, "doesn't work normally" is too vague for me to replicate on my side. What is not running as expected? Is the device turning on? Is code executing? Is something not correct in the CCS debug session? You need to provide more explicit detail on what is not working as expected, otherwise I'm unable to offer any help.

Best regards,

Omer Amir

Hello, 

We've identified where CIO errors are occurring.

Customer uses the time() function to generate random number.

When the time() function is called, the HOSTtime64() function is executed

The CIO error occurs at this point.

And when execution stops, it stops at the line as below.

Strangely, when I run the code step by step, no error occurs.

Also, In SDK example projects such as gpio_ex2_toggle, no error occurs when calling the time() function as shown below.

    for(;;)
    {
        srand(time(NULL));
        random_number = rand() % 16;

        GPIO_togglePin(myGPIOOutput0);
        DEVICE_DELAY_US(1000000);
    }

SY Yoon said:

Customer has been using the code in CCS version 12.1.0. 

Customer built the same code in CCS version 12.4.0. It compiled perfectly and did not show any errors, but when he tried to run it displayed this error.

Is the SAME version of the compiler being used in BOTH CCS 12.1.0 AND CCS 12.4.0?

Thanks

ki

Hi, Ki

Yes, Both versions use the same compiler v22.6.0 LTS version.

I used the CCSv12.4 first.

I compared map files of each CCS version. These are the same.

I have attached output files compiled by version except code.

CCS_v12.4.zip  CCS_v12.1.zip

Could you compare the two versions?

Thank you, I will investigate.

Is address 0xA000 valid writable memory?

Hello Ki,

I can confirm that 0xA000 is a valid writable memory (it is the location of a local shared RAM block).

Best regards,

Omer Amir

Thank you for confirming.

I will try out both executables when I have access to a F28003x target tomorrow.

Thank you for your patience.

ki

Note that the root cause has been found and a fix is being investigate.

A workaround has been found. Please see the tracking link for more details.