problem to load dtbo in Uenv.txt

General Discussion
1

###Additional custom capes
uboot_overlay_addr4=/lib/firmware/ADAFRUIT-SPI0-00A0.dtbo
#uboot_overlay_addr5=/lib/firmware/.dtbo
#uboot_overlay_addr6=/lib/firmware/.dtbo
#uboot_overlay_addr7=/lib/firmware/.dtbo

i don’t undertand why don’t load this file
it doesn’t appear in kernel initial messages…

2

They are loaded by uboot… Before the kernel starts. Plug in a USB to serial adapter into j1 and you’ll see it happen…

3

yes I’m connecting from the serial I see the kernel, but I don’t see the file being loaded

4

Checking for: /uEnv.txt …
Checking for: /boot.scr …
Checking for: /boot/boot.scr …
Checking for: /boot/uEnv.txt …
gpio: pin 55 (gpio 55) value is 1
2183 bytes read in 30 ms (70.3 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt…
gpio: pin 56 (gpio 56) value is 1
Running uname_boot …
loading /boot/vmlinuz-4.19.94-ti-r73 …
10170880 bytes read in 703 ms (13.8 MiB/s)
loading /boot/dtbs/4.19.94-ti-r73/am335x-boneblack-wireless.dtb …
61601 bytes read in 67 ms (897.5 KiB/s)
loading /boot/initrd.img-4.19.94-ti-r73 …

5

Looks like your missing…

enable_uboot_overlays=1

In /boot/uEnv.txt

6

no ,there is enable_uboot_overlays=1

7

is not comment…

8

How old is u-boot?

sudo /opt/scripts/tools/version.sh

or

sudo beagle-version

One of those should be installed.

Regards,

9

UBOOT: Booted Device-Tree:[am335x-boneblack-wireless.dts]
kernel:[4.19.94-ti-r73]
nodejs:[v10.15.2]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr7=/lib/firmware/testoverlay.dtbo]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
pkg:[bb-cape-overlays]:[4.14.20210821.0-0~buster+20210821]
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]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~buster+20190327]
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=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait]
dmesg | grep remote

10

with the sudo /opt/scripts/tools/version.sh command I see testoveray.dtbo loaded, yes there is, but I don’t see it with the start kernel. however I’m trying to insert a dtbo file in the kernel, and to implement a compatible probe function, but I still haven’t succeeded, the module doesn’t match

11

what image are you running?

cat /etc/dogtag
cat /etc/rcn-ee.conf

version.sh should have shown more…

Normally i’d say to run:

sudo apt update
sudo apt install bb-u-boot-am335x-evm

Then:

sudo /opt/u-boot/bb-u-boot-am335x-evm/install.sh
sudo reboot

Regards,

12

BeagleBoard.org Debian Buster IoT Image 2020-04-06

13

distro=Debian
deb_codename=buster
rfs_username=debian
release_date=2020-04-06
third_party_modules=
abi=ad
image_type=iot

14

Okay weird… those commands are safe on that…

15

what is bb-u-boot-am335x-evm for?

16

u-boot for all BeagleBoard.org am335x based devices.

Regards,

17

sorry robert i messed up, i uploaded the dtbo test file in Uenv.txt but i got an error

18

uboot_overlays: loading /lib/firmware/prova.dtbo …
1221 bytes read in 344 ms (2.9 KiB/s)
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND

19

just that i entered pxelinux and i don’t know how to delete that file to reboot

20

this is the file but i don’t understand why…
*/
/dts-v1/;
/plugin/;

/ {
compatible = “ti,beaglebone”, “ti,beaglebone-black”;

/* identification */
part-number = "BB-I2C1";
version = "00A0";

/* state the resources this cape uses */
exclusive-use =
	/* the pin header uses */
	"P9.18",	/* i2c1_sda */
	"P9.17",	/* i2c1_scl */
	/* the hardware ip uses */
	"i2c1";

fragment@0 {
	target = <&am33xx_pinmux>;
	__overlay__ {
		bb_i2c1_pins: pinmux_bb_i2c1_pins {
			pinctrl-single,pins = <
				0x158 0x72	/* spi0_d1.i2c1_sda, SLEWCTRL_SLOW | INPUT_PULLUP | MODE2 */
				0x15c 0x72	/* spi0_cs0.i2c1_scl, SLEWCTRL_SLOW | INPUT_PULLUP | MODE2 */
			>;
		};
	};
};

fragment@1 {
	target = <&i2c1>;	/* i2c1 is numbered correctly */
	__overlay__ {
		status = "okay";
		pinctrl-names = "default";
		pinctrl-0 = <&bb_i2c1_pins>;

		/* this is the configuration part */
		clock-frequency = <100000>;

		#address-cells = <1>;
		#size-cells = <0>;

		/* add any i2c devices on the bus here */

		// commented out example of a touchscreen (taken from BB-BONE-LCD7-01-00A4) */
		// maxtouch@4a {
		//	compatible = "mXT224";
		//	reg = <0x4a>;
		//	interrupt-parent = <&gpio4>;
		//	interrupts = <19 0x0>;
		//	atmel,irq-gpio = <&gpio4 19 0>;
		// };
	};
};

};