We use cookies to provide our visitors with an optimal site experience. View our privacy notice and cookie notice to learn more about how we use cookies and how to manage your settings. By proceeding on our website you consent to the use of cookies.

Continue Continue Privacy Notice

BBAI and SPI/BONE-SPIx_x?

Support Linux Discussions
#1

Hello,

It is late now but whenever anyone wakes up, please do reply. I am trying to configure the AI to work w/ some SPI devices on either the BONE bus or via /dev/spidevx_x/

I tried to change branches in the BeagleBoard-DeviceTrees for kernel 5.4.x-ti and 5.4.x-ti-overlays.

I have been unsuccessful so far. I tried kernel 4.19.x too. So, I cloned, w/ git, the BeagleBoard-DeviceTrees repo. and used make and make install.

I even changed out some of the .dts files to make them so they could work on the current configuration for the AI, e.g. P9_17, 18, 21, 22.

I was able to make bone show up in /dev/ once but all that was available was i2c.

Seth

P.S. Is there a secret or another method outside of using kit to compile the DeviceTrees from beagleboard.org. I have tried different images for the BBAI. None of which have had me making progress.

Also, I see grub is being used along w/ /boot/uEnv.txt being bare and w/out the current ideas from the BBB/BBBW realm w/ uboot-overlays.

#2

Hi @silver2row , the only kernel branch with that feature is 4.19.x-ti…

git clone -b ti-linux-4.19.y https://github.com/RobertCNelson/ti-linux-kernel-dev/
cd ./ti-linux-kernel-dev/
./build_deb.sh

Please run:

sudo /opt/scripts/tools/version.sh

To confirm your setup.

Regards,

#3

Hello Sir,

This is sudo ./version.sh before the git clone -b ti-linux-4.19.y https://github.com/RobertCNelson/ti-linux-kernel-dev/ command.

git:/opt/scripts/:[481db95174653ba485cca3797d4bbbe03c0cded0]
model:[BeagleBoard.org_BeagleBone_AI]
dogtag:[rcn-ee.net Debian Console Image 2020-04-09]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 2019.07-rc4-00001-g607b5b738b (Jul 06 2019 - 21:01:15 -0500)]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am5729-beagleboneai.dts]
kernel:[4.19.94-ti-r42]
/boot/uEnv.txt Settings:
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.14.20200403.0-0rcnee0~buster+20200403]
pkg:[bb-customizations]:[1.20200306.0-0rcnee0~buster+20200306]
pkg:[bb-usb-gadgets]:[1.20200322.0-0rcnee0~buster+20200322]
pkg:[bb-wl18xx-firmware]:[1.20200322.0-0rcnee0~buster+20200322]
pkg:[kmod]:[26-1]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyS0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet]
dmesg | grep remote
[   11.874278] remoteproc remoteproc0: 58820000.ipu is available
[   11.875827] remoteproc remoteproc1: 55020000.ipu is available
[   11.887329] remoteproc remoteproc0: Direct firmware load for dra7-ipu1-fw.xem4 failed with error -2
[   11.887371] remoteproc remoteproc0: powering up 58820000.ipu
[   11.887470] remoteproc remoteproc0: Direct firmware load for dra7-ipu1-fw.xem4 failed with error -2
[   11.887498] remoteproc remoteproc0: request_firmware failed: -2
[   11.907845] remoteproc remoteproc2: 40800000.dsp is available
[   11.918624] remoteproc remoteproc2: Direct firmware load for dra7-dsp1-fw.xe66 failed with error -2
[   11.918662] remoteproc remoteproc2: powering up 40800000.dsp
[   11.918759] remoteproc remoteproc2: Direct firmware load for dra7-dsp1-fw.xe66 failed with error -2
[   11.918788] remoteproc remoteproc2: request_firmware failed: -2
[   11.928214] remoteproc remoteproc3: 41000000.dsp is available
[   11.968520] remoteproc remoteproc3: Direct firmware load for dra7-dsp2-fw.xe66 failed with error -2
[   11.968563] remoteproc remoteproc3: powering up 41000000.dsp
[   11.968661] remoteproc remoteproc3: Direct firmware load for dra7-dsp2-fw.xe66 failed with error -2
[   11.968690] remoteproc remoteproc3: request_firmware failed: -2
[   11.977469] remoteproc remoteproc1: powering up 55020000.ipu
[   11.977510] remoteproc remoteproc1: Booting fw image dra7-ipu2-fw.xem4, size 3751356
[   12.339759] remoteproc remoteproc1: registered virtio0 (type 7)
[   12.339789] remoteproc remoteproc1: remote processor 55020000.ipu is now up
[   22.344582] remoteproc remoteproc1: crash detected in 55020000.ipu: type watchdog
[   22.352293] remoteproc remoteproc1: crash detected in 55020000.ipu: type watchdog
[   22.360031] remoteproc remoteproc1: handling crash #1 in 55020000.ipu
[   22.366960] remoteproc remoteproc1: recovering 55020000.ipu
[   22.461022] remoteproc remoteproc1: stopped remote processor 55020000.ipu
[   22.461053] remoteproc remoteproc1: powering up 55020000.ipu
[   22.489849] remoteproc remoteproc1: Booting fw image dra7-ipu2-fw.xem4, size 3751356
[   22.845749] remoteproc remoteproc1: registered virtio0 (type 7)
[   22.845778] remoteproc remoteproc1: remote processor 55020000.ipu is now up
[   29.278851] remoteproc remoteproc4: 4b234000.pru is available
[   29.303740] remoteproc remoteproc5: 4b238000.pru is available
[   29.316062] remoteproc remoteproc6: 4b2b4000.pru is available
[   29.369366] remoteproc remoteproc7: 4b2b8000.pru is available
dmesg | grep pru
[   24.260334] pruss_uio_shmem 4b200000.pruss_shmem: Allocating gdev
[   24.260448] pruss_uio_shmem 4b200000.pruss_shmem: Allocating info
[   24.260470] pruss_uio_shmem 4b200000.pruss_shmem: Requesting resource
[   24.260980] pruss_uio_shmem 4b200000.pruss_shmem: Mapping resource
[   24.261485] pruss_uio_shmem 4b200000.pruss_shmem: Registering with uio driver
[   24.276417] pruss_uio_shmem 4b200000.pruss_shmem: Saving platform data
[   24.328717] pruss_uio_shmem 4b280000.pruss_shmem: Allocating gdev
[   24.328926] pruss_uio_shmem 4b280000.pruss_shmem: Allocating info
[   24.328951] pruss_uio_shmem 4b280000.pruss_shmem: Requesting resource
[   24.329173] pruss_uio_shmem 4b280000.pruss_shmem: Mapping resource
[   24.329215] pruss_uio_shmem 4b280000.pruss_shmem: Registering with uio driver
[   24.331241] pruss_uio_shmem 4b280000.pruss_shmem: Saving platform data
[   29.278851] remoteproc remoteproc4: 4b234000.pru is available
[   29.279084] pru-rproc 4b234000.pru: PRU rproc node pru@4b234000 probed successfully
[   29.303740] remoteproc remoteproc5: 4b238000.pru is available
[   29.304035] pru-rproc 4b238000.pru: PRU rproc node pru@4b238000 probed successfully
[   29.316062] remoteproc remoteproc6: 4b2b4000.pru is available
[   29.320083] pru-rproc 4b2b4000.pru: PRU rproc node pru@4b2b4000 probed successfully
[   29.369366] remoteproc remoteproc7: 4b2b8000.pru is available
[   29.369634] pru-rproc 4b2b8000.pru: PRU rproc node pru@4b2b8000 probed successfully
dmesg | grep pinctrl-single
[    0.838736] pinctrl-single 4a003400.pinmux: 282 pins, size 1128
dmesg | grep gpio-of-helper
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

Seth

#4

Yeap, everything is just too old on that image… A kernel upgrade isn’t going to fix your problem…

Just grab:

https://rcn-ee.net/rootfs/bb.org/testing/2021-02-22/buster-console/am57xx-debian-10.8-console-armhf-2021-02-22-1gb.img.xz

Regards,

#5

Yes Sir,

Thank you for waking me up!

Seth

P.S. Off to get the newer image.

#6

Hello,

Scratch my last reply…it boots now! Yes sir!

Seth