Part Number: TCI6638K2K
We are using our Custom HW Design based on K2KEVM, using TCI6638K2K Rev 2.0 with MCSDK 220.127.116.11
We are trying different test senarios and test cases and actually we mainly see 2 fatal problems under heavy traffic:
We can't find the root cause of both problems, any help will be appreciated...
Thanks & Regards..
These kinds of problems can be particularly difficult to solve. Since QMSS is a central resource to the system, finding cores at a queue push does not necessarily mean QMSS is the problem. In fact, QMSS push/pops do not block, so if a core is hung on a read/write access to a valid QMSS register, then something catastrophic has likely happened.
Are you able to determine what happens first, the AIF2 errors or DSP hangs? From your description, it sounds like AIF2 memory usage may be the majority of the problem. Since AIF2's timing cannot be delayed without causing serious problems (like breaking the link, descriptor starvation, etc), it is recommended to use the lowest latency resources for it. You should not be using external linking RAM for AIF2 descriptors. K2K has double the linking ram vs. most other Keystone devices, so this should not be a problem. You can also give the AIF2 pktDMA priority over all other pktDMAs in the system (see section 18.104.22.168 of the Navigator user guide), but this is often not necessary.
If you can make the problem disappear by changing the resources used by AIF2, then delays and/or starvation was likely the issue.
In reply to db_woodall:
I think we are facing two different problems; The SoC Hang problem and the AIF starvation problem. We are not sure if they are correlated or not.
After we moved QMSS external link RAM from DDR3A to DDR3B, the SoC Hang problem disappeared but we faced the AIF starvation problem.
AIF starvation occurs rarely (@20MHz, 8 AxC, 2 link, 1 pe_db_starvation counter increased per 8-10 hours) AIF2 descriptors are allocated on internal link RAM and AIF PktDMA has the highest priority in SoC. Additionally we are sure that the SoC Hang occurs before AIF starvation.
The main problem here is the SoC Hang problem since we are not sure about the root cause of problem. Adding unnecessary delays (_mfence() etc.) in qmss queue pushes or moving external link ram from DDR3A to DDR3B are somehow helped us to overcome(??) the SoC Hang problem in our application. We are not sure if we postponed or solved the problem permanently.
Is there any possibility that some sort of bus congestion could be the reason for this? For example I have read a statement regarding this in “KeyStone Connectivity and Priorities” document.
In addition to this in the “KeyStone II Architecture Antenna Interface 2 (AIF2)” document I have read another similar statement below:
And actualy this is the reason why we posted these two problems under the same topic.
We captured the external linkram WR transactions via ProTrace for DDR3A&B. The average duration between access-to-access is almost the same for both.
Thanks in advance..
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.