On Wed, Mar 27, 2019 at 12:04 PM Daniel Kulp <[email protected]> wrote: >
> eeprom:[A335BNLTSE0A4518BBE911FC] > model:[SanCloud_BeagleBone_Enhanced]:WiFi AP > Enabled:[https://github.com/lwfinger/rtl8723bu] There's the problem, why didn't i see this before in your previous emails? For the cape-universal "rewrite" to work, u-boot needs to load "am335x-sancloud-bbe-uboot-univ.dtb" however today v4.19.x-bone only has: debian@beaglebone:/boot/dtbs/4.19.29-bone29$ find . | grep univ ./am335x-bone-uboot-univ.dtb ./am335x-boneblack-uboot-univ.dtb ./am335x-bonegreen-wireless-uboot-univ.dtb debian@beaglebone:/boot/dtbs/4.19.25-ti-r16$ find . | grep univ ./am335x-bone-uboot-univ.dtb ./am335x-boneblack-uboot-univ.dtb ./am335x-bonegreen-wireless-uboot-univ.dtb debian@beaglebone:/boot/dtbs/4.14.103-ti-r100$ find . | grep univ ./am335x-bone-uboot-univ.dtb ./am335x-boneblack-uboot-univ.dtb ./am335x-bonegreen-wireless-uboot-univ.dtb debian@beaglebone:/boot/dtbs/4.14.103-ti-r100$ find . | grep bbe ./am335x-sancloud-bbe.dtb So yeah, i need to grab my bbe, (pretty sure it's at home) and build the *-univ.dtb" files.. > dogtag:[BeagleBoard.org Debian Image 2018-10-07] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2018.09-00002-g9d95a561c9]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2018.09-00002-g9d95a561c9]:[location: dd MBR] > kernel:[4.19.29-bone29] > uboot_overlay_options:[enable_uboot_overlays=1] > uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C2-FAST-00A0.dtbo] > uboot_overlay_options:[disable_uboot_overlay_video=1] > uboot_overlay_options:[disable_uboot_overlay_audio=1] > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-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.20190320.1-0rcnee0~stretch+20190320] > pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227] > pkg:[kmod]:[23-2rcnee1~stretch+20171005] > WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED] > pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217] > groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev > users systemd-journal netdev gpio pwm eqep admin spi i2c tisdk weston-launch > xenomai bluetooth cloud9ide] > cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 > root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M > net.ifnames=0 rootwait quiet] > dmesg | grep remote > [ 0.628740] remoteproc remoteproc0: wkup_m3 is available > [ 0.940053] remoteproc remoteproc0: powering up wkup_m3 > [ 0.940074] remoteproc remoteproc0: Booting fw image > am335x-pm-firmware.elf, size 217168 > [ 0.942727] remoteproc remoteproc0: remote processor wkup_m3 is now up > dmesg | grep pru > > root@FPPTest:/opt/scripts/tools# config-pin -q P9.11 > P9_11 pinmux file not found! > Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P9_11_pinmux/state > > If I can get it working with 4.19, I'd be OK with that, but right now, it's > not. Since I'm trying to create new images for my devices, I can definitely > move everything to 4.19. The "problem" I have is a couple of the > out-of-kernel wifi drivers I build/include don't yet build properly with 4.19 > which is why I've considered staying on 4.14. That's a minor issue though. it looks like the rtl8723bu built.. does it not work? are they shipping with the rtl8821cu now too? 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/CAOCHtYjaPBV9vjBUyuinAhe9coUKg3zBBH8eb0TaSHC-aVGqpQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
