Re: [beagleboard] Re: Pocketbeagle Wifi Dongle Problems

2021-06-10 Thread Patrick Bolton 
Well I have no idea what the problem was.

I have now disconnected the power to P1.01 and it is working fine with only 
power through micro-usb port without PC tether.

Perhaps Im just a rambling lunatic.

Again thank you.



On Thursday, June 10, 2021 at 12:40:57 PM UTC-7 Patrick Bolton wrote:

> reconnected again.
>
> Problem fixed!
>
>
> Power into P1.01 from 5VDC 8A max supply & the usb-pc tether, of course.
>
> Female USB socket tied in per above image.
>
> With nothing connected:
> root@beaglebone:/var/lib/cloud9# udevadm trigger
> root@beaglebone:/var/lib/cloud9# dmesg
> Errors
> [0.001520] timer_probe: no matching timers found
> [0.160126] l4_wkup_cm:clk:0010:0: failed to disable
> [1.223591] omap_voltage_late_init: Voltage driver support not added
>
>
>
> Plugged in dongle.  It's powere light flashed on and off a few times.
> root@beaglebone:/var/lib/cloud9# udevadm trigger
> root@beaglebone:/var/lib/cloud9# dmesg
> Errors
> [0.001520] timer_probe: no matching timers found
> [0.160126] l4_wkup_cm:clk:0010:0: failed to disable
> [1.223591] omap_voltage_late_init: Voltage driver support not added
>
>
> But the dongle is now showing up on lsusb
> Bus 002 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
> 802.11n Wireless Network Adapter
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> and 
>
> ifconfig -a lists the WLAN
> wlan0: flags=-28669  mtu 1500
> ether 50:3e:aa:b1:3d:ec  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> I'm in business.  Thank you.
>
> On Thursday, June 10, 2021 at 11:50:22 AM UTC-7 Patrick Bolton wrote:
>
>> I have also connected 5 8A potential supply power directly to P1.01 and 
>> have the usb connected.
>>
>> On Thursday, June 10, 2021 at 11:32:22 AM UTC-7 Patrick Bolton wrote:
>>
>>> Yes, I tried it exactly per that same image with a variety of power 
>>> supplies.
>>>
>>> I have also been using the hubs from tindie, just in case I'm being 
>>> simple minded, but I've quadruple confirmed.  Measure twice cut once.
>>>
>>>
>>>
>>>
>>> On Thursday, June 10, 2021 at 11:27:03 AM UTC-7 RobertCNelson wrote:
>>>
 On Thu, Jun 10, 2021 at 11:22 AM Patrick Bolton <
 [email protected]> wrote:

> Well I was hopeful the kernel update today would help with the issues, 
> but no such luck.
>
> I powered the board at VIN with a 5VDC 8A power suppy with the 4-usb 
> port version of 2/4-port USB 2.0 HUB Cape for PocketBeagle from 
> microwavemont on Tindie 
> 
>
> Have additional over-current errors.
>
> If I am not supplying the information that is helpful for solving the 
> problem, please let me know.
>

 How exactly do you have the usb port wired?


 https://github.com/beagleboard/pocketbeagle/wiki/FAQ#How_do_I_get_additional_USB_connections

 Regards, 

 -- 
 Robert Nelson
 https://rcn-ee.com/

>>>

-- 
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/5ae6da1b-8838-4739-8471-950adee3a04an%40googlegroups.com.

Re: [beagleboard] Re: Pocketbeagle Wifi Dongle Problems

2021-06-10 Thread Patrick Bolton 
reconnected again.

Problem fixed!


Power into P1.01 from 5VDC 8A max supply & the usb-pc tether, of course.

Female USB socket tied in per above image.

With nothing connected:
root@beaglebone:/var/lib/cloud9# udevadm trigger
root@beaglebone:/var/lib/cloud9# dmesg
Errors
[0.001520] timer_probe: no matching timers found
[0.160126] l4_wkup_cm:clk:0010:0: failed to disable
[1.223591] omap_voltage_late_init: Voltage driver support not added



Plugged in dongle.  It's powere light flashed on and off a few times.
root@beaglebone:/var/lib/cloud9# udevadm trigger
root@beaglebone:/var/lib/cloud9# dmesg
Errors
[0.001520] timer_probe: no matching timers found
[0.160126] l4_wkup_cm:clk:0010:0: failed to disable
[1.223591] omap_voltage_late_init: Voltage driver support not added


But the dongle is now showing up on lsusb
Bus 002 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and 

ifconfig -a lists the WLAN
wlan0: flags=-28669  mtu 1500
ether 50:3e:aa:b1:3d:ec  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I'm in business.  Thank you.

On Thursday, June 10, 2021 at 11:50:22 AM UTC-7 Patrick Bolton wrote:

> I have also connected 5 8A potential supply power directly to P1.01 and 
> have the usb connected.
>
> On Thursday, June 10, 2021 at 11:32:22 AM UTC-7 Patrick Bolton wrote:
>
>> Yes, I tried it exactly per that same image with a variety of power 
>> supplies.
>>
>> I have also been using the hubs from tindie, just in case I'm being 
>> simple minded, but I've quadruple confirmed.  Measure twice cut once.
>>
>>
>>
>>
>> On Thursday, June 10, 2021 at 11:27:03 AM UTC-7 RobertCNelson wrote:
>>
>>> On Thu, Jun 10, 2021 at 11:22 AM Patrick Bolton  
>>> wrote:
>>>
 Well I was hopeful the kernel update today would help with the issues, 
 but no such luck.

 I powered the board at VIN with a 5VDC 8A power suppy with the 4-usb 
 port version of 2/4-port USB 2.0 HUB Cape for PocketBeagle from 
 microwavemont on Tindie 
 

 Have additional over-current errors.

 If I am not supplying the information that is helpful for solving the 
 problem, please let me know.

>>>
>>> How exactly do you have the usb port wired?
>>>
>>>
>>> https://github.com/beagleboard/pocketbeagle/wiki/FAQ#How_do_I_get_additional_USB_connections
>>>
>>> Regards, 
>>>
>>> -- 
>>> Robert Nelson
>>> https://rcn-ee.com/
>>>
>>

-- 
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/a150305c-97d3-47b8-9d46-cdfa2aab3350n%40googlegroups.com.

Re: [beagleboard] Re: Pocketbeagle Wifi Dongle Problems

2021-06-10 Thread Robert Nelson 
On Thu, Jun 10, 2021 at 11:22 AM Patrick Bolton <
[email protected]> wrote:

> Well I was hopeful the kernel update today would help with the issues, but
> no such luck.
>
> I powered the board at VIN with a 5VDC 8A power suppy with the 4-usb port
> version of 2/4-port USB 2.0 HUB Cape for PocketBeagle from microwavemont
> on Tindie
> 
>
> Have additional over-current errors.
>
> If I am not supplying the information that is helpful for solving the
> problem, please let me know.
>

How exactly do you have the usb port wired?

https://github.com/beagleboard/pocketbeagle/wiki/FAQ#How_do_I_get_additional_USB_connections

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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/CAOCHtYg4EckSRsrGvH0nY%3DyXLxCFzhMjd%3Dk147G8nOpD0s7L4w%40mail.gmail.com.

Re: [beagleboard] Re: Pocketbeagle Wifi Dongle Problems

2021-06-03 Thread Patrick Bolton 
My apologies, the 5V 0.8A hub is mislabeled.  

It is 5V 3A output.   The 0.8A was the input 120VAC rating.

On Thursday, June 3, 2021 at 8:55:03 AM UTC-7 Patrick Bolton wrote:

> Yes.
>
> These are the voltage readings with nothing connected on several power 
> supplies options I have:
>
> Voltage Readings
> Pin  Function  USB Power  5V 0.8A HUB  5V 
> 8A power supply
> P1-5Vbus00
>0
> P1-7VIN   4.97  5.152  
>  5.163
> P1-14  3.3V 3.4223.422
>3.422
> P 1.24 Vout 4.9255.108
>5.118
>
> I can not talk to the pb when its on the 5V 8A, but nothing shows up in 
> either on usb power or on a usb power hub.
>
> I just connected it to see if it had any voltage impact.
>
> Thank you.
>
> Pat
>
>
>
>
>
> On Wednesday, June 2, 2021 at 12:01:12 PM UTC-7 [email protected] wrote:
>
>> Have you tried connecting a Powered USB HUB to the USB board attached to 
>> the PocketBeagle so the WiFi module is not drawing current directly from 
>> the PB?
>>
>> It seems there is an over-current condition being reported:
>> * 126.004560] usb usb2-port1: over-current condition*
>>
>> Cheers,
>>
>> Jon
>>
>> On Wed, Jun 2, 2021 at 10:19 AM Patrick Bolton  
>> wrote:
>>
>>> I do not have a standoff on a pocket beagle.
>>>
>>> But the problem is recurring on all models right side up, upside down 
>>> with and without 2/4-port USB 2.0 HUB Cape for PocketBeagle from 
>>> microwavemont on Tindie 
>>> 
>>>  installed 
>>> or a female pin block that keeps any pins or pads from contacting the 
>>> static pad.
>>>
>>> lsusb -v & udevadm trigger --> dmesg  below
>>>
>>> I simply can not believe that the random selection process of purchasing 
>>> 4 pb's over a course of a year yielded four defective devices in my 
>>> possession.  
>>>
>>> OK, I'll admit it: I purchased 6 and burned up 2 pulling too much power 
>>> from a gpio.  That's my simple attempt at humor.
>>>
>>>
>>> [image: IMG_6921.jpg]
>>>
>>> root@beaglebone:/var/lib/cloud9# lsusb -v
>>>
>>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Device Descriptor:
>>>   bLength18
>>>   bDescriptorType 1
>>>   bcdUSB   2.00
>>>   bDeviceClass9 Hub
>>>   bDeviceSubClass 0
>>>   bDeviceProtocol 1 Single TT
>>>   bMaxPacketSize064
>>>   idVendor   0x1d6b Linux Foundation
>>>   idProduct  0x0002 2.0 root hub
>>>   bcdDevice4.19
>>>   iManufacturer   3 Linux 4.19.94-ti-r64 musb-hcd
>>>   iProduct2 MUSB HDRC host driver
>>>   iSerial 1 musb-hdrc.1
>>>   bNumConfigurations  1
>>>   Configuration Descriptor:
>>> bLength 9
>>> bDescriptorType 2
>>> wTotalLength   0x0019
>>> bNumInterfaces  1
>>> bConfigurationValue 1
>>> iConfiguration  0
>>> bmAttributes 0xe0
>>>   Self Powered
>>>   Remote Wakeup
>>> MaxPower0mA
>>> Interface Descriptor:
>>>   bLength 9
>>>   bDescriptorType 4
>>>   bInterfaceNumber0
>>>   bAlternateSetting   0
>>>   bNumEndpoints   1
>>>   bInterfaceClass 9 Hub
>>>   bInterfaceSubClass  0
>>>   bInterfaceProtocol  0 Full speed (or root) hub
>>>   iInterface  0
>>>   Endpoint Descriptor:
>>> bLength 7
>>> bDescriptorType 5
>>> bEndpointAddress 0x81  EP 1 IN
>>> bmAttributes3
>>>   Transfer TypeInterrupt
>>>   Synch Type   None
>>>   Usage Type   Data
>>> wMaxPacketSize 0x0004  1x 4 bytes
>>> bInterval  12
>>> Hub Descriptor:
>>>   bLength   9
>>>   bDescriptorType  41
>>>   nNbrPorts 1
>>>   wHubCharacteristic 0x0011
>>> Per-port power switching
>>> No overcurrent protection
>>> TT think time 8 FS bits
>>>   bPwrOn2PwrGood5 * 2 milli seconds
>>>   bHubContrCurrent  0 milli Ampere
>>>   DeviceRemovable0x02
>>>   PortPwrCtrlMask0xff
>>>  Hub Port Status:
>>>Port 1: .010c power oc suspend
>>> can't get device qualifier: Resource temporarily unavailable
>>> can't get debug descriptor: Resource temporarily unavailable
>>> Device Status: 0x0001
>>>   Self Powered
>>>
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Device Descriptor:
>>>   bLength18
>>>   bDescriptorType 1
>>>   bcdUSB   2.00
>>>   bDeviceClass9

Re: [beagleboard] Re: Pocketbeagle Wifi Dongle Problems

2021-06-03 Thread Patrick Bolton 
Yes.

These are the voltage readings with nothing connected on several power 
supplies options I have:

Voltage Readings
Pin  Function  USB Power  5V 0.8A HUB  5V 
8A power supply
P1-5Vbus00  
 0
P1-7VIN   4.97  5.152  
 5.163
P1-14  3.3V 3.4223.422  
 3.422
P 1.24 Vout 4.9255.108  
 5.118

I can not talk to the pb when its on the 5V 8A, but nothing shows up in 
either on usb power or on a usb power hub.

I just connected it to see if it had any voltage impact.

Thank you.

Pat





On Wednesday, June 2, 2021 at 12:01:12 PM UTC-7 [email protected] wrote:

> Have you tried connecting a Powered USB HUB to the USB board attached to 
> the PocketBeagle so the WiFi module is not drawing current directly from 
> the PB?
>
> It seems there is an over-current condition being reported:
> * 126.004560] usb usb2-port1: over-current condition*
>
> Cheers,
>
> Jon
>
> On Wed, Jun 2, 2021 at 10:19 AM Patrick Bolton  
> wrote:
>
>> I do not have a standoff on a pocket beagle.
>>
>> But the problem is recurring on all models right side up, upside down 
>> with and without 2/4-port USB 2.0 HUB Cape for PocketBeagle from 
>> microwavemont on Tindie 
>> 
>>  installed 
>> or a female pin block that keeps any pins or pads from contacting the 
>> static pad.
>>
>> lsusb -v & udevadm trigger --> dmesg  below
>>
>> I simply can not believe that the random selection process of purchasing 
>> 4 pb's over a course of a year yielded four defective devices in my 
>> possession.  
>>
>> OK, I'll admit it: I purchased 6 and burned up 2 pulling too much power 
>> from a gpio.  That's my simple attempt at humor.
>>
>>
>> [image: IMG_6921.jpg]
>>
>> root@beaglebone:/var/lib/cloud9# lsusb -v
>>
>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Device Descriptor:
>>   bLength18
>>   bDescriptorType 1
>>   bcdUSB   2.00
>>   bDeviceClass9 Hub
>>   bDeviceSubClass 0
>>   bDeviceProtocol 1 Single TT
>>   bMaxPacketSize064
>>   idVendor   0x1d6b Linux Foundation
>>   idProduct  0x0002 2.0 root hub
>>   bcdDevice4.19
>>   iManufacturer   3 Linux 4.19.94-ti-r64 musb-hcd
>>   iProduct2 MUSB HDRC host driver
>>   iSerial 1 musb-hdrc.1
>>   bNumConfigurations  1
>>   Configuration Descriptor:
>> bLength 9
>> bDescriptorType 2
>> wTotalLength   0x0019
>> bNumInterfaces  1
>> bConfigurationValue 1
>> iConfiguration  0
>> bmAttributes 0xe0
>>   Self Powered
>>   Remote Wakeup
>> MaxPower0mA
>> Interface Descriptor:
>>   bLength 9
>>   bDescriptorType 4
>>   bInterfaceNumber0
>>   bAlternateSetting   0
>>   bNumEndpoints   1
>>   bInterfaceClass 9 Hub
>>   bInterfaceSubClass  0
>>   bInterfaceProtocol  0 Full speed (or root) hub
>>   iInterface  0
>>   Endpoint Descriptor:
>> bLength 7
>> bDescriptorType 5
>> bEndpointAddress 0x81  EP 1 IN
>> bmAttributes3
>>   Transfer TypeInterrupt
>>   Synch Type   None
>>   Usage Type   Data
>> wMaxPacketSize 0x0004  1x 4 bytes
>> bInterval  12
>> Hub Descriptor:
>>   bLength   9
>>   bDescriptorType  41
>>   nNbrPorts 1
>>   wHubCharacteristic 0x0011
>> Per-port power switching
>> No overcurrent protection
>> TT think time 8 FS bits
>>   bPwrOn2PwrGood5 * 2 milli seconds
>>   bHubContrCurrent  0 milli Ampere
>>   DeviceRemovable0x02
>>   PortPwrCtrlMask0xff
>>  Hub Port Status:
>>Port 1: .010c power oc suspend
>> can't get device qualifier: Resource temporarily unavailable
>> can't get debug descriptor: Resource temporarily unavailable
>> Device Status: 0x0001
>>   Self Powered
>>
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Device Descriptor:
>>   bLength18
>>   bDescriptorType 1
>>   bcdUSB   2.00
>>   bDeviceClass9 Hub
>>   bDeviceSubClass 0
>>   bDeviceProtocol 1 Single TT
>>   bMaxPacketSize064
>>   idVendor   0x1d6b Linux Foundation
>>   idProduct  0x0002 2.0 root hub
>>   bcdDevice4.19
>>   iManufacturer   3 Linux 4.19.94-ti-r64 musb-hcd
>>   iProduct2 MUSB HDRC host dri