For the BeagleBoard.org family of Boards, i’ve kinda taken this release to “start-over” on things, for users running Debian 10 (Buster), feel free to upgrade thru apt, but tweak your /etc/apt/sources.list as the debian-security repo changed on this release…
deb http://deb.debian.org/debian/ bullseye main contrib non-free
#deb-src http://deb.debian.org/debian/ bullseye main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
#deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free
#deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free
deb [arch=armhf] http://repos.rcn-ee.com/debian/ bullseye main
#deb-src [arch=armhf] http://repos.rcn-ee.com/debian/ bullseye main
For users looking to start fresh, i have daily images here:
Hi Robert,
I’m currently using … (as follows below)… for lvlg development with a 4DLCD70T display, HW Ver 1.01 and I get a display prompt on the LCD after booting. with the latest image (info at end of this reply) there is no display prompt.
Do I need a different dtb to get the 4DLCD70T to work?
thanks,
amf
Linux beaglebone 5.4.106-ti-rt-r31 #1 SMP PREEMPT_RT Sun May 30 11:46:31 CDT 20x
during boot:
debug: process_cape_part_number:[BB-BONE-LCD7-01.]
BeagleBone: cape eeprom: i2c_probe: 0x54: /lib/firmware/BB-BONE-LCD7-01-00A3.dt]
amf@beaglebone:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for amf:
git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46]
eeprom:[A335BNLT000C1619BBBG0011]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-g07d570]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
UBOOT: Loaded Overlay:[BB-BONE-LCD7-01-00A3]
kernel:[5.4.106-ti-rt-r31]
nodejs:[v10.24.0]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.14.20210416.0-0~buster+20210416]
pkg:[bb-wl18xx-firmware]:[1.20210520.0-0~buster+20210520]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~buster+20200716]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/]
dmesg | grep remote
[ 1.964791] remoteproc remoteproc0: wkup_m3 is available
[ 2.141
588] remoteproc remoteproc1: 4a334000.pru is available
[ 2.143965] remoteproc remoteproc2: 4a338000.pru is available
[ 2.149765] remoteproc remoteproc0: powering up wkup_m3
[ 2.149927] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf,8
[ 2.153268] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
[ 2.141588] remoteproc remoteproc1: 4a334000.pru is available
[ 2.141812] pru-rproc 4a334000.pru: PRU rproc node /ocp/interconnect@4a00000y
[ 2.143965] remoteproc remoteproc2: 4a338000.pru is available
[ 2.144167] pru-rproc 4a338000.pru: PRU rproc node /ocp/interconnect@4a00000y
dmesg | grep pinctrl-single
[ 1.420200] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[ 1.440321] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END
new 8/2021 image
during boot: BeagleBone Cape EEPROM: 0x54: BB-BONE-LCD7-01-00A3.dtbo [0xfc93c8f]
no:
/opt/scripts/tools/version.sh
uname:
Linux BeagleBone 5.10.41-ti-r12 #1bullseye SMP PREEMPT Tue Aug 10 10:32:45 UTC 2021 armv7l GNU/Linux
Thanks, this fixed the display issue.
sudo apt install bb-cape-overlays
FYI,
debian@BeagleBone:~$ sudo beagle-version
[sudo] password for debian:
sudo: beagle-version: command not found
debian@BeagleBone:~$ sudo beagle-config
sudo: beagle-config: command not found
Silly question, I’m updating a fleet of PocketBeagles which started out running Debian Stretch-based images.
The last OS update to Buster was achieved by adjusting /etc/apt/sources.list and doing an apt-get update && apt-get dist-upgrade -y, and that seemed to go fine.
I did the same trick yesterday on one of the nodes, and had the update fall flat on its face. I should hook up a serial console to see where it’s failing, but effectively it bricked the OS.
For now I just took a back-up of that failed update, then flashed the latest console image and I’m trying an apt-get dist-upgrade to Bullseye on that now. Update: Having done this, the PocketBeagle boots, but it appears the USB gadget support is broken by this sort of update, making the device inaccessible unless serial console is connected.
Looking in Index of /rootfs/debian-armhf/2021-12-12 I don’t see the console image listed. Are there plans to release such an image? In the application I’m using these for, we’re not using the Cloud9 and NodeRED features that are part of the IoT image, so keeping to a plain and minimal image is desirable.
I’l need to write some more directions on moving from stretch/buster to bullseye…
I’ve dropped conman for systemd-networkd, this allows us to use simple udev rules to enable a lot of things we did in stretch/buster (some of which is not backwards portable to stretch/buster due to new systemd features…)
the opt scripts directory is gone, everything has a debian package now…
yeah, i think we are ready for console/iot images for Bullseye, i’ve got most things works now days on Bullseye…
In 2019 I finally finished my BBB-based NAS (with laser-cut housing). If you’re interested, read about it here.
Since 2018 it didn’t really get any proper software update, and other than the security issues (it’s not internet accessible right now), I’m also very limited by the packages still available.
I’m currently running on Ubuntu 14.04.6 LTS (GNU/Linux 4.4.21-ti-r45 armv7l).
With Debian 11, I could upgrade to the v5 kernel and get kernel support for exFAT so that our removable storage works on all OSses (windows + mac + linux).
Long story short: I’ve not been very active with embedded software in recent years and could use some advice on which image is stable to do a fresh install on the BBB. My goal is to have another rock-solid system that can last for years.
Features I’ve been using
EXT4 filesystem on eMMC (set up to auto-fix when power goes off unexpectedly)
EXT4 filesystem on SSD + HD (I’m spinning the drive down automatically when not used)
Solid kernel (the first one I had wasn’t stable)
Want to add
Set up a solid rsync backup
exFAT to backup external drives
Nothing too crazy, it just needs to be solid and low maintenance for years to come
Hi @phalox , so our 5.4.x-ti, 5.10.x-ti and 5.15.x-bone branches have exfat built-in. For the am335x you really don’t see an advantage between ti the branch and mainline anymore. As 99% of everything is mainline…
Most of my current testing is on v5.10.x and v5.15.x… I’m just finally starting to EOL v4.19.x in my test farm this week… (how many years of testing is that; Nov 2018… so 3 years…)
For the am335x i’d say start with v5.15.x and let me know if you have issues. Right now I’ve got 4 boards in my automatic tester running v5.15x, with more being transited later in the next few weeks…
Starting the 1st of the year, i will have Monthy Bullseye images, you can see a sneak peak with:
Almost 2 months later! It’s about time I get started on this. But before I break my production system running off of the EMMC, I wanted to double check some things.
I see the latest testing image is am335x-debian-11.2-iot-armhf-2022-02-03-4gb.img.xz
Use balenaEtcher - Flash OS images to SD cards & USB drives to put it on an SD card
Plug it into the bbb, power it and it will boot from the SD card instead?
Hi Robert, I’m running the new image now. On my legacy setup, I forced FSCK to auto fix any issues that might occur on the root file system (usually after power was dropped). I was now trying to reimplement this on the new image, but I’m not sure how to pass the ‘fsck -y’ to the systemd. Any advice?
Is /usr/lib/arm-linux-gnueabihf (913M) installed by default? Or did I somehow put a compiler on this system? It’s so full right now that I cannot even do anything anymore So I’m trying to figure out what to delete.
So I’m trying to figure out what to delete.