Hi everyone.

 

I'm going through the setup process of my Helios4, but am encountering issues with the termina/serial login, which appears to be a character set issue of some type, which I can't figure out. Here is what I have so far:

sudo picocom -b 115200 /dev/tty.usbserial-DJ00JLDH
picocom v3.1

port is        : /dev/tty.usbserial-DJ00JLDH
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        :
omap is        :
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready

Ubuntu 18.04.1 LTS helios4 ttyS0

helios4 login:
Ubuntu 18.04.1 LTS helios4 ttyS0

helios4 login: r?????p?????????????p?????????????~p?????????????????????~p??????????????????p?????????????p?????????????~p?????????????????????~p?????????????
Ubuntu 18.04.1 LTS helios4 ttyS0

 

when I try to enter the root login details, the character set is obviously not set correctly, but I am not sure where to begin troubleshooting this, and there is nothing in previous threads or in the Wiki.

 

Any pointers would be greatly appreciated!

 

thanks!

_slayer_

Update on this, as I've not made any progress yet...

 

I've now tried using puTTY from a Windows VM, but it just hangs on connecting...

 

 

you have done this ?

For Windows and Mac OS you will need to install the FTDI driver in order to access the USB to serial bridge used by Helios4. You can find the driver here.

19 hours ago, _slayer_ said:

Any pointers would be greatly appreciated!

I'm facing similar issue once in a while with a specific FTDI dongle, it resolved itself by holding the "enter" key to make it auto-repeat until, after 30 seconds, it get back in proper state :

martin@giroles-hpel8300:~$ picocom -b 115200 /dev/ttyUSB2
picocom v3.2a

port is        : /dev/ttyUSB2
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready
�
  P���wor�:��
             �o�i��ti�e��
Debian GNU/Linux 9 pine64 ttyS0

pine64 login: 
Debian GNU/Linux 9 pine64 ttyS0

pine64 login: 
Debian GNU/Linux 9 pine64 ttyS0

 

I've installed the driver on both.

I use "screen"  instead of  picocom. Have you ever tried this software?

there was a nice little how to in the odroid forum for minicom: https://forum.odroid.com/viewtopic.php?f=53&t=841

I think it's more or less the same for picocom as well (they don't differ that much) and I don't have a mac anymore to test stuff...

 

Keep in mind there are a lot of fake FTDIs on the market (some of them work without issues for example mine. - it's a proved fake, some tend to be more problematic)..

 

btw. once you figured it properly out you might add it to this thread here?

 

always nice to have tutorials enhanced.

Issue Resolved!

 

By keeping the connection active and performing a reboot, I was able to connect in successfully!

On 1/4/2019 at 11:55 AM, Tido said:

I use "screen"  instead of  picocom. Have you ever tried this software?

 

I thought all the cool kids did - Mac and Linux...

 

I suppose there's always minicom on Linux...