I successfully flashed a new coral dev board and verified everything went well using the HDMI video feed. I installed MDT on Windows 10 and can see the device
$ mdt devices
jumbo-wasp (192.168.101.2)
But when I try to connect I get a socket error
$ mdt shell
Waiting for a device...
Connecting to jumbo-wasp at 192.168.101.2
Couldn't establish ssh connection to device: socket error: [WinError 6] The handle is invalid
I've also tried to connect using the serial cable (micro USB) following the directions here: https://coral.ai/docs/dev-board/serial-console/#connect-with-linux
but the device never showed up in my COM adapters.
Any help would be greatly appreciated.
UPDATE:
I am able to use the serial connection now with Putty to connect now (had a bad micro USB cable), but I'm not sure what to do next to get the USB-C connection working with MDT
Finally solved this. The issue was with the Git Bash app they suggested using. Instead I used a Python Terminal and was able to connect.
Note, when trying to adjust the network adapter settings, nmtui would not work, I instead had to use the command line interface nmcli.
I had a similar problem where the mdt devices command could not see my Coral Dev Mini. Git Bash just didn't work at all for me. Eventually I installed the free Ubuntu terminal for Windows 10 and it worked fine. I downloaded it directly from Microsoft
Related
I am planning on using VS Code to work out of WSL2 installed on a remote machine. Before doing that, I wanted to check the direct connectivity from a Windows 10. I followed the instructions given in this blog. Also, the remote Windows 10 is on a VPN.
When I use the command ssh <username>#<IP address>, I get the message
kex_exchange_identification: read: Connection reset
Is there anything I am missing to get the connection going?
I develop on my tablet using android studio.
The tablet is connected to the computer by wifi using
adb connect <ip_andress>:5555
My application contains listeners for USB devices attached/detached.
But unfourtunately, when I connect/disconnect usb device to/from the tablet, the adb connection is getting killed, and I can no longer see the device under "adb devices".
It is not a adb-connection-by-wifi what gets killed. It is just that USB enumerations affect the sys.usb.* system properties which on many devices is causing restart of adbd regardless whether it's being used over USB or tcpip.
Do grep "stop adbd" /init*rc to see what I mean.
You could either comment out those stop adbd lines or just disconnect the USB cable before running your adb connect command.
I was never able to connect my cellphone with my computar through wi-fi.
I had already given up. I followed all the instructions and tips, and nothing worked.
Finally, I did what no one said to do.
I've connected the phone to the WiFi network provided by the cable modem itself and not to some (not all) additional networks that are included in the router.
At home I use one of these networks, because I use a Deco Tp-Link router, which propagates the signal to my entire house, but this network is NOT compatible with ADB. It does not identify it as belonging to the same network.
After this, I use the normal procedure described here.
a) Connect cellphone with a USB cable
b) Find the IP_Phone depends on system in the cell phone. Here I use Settings, About Phone, Status and IP address.
c) Run the following adb commands in Command Prompt (Windows) or Terminal (Linux), where IP_Phone is the IP above mentioned. Normally adb.exe is an executable stored in computer path. adb is already included in Android Studio package.
adb tcpip 5555
adb connect IP_Phone
d) Now disconnect USB cable and it's ready. The cellphone model continues to appear in the status line in the top of Android Studio.
-/-
The best wifi is that defined in Cable Modem. It, unlike an any account defined in my router, answers to a ping command.
ping IP_Phone
Disconnect the usb cable just before running adb connect <*ip_address_of_your_phone*>
When connecting HoloLens via USB to my computer, the device portal is still not available after setting it up as explained in the install tools page.
All I get in the browser 127.0.0.1:10080 is the generic "unable to connect" page.
Is there any way to know what is failing? What could I check? Any tip will be appreciated!
EDIT: browsers used: Edge, Firefox and Chrome.
EDIT2: Hololens development mode is on.
Connecting over USB requires the PC be running IPoverUSB, which is installed with the Windows 10 SDK. You can verify that it's running by checking the Services tab of Task Manager for IpOverUsbSvc.
FYI, another resolution to this issue may be the USB port you are using.
I initially was using a USB 3 port (which I've used to flash my HoloLens many times) and had the same issues.
On a whim, I switched to an older USB2 port and it's working perfectly now. SO try different USB ports if you are having this issue.
I have been using my Rpi for some time now using ssh with no problems until recently when i tried to login using the default password and it refused. After several attempts i packed it away, so it happens that i wanted to use it again earlier on today and when i tried accessing it using PuTTy it gave me a "unable to open connection to raspberrypi.local Host does not exist!" error. so i got a new memory card with Noobs on it reinstalled the OS only to get the same error, "unable to open connection to raspberrypi.local Host does not exist!". i have tried all i can i need help..
I had a very similar problem (connecting from a Windows 10 PC to a Pi Zero over USB using PuTTY), and I solved it by following this guide and by using a non-OTG USB cable/adapter: http://www.circuitbasics.com/raspberry-pi-zero-ethernet-gadget/. My issue seemed to be that the Pi was getting locked into a host-state while using the OTG micro-USB to USB adapter and thus couldn't receive any commands over the "ethernet" USB connection.
Did you check your devices in your network? And did you try it with "raspberrypi" instead of raspberrypi.local?
Good luck!
First of all, there's a similar thread on OpenQNX posted years ago but the solutions don't really apply for me.
Having said that, I want to create an OS image of QNX 6.6.0 to put on a Compact Flash card. This card is plugged in an USB adapter which is connected to my host pc. I'm running Neutrino in a VM (VMware/VirtualBox) for which I enabled USB support. Generally, the adapter works fine under Win (current host) and Linux.
The (apparently out-dated) tutorial I was following stated to search for devices named umass* or hd* after connecting the USB adapter. But there aren't any (except for hd0).
See also "ls /dev" screenshot.
The processes devb-umass and io-usb are running. So I expect that the adapter is detected automatically.
Any suggestions what went wrong?
OK, it seems that I had to restart the usb driver 'devb-umass' (several times). When the card reader is already plugged-in during the booting the driver will not detect it autoamtically. Thus one has to unplug and plug it in again after the devb-umass was getting re-started. It also might have been that the Host Controller Driver (HCD) was set to 'ohci' instead of 'ehci'.
Everything is working now as expected.
(Thanks Tim from the OpenQNX forum! ;) )