• Locked Locked
  • Replies 4 replies
  • Subscribers 119 subscribers
  • Views 6039 views
  • Users 0 members are here
2025 survey

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.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Starting debug server

Mark Griffiths
Note: This was originally posted on 22nd May 2013 at http://forums.arm.com

Hello,



I was using DS5 fine for connecting to my Altera board and then today it just stopped working, even the examples do not work.  So when trying to load the baremetal example, I get this error:



Starting debug server
Waiting for debug server to start accepting connections
processrunner.py:8: RuntimeWarning: Unable to determine _shell_command for underlying os: nt
  import subprocess
RDDI-DAP-DS : ERROR failed to connect to RDDI DAP target
RDDI Error Code 4107 : Connection to target failed.
RDDI DLL = rddi-dap_altera_2.dll
RDDI CFG = C:\Users\mgriffit\AppData\Local\Temp\ds5_8070900945896429705.txt
Failed to launch debug server. Command:
  /debug_server\vstrm_serverd_rddi.exe -rddi_dap_dll rddi-dap_altera_2.dll -rddi_dap_cfg \Local\Temp\ds5_8070900945896429705.txt -pollrate 200
exited with error code: 1


Any ideas  what to try?  What could have happened?
Parents
  • Note: This was originally posted on 23rd May 2013 at http://forums.arm.com

    Hi, well I was thinking something was wrong with the runner scripts that may be OS or OS+environment dependent.  However, your response leads me to conjecture that the switch settings on the board may have changed the configuration so that debug wasn't possible by the route you are choosing. The switches and DIPs on the Cyclone board I have can be used to enable JTAG or USBBlaster debug of the ARM cores in the system.  The error message doesn't help us identify that though.

    Regards,
    Mike.
Reply
  • Note: This was originally posted on 23rd May 2013 at http://forums.arm.com

    Hi, well I was thinking something was wrong with the runner scripts that may be OS or OS+environment dependent.  However, your response leads me to conjecture that the switch settings on the board may have changed the configuration so that debug wasn't possible by the route you are choosing. The switches and DIPs on the Cyclone board I have can be used to enable JTAG or USBBlaster debug of the ARM cores in the system.  The error message doesn't help us identify that though.

    Regards,
    Mike.
Children
No data