Re: Fwd: Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
Hey. yeah, i mixed that up, it was quite confusig -> it works now, thanks :) On 02/12/2016 05:29 PM, Lennart Sorensen wrote: On Fri, Feb 12, 2016 at 02:35:53PM +0100, toogley wrote: i forgot to reply to the list, so for correctness: Forwarded Message Subject: Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection Date: Fri, 12 Feb 2016 01:15:25 +0100 From: toogley To: Milan P. Stanic 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. That has a USB connector and is NOT inside your machine, which means it IS a usb serial adapter. /dev/ttyS0 is obviously wrong in this case.
Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
Hehe. my bananapro successfully boots now. I'm not sure though what is now different in comparison to my previous attempts. Surely, the order of the pins was an issue (as i pointed out here https://lists.debian.org/debian-arm/2016/02/msg00035.html) On 02/12/2016 04:48 PM, Milan P. Stanic wrote: 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
Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
Hey, 1) I was wrong with the order of the pins. The Manual http://www.lemaker.org/product-bananapro-download-35.html clearly shows it has to be: Black --> GND; Green ..> RX; Red --> TX. 2) I successfully ran Bananian 1508 over serial connection. In addition to the lightening red lamp, the LED1 blinks regularly in a green light. On 02/12/2016 03:38 PM, toogley wrote: Ah, thanks. Well, using % sudo screen -fn -U /dev/ttyUSB0 115200 also doesn't work - the screen remains blank. 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
Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
Ah, thanks. Well, using % sudo screen -fn -U /dev/ttyUSB0 115200 also doesn't work - the screen remains blank. 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
Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
i forgot to execute screen as root. % sudo screen /dev/ttyUSB0 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
Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
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
Fwd: Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
i forgot to reply to the list, so for correctness: Forwarded Message Subject: Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection Date: Fri, 12 Feb 2016 01:15:25 +0100 From: toogley To: Milan P. Stanic 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. 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'
Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
additionally, booting debian from an external usb stick as suggested here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780493 also doesn't work. I can't achieve a serial connection and well the system even doesn't boot (i think at least - the status leds don't change) On 02/11/2016 10:13 PM, toogley wrote: Also switching RX and TX doesn't make any difference. thanks btw. for the screen tip - its much simpler. On 02/11/2016 09:54 PM, Vagrant Cascadian wrote: On 2016-02-11, toogley wrote: 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. ... 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. I can't count the number of times I've accidentally switched Rx and Tx, so simply switching them to be sure has worked for me often enough. Working with many different boards, the order of which is which is hard to keep straight... 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 - Bps 9600 BN1 - modem init and reset strings are already removed 6. only the red power lamp is on and minicom says 'offline' I'd also recommend trying screen: screen /dev/ttyS0 115200 Works with most of the boards I use, and doesn't require configuration. Good luck! live well, vagrant
Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
Also switching RX and TX doesn't make any difference. thanks btw. for the screen tip - its much simpler. On 02/11/2016 09:54 PM, Vagrant Cascadian wrote: On 2016-02-11, toogley wrote: 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. ... 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. I can't count the number of times I've accidentally switched Rx and Tx, so simply switching them to be sure has worked for me often enough. Working with many different boards, the order of which is which is hard to keep straight... 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 - Bps 9600 BN1 - modem init and reset strings are already removed 6. only the red power lamp is on and minicom says 'offline' I'd also recommend trying screen: screen /dev/ttyS0 115200 Works with most of the boards I use, and doesn't require configuration. Good luck! live well, vagrant
Re: bananaPro | debian jessie doesn't boot; trying to establish a serial connection
Sometimes it is worth making sure hardware flow control is OFF in minicom, and perhaps carrier detect too. Are you sure 9600 is correct? Most devices I encounter these days are 115200 it seems. https://lists.debian.org/debian-boot/2015/03/msg00314.html seems to mention 115200 on a Banana Pro. both hardware flow control and carrier detect are set to off. I'm not sure 9600 is correct, the Arch wiki suggested it. But I've seen, the lemaker wiki http://wiki.lemaker.org/BananaPro/Pi:How_to_login_to_the_system#Using_the_TTL_serial_port recommends 115200, but still it doesn't boot. in my previous tests e.g. with bananian, my bananapro worked fine - while booting that, a green light flashed up - which does not with debian jessie. ==> Although i didn't found the exact meaning of those light combinations, I'd assume that the OS didn't burn successfully. Anyways, I've changed also my power adapter to a 1200 mA one, but that doesn't change anything.
bananaPro | debian jessie doesn't boot; trying to establish a serial connection
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 - Bps 9600 BN1 - modem init and reset strings are already removed 6. only the red power lamp is on and minicom says 'offline'
Re: banana pro | bananian does boot, debian armhf-netinst not.
Hey, sorry. i complete overlooked that i need of course a sd card image. Thanks. On 12/30/2015 09:13 PM, Karsten Merker wrote: On Wed, Dec 30, 2015 at 08:22:43PM +0100, toogley wrote: Hello, # The versions used: bananian version: 15.08 (released 2015-08-22) debian version: 8.2.0 armhf-netinst (2015-09-06 16:24) Accoding to http://www.debian.org/releases/stable/armhf/ch02s01.html.en the armhf architecture is the correct one. command for both: sudo dd bs=4M if=[path]/[imagename] of=/dev/sde && sync => bananian works, debian not. It simplay doesn't show any reaction => What is my mistake? Hello, from the version string "8.2.0 armhf-netinst (2015-09-06 16:24)" I assume that you have tried to write a netinst CD ISO to an SD card. The CD images are not bootable on armhf; you have to use a proper SD-card image for your target system as described in the installation guide at https://www.debian.org/releases/stable/armhf/ch05s01.html.en#boot-installer-sd-image The SD-card equivalent of the netinst CD is available from http://ftp.nl.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/SD-card-images/ In your case the follwing commands should provide you with a working netinstall SD-card image: $ wget http://ftp.nl.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/SD-card-images/firmware.BananaPro.img.gz $ wget http://ftp.nl.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/SD-card-images/partition.img.gz $ zcat firmware.BananaPro.img.gz partition.img.gz > netinstall.img The resulting "netinstall.img" can then be written to an SD card. HTH, Karsten P.S.: Just as a sidenode: the Jessie installer requires a serial console cable, there is no HDMI output.
banana pro | bananian does boot, debian armhf-netinst not.
Hello, # The versions used: bananian version: 15.08 (released 2015-08-22) debian version: 8.2.0 armhf-netinst (2015-09-06 16:24) Accoding to http://www.debian.org/releases/stable/armhf/ch02s01.html.en the armhf architecture is the correct one. command for both: sudo dd bs=4M if=[path]/[imagename] of=/dev/sde && sync => bananian works, debian not. It simplay doesn't show any reaction => What is my mistake?
