[Fuego] Problems with the serial transport.

Rafael Gago Castano RGC at hms.se
Tue May 30 12:49:17 UTC 2017


Well, today our lead developer came back from a short vacation and it seems that our tests images weren't using bash because of some Yocto misconfiguration. We have moved to bash and everything works.


________________________________
From: Bird, Timothy <Tim.Bird at sony.com>
Sent: Tuesday, May 30, 2017 10:29:16 AM
To: Rafael Gago Castano; fuego at lists.linuxfoundation.org; dhinakar.k at samsung.com
Cc: Frank Rowand
Subject: RE: [Fuego] Problems with the serial transport.



> -----Original Message-----
> From: Rafael Gago Castano on Tuesday, May 30, 2017 4:29 PM
>
> Well, what seemed to fix the issue was turning off the line wrapping (using a
> VT100 control sequence), not the column length:
>
> > printf "printf '\033[?7l'\r" > $SERIAL_DEV

OK - sorry.  I misread the thread.
>
> But it doesn't seem to work consistently, e.g. it did work with our images
> flashed on NAND but not with our image booted for RAM booting. Yesterday
> it stopped working (it may be my mistake).
>
OK - please let me know if you get more information about the
inconsistent behavior.

>
> It would be nice to document these issues for the serial transport:
>
> -Login must be handled separately (it's documented on the serio sources).
I have added a separate 'serlogin' program in the 'next' branch which is intended
to deal with this issue.  It works for me, but is a bit finicky.  But the goal is to
have it completely handle this particular issue.

See https://github.com/tbird20d/serlogin
and
https://bitbucket.org/tbird20d/fuego-core/src/805adb067afc492382ee23bc9178c059b90c043e/engine/overlays/base/base-board.fuegoclass?at=next

> -serio has issues with Busybox adding newlines (it's documented on the serio
> sources).

I'd like to see if this can be fixed in serio.  serio used to turn off
echoing, and we experimented with using a different mechanism
to detect end of program output.

I'm not sure if either of these would affect this issue, but
I'll try to find some time to look at this before the 1.2 release.

>
> I'm still blocked on the Busybox serial issues. I'll post here if I find something.
OK - thanks.
 -- Tim

> ________________________________
>
> From: Bird, Timothy <Tim.Bird at sony.com>
> Sent: Tuesday, May 30, 2017 9:08:31 AM
> To: Rafael Gago Castano; fuego at lists.linuxfoundation.org;
> dhinakar.k at samsung.com
> Subject: RE: [Fuego] Problems with the serial transport.
>
> > -----Original Message-----
> > From: Rafael Gago Castano on Friday, May 26, 2017 8:42 PM
> >
> > It looks like sercp --basic (using echo and cat) works, so it was just a matter
> of
> > disabling line wrapping on the terminal and everything works on the
> BusyBox
> > shell too. I guess that sercp failed because our device has no uuencode.
>
> That's good to hear.  I didn't have time to figure out the problem using the
> busybox
> shell, but it's nice to hear there's an easy workaround (to make the column
> length long
> using stty).
>
> It's too bad you had to figure out the missing 'uuencode' issue yourself.
>
> IMHO it would be good to detect these automatically and adjust serio (or
> Fuego's use of serio) to automatically compensate.  I have a test in the 'next'
> branch that checks various features (presence of programs and other items),
> and reports if there are any problems.  I'll look at adding something to this
> test
> so that at least people will get a warning if there might be issues with the
> serial
> transport.  Also I'll think about doing some extra steps in Fuego, or about
> enhancing serio so that it will automatically deal with these issues.
>
> Thanks for the report!
>  - - Tim
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20170530/4e0d2369/attachment.html>


More information about the Fuego mailing list