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.
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. 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. > On 02/11/2016 11:02 PM, Milan P. Stanic wrote: > >On Thu, 2016-02-11 at 21:03, toogley wrote: > >>Hello. > >> > >>i have a Banana Pro which i want to boot a debian jessie from. I know HDMI > >>doesn't work, so I want to have a serial connection for configuring ssh. > >> > >> > >>1. $ wget > >>http://ftp.nl.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/SD-card-images/firmware.BananaPro.img.gz > >>2. $ wget > >>http://ftp.nl.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/SD-card-images/partition.img.gz > >>3. $ zcat firmware.BananaPro.img.gz partition.img.gz > netinstall.img > >>4. My Banana Pro has three pins in the corner of the LAN Port. I've > >>connected my > >> Pins accoring that http://wiki.lemaker.org/File:USBpl2303.jpg picture > >>(black > >> --> GND; white --> RX; Green --> TX; leaving the red one out) and > >> plugged > >>a > >> power adapter. > >>5. i've set up my minicom like here > >>https://wiki.archlinux.org/index.php/Working_with_the_serial_console#Minicom > >> - Serial Device to /dev/ttySzero > > ^^^^^^^^ > >Are you using USB to serial adapter? > >It is usually /dev/ttyUSB0 (or /dev/ttyUSB1 if you have more interfaces > >connected to computer) and not /dev/ttyS0. > > > >> - Bps 9600 BN1 > >> - modem init and reset strings are already removed > >>6. only the red power lamp is on and minicom says 'offline' > >> > >
