Hello
We work in a pair and use the same Ubuntu machine connected to the target board's onboard JTAG debugger (target connection: CMSIS-DAP, Connection: L35229085B)
Each of us has his own sudo account on that machine and his own Arm Development Studio installation, workspace etc. Of course, we don't use the machine simultaneously - when one of us needs access to the target, the other one disconnects.
The problem is the following. After the PC restart, if I start Arm Development Studio and debug session first - even after I finish my debug session, shut down my Arm Development Studio instance and log off, my counterpart cannot start debug session. And vice versa, if my counterpart, after the PC restart, runs Arm Development Studio and debug session first - I cannot do use it anymore.
The error we see is the following:Unable to connect to conn.Reason:Failed to launch debug server. Command: rddidap_serverdexited with error code:1And in the target console the following messages appear:Starting debug serverWaiting for debug server to start accepting connectionsERROR : Another instance of the server is runningWe have verified - there is no rddi process is running, so, nothing to kill. We have also tried to disconnect and connect back the target board - the problem persist.
The only way to fix the problem is to reboot the PC, which is painful because there are a lot of other things running on it.
Please advise.
Thank you in advance
Dmitriy
Dear Stephen
Thank you for your reply.
Unfortunately that doesn't help.
I shut down debug session and Studio completely on my side, my counterpart removes the file you have mentioned, starts Studio, tries to connect to the target... and see the message that there is already a connection established and continue connecting will terminate the existing one. Of course he selects to continue and the same message appears again:Failed to launch debug server. Command:rddidap_serverdexited with error code:1
ps aux doesn't show anything that seems to be anyhow related to the Studio, rddi server or anything else like this.
Thank you in advance for any further suggestions.
Hi againWhich version of Arm DS are you using? Look in Help > About.The lock files were changed in Arm DS 2024.0, so that they are now on a per-process basise.g. VSTRM_SERVERDEXIT_1234, VSTRM_SERVERDEXIT_56899so multiple runs shouldn't interfere with each other anymore.So please try updating to Arm DS 2024.0, if you haven't done so already. That should hopefully fix your problem.Stephen
Thank you much for your suggestion.
Unfortunately, we are limited to the selection available here: https://developer.arm.com/documentation/102233/2022-0M0So, we are using the most recent of the ones listed there, 2022.0M0.
And no, we don't see the files like VSTRM_SERVERDEXIT...
RegardsDmitriy
Hi Dmitriy,Ah, I see you are using "Arm DS for Morello". Are you actually connecting to a Morello board, or to some other target?In /tmp, do you see other files named VSTRM_... ? If so, try deleting those too, with e.g.rm /tmp/VSTRM_*Does that help?Stephen