More: I tried overriding the dtb in uEnv.txt to force wireless operation without reflashing eeprom - this was reported to work in some cases. How can I tell from the version.sh output if my eeprom is corrupt or incorrect for a BBB Wireless?
On Sunday, December 15, 2019 at 11:00:05 PM UTC-8, ags wrote: > > I've had a BBBW for 1+ years. Just booted, and can't get WiFi working. > > using connmanctl: > > connmanctl> enable wifi > Error wifi: Method "SetProperty" with signature "sv" on interface > "net.connman.Technology" doesn't exist > > Researched and saw convo about "corrupt EEPROM"; tried using > "dtb=am335x-boneblack-wireless.dtb" in /boot/uEnv.txt - no help > > downloaded newer image (4.14.108-ti-r113) to SDcard and booted. Still no > wlan0 > BT and WL LEDs are not illuminated > > ifconfig -a does not show wlan0 > > /opt/scripts/tools/version.sh output: > > debian@beaglebone:/opt/scripts/tools$ sudo ./version.sh > > git:/opt/scripts/:[109f74fb87e6034ae1a8971a244064a8d5e090a5] > > ]eprom:[A335BNLTBBWG2331?O > > model:[TI_AM335x_BeagleBone_Black] > > dogtag:[BeagleBoard.org Debian Image 2019-08-03] > > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2019.04-00002-gbb4af0f50f]:[location: dd MBR] > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2016.11-rc3-00002-g73df7f]:[location: dd MBR] > > kernel:[4.14.108-ti-r113] > > nodejs:[v6.17.0] > > uboot_overlay_options:[enable_uboot_overlays=1] > > > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo] > > uboot_overlay_options:[enable_uboot_cape_universal=1] > > pkg check: to individually upgrade run: [sudo apt install --only-upgrade > <pkg>] > > pkg:[bb-cape-overlays]:[4.4.20190801.0-0rcnee0~stretch+20190801] > > pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227] > > pkg:[kmod]:[23-2rcnee1~stretch+20171005] > > pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~stretch+20190327] > > pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217] > > groups:[debian : debian adm kmem dialout cdrom floppy audio dip video > plugdev users systemd-journal i2c bluetooth netdev gpio pwm eqep remoteproc > admin spi tisdk weston-launch xenomai cloud9ide] > > cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 > root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M > net.ifnames=0 rng_core.default_quality=100 quiet] > > dmesg | grep remote > > [ 1.221200] remoteproc remoteproc0: wkup_m3 is available > > [ 1.441065] remoteproc remoteproc0: powering up wkup_m3 > > [ 1.441181] remoteproc remoteproc0: Booting fw image > am335x-pm-firmware.elf, size 217168 > > [ 1.445381] remoteproc remoteproc0: remote processor wkup_m3 is now up > > [ 9.891469] remoteproc remoteproc1: 4a334000.pru is available > > [ 9.896369] remoteproc remoteproc2: 4a338000.pru is available > > dmesg | grep pru > > [ 9.863842] pruss 4a300000.pruss: creating PRU cores and other child > platform devices > > [ 9.891469] remoteproc remoteproc1: 4a334000.pru is available > > [ 9.891589] pru-rproc 4a334000.pru: PRU rproc node > /ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully > > [ 9.896369] remoteproc remoteproc2: 4a338000.pru is available > > [ 9.896486] pru-rproc 4a338000.pru: PRU rproc node > /ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully > > dmesg | grep pinctrl-single > > [ 0.930034] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 > size 568 > > dmesg | grep gpio-of-helper > > [ 0.942098] gpio-of-helper ocp:cape-universal: ready > > lsusb > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > END > > > I'm really stuck. > -- 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/2738b831-a4fe-41b2-9b60-868f4f1fb17c%40googlegroups.com.
