• State Suggested Answer
  • Locked Locked
  • Replies 10 replies
  • Answers 4 answers
  • Subscribers 120 subscribers
  • Views 3244 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

Cant see Dstream box in browse Debug Hardware Config IP

mickc1

We are trying to connect from a Linux HPC virtual environment in a different subnet with firewall to a Dstream box on a subnet box in our physical location.  We can ping the box from the Linux env and I was also able to update the box firmware with the Debug Hardware Firmware Installer from the Linux env.  However we cannot see the box using the browse function in the Debug Hardware Config IP.  IT has assured us that the firewall is not blocking any communication to/from the Dstream box or the ARM DS-5 v5.25.0 eclipse environment.

My question is, should we be able to see and target this hardware from a different subnet?  What specific requirements are there for communication to work (that aren't required for Firmware updates?)

Regards,
Chris

Parents
  • 0 Arm Employee Badge in reply to mickc1

    Hi Chris... the latter (connecting via debug connection (or via the firmware update utility)) should definitely work across subnets... it is something I frequently do, connecting to development boards in remote offices. I generally am a Windows user... does the problem only arise with Linux setups? Can you confirm which Linux flavor you are running? Could it be some incompatibility with a newer Linux (again, the version of DS-5 you are running is quite (~5 years) old.

    You have already done what I would suggest as the first pass, which would be to ensure you can 'ping' the box, so we know that the box is present on the network.

    I found the below which lists the various ports DSTREAM uses, if this helps your investigation.
    https://community.arm.com/support-forums/f/armds-forum/45417/dstream-networking-ports

    Sorry for your ongoing trouble,

    Ronan

Reply
  • 0 Arm Employee Badge in reply to mickc1

    Hi Chris... the latter (connecting via debug connection (or via the firmware update utility)) should definitely work across subnets... it is something I frequently do, connecting to development boards in remote offices. I generally am a Windows user... does the problem only arise with Linux setups? Can you confirm which Linux flavor you are running? Could it be some incompatibility with a newer Linux (again, the version of DS-5 you are running is quite (~5 years) old.

    You have already done what I would suggest as the first pass, which would be to ensure you can 'ping' the box, so we know that the box is present on the network.

    I found the below which lists the various ports DSTREAM uses, if this helps your investigation.
    https://community.arm.com/support-forums/f/armds-forum/45417/dstream-networking-ports

    Sorry for your ongoing trouble,

    Ronan

Children