-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs in coresight-tools #25
Comments
Thanks - now fixed #1 (Python 2->3 issue) and hopefully fixed #3 part 1. The core affinity problem in #2 is going to take more work, to cope with the fact that the CPU CTIs have not set DEVAFF to indicate their affinity. #3 part 2 is odd - do you have /proc/device-tree on both systems? I'll need to get hold of more device-tree based systems to test this on. We must have thought these asserts were valid at the time of writing. If you pull the latest, I've added a more verbose message to the one that triggers first, it would help if you report back what you see. Thanks for bringing these to our attention. |
Follow-up on On [2]:
Yes, and I added the CoreSight devices to the DT on both boards.
On [1]:
On [2]:
Did you notice anything strange in the csscan outputs? |
means that the DEVARCH register is not set. DEVARCH is a feature of modern CoreSight that allows vendors (including Arm) to indicate compliance to certain device programming interfaces, while still having a free choice of vendor / implementer code, part number etc. Some older devices don't set it. I've pushed some improvements to cs_topology_sysfs.py , which should improve discovery from Device Tree. Right now, it's not discovering CTI connections this way (kernel support for CTI is relatively recent, and for specialised use cases). I will raise that as a separate issue, but can't promise to get round to it any time soon. |
1. In
cs_topology_dts.py
:Output on [1]:
Same on [2] (funnel has different address).
2. In
csscan.py
: with option --topology-ctiOutput on [1]:
Error for address
0x73420000
, same for0x73520000
,0x73620000
and0x73720000
. The program runs without errors when excluding these addresses.Output on [2]:
Error for address
0x24a1c000
. Same for addresses0x24b1c000
,0x24c1c000
and0x24d1c000
. Excluding these addresses causes the device to freeze and eventually crash.3. In
cs_topology_sysfs.py
:Output on [1]:
Output on [2]:
Removing the two
assert
statements indevice_tree_node_property_length
fixes this.Devices:
[1] Nvidia Jetson Nano with Jetson Linux 32.7.5 (based on Ubuntu 18.04 and kernel v4.9)
[2] Nvidia Jetson AGX Xavier with Jetson Linux 35.5.0 (based on Ubuntu 20.04 and kernel v5.10)
The text was updated successfully, but these errors were encountered: