The next Beagle is here, BeaglePlay!

General Discussion
21

I have tried as

fdtoverlays /boot/overlays/k3-am625-beagleplay-bcfserial-no-firmware.dtbo
and
fdtoverlays /overlays/k3-am625-beagleplay-bcfserial-no-firmware.dtbo

but seems to make no difference. I can see the file is there in /boot/firmware/overlays but dont see any mention of it via beagle-version or dmesg…hmmm…

Is there something one must do to “activate” an overlay after editing extlinux.conf?

Anyway maybe thats a red-herring anyway because I can see bcfserial module is loaded…

22

Hi @BarryBeagle , what kernel version (uname -r)

I’d say, apt update/upgrade, after the board went public more private changes got merged to public repo’s…

Regards,

23

uname

Linux BeaglePlay 5.10.162-ti-arm64-r97 #1bullseye SMP Mon Mar 20 22:22:35 UTC 2023 aarch64 GNU/Linux

beagle-version

eeprom:[BEAGLEPLAY-A0-02007801030101640623001478SSSS]
model:[BeagleBoard.org_BeaglePlay]
dogtag:[BeagleBoard.org Debian Bullseye Xfce Image 2023-02-04]
bootloader:[/dev/mmcblk0boot0]:[tiboot3.bin]:[U-Boot SPL 2021.01-gb248392d (Jan 04 2023 - 19:38:45 +0000)]
bootloader:[/dev/mmcblk0]:[/boot/firmware/tiboot3.bin]:[U-Boot SPL 2021.01-gb248392d (Jan 04 2023 - 19:38:45 +0000)]
bootloader:[/dev/mmcblk0]:[/boot/firmware/tispl.bin]:[U-Boot SPL 2021.01-gb248392d (Jan 04 2023 - 19:38:45 +0000)]
bootloader:[/dev/mmcblk0]:[/boot/firmware/u-boot.img]:[U-Boot 2021.01-gb248392d (Jan 04 2023 - 19:38:45 +0000)]
kernel:[5.10.162-ti-arm64-r97]
nodejs:[v12.22.12]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-u-boot-sk-am62]:[2021.01.20230302.1-0~bullseye+20230302]
pkg:[bb-customizations]:[1.20230309.0-0~bullseye+20230309]
pkg:[bb-usb-gadgets]:[1.20230216.0-0~bullseye+20230216]
pkg:[bb-wl18xx-firmware]:[1.20221220.0-0~bullseye+20221220]
cmdline:[root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait net.ifnames=0 quiet]
dmesg | grep remote
[    4.257947] remoteproc remoteproc0: 30074000.pru is available
[    4.258695] remoteproc remoteproc1: 30078000.pru is available
[    7.645473] k3-m4-rproc 5000000.m4fss: configured M4 for remoteproc mode
[    7.670421] remoteproc remoteproc2: 5000000.m4fss is available
[    7.672878] remoteproc remoteproc2: Direct firmware load for am62-mcu-m4f0_0-fw failed with error -2
[    7.672916] remoteproc remoteproc2: powering up 5000000.m4fss
[    7.673014] remoteproc remoteproc2: Direct firmware load for am62-mcu-m4f0_0-fw failed with error -2
[    7.673026] remoteproc remoteproc2: request_firmware failed: -2
dmesg | grep pru
[    4.257947] remoteproc remoteproc0: 30074000.pru is available
[    4.258695] remoteproc remoteproc1: 30078000.pru is available
dmesg | grep pinctrl-single
[    1.609272] pinctrl-single 4084000.pinctrl: 34 pins, size 136
[    1.609781] pinctrl-single f4000.pinctrl: 171 pins, size 684

One thing that occurs to me is I did a git pull in /opt/source in order to apply the fix to enable R4F remoteproc. Perhaps it has something to do with that??

24

Where is /boot/UEnv.txt on the Play?

–Mark

25

It’s under: /boot/firmware/extlinux/extlinux.conf

Regards,

26

Thanks @RobertCNelson , but I don’t see how to tell it which image to boot from.

27

i know you like to customize… extlinux.conf supports a similar menu system like grub, so you can list multiple kernel options.

Sadly since we only store the active kernel under /boot/firmware/ for u-boot to operate on. To swap kernel’s you will need to manually do what is shown in /etc/kernel/postinst.d/zz-uenv_txt or just install the linux-image*deb and this will auto run:

if [ -f /boot/firmware/extlinux/extlinux.conf ] ; then
        if [ -f /boot/vmlinuz-${version} ] ; then
                rm -f /boot/firmware/Image || true
                cat /boot/vmlinuz-${version} | gunzip -d > /boot/firmware/Image
                cp -v /usr/lib/linux-image-${version}/ti/k3-*.dtb /boot/firmware/ || true
                rm -f /boot/firmware/initrd.img || true
                cp -v /boot/initrd.img-${version} /boot/firmware/initrd.img || true
                if [ -d /usr/lib/linux-image-${version}/ti/overlays/ ] ; then
                        mkdir -p /boot/firmware/overlays/ || true
                        cp -v /usr/lib/linux-image-${version}/ti/overlays/*.dtbo /boot/firmware/overlays/ || true
                fi
                echo "zz-uenv_txt: Updated extlinux.conf /boot/firmware/ for: [${version}]"
        fi
fi

Regards,
28

Hi,
Where can I find video output OLDI (LVDS) test setup/plan and results?
Thanks
Paul

29

Think you meant user button (USER_BTN) here. Regarding the schematic, Am I reading this right? Boot mode 3,11,13 are pulled low with USER_BTN?
But Other pins are high, so I’m not tracking how the schematic gives the boot modes described in the notes.
Also, I’d like to test Ethernet Boot as Backup Option - its not possible currently but perhaps blue wire might get me there.