<div dir="auto">Hi Tim,<div dir="auto"><br></div><div dir="auto">I have changed both Fuego and Fuego-core next branch.</div><div dir="auto">When I tried serlogin inside container, I get the below error (the board has been powered on and kept).</div><div dir="auto">'device reports readiness to read but returned no data (device disconnected)</div><div dir="auto"><br></div><div dir="auto">If I connect to the board via minicom and manually login, close the terminal and the run a test e.g. hello_test it works fine.</div><div dir="auto">So it seems serlogin is not able to login automatically to the connected board.</div><div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Dhinakar</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Jun 14, 2017 9:52 AM, "dhinakar k" <<a href="mailto:dhinakar.k@gmail.com">dhinakar.k@gmail.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Hi Tim,</div><div dir="auto"><br></div><div dir="auto">Thanks for your response.</div><div dir="auto">Please see my comments inline.</div><div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Dhinakar<div class="quoted-text"><br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On Jun 14, 2017 5:59 AM, "Bird, Timothy" <<a href="mailto:Tim.Bird@sony.com" target="_blank">Tim.Bird@sony.com</a>> wrote:<br type="attribution"><blockquote class="m_-946584186736975822quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_-946584186736975822quoted-text"><br>
<br>
> -----Original Message-----<br>
> From: dhinakar k on Monday, June 12, 2017 1:14 PM<br>
> Update:<br>
><br>
> I downloaded serlogin from <a href="https://GitHub.com/tbird20d/" rel="noreferrer" target="_blank">https://GitHub.com/tbird20d/</a><br>
> and copied it to the /usr/local/bin folder inside the container.<br>
<br>
</div>Very good! Sorry you had to figure this out on your own.<br>
It's in the Dockerfile in the next branch. I'm guessing<br>
you are still running with an older docker container (based<br>
on v1.1). We really should write a script to move test results<br>
data from an old docker container to the next one, to avoid<br>
people being reluctant to upgrade their containers. Sorry<br>
for the extra pain this has caused you.<br></blockquote></div></div></div></div><div dir="auto"><br></div><div dir="auto">#### No problems. Infact I moved 'fuego' also to 'next' branch but somehow it is stuck at the last stage where it has to start the Jenkins ci server, threw some error, I will reproduce and let you know the error in another thread. So I couldn't try it out.</div><div class="quoted-text"><div dir="auto"><div class="gmail_extra" dir="auto"><div class="gmail_quote"><blockquote class="m_-946584186736975822quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="m_-946584186736975822quoted-text"><br>
><br>
> But now I get 'could not open port ttyUSB0: [Error2] No such file or<br>
> directory:'ttyUSB0' even though it was available (I manually checked it)<br>
<br>
</div>It probably needs /dev/ttyUSB0, or there is a permission problem.<br>
Did you build the docker container with 'docker-create-usb-privileged-<wbr>container.sh'?<br>
Are you using<br>
SERIAL=ttyUSB0<br>
or<br>
SERIAL=/dev/ttyUSB0<br>
in your board file?<br>
<br>
I think serlogin requires the latter format. This needs to be documented.</blockquote></div></div></div><div dir="auto"><br></div></div><div dir="auto">### </div><div dir="auto">Is using <span style="font-family:sans-serif">SERIAL=/dev/ttyUSB0</span></div><div dir="auto">Permissions have been given to /dev/ttyUSB0 , so I think no issue there.</div><div class="quoted-text"><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra" dir="auto"><div class="gmail_quote"><blockquote class="m_-946584186736975822quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_-946584186736975822quoted-text">
> At the prompt inside container I tried 'serlogin -d /dev/ttyUSB0 root' but got<br>
> 'warning: could not verify shell status' error. I manually checked on the board<br>
> via minicom, the shell was pointing to 'bash' shell.<br>
<br>
</div>To verify that we are sitting at a shell prompt, serlogin does the following<br>
command:<br>
ls / | grep ^sb.*n<br>
<br>
This does a directory listing of the root directory, then pipes the results<br>
to grep, looking for the pattern '^sb.*n'. If we're at a shell prompt and<br>
we have a normal root filesystem that has /sbin as a directory, then<br>
this should output '/sbin'.<br><br><br></blockquote><blockquote class="m_-946584186736975822quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br></blockquote></div></div></div></div><div dir="auto"><span style="font-family:sans-serif">#### </span><span style="font-family:sans-serif">ls / | grep ^sb.*n on target board returns 'sbin' </span><br></div><div dir="auto"><span style="font-family:sans-serif">I thought serlogin will login to target by itself? Should I keep my target logged in? I think I have tried that as well...</span></div><div class="quoted-text"><div dir="auto"><span style="font-family:sans-serif"><br></span></div><div dir="auto"><div class="gmail_extra" dir="auto"><div class="gmail_quote"><blockquote class="m_-946584186736975822quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><br>
So either 1) we're not really at a shell prompt where we can execute commands<br>
or 2) /sbin is missing, or 3) there is some permission problem doing 'ls /', or<br>
4) something is eating input so that serlogin is not seeing 'sbin' in the response.<br>
<br>
Can you execute the above command manually at your shell prompt, and see<br>
if you see 'sbin' among the strings in the listing? Also, make sure that you do<br>
not have a terminal on the serial port at the same time that fuego (and serlogin)<br>
are trying to use the serial port to talk to the target board.<br>
<br>
Let me know what you find out.<br>
<br>
Thanks,<br>
-- Tim<br>
<br>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>