Compiler/TMS320F280049C: Some strange phenomenon when define variables in .cla file

Rayna Wang

Expert 3680 points

Part Number: TMS320F280049C
Other Parts Discussed in Thread: C2000WARE

Tool/software: TI C/C++ Compiler

Hi Expert,

I add the below function in the Cla1Task1 in .cla file of "cla_ex3_background_nesting_task_cla" example.

-------------------------------------------------------------------------------------

Phase_VB_SENSE++;

if((Phase_VB_SENSE >= 222222)&& (Phase_VB_SENSE <= 233333))
{
__mdebugstop();
Phase_VB_SENSE = 0;
}

---------------------------------------------------------------------------------------------------------------

There're some confusions when I define variables.

if just define "int32_t Phase_VB_SENSE;" in .cla file, according to the value in expression window, the length of variable is 16bit not 32 bit, the LED is light normally.
if define "extern int32_t Phase_VB_SENSE;" in .cla file & "int32_t Phase_VB_SENSE=0;" in main.c file, the expression window shows the variable is "long" and the value is always "0", the LED is light normally.

The above phenomenon is really weird, and I'm not sure about the reason.

Could you please help to debug this issue or give me some notes about how to configure to get the reasonable variable value?

Thanks!

Best Regards

Rayna

cla_ex3_background_nesting_task_cla

over 5 years ago

0 Lori Heustess over 5 years ago

TI__Guru* 93600 points

Rayna,

Can you send me the following information:

Compiler version
CCS version
C2000Ware version
Files you modified (.c and .cla) - you can send these to me in email.

I will be out of office on Friday. I will get back to you on Monday before end of day in the US.

Regards,

Lori

0 Quentin Fu over 5 years ago in reply to Lori Heustess

Intellectual 800 points

Hi Lori,

Rayna already explained the issue, but let me try to rephrase:

The code below is in *.cla file:

//////////////////////////////////////////////////////////////////

int32_t Phase_VB_SENSE;

__attribute__((interrupt)) void Cla1Task4 ( void )
{

Phase_VB_SENSE = ECAP_getTimeBaseCounter(ECAP4_BASE);

if ((Phase_VB_SENSE >= 222222U) && (Phase_VB_SENSE <= 233333U))
{
__mdebugstop();
}

}

///////////////////////////////////////////////////////////////

so it can be seen Phase_VB_SENSE is defined as "32-bit integer". However, it appears to be 16 bit interger in CCS "Expression Window" when debugging. My impression is the value of Phase_VB_SENSE is correct -- it just shows up as "16 bit" in CCS "Expression Window" for some strange reason.

Please see the screen capture below:

when it stops at the breakpoint((Phase_VB_SENSE >= 222222U) && (Phase_VB_SENSE <= 233333U), Phase_VB_SENSE seems to be 26274 (16 bit) in CCS window.

CCS Version: 9.3.0.00012 is used.

\C2000Ware_3_01_00_00 is used.

0 Praveen Kumar Ravichandran over 5 years ago in reply to Quentin Fu

TI__Expert 4620 points

Hi,

The second image did not get posted properly. Can you please re-attach?

Regards,

Praveen

0 Quentin Fu over 5 years ago in reply to Praveen Kumar Ravichandran

Intellectual 800 points

Hi Praveen,

There is only one image -- I tried to upload twice. If you see a screen capture, then that is it. Thanks.

0 Quentin Fu over 5 years ago in reply to Quentin Fu

Intellectual 800 points

For the attached screen capture, it is defined as " uint32_t Phase_VB_SENSE; " in *.cla file; later on I changed it to " int32_t Phase_VB_SENSE; "

The keypoint is: why does Phase_VB_SENSE show up as 16-bit integer in CCS Expression Window while it is defined as 32-bit integer?

0 Praveen Kumar Ravichandran over 5 years ago in reply to Quentin Fu

TI__Expert 4620 points

Hi,

The variable will be interpreted as 32 bit by the CLA compiler when declared as uint32_t. This seems to be a CLA debugger only artefact. Let me check with the ccs expert on this one and get back.

In the meanwhile, If you have other problems in sharing variables across C28x and CLA, please refer to the below resources:

https://software-dl.ti.com/C2000/docs/cla_software_dev_guide/faq.html#how-is-data-shared-between-the-cla-and-c28x

CLA compiler section of the compiler guide:

http://downloads.ti.com/docs/esd/SPRU514/

Regards,
Praveen

0 Quentin Fu over 5 years ago in reply to Praveen Kumar Ravichandran

Intellectual 800 points

Thanks, Praveen. I am looking forward to your updates.

0 Ki over 5 years ago in reply to Quentin Fu

TI__Guru**** 476741 points

Hello Xiaquan,

Can you provide a small test case? Basically a small project with source files so I can rebuild, and also the executable used?

Please start a private E2E message with me if you wish to share privately

Thank you,

0 Quentin Fu over 5 years ago in reply to Ki

Intellectual 800 points

Hi Ki,

I can not share my design code, but I provided code snippets from which a testcase can be constructed and reproduced the issue.

Rayna described how she modified "cla_ex3_background_nesting_task_cla" example project to reproduce the issue in her first post. This can also server as a testcase.

Thanks,

Xiaoquan

0 Ki over 5 years ago in reply to Quentin Fu

TI__Guru**** 476741 points

Understood. I will try to reproduce using your code example as a baseline

0 Quentin Fu over 5 years ago in reply to Ki

Intellectual 800 points

Thanks, Ki. Looking forward to your updates.

0 Ki over 5 years ago in reply to Quentin Fu

TI__Guru**** 476741 points

I am able to reproduce the issue with CCS 10.1.1. It is being interpreted as an int instead of a long. I will file a bug for this

Thanks

0 Ki over 5 years ago in reply to Ki

TI__Guru**** 476741 points

Ki said:
I am able to reproduce the issue with CCS 10.1.1. It is being interpreted as an int instead of a long. I will file a bug for this

Tracking ID: https://sir.ext.ti.com/jira/browse/EXT_EP-10079

Thanks

0 Ki over 5 years ago in reply to Ki

TI__Guru**** 476741 points

Ki said:
. It is being interpreted as an int instead of a long. I will file a bug for this

Clarification - the Expressions view is interpreting int as 16-bit while a long is correctly interpreted as 32-bits. On CLA, an int is 32-bits

0 Quentin Fu over 5 years ago in reply to Ki

Intellectual 800 points

Thanks, Ki. So although it is defined as int32_t in .cla, but incorrectly interpreted as 16 bit int in Expressions window. Now I need to get/watch this signal's data in Expression window in order to diagnose my design. Is there any workaround?