I did try using MobaXterm on Windows to connect to the serial port. That didn't work.
I got the below error: [image: MobaXterm-serial-error.png] I am indeed plugging both cables to my PC. Sadly, I do not have a USB hub or a power supply for the BBW. On Monday, July 20, 2020 at 5:21:20 AM UTC+2, lazarman wrote: > 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 > <https://overview.mail.yahoo.com/mobile/?.src=Android> > > On Sun, Jul 19, 2020 at 2:54 PM, Rishabh > <rishabh...@gmail.com <javascript:>> wrote: > 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 > > -- > 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 <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/cbdb43e6-b279-4aa2-aa38-d1a02468e574o%40googlegroups.com > > <https://groups.google.com/d/msgid/beagleboard/cbdb43e6-b279-4aa2-aa38-d1a02468e574o%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/7315c84d-af64-4941-8758-cf64d9b1aa65o%40googlegroups.com.
