Part Number: TCI6638K2K
Tool/software: Code Composer Studio
We are using UIA logging in our ARM application on Keystone2 K2K (TCI6638K2K) EVM board (TCIEVMK2X rev 40) and we cannot view the log messages in the CCS-Tools-System Analyzer.
Our software uses SYSLIB v.4 and MCSDK 220.127.116.11 patched for SYSLIB v.4.
We do following steps: 1. As first step we capture the ETH traffic with tcpdump (.pcap format) and we remove the ETH headers and save into a .bin file. 2. Then we open CCS-Debug Perspective - > Tools -> System Analyzer -> import .bin file and point the System Analyzer to the .bin file. 3. We create a custom configuration .uml xml as shown in the picture below 4.
5. Then we save and press START. 6. We expect to see the Logs in the Binary-File window, but nothing appears there. Please see the picture below:
NOTES: - We have tried different versions of CCS including CCS5.4, CCS6.1, CCS6.2, CCS7.1 and CCS7.3. - We have tried different versions of UIA package by choosing it in CCS->Window->Preferences->Products->RTSC. Our software uses uia_2_00_03_43. We have tried uia_1_01_03_25, uia_2_00_06_52, uia_2_00_03_43 and uia_2_20_00_02. - The way we generate the .bin file is confirmed to be correct because the UIA logs from our DSP application are visible in System Analyzer without any issues. - Our older applications which were using an older MCSDK version and SYSLIBv2 or SYSLIBv3 do not have this issue.
Is SYSLIBv4 compatible with CUIA? May you help with an advice how to view the UIA logs of SYSLIB4 ARM application? Kind regards.
Please make sure you read the forum guidelines first.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Yordan Kovachev:
Can you please attach the part of your .cfg file where you have UIA configured? You must use CCS 6 or higher with UIA 2x.
In reply to janet:
Hi Janet,Thank you for helping us.We are using Code Composer Studio Version: 6.2.0.00050.
We are able to successfuly decipher UIA logs generated by DSP where we have .cfg file. We have problem deciphering UIA logs generated by the ARM application. For ARM application we do not have the .cfg file.Attached you may find the Custom UIA Configuration file (.usmxml) created with CCS and .bin files after removal of Ethernet headers.We are looking forward for your analysis result.
Please let us know if something else is needed.Kind regards,Kenan
In reply to Kenan Isa:
In order to use RTOS Analyzer, you need to have BIOS running on the target. In that case, you would have a .cfg file where you configure BIOS and UIA for your target program. Are you running BIOS on the ARM? From your UIA config screen shot, it looks like you have cuia.uia.xml and cuia.rta.xml files. Did you generate these from a .cfg file?
Also, the first 4 (32-bit) words of the binary file should be a UIA packet header. The first word from your binary file is 0020 7400, which doesn't look right to me. I would have expected to see A0....., the 'A' indicating that this is an Event packet.
Hi Janet,We are using CUIA on ARM, and we do have a problem decoding CUIA logs from ARM. We are not using SysBIOS on ARM. Accordingly, we do not have the .cfg file for the ARM application. Yes, we have cuia.uia.xml and cuia.rta.xml files. The cuia*.xml files are from the CUIA package and according to TI, we have reused them when processing anything from the ARM. TI has provided the patch and the description in the release notes.
What might be potentially the problem in this case?
1. cuia*.xml files are incorrect.
2. ARM application CUIA without SysBIOS is not compatible with UIA.
We are looking forward for your replay.Kind regards,Kenan
do you have some further findings?
In reply to ToddMullanix:
My apologies for the delay in responding. I'm in the process of setting up a cUIA development environment, and should have things set up tomorrow (July 6). I'll post again tomorrow once I've been able to get a better understanding of the data you captured.
In reply to BrianC:
We see that CUIA is supported by TI for ARM as per release notes of TI for SysLib 4, it is even mandatory to use CUIA on ARM / Linux subsystem. The CUIA logs generated this way seem to be fine.
What we see lacking is the decoding capabilities for CUIA in CCS, which seems to be in our opinion an incomplete functionallity within CCS.
We are looking forward for the resolution.
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.