We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I am using DStream-ST to debug a custom hardware with SSE-200 subsystem inside. We have added our custom debug components to the AP0 (Coresight APB-AP) and it includes some registers that must be configured first before accessing cores' debug registers. Currently I am able to do this using CSAT and then connect to the core. Now I am looking for way to integrate this within the ArmDS as a part of connecting to target.
I scripted same set of transactions similar to what I do in CSAT, in a .ds script file and gave its path to the:
Debug Configurations > Debugger > Run control > Run target initialization debugger script.
Having DAP logger tool open and listening to DStream, I can see that it tries to access core debug registers first before running my script which is not desired and it fails.
Regards
HiMy name is Stephen and I work at Arm.The Arm DS Debugger offers a "Debug and Trace Services Layer" (DTSL). DTSL is a software layer that sits between the debugger and the RDDI target access API. It allows you to add custom debug and CoreSight support for your platform. Please see:developer.arm.com/.../DTSLDTSL is quite a large topic, but I think this section matches what you are trying to do:developer.arm.com/.../Performing-custom-actions-on-connectAs a simpler (but lower-level) approach, see also:developer.arm.com/.../latestHope this helpsStephen