Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
On Fri, 2016-02-12 at 15:38, toogley wrote:
> Ah, thanks.
>
> Well, using
>
> % sudo screen -fn -U /dev/ttyUSB0 115200
>
> also doesn't work - the screen remains blank.
Sorry if my question sounds stupid but did you connected pins from USB
cable to the board console pins as it is described on the URL which you
posted in the one of your previous mail, i.e. Rx pin from cable to Tx
pin on the board and GND pin?
Another question: did you copied image to SD card and put card properly
in the slot? I'm experiencing blank screen when I forget to put card in
the slot or even when it is in the slot but not laid properly.
In short, to get anything on the screen you must have u-boot flashed to
SD card and insert card in the slot or the screen will be blank.
I'm talking from my experience using BananaPi only, not the Pro variant.
> On 02/12/2016 03:19 PM, Milan P. Stanic wrote:
> >On Fri, 2016-02-12 at 15:09, toogley wrote:
> >>i forgot to execute screen as root.
> >>
> >>% sudo screen /dev/ttyUSB0
> >
> >You forgot to give speed parameter to screen.
> >
> >I start screen to BananaPi (not Pro, but I think their serial console
> >settings are same) serial console with next parameters:
> >screen -fn -U /dev/ttyUSB0 115200
> >
> >-fn means no hardware flow control and -U use UTF-8
> >although -U is not needed I use it in any case.
> >
> >>results in a just blank screen - nothing happens; i had to kill the screen
> >>process.
> >
> >
> >>On 02/12/2016 03:02 PM, toogley wrote:
> >>>Hey.
> >>>
> >>>
> >>>On 02/12/2016 01:22 PM, Milan P. Stanic wrote:
> >>>>You should post your reply to the original mailing list (debian-arm in
> >>>>this case) so other people could help and correct false answer, give
> >>>>additional comment and see if your problem is resolved.
> >>>
> >>>Yeah, that was a mistake -- sorry.
> >>>
> >>>>
> >>>>On Fri, 2016-02-12 at 01:15, toogley wrote:
> >>>>>I use not a USB to serial adapter, just
> >>>>>https://nicegear.co.nz/obj/images/954_LRG.jpg, so i think /dev/ttyS0 is
> >>>>>correct in this case.
> >>>>
> >>>>I see. This device looks like it is USB to Serial adapter (I have
> >>>>several of them around) and not 'simple serial cable'. I will bet that.
> >>>
> >>>Ah, yeah that was fallacy, sry..^^
> >>>
> >>>>Try to see output of the 'dmesg` command just after you insert this
> >>>>device into the USB port of your computer. You should see something
> >>>>like this:
> >>>>---------------------------------------------------------------------
> >>>>usb 1-2.2: new full-speed USB device number 19 using xhci_hcd
> >>>>usb 1-2.2: New USB device found, idVendor=067b, idProduct=2303
> >>>>usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> >>>>usb 1-2.2: Product: USB-Serial Controller
> >>>>usb 1-2.2: Manufacturer: Prolific Technology Inc.
> >>>>pl2303 1-2.2:1.0: pl2303 converter detected
> >>>>usb 1-2.2: pl2303 converter now attached to ttyUSB0
> >>>>---------------------------------------------------------------------
> >>>>
> >>>>Of course, it could be different manufacturer and other data but on the
> >>>>last line you will see which tty is assigned to the device. In my case
> >>>>(above) it is ttyUSB0 which means it is under /dev/ttyUSB0 and this
> >>>>device node should be used for your minicom/screen communication
> >>>>program.
> >>>>
> >>>>Another way is to use ls command to list if the device node exists
> >>>>before you plug this 'cable', i.e before plugged:
> >>>>ls -l /dev/ttyUSB0
> >>>>ls: cannot access /dev/ttyUSB0: No such file or directory
> >>>>
> >>>>and after plugged in:
> >>>>ls -l /dev/ttyUSB0
> >>>>crw-rw---- 1 root dialout 188, 0 Feb 12 13:19 /dev/ttyUSB0
> >>>>
> >>>>And of course last zero could be changed to other number if you already
> >>>>have other USB com port connected to computer.
> >>>
> >>>the output of dmesg:
> >>>
> >>>---------------------------------------------------------------------
> >>>[13622.930094] usb 2-1.1: new full-speed USB device number 3 using ehci-pci
> >>>[13623.024041] usb 2-1.1: New USB device found, idVendor=067b,
> >>>idProduct=2303
> >>>[13623.024051] usb 2-1.1: New USB device strings: Mfr=1, Product=2,
> >>>SerialNumber=0
> >>>[13623.024055] usb 2-1.1: Product: USB-Serial Controller
> >>>[13623.024059] usb 2-1.1: Manufacturer: Prolific Technology Inc.
> >>>[...]
> >>>[13624.074623] usbcore: registered new interface driver usbserial
> >>>[13624.074651] usbcore: registered new interface driver usbserial_generic
> >>>[13624.074675] usbserial: USB Serial support registered for generic
> >>>[13624.076310] usbcore: registered new interface driver pl2303
> >>>[13624.076366] usbserial: USB Serial support registered for pl2303
> >>>[13624.076420] pl2303 2-1.1:1.0: pl2303 converter detected
> >>>[13624.079628] usb 2-1.1: pl2303 converter now attached to ttyUSB0
> >>>---------------------------------------------------------------------
> >>>
> >>>
> >>>% ls -la /dev/ttyUSB0
> >>>crw-rw---- 1 root dialout 188, 0 Feb 12 14:44 /dev/ttyUSB0
> >>>
> >>>% screen /dev/ttyUSB0
> >>>[screen is terminating] # doesn't connect
> >>>
> >>>
> >>>But thanks for the tip of looking into dmesg, i'm at least one step
> >>>closer to the success :P
> >>>
> >>
> >
>
Reply to: