Totally confused about Debian 8, device-tree overlays, and SPIDEV

Wally_Bkg · September 14, 2015, 11:14pm

I’ve a Beaglebone white running Debian 8 image from Robert Nelson:
cat /etc/dogtag: BeagleBoard.org Debian Image 2015-08-16
uname -a: 4.1.6-ti-r14 #1 SMP PREEMPT Thu Sep 3 18:56:03 UTC 2015 armv7l GNU/Linux
ls /dev/spi*: /dev/spidev1.0 /dev/spidev1.1 /dev/spidev2.0 /dev/spidev2.1

I’ve an A5A BeableboneBlack running debian 8 image from Rebort Nelson:
cat /etc/dogtag: BeagleBoard.org Debian Image 2015-04-12
uname -a: 4.1.6-ti-r14 #1 SMP PREEMPT Thu Sep 3 18:56:03 UTC 2015 armv7l GNU/Linux
ls /dev/spi*: ls: cannot access /dev/spi*: No such file or directory

I’ve played with a variety of kernels on both systems trying to track down a USB webcam issue without any success, and have settled on 4.1.6-ti-r14 for no particular reason.

I don’t recall doing anything specific to get SPIDEV active on the BBW and am at a loss as to why its not available on the BBB.

I do note these entries are in /lib firmware on the White but not the Black (along with some others that don’t seem relative at the moment:
BB-ADC-00A0.dtbo
BB-BBBMINI-00A0.dtbo
BB-BONE-AUDI-02-00A0.dtbo
BB-BONE-BACONE-00A0.dtbo
BB-BONE-CRYPTO-00A0.dtbo
BB-BONE-DVID-01-00A3.dtbo
BB-BONE-LCD3-01-00A2.dtbo
BB-BONE-LCD4-01-00A1.dtbo
BB-BONE-LCD7-01-00A3.dtbo
BB-BONE-REPLICAP-00B1.dtbo
BB-BONE-SERL-03-00A1.dtbo
BB-CAN1-00A0.dtbo
BB-I2C1-00A0.dtbo
BB-I2C1-PCA9685-00A0.dtbo
BB-RELAY-4PORT-00A0.dtbo
BB-RTC-01-00A0.dtbo
BB-SPI0-MCP3008-00A0.dtbo
BB-SPIDEV0-00A0.dtbo
BB-SPIDEV1-00A0.dtbo
BB-SPIDEV1A1-00A0.dtbo
BB-UART1-00A0.dtbo
BB-UART2-00A0.dtbo
BB-UART4-00A0.dtbo
BB-UART5-00A0.dtbo

Presumably one of the other kernels I tried has installed these dtbo files. Can I just copy them from the White to the Black and expect SPIDEV to work?
Do I have to do something else on the BBB?

Neither system has anything in /etc/default/capemgr and I’ve never touched uEnv.txt on the white, and on the Black I only changed the cmdline
since my monitor doesn’t do edid right on the BBB and this gives a more readable display:

default

#cmdline=quiet

my monitor that doesn’t get edid right

cmdline=quiet video=HDMI-A-1:1280x720M@60

RobertCNelson · September 14, 2015, 11:52pm

I've a Beaglebone white running Debian 8 image from Robert Nelson:
cat /etc/dogtag: BeagleBoard.org Debian Image 2015-08-16
uname -a: 4.1.6-ti-r14 #1 SMP PREEMPT Thu Sep 3 18:56:03 UTC 2015 armv7l
GNU/Linux
ls /dev/spi*: /dev/spidev1.0 /dev/spidev1.1 /dev/spidev2.0
/dev/spidev2.1

I've an A5A BeableboneBlack running debian 8 image from Rebort Nelson:
cat /etc/dogtag: BeagleBoard.org Debian Image 2015-04-12
uname -a: 4.1.6-ti-r14 #1 SMP PREEMPT Thu Sep 3 18:56:03 UTC 2015 armv7l
GNU/Linux
ls /dev/spi*: ls: cannot access /dev/spi*: No such file or directory

I've played with a variety of kernels on both systems trying to track down a
USB webcam issue without any success, and have settled on 4.1.6-ti-r14 for
no particular reason.

I don't recall doing anything specific to get SPIDEV active on the BBW and
am at a loss as to why its not available on the BBB.

I do note these entries are in /lib firmware on the White but not the Black
(along with some others that don't seem relative at the moment:
BB-ADC-00A0.dtbo
BB-BBBMINI-00A0.dtbo
BB-BONE-AUDI-02-00A0.dtbo
BB-BONE-BACONE-00A0.dtbo
BB-BONE-CRYPTO-00A0.dtbo
BB-BONE-DVID-01-00A3.dtbo
BB-BONE-LCD3-01-00A2.dtbo
BB-BONE-LCD4-01-00A1.dtbo
BB-BONE-LCD7-01-00A3.dtbo
BB-BONE-REPLICAP-00B1.dtbo
BB-BONE-SERL-03-00A1.dtbo
BB-CAN1-00A0.dtbo
BB-I2C1-00A0.dtbo
BB-I2C1-PCA9685-00A0.dtbo
BB-RELAY-4PORT-00A0.dtbo
BB-RTC-01-00A0.dtbo
BB-SPI0-MCP3008-00A0.dtbo
BB-SPIDEV0-00A0.dtbo
BB-SPIDEV1-00A0.dtbo
BB-SPIDEV1A1-00A0.dtbo
BB-UART1-00A0.dtbo
BB-UART2-00A0.dtbo
BB-UART4-00A0.dtbo
BB-UART5-00A0.dtbo

So what you are seeing with "2015-08-16" is the full integration of
v4.1.x + bb.org-overlays (1) + config-pin (2), known as the
"universal-io"...

1: GitHub - beagleboard/bb.org-overlays: Device Tree Overlays for bb.org boards
2: GitHub - cdsteinkuehler/beaglebone-universal-io: Device tree overlay and support scripts for using most available hardware I/O on the BeagleBone without editing dts files or rebuilding the kernel

Presumably one of the other kernels I tried has installed these dtbo files.
Can I just copy them from the White to the Black and expect SPIDEV to work?
Do I have to do something else on the BBB?

So to "sync" 2015-04-12 to 2015-08-16..

1: Update /opt/scripts/

cd /opt/scripts/
git pull

Based on a whole list of critera, we load a specific: "config-pin overlay"

github.com

RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L279


      
          	mac_addr0=$(hexdump -v -e '1/1 "%02X" ":"' ${mac_address} | sed 's/.$//')
          	echo "${log} cpsw: ${mac_addr0}"
          elif [ -f ${mac_address_v54} ] && [ -f /usr/bin/hexdump ] ; then
          	echo "${log} cpsw: ethernet@0/slave@200/mac-address"
          	mac_addr0=$(hexdump -v -e '1/1 "%02X" ":"' ${mac_address_v54} | sed 's/.$//')
          	echo "${log} cpsw: ${mac_addr0}"
          else
          	echo "${log} cpsw: mac-address location changed again..."
          	mac_addr0="1C:BA:8C:A2:ED:68"
          	echo "${log} cpsw: ${mac_addr0}"
          fi
          
          #Some devices are showing a blank mac_addr0 [00:00:00:00:00:00], let's fix that up...
          if [ "x${mac_addr0}" = "x00:00:00:00:00:00" ] ; then
          	echo "${log} cpsw: mac came up 00:00:00:00:00:00 fixing..."
          	mac_addr0="1C:BA:8C:A2:ED:68"
          	echo "${log} cpsw: ${mac_addr0}"
          fi
          
          
          mac_addr0_octet_1_5=$(echo ${mac_addr0} | cut -c 1-14)

2: Update "bb.org-overlays"

git clone GitHub - beagleboard/bb.org-overlays: Device Tree Overlays for bb.org boards
cd ./bb.org-overlays

./dtc-overlay.sh
./install.sh

3: update "config-pin"..

git clone GitHub - cdsteinkuehler/beaglebone-universal-io: Device tree overlay and support scripts for using most available hardware I/O on the BeagleBone without editing dts files or rebuilding the kernel
sudo cp -v ./beaglebone-universal-io/config-pin /usr/local/bin/
sudo chmod +x /usr/local/bin/config-pin

Neither system has anything in /etc/default/capemgr and I've never touched
uEnv.txt on the white, and on the Black I only changed the cmdline
since my monitor doesn't do edid right on the BBB and this gives a more
readable display:
# default
#cmdline=quiet
# my monitor that doesn't get edid right
cmdline=quiet video=HDMI-A-1:1280x720M@60

Btw, since the white lacks emmc/hdmi we can assume a few things, so if
you need a specific perpheral that's used by eMMC/hdmi/etc, make sure
you enable the custom "black" *.dtb

github.com

RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L244


      
          if [ ! "x${usb_image_file}" = "x" ] ; then
          	echo "${log} usb_image_file=[`readlink -f ${usb_image_file}`]"
          fi
          
          #pre nvmem...
          eeprom="/sys/bus/i2c/devices/0-0050/eeprom"
          if [ -f ${eeprom} ] && [ -f /usr/bin/hexdump ] ; then
          	usb_iserialnumber=$(hexdump -e '8/1 "%c"' ${eeprom} -n 28 | cut -b 17-28)
          fi
          
          #[PATCH (pre v8) 0/9] Add simple NVMEM Framework via regmap.
          eeprom="/sys/class/nvmem/at24-0/nvmem"
          if [ -f ${eeprom} ] && [ -f /usr/bin/hexdump ] ; then
          	usb_iserialnumber=$(hexdump -e '8/1 "%c"' ${eeprom} -n 28 | cut -b 17-28)
          fi
          
          #[PATCH v8 0/9] Add simple NVMEM Framework via regmap.
          eeprom="/sys/bus/nvmem/devices/at24-0/nvmem"
          if [ -f ${eeprom} ] && [ -f /usr/bin/hexdump ] ; then
          	usb_iserialnumber=$(hexdump -e '8/1 "%c"' ${eeprom} -n 28 | cut -b 17-28)
          fi

Regards,

Wally_Bkg · September 15, 2015, 6:12pm

Thank you so much.
Its easy when you tell me how to do it

If I’d updated the kernel with your /opt/scripts/update_kernel.sh instead of using apt-get install linux-image- would all this have happened "automatically?

If so perhaps a little more details in the Kernel Upgrade section of the BeagleBoard:BeagleBoneBlack Debian Wiki about the shell script parameters would help with making a kernel selection.

Thanks again for a quick and correct response to solve my issue!

–wally.

RobertCNelson · September 15, 2015, 6:20pm

Thank you so much.
Its easy when you tell me how to do it

If I'd updated the kernel with your /opt/scripts/update_kernel.sh instead of
using apt-get install linux-image- would all this have happened
"automatically?

update_kernel.sh only installs the linux-image + (sgx kernel modules)
via apt-get...

If so perhaps a little more details in the Kernel Upgrade section of the
BeagleBoard:BeagleBoneBlack Debian Wiki about the shell script parameters
would help with making a kernel selection.

Thanks again for a quick and correct response to solve my issue!

For the overlay repo, i'm currently waiting to this dtc patchset hits
the dtc repo..

Then i'll package dtc & bb.org-overlays...

Just don't want to get stuck in a pant's down 3.8 situation again.

Regards,