BBW not booting when serial to USB cable connected

[Rishabh]

Hi,

I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows 10. I am trying to use a PL2303HXA serial to USB cable to get the serial output to my terminal in Ubuntu. I am doing this to view U-Boot.

Whenever the serial to USB is connected, the board doesn't boot up. 

When the serial to USB cable is connected and I run

picocom -b 115200 /dev/ttyUSB0

the terminal waits for data on the port. As soon as I try to power up the board with the micro-USB cable, I get a fatal error and the serial port connection gets lost.

picocom v2.2

port is        : /dev/ttyUSB0
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
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        :
omap is        :
emap is        : crcrlf,delbs,

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

Terminal ready

FATAL: term closed

The board boots up only when the serial to USB cable is disconnected from the PC.

I tried to connect the serial to USB after powering up the board and that powers off the board. I am not sure why but the two connections (serial to USB and micro-USB power cable) seem to be mutually exclusive. I would appreciate any suggestions on how to resolve this issue.

Thanks,

Rishabh

[Dennis Lee Bieber]

On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Rishabh

<rishabh.gupta777-Re...@public.gmane.org> wrote:

>I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows
>10. I am trying to use a PL2303HXA serial to USB cable to get the serial
>output to my terminal in Ubuntu. I am doing this to view U-Boot.
>

Wonder if Win10 may be getting in the way... The driver for the HXA is
no longer supported in Win10.
http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
"""
NOTE:

Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip
versions.
"""

I don't know how VirtualBox handles USB devices -- if they pass through
to the guest OS as raw devices, or if VBox is intercepting the guest I/O
and mapping through the host OS...

https://www.google.com/search?q=PL2303HXA+&oq=PL2303HXA


--
Dennis L Bieber

[Mark Lazarewicz]

Virtual Box support of SUB driver's was squirrelly 2 years ago.

If I'm not mistaken at one point Mr Robert refused to support builds.

I was  able to get it to work but the flakiness of serial output wasn't worth the aggravation 

Sent from Yahoo Mail on Android

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/58q9hfdcb0idakr5a77iamv34qm4cb4ilc%404ax.com.

[Mark Lazarewicz]

Try disabling the driver in win10 before starting virtual  box before starting VM then in Linux VM check which try enumerated and connect  to it was the fix I think.  With multiple USB devices it would change if I remember and you  might  Google which VB version supports SUB best, Again that was several years back

This phenomenon was easily  found and described  by googling 

Sent from Yahoo Mail on Android

To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1350777360.2861083.1595210466223%40mail.yahoo.com.

[jonnymo]

Are you plugging both USB cables directly to your PC or are you using a Powered USB Hub?  

I would suggest using a powered USB hub in this case if you were not using one already or power the BBW via the barrel jack.

Cheers,

Jon

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1930140602.2868269.1595210819228%40mail.yahoo.com.

[Mark Lazarewicz]

Did you  try this using a Windows serial terminal as well?

Your fatal error is in linux terminal in virtual machine

Let us know if there  is a difference and use a powered hub or power supply  as was suggested 

Sent from Yahoo Mail on Android

--

For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/cbdb43e6-b279-4aa2-aa38-d1a02468e574o%40googlegroups.com.

[rishabh....@gmail.com]

I did try using MobaXterm on Windows to connect to the serial port. That didn't work.

I got the below error:

I am indeed plugging both cables to my PC. Sadly, I do not have a USB hub or a power supply for the BBW.

To unsubscribe from this group and stop receiving emails from it, send an email to beagl...@googlegroups.com.

[rishabh....@gmail.com]

I got to know that the driver is no longer supported when I first connected the cable. The driver still seems to work though.

Also, I added filters in the VM's settings and that is how picocom was able to connect to /dev/ttyUSB0.

On Monday, July 20, 2020 at 2:51:55 AM UTC+2, Dennis Bieber wrote:

On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Rishabh

[jonnymo]

That error you are seeing appears to come from your USB to Serial interface.

Note:

http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41

Jon

On Tue, Jul 21, 2020 at 6:48 AM <rishabh....@gmail.com> wrote:

I got to know that the driver is no longer supported when I first connected the cable. The driver still seems to work though.

Also, I added filters in the VM's settings and that is how picocom was able to connect to /dev/ttyUSB0.

On Monday, July 20, 2020 at 2:51:55 AM UTC+2, Dennis Bieber wrote:

On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Rishabh

<rishabh.gupta777-Re...@public.gmane.org> wrote:

>I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows
>10. I am trying to use a PL2303HXA serial to USB cable to get the serial
>output to my terminal in Ubuntu. I am doing this to view U-Boot.
>

        Wonder if Win10 may be getting in the way... The driver for the HXA is
no longer supported in Win10.
http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
"""
 NOTE:

    Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip
versions.
"""

        I don't know how VirtualBox handles USB devices -- if they pass through
to the guest OS as raw devices, or if VBox is intercepting the guest I/O
and mapping through the host OS...

https://www.google.com/search?q=PL2303HXA+&oq=PL2303HXA


--
Dennis L Bieber

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/590f7b0d-7cfb-4e0f-99e6-0efe7deb3c4fo%40googlegroups.com.

[rishabh....@gmail.com]

Thanks Jon, for the link. I tried modifying my current driver installation. It still shows the same error.

Although, now the board boots up but the serial connection gets dropped. The serial and power connections are somehow still mutually exclusive. The serial connection appears only when I turn off and plug out the micro-USB (power).

On Tuesday, July 21, 2020 at 4:54:30 PM UTC+2, jonnymo wrote:

That error you are seeing appears to come from your USB to Serial interface.

Note:

http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41

Jon

On Tue, Jul 21, 2020 at 6:48 AM <rishabh...@gmail.com> wrote:

I got to know that the driver is no longer supported when I first connected the cable. The driver still seems to work though.

Also, I added filters in the VM's settings and that is how picocom was able to connect to /dev/ttyUSB0.

On Monday, July 20, 2020 at 2:51:55 AM UTC+2, Dennis Bieber wrote:

On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Rishabh

<rishabh.gupta777-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

>I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows
>10. I am trying to use a PL2303HXA serial to USB cable to get the serial
>output to my terminal in Ubuntu. I am doing this to view U-Boot.
>

        Wonder if Win10 may be getting in the way... The driver for the HXA is
no longer supported in Win10.
http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
"""
 NOTE:

    Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip
versions.
"""

        I don't know how VirtualBox handles USB devices -- if they pass through
to the guest OS as raw devices, or if VBox is intercepting the guest I/O
and mapping through the host OS...

https://www.google.com/search?q=PL2303HXA+&oq=PL2303HXA


--
Dennis L Bieber

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

To unsubscribe from this group and stop receiving emails from it, send an email to beagl...@googlegroups.com.

[rishabh....@gmail.com]

I got a DC adapter to power the board. Although the serial connection does not get dropped on powering up, I do not see the bootloader loading.

Some time back, I had managed to get access to the U-Boot bootloader on the serial terminal with the USB power itself. It didn't show up again. The behavior has not been consistent. Presently, the serial connection drops out if I try to power using USB.

I would appreciate any inputs to solve the issue.

[Rishabh Kumar Gupta]

I found out the issue. I had used the wrong connections; connected 5V instead of ground!

After using the right connections, it worked even with the USB power.

On Sunday, August 16, 2020 at 8:43:48 PM UTC+2 rishabh....@gmail.com wrote:

I got a DC adapter to power the board. Although the serial connection does not get dropped on powering up, I do not see the bootloader loading.

Some time back, I had managed to get access to the U-Boot bootloader on the serial terminal with the USB power itself. It didn't show up again. The behavior has not been consistent. Presently, the serial connection drops out if I try to power using USB.

I would appreciate any inputs to solve the issue.

On Thursday, July 23, 2020 at 12:45:57 AM UTC+2, Rishabh Kumar Gupta wrote:

Thanks Jon, for the link. I tried modifying my current driver installation. It still shows the same error.

Although, now the board boots up but the serial connection gets dropped. The serial and power connections are somehow still mutually exclusive. The serial connection appears only when I turn off and plug out the micro-USB (power).

On Tuesday, July 21, 2020 at 4:54:30 PM UTC+2, jonnymo wrote:

That error you are seeing appears to come from your USB to Serial interface.

Note:

http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41

Jon

On Tue, Jul 21, 2020 at 6:48 AM <rishabh...@gmail.com> wrote:

I got to know that the driver is no longer supported when I first connected the cable. The driver still seems to work though.

Also, I added filters in the VM's settings and that is how picocom was able to connect to /dev/ttyUSB0.

On Monday, July 20, 2020 at 2:51:55 AM UTC+2, Dennis Bieber wrote:

On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Rishabh

<rishabh.gupta777-Re...@public.gmane.org> wrote:

>I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows
>10. I am trying to use a PL2303HXA serial to USB cable to get the serial
>output to my terminal in Ubuntu. I am doing this to view U-Boot.
>

        Wonder if Win10 may be getting in the way... The driver for the HXA is
no longer supported in Win10.
http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
"""
 NOTE:

    Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip
versions.
"""

        I don't know how VirtualBox handles USB devices -- if they pass through
to the guest OS as raw devices, or if VBox is intercepting the guest I/O
and mapping through the host OS...

https://www.google.com/search?q=PL2303HXA+&oq=PL2303HXA


--
Dennis L Bieber