Beaglebone Black Industrial universal cape not working...
308 views
Skip to first unread message
Daniel Kulp
Dec 5, 2017, 4:46:22 PM12/5/17
to BeagleBoard
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?
Robert Nelson
Dec 5, 2017, 4:56:37 PM12/5/17
to Beagle Board, d...@kulp.com
Daniel Kulp
Dec 5, 2017, 5:08:12 PM12/5/17
to BeagleBoard
It's the Element14 Beaglebone Black Industrial
Thanks!
Dan
Daniel Kulp
Dec 5, 2017, 5:13:33 PM12/5/17
to BeagleBoard
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?
Robert Nelson
Dec 5, 2017, 5:19:18 PM12/5/17
to Beagle Board, d...@kulp.com
On Tue, Dec 5, 2017 at 4:13 PM, Daniel Kulp <d...@kulp.com> wrote:
>
> 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?
Your board has a weird eeprom, please run:
>
> 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?
sudo /opt/scripts/tools/version.sh
That board should have:
https://github.com/beagleboard/image-builder/blob/master/readme.md
Element14 BeagleBone Black Industrial:
A0: [aa 55 33 ee 41 33 33 35 42 4e 4c 54 45 49 41 30 |.U3.A335BNLTEIA0|]
Daniel Kulp
Dec 5, 2017, 5:30:38 PM12/5/17
to BeagleBoard
Using the 9.1 based image, I get:
eeprom:[A335BNLTEIA03716BBBK1337]model:[TI_AM335x_BeagleBone_Black]dogtag:[BeagleBoard.org Debian Image 2017-08-31]bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2017.09-00002-g0f3f1c7907]kernel:[4.4.91-ti-r137]nodejs:[v6.12.0]uboot_overlay_options:[enable_uboot_overlays=1]uboot_overlay_options:[disable_uboot_overlay_video=1]uboot_overlay_options:[disable_uboot_overlay_audio=1]uboot_overlay_options:[disable_uboot_overlay_adc=1]uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]uboot_overlay_options:[enable_uboot_cape_universal=1]pkg:[bb-cape-overlays]:[4.4.20171107.0-0rcnee1~stretch+20171107]pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]Using the latest stuff, I get:
git:/opt/scripts/:[e5c23dc2a45f5c9ace291dd32e7c3d79edc1932d]eeprom:[A335BNLTEIA03716BBBK1337]model:[Octavo_Systems_OSD3358-SM-RED]dogtag:[BeagleBoard.org Debian Image 2017-10-10]bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2017.11-00002-g7b415acfc1]bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.11-00002-g7b415acfc1]kernel:[4.4.91-ti-r137]uboot_overlay_options:[enable_uboot_overlays=1]uboot_overlay_options:[disable_uboot_overlay_video=1]uboot_overlay_options:[disable_uboot_overlay_audio=1]uboot_overlay_options:[disable_uboot_overlay_adc=1]uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]uboot_overlay_options:[enable_uboot_cape_universal=1]pkg:[bb-cape-overlays]:[4.4.20171126.0-0rcnee1~stretch+20171126]pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
Robert Nelson
Dec 5, 2017, 5:40:07 PM12/5/17
to Beagle Board
u-boot, it just worked till i added the latest board and then broke
it..
I have that board somewhere here at work, i'll get it fixed tomorrow..
Jose Valenzuela San Juan
Dec 6, 2017, 1:47:51 PM12/6/17
to BeagleBoard
Is there a workaround while we wait for the fix?
Looking forward for when its ready, I'm also working on an Element14 BeagleBone Black Industrial.
Please let us know when ready.
Regards!
Robert Nelson
Dec 6, 2017, 3:22:14 PM12/6/17
to Beagle Board, Jose Valenzuela San Juan
On Wed, Dec 6, 2017 at 12:47 PM, Jose Valenzuela San Juan
<java...@gmail.com> wrote:
> Is there a workaround while we wait for the fix?
>
> Looking forward for when its ready, I'm also working on an Element14
> BeagleBone Black Industrial.
> Please let us know when ready.
Okay, i found the issue and pretty sure it's resolved.
<java...@gmail.com> wrote:
> Is there a workaround while we wait for the fix?
>
> Looking forward for when its ready, I'm also working on an Element14
> BeagleBone Black Industrial.
> Please let us know when ready.
Of course i can't find that board at my desk..
Plese run:
cd /opt/scripts/tools/developers/
git pull
sudo ./update_bootloader.sh --beta
sudo reboot
and then share with us your serial boot log, so we can verify..
Then i'll move that version from "beta" to "normal"..
Daniel Kulp
Dec 6, 2017, 3:33:08 PM12/6/17
to BeagleBoard
MUCH MUCH better... The GPIO's all come up correctly.
U-Boot 2018.01-rc1-00002-g965cb1b342 (Dec 06 2017 - 13:32:27 -0600), Build: jenkins-github_Bootloader-Builder-15
CPU : AM335X-GP rev 2.1I2C: readyDRAM: 512 MiBNo match for driver 'omap_hsmmc'No match for driver 'omap_hsmmc'Some drivers were not foundReset Source: Power-on reset has occurred.MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1Using default environment
Board: BeagleBone Black<ethaddr> not set. Validating first E-fuse MACBeagleBone Black:Model: Element14 BeagleBone Black Industrial:BeagleBone: cape eeprom: i2c_probe: 0x54:BeagleBone: cape eeprom: i2c_probe: 0x55:BeagleBone: cape eeprom: i2c_probe: 0x56:BeagleBone: cape eeprom: i2c_probe: 0x57:Net: eth0: MII MODEcpsw, usb_etherPress SPACE to abort autoboot in 2 secondsboard_name=[A335BNLT] ...board_rev=[EIA0] ...switch to partitions #0, OKmmc0 is current deviceSD/MMC found on device 0** Bad device 0:2 0x82000000 **** Bad device 0:2 0x82000000 **switch to partitions #0, OKmmc0 is current deviceScanning mmc 0:1...gpio: pin 56 (gpio 56) value is 0gpio: pin 55 (gpio 55) value is 0gpio: pin 54 (gpio 54) value is 0gpio: pin 53 (gpio 53) value is 1switch to partitions #0, OKmmc0 is current devicegpio: pin 54 (gpio 54) value is 1Checking for: /uEnv.txt ...Checking for: /boot.scr ...Checking for: /boot/boot.scr ...Checking for: /boot/uEnv.txt ...gpio: pin 55 (gpio 55) value is 12042 bytes read in 36 ms (54.7 KiB/s)Loaded environment from /boot/uEnv.txtChecking if uname_r is set in /boot/uEnv.txt...gpio: pin 56 (gpio 56) value is 1Running uname_boot ...loading /boot/vmlinuz-4.4.91-ti-r137 ...8889560 bytes read in 601 ms (14.1 MiB/s)uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb ...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/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 467 ms (1000 Bytes/s)uboot_overlays: loading /lib/firmware/univ-bbb-Exx-00A0.dtbo ...92641 bytes read in 517 ms (174.8 KiB/s)loading /boot/initrd.img-4.4.91-ti-r137 ...6259413 bytes read in 439 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] ...debug: [bootz 0x82000000 0x88080000:5f82d5 88000000] ...## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Ramdisk to 8fa07000, end 8ffff2d5 ... OK reserving fdt memory region: addr=88000000 size=83000 Loading Device Tree to 8f981000, end 8fa06fff ... OK
Starting kernel ...
Thanks!
Dan
Daniel Kulp
Dec 6, 2017, 6:08:38 PM12/6/17
to BeagleBoard
Things are definitely working better. My GPIO's are available and working, config-pin works, etc... Major thanks!
Question: Longer term, should the /proc/device-tree/model continue to read "TI AM335x BeagleBone Black" or should that eventually be updated to give a unique name like "TI AM335x BeagleBone Black Industrial" or something to distinguish the model like there is for the "Wireless" versions and Blue and Green and such? I don't really care, but I'd like to get an idea so I can plan on updating my own scripts if needed.
Thanks for the quick turnaround!
Dan
On Wednesday, December 6, 2017 at 3:22:14 PM UTC-5, RobertCNelson wrote:
Jose Valenzuela San Juan
Dec 11, 2017, 3:13:28 PM12/11/17
to BeagleBoard
The last image (bone-debian-9.3-console-armhf-2017-12-10-1gb.img.xz) is working fine for me.
The workaround worked too.Thanks!
Reply all
Reply to author
Forward
0 new messages