Debian 11 (bullseye) Testing Images

I’m using the internal EMMC, which is 4GB. So it’s full right now!
Let me check what installed the compiler, which I think was not installed by default?

Any hint about FSCK? Where can I configure this?

add it to /boot/uEnv.txt (cmdline) line…

Regards,

1 Like

Hi All,

I did a clean install with am335x-debian-11.2-iot-armhf and checked df -h on the eMMC. It seems that this image fills up majority of the eMMC.

toon@BeagleBone:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            213M     0  213M   0% /dev
tmpfs            49M  1.3M   47M   3% /run
/dev/mmcblk1p1  3.5G  3.2G  125M  97% /
tmpfs           241M     0  241M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            49M     0   49M   0% /run/user/1000

Is there anything obvious that can be removed? With this amount of default install, it becomes hard to still use the eMMC. Should I switch to running of an SD card?

I tried the minimal image, and that seems the be better.

debian@BeagleBone:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            215M     0  215M   0% /dev
tmpfs            49M  1.3M   48M   3% /run
/dev/mmcblk1p1  3.5G  856M  2.5G  26% /
tmpfs           242M     0  242M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            49M     0   49M   0% /run/user/1000

I’ve installed samba which takes up 100MB, but otherwise it seems to be fitting…

Hi there,

Apologies in advance if this is the wrong thread to post my question…

I have a BeagleBone Blue and tried out a recent ‘bullseye’ image from here and also latest ‘buster’ console image from here - both running from sdcard.

When I run ‘rc_test_drivers’ (from librobotcontrol) I get this (expected) result under ‘buster’:

root@beaglebone:~# rc_test_drivers

Kernel: 4.19.94-ti-r42
BeagleBoard_org Debian Buster Console Image 2020-04-06
Debian: 10.12

PASSED: gpio 0
PASSED: gpio 1
PASSED: gpio 2
PASSED: gpio 3
PASSED: pwm0
PASSED: pwm1
PASSED: pwm2
PASSED: eqep0
PASSED: eqep1
PASSED: eqep2
PASSED: pru-rproc
PASSED: uart1
PASSED: uart2
PASSED: uart4
PASSED: uart5
PASSED: i2c1
PASSED: i2c2
PASSED: spi
PASSED: LED
PASSED: ADC iio

Currently running on a:
MODEL_BB_BLUE
Robot Control library Version:
1.0.5

However, the result under ‘bullseye’ is not so good:

root@BeagleBone:~# rc_test_drivers

Kernel: 5.10.109-ti-r43
BeagleBoard_org Debian Bullseye Minimal Image 2022-05-01
Debian: 11.3

PASSED: gpio 0
PASSED: gpio 1
PASSED: gpio 2
PASSED: gpio 3
ERROR: ti-pwm driver not loaded for hrpwm0
ERROR: ti-pwm driver not loaded for hrpwm1
ERROR: ti-pwm driver not loaded for hrpwm2
ERROR: ti-eqep driver not loaded for eqep0
ERROR: ti-eqep driver not loaded for eqep1
ERROR: ti-eqep driver not loaded for eqep2
PASSED: pru-rproc
ERROR: uart1 driver not loaded
ERROR: uart2 driver not loaded
ERROR: uart4 driver not loaded
ERROR: uart5 driver not loaded
ERROR: i2c1 driver not loaded
PASSED: i2c2
ERROR: spi driver not loaded
PASSED: LED
PASSED: ADC iio

Currently running on a:
MODEL_BB_BLUE
Robot Control library Version:
1.0.5

After enabling some extra overlays (guessing) in uEnv.txt:

uname_r=5.10.109-ti-r43
dtb=am335x-boneblue.dtb
enable_uboot_overlays=1
uboot_overlay_pru=AM335X-PRU-RPROC-4-19-TI-00A0.dtbo
uboot_overlay_addr0=BB-I2C1-00A0.dtbo
uboot_overlay_addr1=BB-SPIDEV0-00A0.dtbo
uboot_overlay_addr2=BB-SPIDEV1-00A0.dtbo
uboot_overlay_addr3=BB-UART1-00A0.dtbo
uboot_overlay_addr4=BB-UART4-00A0.dtbo
uboot_overlay_addr5=BB-UART5-00A0.dtbo
uboot_overlay_addr6=BB-UART4-RTSCTS-00A0.dtbo
uboot_overlay_addr7=BB-I2C2-RTC-DS1338.dtbo
disable_uboot_overlay_video=1
dtb_overlay=dev-USB-PWR-CTL-00A1.dtbo
enable_uboot_cape_universal=1
console=ttyS0,115200n8
cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100

…made only slight difference:

root@BeagleBone:/boot# rc_test_drivers

Kernel: 5.10.109-ti-r43
BeagleBoard_org Debian Bullseye Minimal Image 2022-05-01
Debian: 11.3

PASSED: gpio 0
PASSED: gpio 1
PASSED: gpio 2
PASSED: gpio 3
ERROR: ti-pwm driver not loaded for hrpwm0
ERROR: ti-pwm driver not loaded for hrpwm1
ERROR: ti-pwm driver not loaded for hrpwm2
ERROR: ti-eqep driver not loaded for eqep0
ERROR: ti-eqep driver not loaded for eqep1
ERROR: ti-eqep driver not loaded for eqep2
PASSED: pru-rproc
ERROR: uart1 driver not loaded
ERROR: uart2 driver not loaded
ERROR: uart4 driver not loaded
ERROR: uart5 driver not loaded
PASSED: i2c1
PASSED: i2c2
PASSED: spi
PASSED: LED
PASSED: ADC iio

Currently running on a:
MODEL_BB_BLUE
Robot Control library Version:
1.0.5

I found there is a ti-eqep kernel module but loading it didn’t make any difference …not sure about the others

So, am I expecting too much from a ‘testing’ image or do I simply need to understand/do more with my configuration to have ‘rc_test_drivers’ produce a 100% PASSED result?

BTW, in case anyone is wondering, I had to manually replace the ‘.’ with a ‘_’ (re ‘BeagleBoard_org’ text in above rc_test_drivers output) as this forum wont let me post more than two links (as a new user) …even though I am not explicitly specifying that text as a link

Hi @RobertCNelson

Am hoping you may be able to comment on my post (above) …suspect my expectations re ‘testing’ images is likely too-high/premature but also hoping full functionality is not too far away?

1 Like

@pka ,

I am not sure how far along you are in this build of librobotcontrol for the am335x-boneblue.dts and kernel 5.10.x but…

  1. GitHub - beagleboard/librobotcontrol: Robotics Focused library for embedded Linux computers.

Seth

P.S. This may help. Also, looking into the issues section could provide some feedback from already configured answers. I am issue 213 on the list. So, w/ time and effort, comes things and stuff. Jump on in!

The Robot Control library has a lot of kernel dependency built into it… Right now it really only supports v4.19.x-ti…

it needs to be ported to v5.4.x-ti/v5.10.x-ti…

Regards,

the solution was
wget https://npmjs.org/install.sh
sudo chmod +x install.sh
sudo ./install.sh|

hello
I’m using this image debian 11 in my beaglebone black, but this image doesn’t have npm and I can’t use manage pallete with node-red, maybe may you help me with this problem in debian 11 latest bone-debian-11.3-iot-armhf-2022-05-10-4gb.img.xz

best regards

There’s a conflict between npm and VS Code Server… Currently the iot snapshots come with VS Code Server installed by default…

Regards,

Maybe someone have a copy of this image ? the link is broken now
bone-debian-11.3-iot-armhf-2022-05-10-4gb.img.xz

This image was working very good in a project, if you can share thanks a lot !

Best regards

and re-uploaded… That’s scary, that was a daily ‘build’ snapshot…

Either make sure to archive the version you need, or look to switch to the monthly snapshots…

Regards,