[ALL] Debian 9 (Stretch) now out

Starting today, all the minimal Debian 8 (Jessie) based root file systems options have been replaced by Debian 9 (Stretch).

https://eewiki.net/display/linuxonarm/Home

Which was released over the weekend:

https://www.debian.org/News/2017/20170617

Due to the extra work required for the “barefs” minimization, that’ll take a few days of testing.

Regards,

hi Robert,

I recently purchased a 4D systems LCD designed for the beaglebone (gen4-4DCAPE-43CT-CLB).
It is connected to a beaglebone green board. As I’m sure you know, the beaglebone green does not have a power jack so the setup is powered through the nimbelink cape.To prevent pin conflicts, the nimbelink cape does not have a module plugged in (its basically just a power source).

The beaglebone green board is running the latest debian stretch =>


debian@beaglebone:~$ cat /proc/version
Linux version 4.9.45-ti-r57 (root@b9-am57xx-beagle-x15-2gb) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)
#1 SMP PREEMPT Fri Aug 25 22:58:38 UTC 2017


When I power on the setup, the LCD backlight comes on and thats about it. I get no cursor, I get no Openbox

I’ve tried disabling the eMMc and boot from SDcard. No success. The backlight did not even come on.
I’ve verified the overlay file on the beaglebone is exactly whats on github.

Any help will be very much appreciated.

thanks toyo

Hi Toyo,

Which Nimbelink cape? We’ve moved to u-boot overlays, please run:

sudo /opt/scripts/tools/version.sh

So we can debug what version of u-boot your dealing with.

Regards,

hi Robert

  • the nimbelink cape is the beaglebone cape lite

  • i attached a screen shot of version.sh

thanks

Hi Toyo,

These two capes can’t be used together without modification to the Nimbelink overlay file:

The Nimbelink Cape:

Pins P8_33/P8_35 used for UART4 are needed by the LCD.

Regards,

hi Robert

Thanks so much for pointing this out. I should have looked at the datasheet more closely.

Thought I’d take another crack at the BBB. The Debian Weezy 7.11 works with the 4D Systems 4DCAPE-43T BB-BONE-LCD4-01-00A1.dtbo which is also in the Debian 9 Stretch /lib/firmware directory.

The EEROM of the 4D Systems LCD4.3T display shows up:
root@beaglebone:/# cat /sys/devices/platform/bone_capemgr/slots
0: P—L- 0 4D 4.3 LCD CAPE- 4DCAPE-43T ,00A1,4D SYSTEMS ,BB-BONE-LCD4-01
1: PF---- -1
2: PF---- -1
3: PF---- -1

Version of the OS is:
root@beaglebone:/# /opt/scripts/tools/version.sh
git:/opt/scripts/:[5416919c1969011813689dc5529498c913995584]
eeprom:[A335BNLT000B1114BBBK2834]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2017-08-31]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2017.09-rc2-00002-g7c9 353]
kernel:[4.9.45-ti-r57]
nodejs:[v6.11.2]
uboot_overlay_options:[enable_uboot_overlays=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.20170728.0-0rcnee1~stretch+20170728]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
dmesg | grep pinctrl-single
[ 2.886385] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[ 3.662597] pinctrl-single 44e10800.pinmux: pin PIN40 already requested by 0- 0070; cannot claim for panel
[ 3.679731] pinctrl-single 44e10800.pinmux: pin-40 (panel) status -22
[ 3.693534] pinctrl-single 44e10800.pinmux: could not request pin 40 (PIN40) from group pinmux_bb_lcd_lcd_pins on device pinctrl-single
END

I’m guessing it’s something to do with pin 40? This is a stock BBB with no other cards and fresh install of Debian Stretch. Pull the SD card and insert the one with Wheezy and it works. Should not that .dtbo supplied with ‘stretch’ work? Or do new uboot device overlays need to be recompiled and the EEROM changed?

Digikey says they still have 61 of the https://www.digikey.ca/products/en?keywords=1613-1012-ND in stock so there should probably be support for this module?

Please re-test with:

https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-lxqt/

Regards,

Which one? There are 5 versions in that link. It’s a 2GB Beaglelbone Black so needs to run off the16GB SD.

Use:
bone-debian-9.3-lxqt-armhf-2018-01-14-4gb.img.xz

It’ll run off the MicroSD, make sure the eMMC doesn’t have a version of U-Boot to get in the way…

Regards,

Took a random stab that bone-debian-9.3-lxqt-armhf-2018-01-14-4gb.img.xz was the one to try.
Don’t know how to make sure “eMMC doesn’t have a version of U-Boot to get in the way…”

Booted with HDMI monitor connected. LXQT came up. Custom Cape for one-wire was discovered but not loaded. Added compiled dtbo but still not loaded on reboot. Will deal with that on a separate subject heading.

shutdown -h now.
Still has 90 second delay till shutdown bug that showed up after Wheezy. Also a separate issue that I will raise on a separate subject heading.

Removed custom cape. installed 4D Systems LCD4 which looks like it was discovered but not loaded.
Blank screen on LCD after boot.

And here’s the output (the 2013 looks suspicious. Is this the uboot getting in the way?):

U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img

U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53)

I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net: not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
1359 bytes read in 65 ms (19.5 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc …
Running uenvcmd …
2060 bytes read in 44 ms (44.9 KiB/s)
debug: [/boot/vmlinuz-4.9.76-ti-r91] …
9961280 bytes read in 1683 ms (5.6 MiB/s)
debug: [/boot/initrd.img-4.9.76-ti-r91] …
6269510 bytes read in 1075 ms (5.6 MiB/s)
debug: [/boot/dtbs/4.9.76-ti-r91/am335x-boneblack.dtb] …
63583 bytes read in 148 ms (418.9 KiB/s)
debug: [console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet] …
debug: [bootz 0x82000000 0x88080000:5faa46 0x88000000] …

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Using Device Tree in place at 88000000, end 8801285e

Starting kernel …

[ 0.001594] clocksource_probe: no matching clocksources found
[ 1.998167] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 2.296265] omap_voltage_late_init: Voltage driver support not added
[ 2.304127] PM: Cannot get wkup_m3_ipc handle
[ 2.657034] bone_capemgr bone_capemgr: slot #0: ‘4D 4.3 LCD CAPE- 4DCAPE-43T ,00A1,4D SYSTEMS ,BB-BONE-LCD4-01’
[ 2.693416] bone_capemgr bone_capemgr: slot #1: No cape found
[ 2.726016] bone_capemgr bone_capemgr: slot #2: No cape found
[ 2.758104] bone_capemgr bone_capemgr: slot #3: No cape found
[ 2.809977] pinctrl-single 44e10800.pinmux: pin PIN40 already requested by 0-0070; cannot claim for panel
[ 2.832455] pinctrl-single 44e10800.pinmux: pin-40 (panel) status -22
[ 2.845520] pinctrl-single 44e10800.pinmux: could not request pin 40 (PIN40) from group pinmux_bb_lcd_lcd_pins on device pinctrl-single
[ 2.870758] panel panel: Error applying setting, reverse things back

Debian GNU/Linux 9 beaglebone ttyS0

BeagleBoard.org Debian Image 2018-01-14

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

beaglebone login:

Yeah your version of U-Boot on the eMMC is too old, it doesn’t know how to handle U-Boot Overlays, thus it’s loading the wrong base dtb and overlays for your Board/cape combination.

Run lsblk, i’m pretty sure in the 2013.04 era we used a fat boot partition, it should be /dev/mmcblk1?

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

Regards,

Hi Robert,
You are correct of course.

root@beaglebone:/dev# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 14.5G 0 disk
└─mmcblk0p1 179:1 0 3.3G 0 part /
mmcblk1 179:8 0 1.8G 0 disk
├─mmcblk1p1 179:9 0 70.6M 0 part
└─mmcblk1p2 179:10 0 1.7G 0 part
mmcblk1boot0 179:24 0 1M 1 disk
mmcblk1boot1 179:32 0 1M 1 disk

I’m guessing if I clear out the mmcblk1 that I will destroy the Angstrom partition and all my user files.
sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100

Not only that, but since the new distributions no longer come with a FAT partition and the uEnv.txt file needs to be renamed, a working Linux System is mandatory. Up till now with these new distributions I boot Angstrom off the 2GB flash and then insert the MicroSD card and edit the filename to produce the uEnv.txt. Then reboot.

Trashing the /dev/mmcblk1 takes away that ability? Is there not a different solution that won’t kill the Angstrom version on the MicroSD. It’s how I can test that my hardware is still functional.

If I hold down the button above the SD card and apply power I get this with no mention of U-Boot from 2013 but still no LCD display:

U-Boot SPL 2018.01-00002-gcc9c2d1992 (Jan 09 2018 - 14:46:27)
Trying to boot from MMC1

U-Boot 2018.01-00002-gcc9c2d1992 (Jan 09 2018 - 14:46:27 -0600), Build: jenkins-github_Bootloader-Builder-26

CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
No match for driver 'omap_hsmmc’
No match for driver 'omap_hsmmc’
Some drivers were not found
Reset Source: Power-on reset has occurred.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Board: BeagleBone Black
not set. Validating first E-fuse MAC
BeagleBone Black:
BeagleBone: cape eeprom: i2c_probe: 0x54: /lib/firmware/BB-BONE-LCD4-01-00A1.dtbo [0xfe93c1f]
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net: eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] …
board_rev=[000B] …
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
** Bad device 0:2 0x82000000 **
** Bad device 0:2 0x82000000 **
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt …
1359 bytes read in 51 ms (25.4 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from /uEnv.txt
Importing environment from mmc …
Checking if uenvcmd is set …
gpio: pin 56 (gpio 56) value is 1
Running uenvcmd …
2060 bytes read in 39 ms (50.8 KiB/s)
debug: [/boot/vmlinuz-4.9.76-ti-r91] …
9961280 bytes read in 660 ms (14.4 MiB/s)
debug: [/boot/initrd.img-4.9.76-ti-r91] …
6269510 bytes read in 429 ms (13.9 MiB/s)
debug: [/boot/dtbs/4.9.76-ti-r91/am335x-boneblack.dtb] …
63583 bytes read in 129 ms (480.5 KiB/s)
debug: [console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet] …
debug: [bootz 0x82000000 0x88080000:5faa46 0x88000000] …

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Using Device Tree in place at 88000000, end 8801285e

Starting kernel …

[ 0.000923] clocksource_probe: no matching clocksources found
[ 1.389128] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 1.634815] omap_voltage_late_init: Voltage driver support not added
[ 1.642183] PM: Cannot get wkup_m3_ipc handle
[ 1.939151] bone_capemgr bone_capemgr: slot #0: ‘4D 4.3 LCD CAPE- 4DCAPE-43T ,00A1,4D SYSTEMS ,BB-BONE-LCD4-01’
[ 1.975621] bone_capemgr bone_capemgr: slot #1: No cape found
[ 2.008307] bone_capemgr bone_capemgr: slot #2: No cape found
[ 2.039366] bone_capemgr bone_capemgr: slot #3: No cape found
[ 2.097329] pinctrl-single 44e10800.pinmux: pin PIN40 already requested by 0-0070; cannot claim for panel
[ 2.122755] pinctrl-single 44e10800.pinmux: pin-40 (panel) status -22
[ 2.135739] pinctrl-single 44e10800.pinmux: could not request pin 40 (PIN40) from group pinmux_bb_lcd_lcd_pins on device pinctrl-single
[ 2.160212] panel panel: Error applying setting, reverse things back
[ OK ] Started LSB: Start daemon at boot time.
[ OK ] Started Connection service.
[ OK ] Started Login Service.
[ OK ] Reached target Network.
Starting The Apache HTTP Server…
Starting OpenBSD Secure Shell server…
Starting Permit User Sessions…
[ OK ] Reached target Network is Online.
Starting Daily apt download activities…
Starting LSB: Advanced IEEE 802.11 management daemon…
[ OK ] Started LSB: Start busybox udhcpd at boot time.
[ OK ] Started LSB: Advanced IEEE 802.11 management daemon.
[ OK ] Started Permit User Sessions.
[ OK ] Started Getty on tty1.
Starting Light Display Manager…
[ OK ] Created slice system-systemd\x2dbacklight.slice.
Starting Load/Save Screen Backlight…ightness of backlight:backlight…
[ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
Starting LSB: set CPUFreq kernel parameters…
[ OK ] Started Load/Save Screen Backlight Brightness of backlight:backlight.
Starting Hostname Service…
Starting WPA supplicant…
[ OK ] Started OpenBSD Secure Shell server.
[ OK ] Found device /dev/ttyS0.
[ OK ] Started LSB: set CPUFreq kernel parameters.
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Reached target Login Prompts.
[ OK ] Started WPA supplicant.
[ OK ] Started Light Display Manager.
[ OK ] Started Hostname Service.
[ OK ] Started The Apache HTTP Server.

Debian GNU/Linux 9 beaglebone ttyS0
Debian Image 2018-01-14
default username:password is [debian:temppwd]

Ah still running Angstrom, that image can still be downloaded from beagleboard.org so you can re-install it. (ps Angstrom has been Un-Supported for a few years now…)

Erasing the eMMC, will break Angstrom.

Renaming “/uEnv.txt” as you did will “disable” U-Boot Overlays, this was setup to allow users to use the old Kernel Overlays path (which is also now gone in our v4.15.x kernel branch)…

On the plus side, your cape was detected and U-Boot Overlays:

BeagleBone: cape eeprom: i2c_probe: 0x54: /lib/firmware/BB-BONE-LCD4-01-00A1.dtbo [0xfe93c1f]

So remove /uEnv.txt and erase the version of U-Boot eMMC then retry booting…

Regards,

Alright. Had a few minutes here so I ‘borrowed’ the Milling Machine BBB running machinekit off an SD card.
It had a 3.8.x Debian running off the 4GB eMMC which I don’t use so I trashed the eMMC with dd and renamed the MicroSD card uEnv.txt to bbb-uEnv.txt

And now I have a working 4D Systems LCD4 screen.

However, old as Angstrom and Debian Wheezy may be, they detect both the LCD4 display and the BB-W1-P8.11-00A0.dtbo one-wire prototype cape. So far this version can’t see that proto cape.

In summary:

  1. Download bone-debian-9.3-lxqt-armhf-2018-01-14-4gb.img.xz
  2. if lsblk shows a FAT partition on internal flash use
    sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100
    to clear it.
  3. Make sure /uEnv.txt does not exist on the MicroSD card.
  4. reboot and eventually LCD display shows LXQT user interface.

Have I missed anything?

For the one wire cape, does it have an eeprom, did u-boot detect it?

If not just add this to /boot/uEnv.txt

uboot_overlay_addr4=/lib/firmware/BB-W1-P8.11-00A0.dtbo

However, if that still doesn’t work, i’ll take a look at one-wire tomorrow at work.

Regards,

Hi Robert,
I’m using the
https://www.digikey.ca/products/en?keywords=DS1822%2B-ND%20 rather than the more common DS18B20 sensor simply because I have lots and use it and it’s internal serial number on all my products.

root@beaglebone:/sys/devices/w1_bus_master1/22-000000219f58# cat w1_slave
4c 01 4b 46 7f ff 04 10 f5 : crc=f5 YES
4c 01 4b 46 7f ff 04 10 f5 t=20750
root@beaglebone:/sys/devices/w1_bus_master1/22-000000219f58#

Once I added
uboot_overlay_addr3=/lib/firmware/BB-W1-P8.11-00A0.dtbo
and rebooted the cape showed up as did the w1_bus_master1 folder.

I chose addr3 because the cape eerom is also wired for that location. Seemed simpler.

cat /sys/bus/i2c/devices/2-0057/eeprom | hexdump -C

00000000  aa 55 33 ee 41 30 4f 6e  65 57 69 72 65 20 70 6c  |.U3.A0OneWire pl|
00000010  75 73 20 43 41 4e 62 75  73 00 00 00 00 00 00 00  |us CANbus.......|
00000020  00 00 00 00 00 00 30 30  41 30 41 75 74 6f 41 72  |......00A0AutoAr|
00000030  74 69 73 61 6e 73 20 49  6e 63 42 42 2d 57 31 2d  |tisans IncBB-W1-|
00000040  50 38 2e 31 31 00 00 00  00 00 00 00 00 00 00 00  |P8.11...........|
00000050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

Here’s the start boot log just for reference.

U-Boot SPL 2018.01-00002-gcc9c2d1992 (Jan 09 2018 - 14:46:27)
Trying to boot from MMC1

U-Boot 2018.01-00002-gcc9c2d1992 (Jan 09 2018 - 14:46:27 -0600), Build: jenkins-github_Bootloader-Builder-26

CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
No match for driver 'omap_hsmmc’
No match for driver 'omap_hsmmc’
Some drivers were not found
Reset Source: Global warm SW reset has occurred.
Reset Source: Power-on reset has occurred.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Board: BeagleBone Black
not set. Validating first E-fuse MAC
BeagleBone Black:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57: /lib/firmware/BB-W1-P8-00A0.dtbo [0xedc7bef]
Net: eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] …
board_rev=[00C0] …
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
** Bad device 0:2 0x82000000 **
** Bad device 0:2 0x82000000 **
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt …
Checking for: /boot.scr …
Checking for: /boot/boot.scr …
Checking for: /boot/uEnv.txt …
gpio: pin 55 (gpio 55) value is 1
2068 bytes read in 50 ms (40 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt…
gpio: pin 56 (gpio 56) value is 1
Running uname_boot …
loading /boot/vmlinuz-4.9.76-ti-r91 …
9961280 bytes read in 670 ms (14.2 MiB/s)
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] …
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb …
loading /boot/dtbs/4.9.76-ti-r91/am335x-boneblack-uboot.dtb …
61174 bytes read in 57 ms (1 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] …
uboot_overlays: loading /lib/firmware/BB-W1-P8.11-00A0.dtbo …
974 bytes read in 685 ms (1000 Bytes/s)
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo …
1105 bytes read in 635 ms (1000 Bytes/s)
uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo …
4169 bytes read in 469 ms (7.8 KiB/s)
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo …
695 bytes read in 212 ms (2.9 KiB/s)
uboot_overlays: loading /lib/firmware/AM335X-PRU-UIO-00A0.dtbo …
853 bytes read in 396 ms (2 KiB/s)
uboot_overlays: [uboot_detected_capes=BB-W1-P8,] …
uboot_overlays: cape universal disabled, external cape enabled or detected…
loading /boot/initrd.img-4.9.76-ti-r91 …
6269510 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 uboot_detected_capes=BB-W1-P8, coherent_pool=1M net.ifnames=0 quiet] …
debug: [bootz 0x82000000 0x88080000:5faa46 88000000] …

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fa05000, end 8ffffa46 … OK
reserving fdt memory region: addr=88000000 size=70000
Loading Device Tree to 8f992000, end 8fa04fff … OK

Starting kernel …

[ 0.000938] clocksource_probe: no matching clocksources found
[ 1.388903] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 1.636813] omap_voltage_late_init: Voltage driver support not added
[ 1.644131] PM: Cannot get wkup_m3_ipc handle

Debian GNU/Linux 9 beaglebone ttyS0

BeagleBoard org Debian Image 2018-01-14

Support/FAQ: “http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

beaglebone login: root
Password:
Last login: Tue Jan 16 01:11:49 UTC 2018 on ttyS0
Linux beaglebone 4.9.76-ti-r91 #1 SMP PREEMPT Fri Jan 12 00:09:08 UTC 2018 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@beaglebone:~#

I will write up a step by step description of how I got here.

The DS1822+ temperature sensor is on the PC board bottom RHS connected to a proto cape by an eight foot shielded cable. Eventually I’ll have a CAN bus driver too but to do that I have to cut trace on the LCD4 from 4D systems since they used one of the CAN bus signals for the Enter Key.

John

And you found a bug in my eeprom parser…

00000030 74 69 73 61 6e 73 20 49 6e 63 42 42 2d 57 31 2d |tisans IncBB-W1-|
00000040 50 38 2e 31 31 00 00 00 00 00 00 00 00 00 00 00 |P8.11…|

and

BeagleBone: cape eeprom: i2c_probe: 0x57: /lib/firmware/BB-W1-P8-00A0.dtbo [0xedc7bef]

I currently exit when i hit “.”…

I need to fix that.

Till then a quick fix is to rename it as “BB-W1-P8-00A0.dtbo”…

Regards,

Robert,
Not enough information for me in your reply.
You wrote.
–> Till then a quick fix is to rename it as “BB-W1-P8-00A0.dtbo”…<–

What “it” is that? Change the EEROM? What needs to be renamed?

Is this bug why
"uboot_overlay_addr3=/lib/firmware/BB-W1-P8.11-00A0.dtbo" is required in /boot/uEnv.txt?
Thanks

John
p.s. Ah. Just looked at your source code. Embedded ‘.’ are not allowed in the file name. So the dts file and resulting dtbo file should be BB-W1-P8_11-00A0.dts (dtbo)
That would explain why I also had a copy of the files named like that. Probably stumbled on that solution by accident. The /lib/firmware has your BB_W1_P9.12 also has the embedded ‘.’.