Android Things: Intel Edison: Using USB and Debugging

1
votes

Has anyone had any luck using USB debugging with an Edison while also using a USB peripheral? It looks like you have to use the switch to activate the bigger USB port, which also cuts off the debugging port. I'm trying to use a USB camera, but can't see the debugger info to actually figure out what's not correct. I also get a connection refused when attempting to use adb connect on the wifi ip.

1
intelandroid-thingsintel-edison
If reading logs over the serial debug console is enough for you and you run into some obstacle connecting to it, you might look at a couple of solutions: using PuTTY (Windows) and both GNU Screen and Minicom (Linux) – Onik

1 Answers

4
votes

It looks like you have to use the switch to activate the bigger USB port, which also cuts off the debugging port.

Correct, only one port can be active at a time between the USB Host and USB OTG on the Edison. If you just need access to logs for debugging, connect another USB cable for the serial debug console as described on the Android Things Edison page. This will give you shell access and you can run logcat.

I'm trying to use a USB camera, but can't see the debugger info to actually figure out what's not correct.

It's worth noting that USB cameras are not supported in the current preview release. It's unlikely that the device will be recognized as a camera through the APIs, though you may still be able to access it as a raw USB device if you wish.

I also get a connection refused when attempting to use adb connect on the wifi ip.

The Edison defaults to USB mode for ADB, but you should be able to set it to TCP mode to connect over the network (much like an Android phone):

$ adb tcpip 5555
$ adb connect <ip address>:5555

…or the following, which should persist the configuration across a reboot:

$ adb root
$ adb shell setprop persist.adb.tcp.port 5555
$ adb reboot
$ adb wait-for-device
$ adb connect <ip address>:5555