Re: [beagleboard] Re: bbgw wlan0 users

2018-02-18 Thread migue . fonseca 
This actually solved my problem, now it is working just perfect!!. Please 
see this post: 

So on the BeagleBone Family, we use an eeprom id to detect what board you 
have.  In your case, the board eeprom got mis-written too.

Which is easy to fix, near the 5Volt header there are 4 copper holes (TP2 
-> TP5) that's for a LiPo battery, next to that is IC4, followed by TP1.

TP1: is write protect pin for the i2c eeprom.  To allow us to write a 
correct ID, we need to GND that pin (TP1)

On the P9 header:

http://beagleboard.org/static/images/cape-headers.png

Pin's 1 & 2 are GND, connect either P9.1/P9.2 to TP1 with a short piece of 
wire.  Then you can exicute


*sudo dd 
if=/opt/scripts/device/bone/bbbw-eeprom.dump 
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom*

El domingo, 18 de febrero de 2018, 13:36:50 (UTC-6), sbsa...@gmail.com 
escribió:
>
> Did anyone get this going?  Honestly, I have spent a few hours and the 
> image for the BBBW bone-debian-9.3-lxqt-armhf-2018-01-28-4gb.img also gives 
> the same error:
>
> Method "SetProperty" with signature "sv" on interface 
> "net.connman.Technology" doesn't exist
>
> With the word wireless in it, I feel it would be easier to get it going? :(
>
> On Monday, May 29, 2017 at 12:24:26 PM UTC-4, RobertCNelson wrote:
>>
>>
>>
>> On Mon, May 29, 2017 at 12:02 AM, Migue Fonseca  
>> wrote:
>>
>>> Hey my friend, thanks for your quick reply. I retested everything with 
>>> the new image, same result:
>>> [image: Imágenes integradas 1]
>>>
>>> Could this be a driver issue? Let me know what you think.
>>>
>>
>> Please run version.sh:
>>
>> debian@test-bbbw-11:/opt/scripts/tools$ sudo ./version.sh
>> git:/opt/scripts/:[0e222d4aeb4f1c06dcdd025e0b1e1835404e1551]
>> eeprom:[A335BNLTBWA0*]
>> dogtag:[BeagleBoard.org Debian Image 2016-10-23]
>> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
>> 2017.05-2-g962663a0e0]
>> kernel:[4.4.62-ti-rt-r105]
>> nodejs:[v0.12.18]
>>
>> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/504fb711-070a-4e38-824c-c2c467f49a95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2018-02-18 Thread sbsaylors 
Did anyone get this going?  Honestly, I have spent a few hours and the 
image for the BBBW bone-debian-9.3-lxqt-armhf-2018-01-28-4gb.img also gives 
the same error:

Method "SetProperty" with signature "sv" on interface 
"net.connman.Technology" doesn't exist

With the word wireless in it, I feel it would be easier to get it going? :(

On Monday, May 29, 2017 at 12:24:26 PM UTC-4, RobertCNelson wrote:
>
>
>
> On Mon, May 29, 2017 at 12:02 AM, Migue Fonseca  > wrote:
>
>> Hey my friend, thanks for your quick reply. I retested everything with 
>> the new image, same result:
>> [image: Imágenes integradas 1]
>>
>> Could this be a driver issue? Let me know what you think.
>>
>
> Please run version.sh:
>
> debian@test-bbbw-11:/opt/scripts/tools$ sudo ./version.sh
> git:/opt/scripts/:[0e222d4aeb4f1c06dcdd025e0b1e1835404e1551]
> eeprom:[A335BNLTBWA0*]
> dogtag:[BeagleBoard.org Debian Image 2016-10-23]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2017.05-2-g962663a0e0]
> kernel:[4.4.62-ti-rt-r105]
> nodejs:[v0.12.18]
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/fd13412b-8677-43c8-b50f-fb92d88e1264%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2017-05-29 Thread Robert Nelson 
On Mon, May 29, 2017 at 12:02 AM, Migue Fonseca 
wrote:

> Hey my friend, thanks for your quick reply. I retested everything with the
> new image, same result:
> [image: Imágenes integradas 1]
>
> Could this be a driver issue? Let me know what you think.
>

Please run version.sh:

debian@test-bbbw-11:/opt/scripts/tools$ sudo ./version.sh
git:/opt/scripts/:[0e222d4aeb4f1c06dcdd025e0b1e1835404e1551]
eeprom:[A335BNLTBWA0*]
dogtag:[BeagleBoard.org Debian Image 2016-10-23]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2017.05-2-g962663a0e0]
kernel:[4.4.62-ti-rt-r105]
nodejs:[v0.12.18]

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiyS2%3DG1PEsv-ZZGtgW9XzLUtt4msY%2B1503M7L9uSrj3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2017-05-28 Thread Robert Nelson 
On Sun, May 28, 2017 at 7:51 PM,   wrote:
> Hey Robert, unfortunatelly I just lost ~$75 with the BBBW. It has been a
> terrible experience just to trying to make the Wifi/connmanctl work. I've
> used maybe 4 different distros images with no luck. Would you please help me
> understand what is happening with this board? I've found so many posts
> refering to this error "Error disabling wifi tethering: Method "SetProperty"
> with signature "sv" on interface "net.connman.Technology" doesn't exist" but
> no one seems to know what is happening. Thanks for any help you can give us.

So grab this image:

https://rcn-ee.net/rootfs/bb.org/testing/2017-05-28/lxqt-4gb/BBB-blank-debian-8.8-lxqt-4gb-armhf-2017-05-28-4gb.img.xz

Burn it to an sdcard with etcher.io

let it flash the eMMC

Then retest:

sudo connmanctl
connmanctl> enable wifi
connmanctl> scan wifi
connmanctl> services
connmanctl> agent on
connmanctl> connect wifi_*_managed_psk
connmanctl> quit

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjOmGXKkemT17m5DeBLQTwixcGnzpZ8e7zCsJ7%2BN06pFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2017-01-04 Thread Robert Nelson 
On Wed, Jan 4, 2017 at 3:02 AM, Linq John  wrote:
>
> I got similar testing results as imjoh...@gmail.com
> Most image failed to boot.
>
> BBGW-blank-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
> and
> bone-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
> booted successfully,
> but wlan0 did not work.
>
> I did a lot of manual work on
> BBGW-blank-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
> after that, I could make wlan0 working, but I didn't know what I was doing,
> just guessing, trial and error.
> And even wlan0 is working, it is not stable.
>
> I have to work on some other projects.
> Hope SEEED would provide a real fix.

The "seeed" variants add a WiFi captive portal along with their
documentation on the usb flash drive that pop's up.  Otherwise they
are exactly the same as the non-seeed images.

That WiFi captive portal can make things interesting if you try to
manually control the wlan0..

Give the generic iot image a try:

https://rcn-ee.net/rootfs/bb.org/testing/2017-01-03/iot/

To see if i've fixed some of the issues..

Remember to use connman to control wlan0

sudo connmanctl
#connmanctl> scan wifi
#connmanctl> services
#connmanctl> agent on
#connmanctl> connect wifi_*_managed_psk
#connmanctl> quit


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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgPUe3CT%3DcNDx-AMhiKe1DEZeqyfsq-qx6RcMNKyc5mdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2017-01-04 Thread Robert Nelson 
J,

On Mon, Jan 2, 2017 at 7:33 PM,   wrote:
> Robert,
> I tried that build and also the last one from yesterday (1/1) but I cannot
> make the wlan0 work on any of those builds.
> When I do a ifconfig I get this:
>
> root@beaglebone:~# ifconfig wlan0 up
> SIOCSIFFLAGS: No such file or directory
>
> And this is the dmesg:
>
> [   29.792544] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> ti-connectivity/wl1271-nvs.bin failed with error -2
> [   30.147603] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
> [   30.243578] wlcore: loaded
> [  188.343428] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  188.343465] wlcore: ERROR could not get firmware
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  188.711351] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  188.711388] wlcore: ERROR could not get firmware
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  189.075369] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  189.075406] wlcore: ERROR could not get firmware
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  189.086887] wlcore: ERROR firmware boot failed despite 3 retries
>
>
> What do you think could be the problem here? Is this a problem with the
> ti-connectivity version?

What image was this?  It's missing the firmware.. Grab the iot from last night:

https://rcn-ee.net/rootfs/bb.org/testing/2017-01-03/iot/

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjQ7%3D9ONpPfAQMmrz1jjJBEUWM95EsFGHMu8TEnW3ZzNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2017-01-04 Thread Linq John 

I got similar testing results as imjoh...@gmail.com
Most image failed to boot.

BBGW-blank-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
and
bone-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
booted successfully,
but wlan0 did not work.

I did a lot of manual work on 
BBGW-blank-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
after that, I could make wlan0 working, but I didn't know what I was doing, 
just guessing*,* trial and error.
And even wlan0 is working, it is not stable.

I have to work on some other projects.
Hope SEEED would provide a real fix.


imjoh...@gmail.com於 2017年1月3日星期二 UTC+8上午10時04分45秒寫道：
>
> Robert,
> I tried that build and also the last one from yesterday (1/1) but I cannot 
> make the wlan0 work on any of those builds.
> When I do a ifconfig I get this:
>
> root@beaglebone:~# ifconfig wlan0 up
> SIOCSIFFLAGS: No such file or directory
>
> And this is the dmesg:
>
> [   29.792544] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl1271-nvs.bin failed with error -2
> [   30.147603] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
> [   30.243578] wlcore: loaded
> [  188.343428] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  188.343465] wlcore: ERROR could not get firmware 
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  188.711351] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  188.711388] wlcore: ERROR could not get firmware 
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  189.075369] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  189.075406] wlcore: ERROR could not get firmware 
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  189.086887] wlcore: ERROR firmware boot failed despite 3 retries
>
>
> What do you think could be the problem here? Is this a problem with the 
> ti-connectivity version?
> Thanks for your help and time!
> Regards,
> J
>
> On Friday, December 30, 2016 at 6:44:55 AM UTC-8, RobertCNelson wrote:
>>
>> On Fri, Dec 30, 2016 at 2:37 AM, Linq John  wrote: 
>> > 
>> > I brought a Beaglebone Green Wireless. 
>> > At the first day, its wifi worked, so I did some apt-get 
>> > update/upgrade/dis-upgrade. 
>> > My main purpose is to use it to do some python work. UART/I2C/GPIO etc. 
>> > So I didn't discover that the wifi no longer working after the apt-get 
>> > upgrade. 
>> > I spent two working days trying to make its wifi working again, but no 
>> > success. 
>> > I didn't record the version info of the original working Debian. 
>> > And I can't find the pre-load image from 
>> > https://debian.beagleboard.org/images/ 
>> > What I can find are: 
>> > bone-debian-8.5-seeed-gcp-iot-armhf-2016-08-26-4gb.img.xz - failed to 
>> boot 
>> > bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz - failed to boot 
>> > bone-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz - wifi doesn't 
>> work 
>> > I also tried to use the kernel in *-iot-armhf-2016-12-09-* with 
>> > *seeed-iot-armhf-2016-11-06*, but no success. 
>> > (By changing uname_r of uEnv.txt, and even by renaming the files.) 
>> > After all these I found a thread in TI E2E: 
>> > 
>> https://e2e.ti.com/support/wireless_connectivity/wilink_wifi_bluetooth/f/307/p/541235/1978301
>>  
>> > So I guess it's a hardware problem, but without wifi, there is no 
>> internet 
>> > connection on BBGW, 
>> > then I am not able to install python packages, my BBGW becomes useless. 
>> > 
>> > And I guess the below images are not for BBGW. 
>> > https://rcn-ee.net/rootfs/2016-11-10/microsd/ 
>> > 
>> > Is there any work-around available for a general user? 
>>
>> Use this build: 
>>
>> https://rcn-ee.net/rootfs/bb.org/testing/2016-12-27/ 
>>
>> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5affe43c-e6a6-4437-b12f-de8ea8ceeb7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2017-01-02 Thread imjohncable 
Robert,
I tried that build and also the last one from yesterday (1/1) but I cannot 
make the wlan0 work on any of those builds.
When I do a ifconfig I get this:

root@beaglebone:~# ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory

And this is the dmesg:

[   29.792544] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
ti-connectivity/wl1271-nvs.bin failed with error -2
[   30.147603] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   30.243578] wlcore: loaded
[  188.343428] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
ti-connectivity/wl18xx-fw-4.bin failed with error -2
[  188.343465] wlcore: ERROR could not get firmware 
ti-connectivity/wl18xx-fw-4.bin: -2
[  188.711351] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
ti-connectivity/wl18xx-fw-4.bin failed with error -2
[  188.711388] wlcore: ERROR could not get firmware 
ti-connectivity/wl18xx-fw-4.bin: -2
[  189.075369] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
ti-connectivity/wl18xx-fw-4.bin failed with error -2
[  189.075406] wlcore: ERROR could not get firmware 
ti-connectivity/wl18xx-fw-4.bin: -2
[  189.086887] wlcore: ERROR firmware boot failed despite 3 retries


What do you think could be the problem here? Is this a problem with the 
ti-connectivity version?
Thanks for your help and time!
Regards,
J

On Friday, December 30, 2016 at 6:44:55 AM UTC-8, RobertCNelson wrote:
>
> On Fri, Dec 30, 2016 at 2:37 AM, Linq John  > wrote: 
> > 
> > I brought a Beaglebone Green Wireless. 
> > At the first day, its wifi worked, so I did some apt-get 
> > update/upgrade/dis-upgrade. 
> > My main purpose is to use it to do some python work. UART/I2C/GPIO etc. 
> > So I didn't discover that the wifi no longer working after the apt-get 
> > upgrade. 
> > I spent two working days trying to make its wifi working again, but no 
> > success. 
> > I didn't record the version info of the original working Debian. 
> > And I can't find the pre-load image from 
> > https://debian.beagleboard.org/images/ 
> > What I can find are: 
> > bone-debian-8.5-seeed-gcp-iot-armhf-2016-08-26-4gb.img.xz - failed to 
> boot 
> > bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz - failed to boot 
> > bone-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz - wifi doesn't 
> work 
> > I also tried to use the kernel in *-iot-armhf-2016-12-09-* with 
> > *seeed-iot-armhf-2016-11-06*, but no success. 
> > (By changing uname_r of uEnv.txt, and even by renaming the files.) 
> > After all these I found a thread in TI E2E: 
> > 
> https://e2e.ti.com/support/wireless_connectivity/wilink_wifi_bluetooth/f/307/p/541235/1978301
>  
> > So I guess it's a hardware problem, but without wifi, there is no 
> internet 
> > connection on BBGW, 
> > then I am not able to install python packages, my BBGW becomes useless. 
> > 
> > And I guess the below images are not for BBGW. 
> > https://rcn-ee.net/rootfs/2016-11-10/microsd/ 
> > 
> > Is there any work-around available for a general user? 
>
> Use this build: 
>
> https://rcn-ee.net/rootfs/bb.org/testing/2016-12-27/ 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0f0e7b9b-3b9a-43b7-b658-66eccc71fdd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2016-12-30 Thread Robert Nelson 
On Fri, Dec 30, 2016 at 2:37 AM, Linq John  wrote:
>
> I brought a Beaglebone Green Wireless.
> At the first day, its wifi worked, so I did some apt-get
> update/upgrade/dis-upgrade.
> My main purpose is to use it to do some python work. UART/I2C/GPIO etc.
> So I didn't discover that the wifi no longer working after the apt-get
> upgrade.
> I spent two working days trying to make its wifi working again, but no
> success.
> I didn't record the version info of the original working Debian.
> And I can't find the pre-load image from
> https://debian.beagleboard.org/images/
> What I can find are:
> bone-debian-8.5-seeed-gcp-iot-armhf-2016-08-26-4gb.img.xz - failed to boot
> bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz - failed to boot
> bone-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz - wifi doesn't work
> I also tried to use the kernel in *-iot-armhf-2016-12-09-* with
> *seeed-iot-armhf-2016-11-06*, but no success.
> (By changing uname_r of uEnv.txt, and even by renaming the files.)
> After all these I found a thread in TI E2E:
> https://e2e.ti.com/support/wireless_connectivity/wilink_wifi_bluetooth/f/307/p/541235/1978301
> So I guess it's a hardware problem, but without wifi, there is no internet
> connection on BBGW,
> then I am not able to install python packages, my BBGW becomes useless.
>
> And I guess the below images are not for BBGW.
> https://rcn-ee.net/rootfs/2016-11-10/microsd/
>
> Is there any work-around available for a general user?

Use this build:

https://rcn-ee.net/rootfs/bb.org/testing/2016-12-27/

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhzVm-wEkPD4vFZi51RQwnKfd6Mbx5WCae6q39EjRhtMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2016-09-29 Thread Robert Nelson 
Okay, 4.4.22-ti-r49 has hit the repo:

With, (the default)

dtb=am335x-bonegreen-wireless.dtb

debian@beaglebone:~$ dmesg | grep wl
[2.446968] wlan-en-regulator: disabling
[   35.950050] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   36.027459] wlcore: loaded
[   36.425547] wlcore: PHY firmware version: Rev 8.2.0.0.236
[   36.465441] wlcore: firmware booted (Rev 8.9.0.0.69)
[   36.479113] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   37.165183] wlcore: ERROR ELP wakeup timeout!
[   37.169902] WARNING: CPU: 0 PID: 1093 at
drivers/net/wireless/ti/wlcore/main.c:797
wl12xx_queue_recovery_work.part.8+0x46/0x48 [wlcore]()
[   37.169914] Modules linked in: arc4 wl18xx wlcore bnep mac80211
cfg80211 hci_uart btbcm btqca bluetooth rfkill 8021q garp mrp stp llc
snd_soc_evm snd_soc_wilink8_bt omap_sham omap_aes_driver asix usbnet
mii omap_rng rng_core snd_soc_davinci_mcasp snd_soc_edma snd_soc_omap
wlcore_sdio snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd
soundcore evdev uio_pdrv_genirq uio usb_f_acm u_serial usb_f_rndis
g_multi usb_f_mass_storage u_ether libcomposite
[   37.170282] [] (warn_slowpath_null) from []
(wl12xx_queue_recovery_work.part.8+0x46/0x48 [wlcore])
[   37.170465] [] (wl12xx_queue_recovery_work.part.8
[wlcore]) from [] (wl12xx_queue_recovery_work+0x12/0x14
[wlcore])
[   37.170608] [] (wl12xx_queue_recovery_work [wlcore]) from
[] (wl1271_ps_elp_wakeup+0x192/0x198 [wlcore])
[   37.170750] [] (wl1271_ps_elp_wakeup [wlcore]) from
[] (wl1271_op_add_interface+0x78/0x774 [wlcore])
[   37.171374] [] (wl1271_op_add_interface [wlcore]) from
[] (drv_add_interface+0x38/0x118 [mac80211])
[   37.177169] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.69
[   37.177456] WARNING: CPU: 0 PID: 6 at
drivers/net/wireless/ti/wlcore/io.h:65 wlcore_set_partition+0x6e/0x374
[wlcore]()
[   37.177465] Modules linked in: arc4 wl18xx wlcore bnep mac80211
cfg80211 hci_uart btbcm btqca bluetooth rfkill 8021q garp mrp stp llc
snd_soc_evm snd_soc_wilink8_bt omap_sham omap_aes_driver asix usbnet
mii omap_rng rng_core snd_soc_davinci_mcasp snd_soc_edma snd_soc_omap
wlcore_sdio snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd
soundcore evdev uio_pdrv_genirq uio usb_f_acm u_serial usb_f_rndis
g_multi usb_f_mass_storage u_ether libcomposite
[   37.177713] Workqueue: phy0 wl1271_recovery_work [wlcore]
[   37.177924] [] (warn_slowpath_null) from []
(wlcore_set_partition+0x6e/0x374 [wlcore])
[   37.178071] [] (wlcore_set_partition [wlcore]) from
[] (wl1271_recovery_work+0x60/0x250 [wlcore])
[   37.178162] [] (wl1271_recovery_work [wlcore]) from
[] (process_one_work+0xf1/0x328)
[   37.178242] wlcore: down
[   41.032208] wlcore: ERROR timeout waiting for the hardware to
complete initialization
[   44.369031] wlcore: ERROR timeout waiting for the hardware to
complete initialization
[   46.452849] wlcore: ERROR timeout waiting for the hardware to
complete initialization
[   46.462838] wlcore: ERROR firmware boot failed despite 3 retries
[   46.469625] Modules linked in: arc4 wl18xx wlcore bnep mac80211
cfg80211 hci_uart btbcm btqca bluetooth rfkill 8021q garp mrp stp llc
snd_soc_evm snd_soc_wilink8_bt omap_sham omap_aes_driver asix usbnet
mii omap_rng rng_core snd_soc_davinci_mcasp snd_soc_edma snd_soc_omap
wlcore_sdio snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd
soundcore evdev uio_pdrv_genirq uio usb_f_acm u_serial usb_f_rndis
g_multi usb_f_mass_storage u_ether libcomposite
[   46.475593] wlan0:  Failed check-sdata-in-driver check, flags: 0x0
[   46.475600] Modules linked in: arc4 wl18xx wlcore bnep mac80211
cfg80211 hci_uart btbcm btqca bluetooth rfkill 8021q garp mrp stp llc
snd_soc_evm snd_soc_wilink8_bt omap_sham omap_aes_driver asix usbnet
mii omap_rng rng_core snd_soc_davinci_mcasp snd_soc_edma snd_soc_omap
wlcore_sdio snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd
soundcore evdev uio_pdrv_genirq uio usb_f_acm u_serial usb_f_rndis
g_multi usb_f_mass_storage u_ether libcomposite


and with:

dtb=am335x-bonegreen-wireless-led-hack.dtb

debian@beaglebone:~$ dmesg | grep wl
[   35.993746] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   36.063117] wlcore: loaded
[   36.461283] wlcore: PHY firmware version: Rev 8.2.0.0.236
[   36.501070] wlcore: firmware booted (Rev 8.9.0.0.69)
[   36.515063] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   36.794484] wlcore: down
[   37.519933] wlcore: down
[   37.576262] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   37.578035] device wlan0 entered promiscuous mode
[   37.804938] tether: port 1(wlan0) entered forwarding state
[   37.805046] tether: port 1(wlan0) entered forwarding state

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 beagleboard+unsubscr...@googlegroups.com.
To