After following the steps outlined at Intels USB SSH Networking guide https://software.intel.com/en-us/node/721524 https://software.intel.com/en-us/node/721524 I am still not able to ssh into my Joule and on my Host machine (CentOS7 laptop) I cannot even see a wired connection.
On the host machine:
So the whole guide is way off already, as its clearly not assigning the Joule an IP address or even recognizing the usb0 as an eth interface.
What do I need to do to get USB OTG configured to be a Ethernet device so that I may ssh from my CentOS7 machine to Joule 570x?
let me know what else I can answer to help please.
No This issue has not been resolved I have not noticed dmesg showing any difference on the host machine when I plug the usb in?
So I have taken a few new steps. I installing Ubuntu on the Joule
My Setup now looks like:
Joule Machine: Ubuntu 16.04
Host Machine: CentOS
Joule Is plugged into the USB-C connector (JOULE SIDE) plugged into USB-A (HOST SIDE)
Still nothing on dmesg on the Host machine (CentOS)
I ran modprobe g_ether to get the module loaded on the Joule side and I am presented with a message inside dmesg:
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
Still no connection identified inside the CentOS machine (HOST)
Then On the Joule I Run
I see usb0 interface displayed; however, no connection details but it does mention ETHERNET
but the HOST side does not have any connection established setup and I see no WIRED CONNECTION setup
What should be my next steps?
Thank you for your patience.
I followed the article on an Ubuntu machine and was able to connect through SSH without issue.
You will have to connect both a USB 2.0 Micro B and a Type C. The Micro USB is needed when following the first part of the guide and connect through Picocom.
The ttyUSB0 device is listed under the /dev/ directory in Linux (Ubuntu), this is the one device you need to access using picocom (devices under dev dir + picocom terminal.jpg). List the devices using the ls command, ls -l "/dev/tty*".
It's possible that since you're running a host CentOS machine the outputs or commands that are shown in the guide could be different.
The guide we have was made for Ubuntu.
If you're still having issues, please attach a screenshot with your terminal output so I can take a look.
Hope this helps.