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 [email protected] 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 <[email protected]> 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.
>>>>
>>>>
>>>> [image: PL2303HXA-driver-properties.png]
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 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 
>>>>> <[email protected]> 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 [email protected].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/beagleboard/590f7b0d-7cfb-4e0f-99e6-0efe7deb3c4fo%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/beagleboard/590f7b0d-7cfb-4e0f-99e6-0efe7deb3c4fo%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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6c8b21cd-ba91-440c-8b3e-4202c6b67930n%40googlegroups.com.

Reply via email to