Other Parts Discussed in Thread: C2000WARE
Tool/software:
Hello,
I have a CLA task that is triggered by the C28x core software.
The code of the task is pretty simple:
__interrupt void step(void)
{
__mdebugstop();
GPIO_togglePin(40U);
G_U.V1 = ADC_readResult(ADCBRESULT_BASE, ADC_SOC_NUMBER0);
G_U.V2 = ADC_readResult(ADCCRESULT_BASE, ADC_SOC_NUMBER0);
G_U.Vex = ADC_readResult(ADCDRESULT_BASE, ADC_SOC_NUMBER0);
G_U.i = exec_count;
if (exec_count == 36)
{
exec_count = 0;
}
else
{
exec_count++;
}
}
The manipulated variable are defined like that in C28x core code:
#pragma DATA_SECTION(G_U,"Cla1DataRam") G_ExternalInputs G_U; #pragma DATA_SECTION(exec_count,"Cla1ToCpuMsgRAM") int16_t exec_count;
The structure type definition is the following:
typedef struct {
uint32_T V1; /* '<Root>/V1' */
uint32_T V2; /* '<Root>/V2' */
uint32_T Vex; /* '<Root>/Vex' */
int32_T i; /* '<Root>/i' */
uint32_T PinProg; /* '<Root>/PinProg' */
} G_ExternalInputs;
When I run the code, the variable are updated properly, except for the V1 element in the G_U structure which stays at 0.
I ran the code with the debugger to try to understand and the corresponding assembly is the following:
I must admit there is one odd thing I don't understand in that dissassembly is the line which gets replaced by .word 0x7BC0.
But anyways, when I ran it step by step, MR0 does contain the correct value after the MMOVZ16 MR0,@xb20
But then it goes to 0 after the first NOP following the MMOV32 @0x9808, MR0 and thus the 0 is stored in the structure item.
This behavior does not happen for the other variables of the structure, there I see the MR0 register changing accordingly to the execution of the MLSR/MMOV along while the NOP executes.
Not sure what is going on there, any ideas ?
Clément
