TMS320F28P650DK: XBAR_REGS

Liu tingwei

Part Number: TMS320F28P650DK
Other Parts Discussed in Thread: C2000WARE

We have used the latest version of C2000ware, and the register declaration of XbarRegs has also used the following format:

#pragma DATA_SECTION(XbarRegs,"XbarRegsFile");

volatile struct XBAR_REGS XbarRegs __attribute__((noblocked));

The following warning will still be issued：

#10462-D Symbol, "XbarRegs", referenced in "./Sources/06_DigitalCtrlAPI/DigitalCtrlAPI.obj", assumes that data is blocked but is accessing non-blocked data in "./Ti.Headers/f28p65x_globalvariabledefs.obj". Runtime failures may result.

Can you provide the corresponding solutions?

over 2 years ago

0 Ryan Ma over 2 years ago

TI__Mastermind 27736 points

Hi Liu,

These threads should help with debugging this warning. The best answer is to make sure the shared data variables are defined in the C28x code and not in the CLA code.

1. https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/894951/tms320f28379d-10462-d-warning-when-running-fcl_f2837x_tmdxiddk

2. https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/900270/ccs-tms320f28377d-complier-warning-10462

Best,

Ryan Ma

0 Liu tingwei over 2 years ago in reply to Ryan Ma

Prodigy 80 points

Hi Ryan：

We do not define shared data variables in the CLA code. Instead, the register function provided by TI(f28p65x_globalvariabledefs.c) is directly referenced in the interrupt function of C28x. As follows:

OcpFlags = XbarRegs.XBARFLG2.all & 0x03F;

And when we add this XbarRegs register to the routine provided by TI, the corresponding failure is also reported。

Could you please provide us with relevant routines to use this register, so that we can refer to the method of using this register。

0 Ryan Ma over 2 years ago in reply to Liu tingwei

TI__Mastermind 27736 points

Hi Liu,

Could you provide the .map file? I am wondering if the linker is placing this XbarREgs register in a blocked section.

Here is a good reference for noblocked vs blocked declarations.

Best,

Ryan Ma

0 Ryan Ma over 2 years ago

TI__Mastermind 27736 points

Liu tingwei said:
#10462-D Symbol, "XbarRegs", referenced in "./Sources/06_DigitalCtrlAPI/DigitalCtrlAPI.obj", assumes that data is blocked but is accessing non-blocked data in "./Ti.Headers/f28p65x_globalvariabledefs.obj". Runtime failures may result.

It seems that there are two files that use the XBAR_REGS struct and one file has it marked as blocked. While the other file has it marked as no blocked (f28p65x_globalvariabledefs). Can you try to declare in the /DigitalCtrlAPI the struct as a noblocked?

0 Ryan Ma over 2 years ago in reply to Ryan Ma

TI__Mastermind 27736 points

Hi Liu,

I have found the issue, all I had to do was add the __attribute__((noblocked)) to the f28p65x_xbar.h file and recompile.

Please let me know if this solves the issue.

Best regards,

Ryan Ma

0 Liu tingwei over 2 years ago in reply to Ryan Ma

Prodigy 80 points

After following the changes you provided, CCS reported another problem：

#1173-D unknown attribute "noblocked"

0 Ryan Ma over 2 years ago in reply to Liu tingwei

TI__Mastermind 27736 points

Hi Liu,

What version of CCS are you using?

0 Liu tingwei over 2 years ago in reply to Ryan Ma

Prodigy 80 points

Hi Ryan：

CCS 12.6.0

0 Ryan Ma over 2 years ago in reply to Liu tingwei

TI__Mastermind 27736 points

Apologize, but I am unable to reproduce this warning. Are you in the f28p65x_xbar.h file? Did you makes sure to clean project, then try rebuilding it?