Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows OS: Connected dev board not visible in mdt using Git Bash #102

Open
trezbit opened this issue Jun 6, 2021 · 2 comments
Open

Windows OS: Connected dev board not visible in mdt using Git Bash #102

trezbit opened this issue Jun 6, 2021 · 2 comments
Assignees

Comments

@trezbit
Copy link

trezbit commented Jun 6, 2021

What I ran

Got For Windows - Git Bash 2.31.1

  1. Installed mdt and confirmed it is available via Git Bash following suggestions in winpty: error: cannot start 'mdt': Not found in PATH #97 to address path issues
  2. Connected the dev board via USB, confirmed a new Network Adapter (Remote NDIS Compatible Device) shows up in Device Manager
  3. Ran mdt devices

What the docs said should happen

Connected dev board should be listed

What actually happened

After some wait nothing gets listed (mdt cannot see the connected device)
Running mdt wait-for-device stalls in "Waiting for device..."

@GokulSudheesh
Copy link

I had the same issue and this worked for me.

First connect your board to your PC.

Go to Control Panel > Network and Internet > Network and Sharing Center

Here you will see an Unidentified network click on it and go to Properties.
In properties, go to Sharing and check Allow other network users to connect through this computer's internet connection.

Now try running mdt shell command.
After you have successfully connected your board, make sure to uncheck the previous option in Network Sharing.

@nrg0004
Copy link

nrg0004 commented Dec 1, 2021

I did the above but it did not fix my problem. Here is what fixed it -

Apparently the dev board is seen as a unidentified network under public networks. My Windows Firewall settings blocked python.exe from writing to or reading to public networks. I did the following -

How to check if Windows Firewall is blocking a program

  • Press Windows Key + R to open Run.
  • Type control and press OK to open Control Panel.
  • Click on System and Security.
  • Click on Windows Defender Firewall.
  • From the left pane Allow an app or feature through Windows Defender Firewall.
  • In the allowed apps window, scroll through all the apps.
  • Locate the app you want to review and see if the app is checked. Here the python.exe was not checked. I changed the setting and voila, mdt devices finds the device and everything works on from here.
  • If it is unchecked, the app is blocked on the Firewall.
  • If your program is blocked, simply check the app and click OK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants