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.

TMS320F280049: What happened to Cla1SoftIntRegs definition in C2000Ware 3.03 onwards

Part Number: TMS320F280049
Other Parts Discussed in Thread: C2000WARE

Hi

In moving to the latest C2000Ware we have discovered that in C2000Ware 3.03 onwards the register definitions for the CLA only software interrupt triggers have disappeared. Is there a reason for this; is there a problem with them?

In f28004x_globalvariabledefs.c Cla1SoftIntRegs has gone.

In f28004x_headers_nonbios.cmd   "Cla1SoftIntRegsFile   : > PIE_CTRL,      PAGE = 1, type=DSECT" is also missing.

Any thoughts?

Stewart

  • Hi Stewart,

    The header files are now generated using a script. This might have caused this issue . Have forwarded your query to an expert . You will get a response soon.

    Best Regards

    Siddharth

  • Hi Stewart,

    Cla1SoftIntRegs is actually a subset of Cla1OnlyRegs. Cla1OnlyRegs contains the list of all registers that are available on CLA starting at 0x0C00 and Cla1SoftIntRegs is set of those registers at offset 0xE0.

    The address 0x0C00 and 0x0CE0 are in the CLA address space and we could not map them in the f28004x_headers_nonbios.cmd file which contains addresses for the C28x memory space.

    In f28004x_headers_nonbios.cmd   "Cla1SoftIntRegsFile   : > PIE_CTRL,      PAGE = 1, type=DSECT" assigns the Cla1SoftIntRegs  at address 0x0CE0 because PIE_CTRL registers also start at address 0xCE0 (on C28x memory space). This technically works correctly, but might be misleading. Also we could not map the entire Cla1OnlyRegs struct.

    Regards,

    Veena

  • Steward,

    To access the CLA only registers from .cla file, you can use a pointer to that address.

    Eg:

    #define Cla1OnlyRegs ((volatile struct CLA_ONLY_REGS *)(uintptr_t)0x0C00U)

    Cla1OnlyRegs->SOFTINTEN.bit.TASK1 = 1;

    Regards,

    Veena

  • Thank you for the details Veena. I will use your pointer method.