Page 1 of 1

No connection because disabled WiFi

Posted: Fri Dec 09, 2016 11:31 am
by nti
Hi

I've disabled the WiFi connection on the OpenWRT web interface by mistake. Now I'm unable to connect to the VoCore2 :-( I've enabled ssh access to the WAN interface before that misfortune, but it seems this setting was not stored.

What can I do to connect the little box again?

Re: No connection because disabled WiFi

Posted: Fri Dec 09, 2016 3:32 pm
by Vonger
You can connect it to your computer, and it will create a serial port, then use putty or other serial port tool (115200, 8n1) you will able to login it from uart.

Re: No connection because disabled WiFi

Posted: Tue Dec 13, 2016 9:48 pm
by nti
Thanks a lot. I try to connect via microusb and screen or picocom but I don't know which pseudo device to use on OS X or raspbian. On both I have a new timestamp on the entry "/dev/ptmx" after connecting the vcore, but I can't connect to the terminal. Also /dev/ttys00x on OS X don't work. /dev/ttyUSBxxx isn't there on raspbian. Do I need some drivers ?

Re: No connection because disabled WiFi

Posted: Wed Dec 14, 2016 4:02 pm
by Vonger
It should be /dev/tty.usb______1

Re: No connection because disabled WiFi

Posted: Thu Dec 15, 2016 7:35 pm
by noblepepper
On linux (raspian should qualify) you should see something like this in the output from dmesg when you plug in the USB device:
Code: Select all
[3496703.065311] usb 1-2.4: new full-speed USB device number 61 using ehci-pci
[3496703.158109] usb 1-2.4: New USB device found, idVendor=067b, idProduct=2303
[3496703.158117] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[3496703.158122] usb 1-2.4: Product: USB-Serial Controller
[3496703.158126] usb 1-2.4: Manufacturer: Prolific Technology Inc.
[3496703.158694] pl2303 1-2.4:1.0: pl2303 converter detected
[3496703.160330] usb 1-2.4: pl2303 converter now attached to ttyUSB0


Run dmesg before and after you plug it in and see if anything new appears.

In the example above the device to use would be /dev/ttyUSB0 ( the last line of the output )

Also check the permissions:
Code: Select all
$ ls -l /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 Dec 15 13:09 /dev/ttyUSB0

In this example you have to be root or in the dialout group to access the device
Code: Select all
$ groups
pep dialout cdrom floppy sudo audio dip video plugdev scanner bluetooth netdev

I'm in the dialout group.