Uhgg... also just discovered that the /proc/device-tree-model now reads: Octavo Systems OSD3358-SM-RED
On the older stretch 9.1 based image I have, it reads "TI AM335x BeagleBone Black" just like the black's. That's going to break a bunch of things for me as well. :( I need to use the industrial version as we hit temperatures well below freezing. Is this a uBoot thing? Would dropping back to the older uBoot help? On Tuesday, December 5, 2017 at 4:46:22 PM UTC-5, Daniel Kulp wrote: > > > I have an image that works fine on a Beaglebone Black and Beaglebone > green, but it's not working properly on the "red" industrial version. For > some reason, the uboot_capemgr isn't being loaded by uboot on the Red > whereas it is using the exact same SD card/Image as I use on the others. > > Connecting a serial cable, on the normal black, I see: > > loading /boot/dtbs/4.4.91-ti-r137/am335x-boneblack-uboot.dtb ... > 57290 bytes read in 263 ms (211.9 KiB/s) > uboot_overlays: [fdt_buffer=0x60000] ... > uboot_overlays: loading /lib/firmware/AM335X-20-00A0.dtbo ... > 378 bytes read in 363 ms (1000 Bytes/s) > uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ... > 1105 bytes read in 108 ms (9.8 KiB/s) > uboot_overlays: uboot loading of [/lib/firmware/BB-HDMI-TDA998x-00A0.dtbo] > disabled by /boot/uEnv.txt [disable_uboot_overlay_video=1]... > uboot_overlays: uboot loading of [/lib/firmware/BB-ADC-00A0.dtbo] disabled > by /boot/uEnv.txt [disable_uboot_overlay_adc=1]... > uboot_overlays: loading /lib/firmware/AM335X-PRU-UIO-00A0.dtbo ... > 853 bytes read in 466 ms (1000 Bytes/s) > uboot_overlays: loading /lib/firmware/univ-bbb-Exx-00A0.dtbo ... > 92641 bytes read in 515 ms (174.8 KiB/s) > loading /boot/initrd.img-4.4.91-ti-r137 ... > 6259413 bytes read in 438 ms (13.6 MiB/s) > debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 > root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M > net.ifnames=0 quiet] ... > > > But on the Red, I see: > > loading /boot/dtbs/4.4.91-ti-r137/am335x-boneblack-uboot.dtb ... > 57290 bytes read in 262 ms (212.9 KiB/s) > uboot_overlays: [fdt_buffer=0x60000] ... > uboot_overlays: loading /lib/firmware/OSD3358-00A0.dtbo ... > 441 bytes read in 532 ms (0 Bytes/s) > uboot_overlays: loading /lib/firmware/M-BB-OSD3358-SM-RED-00A0.dtbo ... > 285 bytes read in 450 ms (0 Bytes/s) > uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ... > 1105 bytes read in 107 ms (9.8 KiB/s) > uboot_overlays: uboot loading of [/lib/firmware/BB-HDMI-TDA998x-00A0.dtbo] > disabled by /boot/uEnv.txt [disable_uboot_overlay_video=1]... > uboot_overlays: uboot loading of [/lib/firmware/BB-ADC-00A0.dtbo] disabled > by /boot/uEnv.txt [disable_uboot_overlay_adc=1]... > uboot_overlays: loading /lib/firmware/AM335X-PRU-UIO-00A0.dtbo ... > 853 bytes read in 459 ms (1000 Bytes/s) > loading /boot/initrd.img-4.4.91-ti-r137 ... > 6259413 bytes read in 438 ms (13.6 MiB/s) > debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 > rootwait coherent_pool=1M net.ifnames=0 quiet] .... > > Is there something about the OSD3358-00A0 and M-BB-OSD3358-SM-RED-00A0 > compared to the normal AM335X-20-00A0 that would cause the universal cape > manager to not be detected or loaded? Is there an easy workaround? > -- 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/3bdb4f7f-58f7-494d-8139-83d934d2f030%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
