Sorry for the delay, I didn't get a notification of your posting. I believe the real problem has been found, and it is unrelated to USB audio.
My system was configured to launch the AlexaBeagleBone project automatically on boot as a service. The AlexaBeagleBone service attempts to connect to Amazon immediately, which is a problem, because the wireless modules does not have an IP address yet. In the case where I remove the USB audio, the AlexaBeagleBone service fails to launch, because it cannot open the audio card. I realized all this because I'm having another similar issue where wlcore crashes when I try to launch the OpenSprinkler firmware during boot. I've tried creating a systemd service to wait for connman to setup wifi, but so far no luck... If anyone knows how to create a proper systemd script that waits for connman to establish a wifi connection, I'd be pretty happy :) For now I'll try to accomplish the same in a separate script. Regards, Mike On Wednesday, July 27, 2016 at 1:20:48 AM UTC-5, jug wrote: > > Hey Mike > > Here is the lastest firmware of bbgw updated by Seeed > https://rcn-ee.net/rootfs/bb.org/testing/2016-07-21/seeed-iot/ > You can try it. > > 在 2016年7月22日星期五 UTC+8上午2:19:18,Mike Erdahl写道: >> >> Testing with a powered USB 2.0 hub did not change the behavior, >> unfortunately. >> >> I'm beginning to think my WiLink8 module might be defective, or the >> driver has some serious issue. Listening to an audio stream, using VLC, >> the radio basically died: >> >> [ 594.594514] wlcore: ERROR ELP wakeup timeout! >> >> >> [ 596.130637] wlcore: ERROR ELP wakeup timeout! >> >> >> [ 597.679125] wlcore: ERROR ELP wakeup timeout! >> >> >> [ 599.815511] wlcore: ERROR timeout waiting for the hardware to complete >> initialization >> >> [ 601.902753] wlcore: ERROR timeout waiting for the hardware to complete >> initialization >> >> [ 603.993727] wlcore: ERROR timeout waiting for the hardware to complete >> initialization >> >> [ 604.002765] wlcore: ERROR firmware boot failed despite 3 retries >> >> >> [ 604.098278] wlan0: failed to remove key (0, 04:bd:88:26:df:01) from >> hardware (-5) >> >> [ 604.327480] wlan0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from >> hardware (-5) >> >> >> Unfortunately I'm out of time to debug, so back to USB WiFi for now :( >> >> >> Regards, >> Mike >> >> >> On Wednesday, July 20, 2016 at 2:57:26 PM UTC-5, Mike Erdahl wrote: >>> >>> Hi Robert, >>> >>> Thank you for the suggestions! >>> >>> Unfortunately updating the kernel did not fix the issue- pretty much the >>> same backtraces. >>> >>> I was thinking along the lines of getting a powered USB hub as well. >>> >>> Interestingly, on the failed case, removing the USB audio card, then >>> performing a warm reset is not enough- I must cold boot for wlcore to come >>> up successfully again. >>> >>> I will track down a powered hub and report back. >>> >>> Regards, >>> Mike >>> >>> On Wednesday, July 20, 2016 at 2:09:35 PM UTC-5, RobertCNelson wrote: >>>> >>>> Hi Mike >>>> >>>> On Wed, Jul 20, 2016 at 2:03 PM, Mike Erdahl <mike....@gmail.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I'm working on a project that requires audio input/ output, so using a >>>>> C-Media chipset based solution from Sabrent. >>>>> >>>>> With the latest BB.org kernel/ filesystem (Kernel 4.4.9, Debian 8.4), >>>>> wlcore driver crashes during kernel boot if my USB audio card is >>>>> installed. Booting without the card installed, then installing after the >>>>> kernel seems to always work fine (WiFi throughput is normal, USB audio >>>>> in/ >>>>> out works as expected). >>>>> >>>>> Occasionally I can poweroff, then back on, without removing USB audio >>>>> card, and wlcore is happy. I would say this occurs < 10%. >>>>> >>>>> Below are snippets of my kernel logs in good vs bad case: >>>>> >>>>> debian@beaglebone:~$ uname -a >>>>> >>>>> >>>>> >>>>> >>>> Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l >>>>> GNU/Linux >>>>> >>>> >>>> Can you please re-test with 4.4.15-ti-r37 >>>> >>>> sudo apt-get update ; sudo apt-get install linux-image-4.4.15-ti-r37 ; >>>> sudo reboot >>>> >>>> Otherwise it smells like a power issue. >>>> >>>> A quick test, if you can put a "powered" usb hub between the Green >>>> Wireless and your usb audio card. >>>> >>>> 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/22c2f74a-b4b6-4ac9-8180-8dc237aee838%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.