Hi, we have been trying to use the Coresight component on AGX Orin development kit to collect the CPU complex runtime trace lately. However we are experiencing issues that is strange and we were wondering if there are any implementation issues on the AGX Orin CPU.
The way we set up the Coresight is compiling the kernel with Coresight driver option enabled and the device tree file is also changed to enable the Coresight components, including TMC/TPIU/ETM/etc. However, when we try to operate the Coresight to collect and dump the trace via sysfs the Coresight driver just always fails, see the following screenshot.
Upon further investigation, we noticed that the TMC driver probe always fails which could potentially lead to the problem. We suspect that the memory address of TMC which is provided in the device tree files is not correct. We were wondering if NVDIA engineers ever had this issue before? Please let me know if you need any other information. Thank you!
Hi
This would need other users to share experience. By default we have tegrastats to check loading of hardware blocks. You can execute sudo tegrastats to get runtime frequency and loading of each CPU core.
However I don’t think it shows anything specific with the Coresight or any other debug components of the CPU complex? I was also checking over the technical reference manual but it did not mention anything about the memory mapped io physical address of on chip components. Could you please enlighten me where can I find those information if possible? I remember those info are available on TX2 platform technical reference manual. Thanks!
