Omega2 I can't get serial connection

JBarbosa

My Omega2 + mini Dock does not start the wifi network (it was a long time ago, I don't remember what I did to make this happen), so I'm trying to update the firmware via USB, I'm following the documentation but I can't connect to the serial port, when I run the command screen /dev/ttyUSB0 115200 the terminal has no response (yes, I pressed enter several times), after closing the terminal and running the command sudo dmesg I have the error: cp210x ttyUSB0: failed set request 0x12 status: -110

is he dead?

crispyoz

@Josinaldo-Albuquerque-Barbosa Try a factory reset this may fix the wifi issue before spending to much time on the serial matter, the procedure is here

JBarbosa

I've tried, it blinks for about 30 seconds but nothing happens

crispyoz

@JBarbosa Flashing for 30 seconds (please provide the precise number of seconds) suggests the device is booting, does the LED ever stop blinking and go solid? so you would expect it to be sending data to the terminal, so there is few things I would do next. Check /dev/ttyUSB0 exists

ls -la /dev/

I'm assuming it does as dmesg indicated it found the cp210.

Screen should complain if there is a permissions issue, but to be safe use sudo:

sudo screen /dev/ttyUSB0 115200

I prefer to use minicom because you can change communication parameters on the fly and running multiple versions of screen on the same port doesn't complain but causes problems:

sudo minicom -D /dev/ttyUSB0

I would change the USB cable, if still no luck, try using a different USB port or ideally a different computer, not all USB port are the same.

Please post some of the log, specifically unplug the USB cable, wait 10 seconds, then plug it back in wait about 20 seconds. The portion of the log I am interested in includes the unplugging and then after the end of the 20 seconds.

JBarbosa

@crispyoz I press the reset key and turn it on, it starts flashing for 30 seconds (after 11 seconds I release the reset), it turns off and turns on remaining solid, I check the wifi connection and I can't find it.

ls -la /dev/ttyUSB0* -> crw-rw---- 1 root dialout 188, 0 mar 13 02:33 /dev/ttyUSB0
sudo screen /dev/ttyUSB0 115200 -> same result
sudo minicom -D /dev/ttyUSB0 -> same result

I have already tried another cable and on a macbook (I installed the drive but the USB was not displayed)

with this command sudo dmesg?

[32670.851688] usb 1-10: new full-speed USB device number 27 using xhci_hcd
[32671.126168] usb 1-10: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[32671.126172] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32671.126174] usb 1-10: Product: CP2102 USB to UART Bridge Controller
[32671.126176] usb 1-10: Manufacturer: Silicon Labs
[32671.126178] usb 1-10: SerialNumber: 0001
[32671.143174] cp210x 1-10:1.0: cp210x converter detected
[32671.159190] usb 1-10: cp210x converter now attached to ttyUSB0
[32748.025003] usb 1-10: USB disconnect, device number 27
[32748.025209] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[32748.025231] cp210x 1-10:1.0: device disconnected
[32759.872249] usb 1-10: new full-speed USB device number 28 using xhci_hcd
[32760.146626] usb 1-10: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[32760.146630] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32760.146633] usb 1-10: Product: CP2102 USB to UART Bridge Controller
[32760.146634] usb 1-10: Manufacturer: Silicon Labs
[32760.146636] usb 1-10: SerialNumber: 0001
[32760.163648] cp210x 1-10:1.0: cp210x converter detected
[32760.179611] usb 1-10: cp210x converter now attached to ttyUSB0

JBarbosa

When I turn it on normally the LED is solid all the time

crispyoz

@JBarbosa OK so it looks like your serial communications is working ok to the minidoc, just that the Omega2 is not talking to it.

It's a little puzzling because u-boot will start displaying stuff in 2 or 3 seconds, so even if the firmware is trashed you'd get something on the terminal. But since you are getting hardware responses on the terminal it suggests hardware is not the issue. My next step would be to swap the dock, the swap the Omega2 so we can tie it down to one or the other. I assume you have neither of these and you don't have an ethernet expansion, correct me if I assume incorrectly.

I have 2 other things I would try.

Let the device boot for about a minute and a half. Omega2 is typically about a minute but just to be safe. Press enter once, wait a couple of seconds and press enter again. Repeat this 3 times. Wait 15 seconds. Carefully enter the default username and password (root/onineer), wait 5 seconds. Type reboot and press enter.

I'm trying to see if the Omega2 is receiving but not sending to/fro the terminal, for whatever reason. If it seems to reboot then that's progress. If nothing happens then cross this ff our list.

2.Since you don't have an ethernet expansion or other dock (I assume) you can jimmy up an ethernet connection. Take a look at this thread. Depending on your technical skills it may be a solution to debrick your device