> Hello everyone,
I received my A64, the power supply and the USB-Serial-Cable-F, thanks Olimex.
I connected the serial cable by following the instructions in the FAQ:
"The RX line of the cable (GREEN wire) should go to TX line of the target board; the TX line of the cable (RED wire) should go to the RX line of the target board. The BLUE wire should go to the target's GND line. ".
In link a photo of the connection on the map :
By cons when I connect the USB to my computer, the A64 is not detected. I did not install the usb driver because my PC is on Linux Mageia and the driver is an exe file. Is this a concern?
I still tried the HDMI method. The boot works fine on my television until the login request. But this time it is my keyboard which is not recognized :'( . However I think that the problem comes from the keyboard which is an old old multimedia keyboard 1990-2000 bought second-hand.
Please could you tell me what's wrong with my UART connection?
Thanks
Hello albertjohn
I think you got the wrong subject. There was no mention of the printer Brother in my request.
Don't you ?
It's SPAM!
(Reported to mod hours ago...)
John
The UART connection seems fine. Make sure that you power the board from the power barrel jack. Is the cable recognized under your Linux system? How is the cable listed in your Linux? You need to open serial terminal on the port of the cable.
If you have problems getting it working, the chip inside the cable should be PL2303, so search online for "PL2303 Linux"!
Thank you for your answer,
no, the cable is not recognized by my file explorer when I connect it. (KDE dolphin)
It should be listed in the explorer, right?
ok I'm going to get PL2303 Linux, will it be necessary to install a driver according to you ?
Thanks
Where (which path) do you look in dolphin?
You can probably find it via dmesg
John
The usb is detected, here is what sudo -v lsusb sends me back:Bus 003 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x067b Prolific Technology, Inc.
idProduct 0x2303 PL2303 Serial Port
bcdDevice 3.00
iManufacturer 1 Prolific Technology Inc.
iProduct 2 USB-Serial Controller
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0027
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)
here is what sudo dmesg sends me for Prolific Technology :usb 3-1: Manufacturer: Prolific Technology Inc.
[ 9114.347862] usbcore: registered new interface driver usbserial_generic
[ 9114.347898] usbserial: USB Serial support registered for generic
[ 9114.359476] usbcore: registered new interface driver pl2303
[ 9114.359522] usbserial: USB Serial support registered for pl2303
[ 9114.359599] pl2303 3-1:1.0: pl2303 converter detected
[ 9114.382845] usb 3-1: pl2303 converter now attached to ttyUSB0
[ 9452.696455] usb 3-1: USB disconnect, device number 2
[ 9452.697031] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[ 9452.697102] pl2303 3-1:1.0: device disconnected
[ 9594.279431] usb 3-1: new full-speed USB device number 3 using ohci-pci
[ 9594.442404] usb 3-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00
[ 9594.442414] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9594.442419] usb 3-1: Product: USB-Serial Controller
[ 9594.442424] usb 3-1: Manufacturer: Prolific Technology Inc.
[ 9594.447448] pl2303 3-1:1.0: pl2303 converter detected
[ 9594.470833] usb 3-1: pl2303 converter now attached to ttyUSB0
[11994.250498] usb 3-1: USB disconnect, device number 3
[11994.251082] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[11994.251151] pl2303 3-1:1.0: device disconnected
[12808.567429] usb 3-1: new full-speed USB device number 4 using ohci-pci
[12808.731482] usb 3-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00
[12808.731493] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[12808.731498] usb 3-1: Product: USB-Serial Controller
[12808.731503] usb 3-1: Manufacturer: Prolific Technology Inc.
[12808.736761] pl2303 3-1:1.0: pl2303 converter detected
[12808.759910] usb 3-1: pl2303 converter now attached to ttyUSB0
The problem is that this informations does not correspond to what putty asks me for the serial connection:
Below is a screenshot of what putty is calling for.
https://screenshot-putty (https://prismx.nohost.me/nextcloud/index.php/s/4ESitTwb83jbSS2)
It seem fine, change the settings in puTTY to ttyUSB0:
(https://i.imgur.com/TJ5VKWv.png)
Hey Lubolimex,;D Thanks your putty setup worked well. ;D
I had to start putty as root, though.
I would have one last question for the login please:
LOGIN: root
PASSWORD: olimex
doesn't work.
As I could see on the forum I tried:
LOGIN: root
PASSWORD: password
but unfortunately the same result.
I boot on the Debian Buster with armbian Linux (ttySO)
thanks
Sorry Lubolimex,
I found the information on armbian's website.
h**ps://docs.armbian.com/
The login is
Login: root
Password : 1234
Topic resolved
Thank you, Olimex.
If you needed root you need to set the permissions on /dev/ttyUSB0 and/or put your login into the right group (dialout or whatever).
John