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.
Hello,
I've seen and understood the previous threads and information about a new diagnostic for latest compile link tools for the C28X family, that will flag a shared variable between CLA and CPU as a mis-match between blocked and non-blocked access. An example thread is below:
My question is not so much about that warning, but that I am only getting it for one shared CLA/CPU variable, and not for others in my project. And I'm wondering why that is occurring. Example, I have two sets of files:
a.c and a_.cla, which both share variable cla_var_0. It is declared in a_.cla, but referenced in a.c, via extern.
I then have
b.c and b_.cla, which share cla_var_1. It is delcared in b_.cla, and referenced in b.c, via extern.
The variable cla_var_0 does not generate the blocked/non-blocked warning (#10462-D), but cla_var_1 does.
Why would almost an exact same circumstance generate the warning in one case, but not the other?
Any comments, assistance appreciated.
Robert
For the cla_var_0 case, where the diagnostic does not get issued, I'd appreciate if you would submit a test case. Is it organized as a CCS project? If so, please create a zip file by following the directions in the article Sharing projects, then attach that zip to your next post.
Thanks and regards,
-George
Hi George,
Thanks for the reply. As is typical of most of my interactions with E2E, it is code within a larger IP-sensitive CCS project, so I couldn't zip and post.
Robert
Are you willing to send it just to me, by private message? If so, hover your mouse over my name or avatar. A box will pop up. Click on Send a private message. In the message compose interface which comes up, use the paper clip icon to attach the zip file.
Thanks and regards,
-George
This issue is a concern, but not holding up progress. So I'd like to take a raincheck on further investigation, since a bit uneasy about sending the whole project externally. Thanks for the offer though. If you have any other ideas how to investigate, without requiring that (full project), please let me know. Likewise, if I'm able to recreate the same situation in a test project, I'll post back here (although I suspect the issue is likely a result of the size of the project, and the associated amount of shared CPU/CLA shared variables in it, via "extern").