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

[beagleboard] Re: Pocketbeagle Wifi Dongle Problems

2021-06-02 Thread Dennis Lee Bieber 
On Tue, 1 Jun 2021 09:33:31 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Patrick Bolton
 wrote:

>This morning,  I setup a brand spanking new pocketbeagle straight out of 
>the package and have very concerning errors on installation of the most 
>recent image.  Nothing whatsoever is connected other than the USB cable to 
>my PC. And the device is sitting on a grounded anti-static pad.
>

Do you have standoffs on that board...Sitting on an anti-static pad
could be making contact with some underside circuitry, causing unexpected
voltages on some pins.


-- 
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/s3efbgt3mlajr2sfg186aij9ud3pdmro1h%404ax.com.

[beagleboard] Re: Pocketbeagle Wifi Dongle Problems

2021-06-01 Thread Patrick Bolton 
They are also immediately restarting themselves upon shutdown either by 
software shutdown or button shutdown.

On Tuesday, June 1, 2021 at 9:33:31 AM UTC-7 Patrick Bolton wrote:

> I can not possibly be the unique case of these problems.  I'm certainly 
> not that special and it's rather frustrating.
>
> This morning,  I setup a brand spanking new pocketbeagle straight out of 
> the package and have very concerning errors on installation of the most 
> recent image.  Nothing whatsoever is connected other than the USB cable to 
> my PC. And the device is sitting on a grounded anti-static pad.
>
> [image: new PB.jpg]
>
>  *[  443.396338] usb usb2-port1: over-current condition*
> *[  443.440703] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (81, 
>  *[  443.593123] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (81, 
>  *[  443.745563] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (81, 
>  *[  443.897981] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (80, 
> 
> full dmesg below
>
> It is very concerning to have an overcurrent situation right out of the 
> box.
>
> Additional research indicates that these errors may be related to a 
> malfunctioning 25Mhz crystal oscillator used for USB timing.  At least 
> that's what I founnd on a TI site discussing their usb controllers related 
> to these errors.
>
> This is beyond my understanding of device construction, but can I be 
> burning up my usb timing crystal immediately on 1st plug in?
>
> Is this a typical subcomponent of a USB hub?  
>
> Or is this simply the confirmation of the lack of any RTC on the PB? 
>
> I proceeded with the usual set up:
>
> Set up:
> 1) Image:  
> https://debian.beagleboard.org/images/bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz
> 2) apt update
> 3) apt upgrade
> 4) reboot  <--- I didn't use init 6 lol
>
> The above errors were not present after upgrade, but the following errors 
> remain:
> [0.001560] timer_probe: no matching timers found
> [0.159609] l4_wkup_cm:clk:0010:0: failed to disable
> [1.215108] omap_voltage_late_init: Voltage driver support not added
> [1.708436] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (80, 
> 
>
> 5) cd /opt/scripts/tools / git pull || true
> 6) /opt/scripts/tools/update_kernel.sh
> 7) reboot
>
> same dmesg as after upgrade
>
> 8) /opt/scripts/tools/version.sh
> 9)  reboot
> 10) apt update
> 11) apt upgrade
> 12) reboot
>
>
>
>
>
>
>
>
> root@beaglebone:/var/lib/cloud9# udevadm trigger
> root@beaglebone:/var/lib/cloud9# dmesg
> [0.00] Booting Linux on physical CPU 0x0
> [0.00] Linux version 4.19.94-ti-r42 
> (voodoo@x3-am57xx-beagle-x15-2gb) (gcc version 8.3.0 (Debian 8.3.0-6)) 
> #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020
> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), 
> cr=10c5387d
> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
> instruction cache
> [0.00] OF: fdt: Machine model: TI AM335x PocketBeagle
> [0.00] Memory policy: Data cache writeback
> [0.00] cma: Reserved 48 MiB at 0x9c80
> [0.00] On node 0 totalpages: 130560
> [0.00]   Normal zone: 1148 pages used for memmap
> [0.00]   Normal zone: 0 pages reserved
> [0.00]   Normal zone: 130560 pages, LIFO batch:31
> [0.00] CPU: All CPU(s) started in SVC mode.
> [0.00] AM335X ES2.1 (sgx neon)
> [0.00] random: get_random_bytes called from 
> start_kernel+0xac/0x4b4 with crng_init=0
> [0.00] percpu: Embedded 17 pages/cpu s38988 r8192 d22452 u69632
> [0.00] pcpu-alloc: s38988 r8192 d22452 u69632 alloc=17*4096
> [0.00] pcpu-alloc: [0] 0
> [0.00] Built 1 zonelists, mobility grouping on.  Total pages: 
> 129412
> [0.00] Kernel command line: console=ttyO0,115200n8 
> root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
> net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet
> [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 
> bytes)
> [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 
> bytes)
> [0.00] Memory: 438576K/522240K available (13312K kernel code, 
> 1136K rwdata, 4308K rodata, 1024K init, 350K bss, 34512K reserved, 49152K 
> cma-reserved, 0K highmem)
> [0.00] Virtual kernel memory layout:
>vector  : 0x - 0x1000   (   4 kB)
>fixmap  : 0xffc0 - 0xfff0   (3072 kB)
>vmalloc : 0xe000 - 0xff80   ( 504 MB)
>lowmem  : 0xc000 - 0xdfe0   ( 510 MB)
>pkmap   : 0xbfe0 - 0xc000   (   2 MB)
>modules : 0xbf00 - 0xbfe0   (  14 MB)
>  .text : 0x(ptrval) - 0x(ptrval)   (14304 kB)
>  .init : 0x(ptrval) - 0x(ptrval)   (1024 kB)
>  .data : 0x(ptrval) - 0x(ptrval)   (1137 kB)
>   .bss : 0x(ptrval) - 0x(ptrval)

[beagleboard] Re: Pocketbeagle Wifi Dongle Problems

2021-05-31 Thread Dennis Lee Bieber 
On Mon, 31 May 2021 08:09:54 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Patrick Bolton
 wrote:

>I am having problems with wifi dongles with the pocketbeagle.

You've pasted a novel of logs, but nowhere do you state exactly what
"problems" means?

>
>I have two dongles:
>1) Edimax EW-7811Un:  
>EDIMAX - Wireless Adapters - N150 - N150 Wi-Fi Nano USB Adapter, Ideal for 
>Raspberry Pi 
>
>
>2) tp-link  TL-WN725N V3
>TL-WN725N | 150Mbps Wireless N Nano USB Adapter | TP-Link 
>

Have you read
https://static.tp-link.com/2018/201812/20181207/Installation%20Guide%20for%20Linux.pdf
(Granted, the OS/kernel specified in the R-Pi section is antique, but the
rest /might/ apply).

>
>I have tried them in two configurations:
>1)   I cut a usb-a female cable and wired it to the PB in accordance with:
>https://i1.wp.com/www.teachmemicro.com/wp-content/uploads/2018/03/pocketbeagle-usb-type-a.jpg?w=590&ssl=1
>2)  2-port usb hub from tindie
>2/4-port USB 2.0 HUB Cape for PocketBeagle from microwavemont on Tindie 
>
>
>Voltage Readings
>Pin  Function  USB Power  5V 0.8A HUB  5V 
>8A power supply

How are you powering the Beagle and hub? Note that USB 2.0 standard is
that only 0.5A is available (and often needs a powered hub to get that). If
the beagle is being powered from a USB connection, you will have much less
current available for any devices connected to it, as the Beagle itself
requires some fraction of the available power (it's why Beagle Bone Black
is recommended to use a barrel connector rather than USB when flashing the
eMMC). A 5V 8A supply is not doing much unless you've wired directly to the
hub 5V source (or P1-1

Since the WiFi adapter runs a micro-radio, you likely need a higher
current just for it, so powering from the USB into the Beagle may not be
viable. I know R-Pi boards with WiFi operate off a USB connection, but that
is not a data connection -- just a specialized power mode which modern hubs
can recognize and provide a touch more current.

>Image:  
>https://debian.beagleboard.org/images/bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz
>2) apt update
>3) apt upgrade
>4) init 6

Pardon, but why the "init 6" (especially as Debian has adopted the
systemd start up, deprecating "init" mode). 


>2) tp-link driver update
>Download for TL-WN725N | TP-Link 
>
>

Okay -- you've probably read the referenced PDF then, as the downloads
are source needing to be compiled. But I note 
"4. This is a beta version; unknown bugs may still exist. The formal
version is coming soon." 
and that was three years ago... Only the Mac version has seen updates newer
than the Linux beta. The beta is also only "tested" up to kernel 4.4.3, and
recent Beagle images are on what, 4.19.x

https://wiki.debian.org/WiFi (possibly a bit dated)
"""
Currently there are only a few modern wifi chipsets readily available that
work with free software systems. For USB wifi devices this list includes
the Realtek RTL8187B chipset (802.11G) and the Atheros AR9170 chipset
(802.11N). For Mini PCIe all cards with an Atheros chipset are supported. 
"""
"""
Edimax EW-7811Un

USB adapter

1 (9,[nPP],[B]), 1 (NOOBS,2015,[B]), 1 (2013,[B]), 1 (2016,[B]), 1 (2014),
1 (ARMv6,[B])

For a guide see multiple in the Amazon reviews. There seems to be a problem
with this dongle's range.
"""
"""
Device

Confirmed

Drawbacks/Comments

Guide

TP-Link TL WN821N

(./)

- The original code of the driver is copyrighted and later contributors
don't know by whom.
The driver download does not contain license information.
(Most C files are licensed under GNU General Public License (GPL), version
2.)
- Only works when disabling random MAC addresses.

1. Update: sudo apt-get update && apt-get upgrade && && apt-get
dist-upgrade and reboot if you updated the kernel
2. Connect the device. lsusb should show 2357:0107
3. Install required packages: sudo apt-get install gcc-6 git
build-essential
4. Get the latest driver from ?GitHub and install it:
git clone https://github.com/jeremyb31/rtl8192eu-linux-driver.git
cd rtl8192eu-linux-driver
sudo make
sudo make install
5. Reboot and check that the kernel module is loaded by running: lsmod
6. Use your network-interface to connect to the WLAN. You could use the
pre-installed NetworkManager for that.
(7.) Edit NetworkManager.conf as root: sudo kate
/etc/NetworkManager/NetworkManager.conf
Append the following:
[device]
wifi.scan-rand-mac-address=no
Save and run: /etc/init.d/network-manager restart
"""


>root@beaglebone:/var/lib/cloud9# lsusb
>Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>Bus 001 Device 001: ID 1d6b