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

MGD 5.1.0 not able to connect to an IP

Hi Team,

I have downloaded MGD 5.1.0 and not able to connect using IP to my linux target ( port 5002 as mentioned in document). It could not locate the network connections.

Is there any guideline to follow on target and host to make it working? I am able to connect target via network using putty on SSH (port 22).

Steps I did:

- I started MGD as administrator user

- Run mgddaemon, see log below

root@linux0:~# ./mgddaemon
944172584714: mgd_daemon[2094]: [2094]:INFO: Main: The MGD daemon is starting
Daemon is version: D020
Socket is: \0mgddaemon
944172584731: mgd_daemon[2094]: [2094]:DEBUG: DeviceInfo: GL_VENDOR = ARM, GL_RENDERER = Mali-T880, GL_VERSION = OpenGL ES 3.2 v1.r13p0-00rel0.7381436e6963ff63f2ae2be6a4f45c3a
944172584731: mgd_daemon[2094]: [2094]:INFO: HostConnection: Initializing host connection
944172584731: mgd_daemon[2094]: [2094]:INFO: InterceptorListener: Initializing interceptor listener
944172584735: mgd_daemon[2094]: [2094]:INFO: CountersListener: Initializing Mali counters listener
944172584735: mgd_daemon[2094]: [2094]:INFO: Daemon: Daemon initializing
944172584735: mgd_daemon[2094]: [2107]:INFO: Daemon: Daemon running
944172584736: mgd_daemon[2094]: [2107]:INFO: Daemon: Daemon is version: D020
944172584736: mgd_daemon[2094]: [2106]:INFO: InterceptorListener: Interceptor Listener waiting for connections
944172584736: mgd_daemon[2094]: [2105]:INFO: HostConnection: Host connection listening

- Open Device manager and Connect to an IP using port 5002 , but no luck on connecting.

- I also tried to run the application as follows

root@linux0:~# export XDG_RUNTIME_DIR=/var/run/root/1000/
root@linux0:~# layer-add-surfaces 1000 1 &
[1] 2113
root@linux0:~# layerid=1000 is already used.
CreateWithDimension: layer ID (1000), Width (1920), Height (720)
SetVisibility      : layer ID (1000), ILM_TRUE
layer: 1000 created

root@linux0:~#
root@linux0:~# LD_PRELOAD=/home/root/libinterceptor.so /usr/bin/EGLWLMockNavigation
944172703017: mgd_interceptor[2115]: [2115]:INFO: DuplicateLibraryDetector: First interceptor loaded
944172703017: mgd_interceptor[2115]: [2115]:INFO: PassThroughClApi: Found the following libraries for 'cl': {/usr/lib64/libOpenCL.so, libOpenCL.so}
944172703017: mgd_interceptor[2115]: [2115]:INFO: PassThroughEglApi: Found the following libraries for 'egl': {/usr/lib64/libEGL.so, libEGL.so}
944172703018: mgd_interceptor[2115]: [2115]:INFO: PassThroughGlesApi: Found the following libraries for 'gles': {/usr/lib64/libGLESv2.so, /usr/lib64/libGLESv1_CM.so, libGLESv2.so, libGLESv1_CM.so}
944172703020: mgd_interceptor[2115]: [2115]:WARNING: GatorConnection: Not connected to gatord, the application will run normally but Streamline will not collect annotations. To collect annotations, please verify you are running gatord 5.22 or later and that SELinux is disabled.
944172703022: mgd_interceptor[2115]: [2115]:ERROR: Interceptor: MGD failed to read the process whitelist file: No reason provided. (Does the file exist & have correct permissions?)
944172703022: mgd_interceptor[2115]: [2115]:INFO: MarshallerBase: Connecting to daemon. Sending header...
944172703022: mgd_interceptor[2115]: [2115]:INFO: Interceptor: Interceptor loaded for 2115: /usr/bin/EGLWLMockNavigation
944172703022: mgd_interceptor[2115]: [2115]:INFO: Interceptor: Activating tracing
944172703023: mgd_interceptor[2115]: [2119]:INFO: ListenerThread: Received new message: C:1 E:0 F:0
944172703023: mgd_interceptor[2115]: [2119]:INFO: Interceptor: Host detached
surface                : 10 created
Shader setup complete.
SetDestinationRectangle: surface ID (10), Width (800), Height (480)
SetSourceRectangle     : surface ID (10), Width (800), Height (480)
SetVisibility          : surface ID (10), ILM_TRUE
layerAddSurface        : surface ID (10) is added to layer ID (1000)

Thank you.

Best regards,

Vikash

Top replies

Peter Harris over 4 years ago +2 verified

Hi Vikash, Possible problem #1: The Device Manager uses UDP broadcasts on port 5003 to find available devices on the network. This may be filtered out if the device is on a different subnet, or if...

+1 Peter Harris over 4 years ago

Hi Vikash,

Possible problem #1:

The Device Manager uses UDP broadcasts on port 5003 to find available devices on the network. This may be filtered out if the device is on a different subnet, or if any firewalls are present on the network or target device. If no device is showing up in the scan you will need to manually enter the device IP address in the address box in the Device Manager.

Possible problem #2:

The network or target device may have a firewall configuration which blocks in-bound TCP connections on port 5002, so the tool cannot establish a persistent link. This is a "known issue" on many Chrome OS target, for example. See this section of the user manual for more information:

https://developer.arm.com/docs/101545/latest/target-installation/chrome-os/tracing-a-linux-application-on-chrome-os

Cheers,
Pete
Cancel
Up +2 Down

Cancel

0 Vikash over 4 years ago in reply to Peter Harris

Hi Pete,

I tried using following command on target but no luck. Not sure what is stopping.

sudo iptables -A INPUT -p tcp -m tcp --dport 5002 -j ACCEPT

Is there any other way I can capture the trace and analyze offline using MGD without using network?

Best Regards,

Vikash