HELP!! I don't get any USB device in Windows 10 once I connect a Neo Full to my PC. Disk image hash (MD5) = 1f2e17c1e425dc3d944f03c2d83e073a Downloaded both from Sourgeforce and Mirror EU, same result. Any ideas? Greg
I did not get it working at first, but here are my notes as I tried to fix mine live after seeing your post. I document as I brainstorm/debug, if you want to skip to TAG below of SOLUTION, I will not know I had the problem as well on the previous 2 development fast track releases of windows 10. I am currently on this one: Run a cmd prompt and type ver to get the following output if unfamiliar. Microsoft Windows [Version 10.0.10586] (c) 2015 Microsoft Corporation. All rights reserved. I confirm I was not able to get the IP stack over USB to work without taking some steps. The first time I made the mistake that I was using one of the USB cables that does not provide data, only power for recharging. DOH! I use these for my raspberry pi's as they are quite handy and prevent the MicroUSB port from getting loose/sloppy from many insertions... But they are not the right thing for this kind of setup. Note, some cheap USB charger cables can have the same effect. If you don't see windows mount the /boot filesystem when the neo powers up, this could be part of the problem. I have a local hdmi console hooked up and the neo full with beta5 is showing the USB IP interface of 192.168.7.2 as the documentation states it should. from a windows cmd prompt from the win10 host, i see via ipconfig: Windows IP Configuration Wireless LAN adapter Wi-Fi: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Wireless LAN adapter Local Area Connection* 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Wireless LAN adapter Local Area Connection* 3: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Ethernet adapter Ethernet: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::d4ac:564e:23cf:e7ec%5 Autoconfiguration IPv4 Address. . : 169.254.231.236 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : Ethernet adapter Ethernet 2: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::2cbe:df78:c42b:145d%10 IPv4 Address. . . . . . . . . . . : 192.168.1.28 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 Nothing here that looks like an NDIS driver with IP over USB. So then I looked at Device Manager... Device Manager Views: The driver for RNDIS appears to not be installed, will have to research that part further. HOWEVER, I see that USB serial port COM4 is present. I fired up putty and pointed it to COM4 @9600 baud and it worked to connect cmdline. PUTTY Connection: And when the Neo is booting I get a popup window on my pc that shows the /boot filesystem of the SDCard image. This image is for the beta 5 image fresh off the EU server an hour ago. Explorer View : SOLUTION: I was curious about this myself. I recall seeing some NDIS instructions somewhere, but I cannot seem to find them just yet. Ok after watching this youtube video {marker 1:14]} it helped me find them again. They are here. The step that was necessary is that I needed to do the NDIS configuration. After those steps I wound up with this: Then from the cmd prompt I now see it from ipconfig: ---extra stuff deleted--- Ethernet adapter Ethernet 5: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::9168:ade4:cc4a:5fde%42 IPv4 Address. . . . . . . . . . . : 192.168.7.1 Subnet Mask . . . . . . . . . . . : 255.255.255.252 Default Gateway . . . . . . . . . :C:\Users>ping 192.168.7.2 Pinging 192.168.7.2 with 32 bytes of data: Reply from 192.168.7.2: bytes=32 time<1ms TTL=64 Reply from 192.168.7.2: bytes=32 time<1ms TTL=64 Reply from 192.168.7.2: bytes=32 time<1ms TTL=64 Reply from 192.168.7.2: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.7.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms So that is good. I use cygwin instead of putty for ssh. I tried to connect as ssh udooer@192.168.7.2 and it WORKED.. !!! Yippee, thanks for inspiration to try and get it solved. Perhaps that may work or help you figure out what is behaving differently.. As an unexpected benefit the putty session remained connected while I was installing the NDIS drivers and while connected over that path. The windows file explorer connection to the filesystem of the sdcard /boot partion is still connected and working. but not to the other partitions of the sdcard (ie: / or /dev, etc) So now I am connected to the neo on local graphical console, serial, ip over NDIS/USB, ethernet and wifi simultaneously. Next up is to try hardline usb to the arduino console ports with my ftdi-friend next. (I think I have to watch out this one to make sure I use the 3.3Vdc version not the 5V version since I have both around) Cheers ------Sidebar----- I ran into similar USB connection issues with using my mac laptop loaded with the latest El Capitan, eventually I found that the NDIS drivers do not work with El Capitan yet, something totally out of the scope for this thread, and out of the control of the UDOO team. That is partly why I postponed debugging windows 10 via USB, already had this grief on OS X. Good luck.
You have multiple possibilities to connect to the Udoo Neo Using serial console over USB (On GNU/Linux this is gtkterm program connecting to /dev/ttyACM0 with baudrate 9600) You can tether Internet from your PC/Laptop to the Udoo Neo board over USB, on Linux by enabling packet forwarding and setting SNAT, but it's cumbersome and I prefer using WiFi for now. Using ssh over USB (ssh 192.168.7.2 -l udooer) to just access the board Using WiFi which will fetch random IP address from your local DHCP server (access-point) and you can use Internet this way This requires setting up /etc/network/interfaces file by adding auto wlan0 allow-hotplug wlan0 iface wlan0 inet dhcp wpa-conf /etc/wpa_supplicant/wpa.conf Generating /etc/wpa_supplicant/wpa.conf with wpa_passphrase and saving output to /etc/wpa_supplicant/wpa.conf On WiFi access-point assign specific IP address to board MAC address ip link show wlan0 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether 5c:31:3e:cd:8a:3a brd ff:ff:ff:ff:ff:ff Reboot board Using Bluetooth and rfcomm utility, it's the same as serial console but over bluetooh, and I havent tried this over this device. Once you are connected via serial, you can install vnc server and access device via virtual desktop if you want. So there are multiple options for headless access, there are even TX,RX pins for serial out. Finally, connect HDMI monitor to micro-HDMI and usb mouse/keyboard via USB hub to USB port If you want to use it as small computer. Plenty of options!!