Weirdness with new beaglebone black boards

GoogleGroups
1

I got a shipment of beaglebone blacks in this week. They will boot on
the provided kernel 4.1
i have not tested anything more with that kernel.

I have a SD card with some custom tests for specific hardware that runs
with a beaglebone black
it runs the 4.14 kernel and works fine on an older beaglebone black
all tests run everything works as expected on my custom hardware.

here is a pastebin of the dmesg https://pastebin.com/uY4M3FmW

Now this same working SD card when plugged into the new beaglebones
dmesg https://pastebin.com/z0k42qMA

First off I2C-1 fails to work, The SD card loads the overlay from
uEnv.txt but no workie
second i have one I/O pin that fails to work GPIO3_21 ahclkx P9-25 A14
This fails when not plugged into anything except power and ethernet

This all works flawlessly on my other beaglebone black

I have a few of these new beaglebones that fail the same way. I have
not tested them all

from the dmesg a few things stand out

old beaglebone: [ 0.000000] Kernel command line:
console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
net.ifnames=0 quiet

new beaglebone: [ 0.000000] Kernel command line:
console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait
coherent_pool=1M net.ifnames=0 quiet

Why would capemgr load on boot on old bone but not new bone ?

remember this is the same SD card booting on different bones, Why are
these lines different.

Again

old beaglebone: [ 0.470487] omap_i2c 44e0b000.i2c: could not
find pctldev for node
/ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c0_pins, deferring
probe
[ 0.470541] omap_i2c
4802a000.i2c: could not find pctldev for node
/ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_bb_i2c1_pins,
deferring probe
[ 0.471941] omap_i2c
4819c000.i2c: bus 2 rev0.11 at 100 kHz

new beaglebone: [ 0.486500] omap_i2c 44e0b000.i2c: could not find
pctldev for node
/ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c0_pins, deferring
probe
[ 0.487908] omap_i2c
4819c000.i2c: bus 2 rev0.11 at 100 kHz

Its like I2C-1 is not there, maybe a pinmux change in hardware/firmware ?

I will stop there as you can see the other changes in the pastebins

Now the only thing i can think of is that the processors guts have changed
old processor AM3358BZCZ100 45C9DSW G1 962B ZCZ
new processor AM3358BZCZ100 6BC5EYW G1 962B ZCZ

Reading the processor errata seems there are lots of changes but nothing
that stands out to me
http://www.ti.com/lit/pdf/sprz360

Maybe one of you other list mates can shed some insight to this vexing issue

2

Let's find out:

sudo /opt/scripts/tools/version.sh

Regards,

3

New BBB

root@beaglebone:/home/debian# sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[ea6ea9fca05f36f5044398884375b0231348d6e2]
eeprom:[A335BNLT00C02017BBBK136F]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-01-28]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
2018.01-00002-g9aa111a004]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2016.01-00001-g4eb802e]
kernel:[4.14.20-ti-r36]
nodejs:[v6.12.3]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr5=/lib/firmware/BB-I2C1-00A0.dtbo]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[disable_uboot_overlay_audio=1]
uboot_overlay_options:[disable_uboot_overlay_wireless=1]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20180126.0-0rcnee0~stretch+20180126]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~stretch+20180104]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm
eqep admin spi tisdk weston-launch xenomai]
dmesg | grep pinctrl-single
[ 0.945104] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800
size 568
END
root@beaglebone:/home/debian#

Old BBB

root@beaglebone:/home/debian# sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[ea6ea9fca05f36f5044398884375b0231348d6e2]
eeprom:[A335BNLT00C03214BBBK7892]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-01-28]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
2018.01-00002-g9aa111a004]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2017.07-rc2-00002-g2e6ea0]
kernel:[4.14.20-ti-r36]
nodejs:[v6.12.3]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr5=/lib/firmware/BB-I2C1-00A0.dtbo]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[disable_uboot_overlay_audio=1]
uboot_overlay_options:[disable_uboot_overlay_wireless=1]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20180126.0-0rcnee0~stretch+20180126]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~stretch+20180104]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm
eqep admin spi tisdk weston-launch xenomai]
dmesg | grep pinctrl-single
[ 0.929641] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800
size 568
END
root@beaglebone:/home/debian#

4

Clear out the eMMC bootloader in both boards, then you'll get similar booting..

Regards,

5

uboot too old ? on new board ?

6

Well both boards. :wink:

Just clear them out, and they'll operate exactly the same..

Regards,

7

how would one go about doing that from command line

will this affect booting from EMMC

I just googled how to clear out EMMC and did not see anything related to
that

BTW Welcome back Robert

8

how would one go about doing that from command line

will this affect booting from EMMC

yeap. but that's not the issue you are facing...

I just googled how to clear out EMMC and did not see anything related to
that

sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10

BTW Welcome back Robert

yeah, Europe was a lot of fun.. :wink:

Regards,

9

Once tested these bones will need to have a custom image flashed.

I dont have this image so i cannot flash the bone.
I can flash a new image if i need to.

I want to make sure that the board can be flashed and work from the EMMC
once
i send them off to never never land of customers.

10

Okay...

Well, you have your answer for the weirdness...

Different versions of u-boot in the eMMC..

Regards,