Hey Robert,
I’m trying to get the latest Debian 10 snapshot to boot on the Beaglebone AI and it doesn’t seem to boot. When I boot with the serial connector to see what’s going on, it continually resets:
U-Boot 2022.04-ge0d31da5 (Aug 23 2022 - 19:11:21 +0000)
CPU : DRA752-GP ES2.0
Model: BeagleBoard.org BeagleBone AI
Board: BeagleBone AI REV A
DRAM: 1 GiB
Core: 60 devices, 16 uclasses, devicetree: separate
MMC: no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
mmc@480d1000 - probe failed: -110
OMAP SD/MMC: 0, OMAP SD/MMC: 1no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
Loading Environment from nowhere... OK
BeagleBone Cape EEPROM: no EEPROM at address: 0x54
BeagleBone Cape EEPROM: no EEPROM at address: 0x55
BeagleBone Cape EEPROM: no EEPROM at address: 0x56
BeagleBone Cape EEPROM: no EEPROM at address: 0x57
Net: eth2: ethernet@48484000
Press SPACE to abort autoboot in 1 seconds
switch to partitions #0, OK
mmc0 is current device
Partition Map for MMC device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 8192 1835008 3b958808-01 83 Boot
Scanning mmc device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
1395 bytes read in 3 ms (454.1 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt ...
debug: [uname_r=4.19.94-ti-r73] ...
loading /boot/vmlinuz-4.19.94-ti-r73 ...
10170880 bytes read in 443 ms (21.9 MiB/s)
loading /boot/dtbs/4.19.94-ti-r73/am5729-beagleboneai.dtb ...
253052 bytes read in 17 ms (14.2 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
loading /boot/initrd.img-4.19.94-ti-r73 ...
7411241 bytes read in 325 ms (21.7 MiB/s)
debug: [console=ttyS0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet] ...
debug: [bootz 0x82000000 0x88080000:711629 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x9b3200 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f8ee000, end 8ffff629 ... OK
ERROR: reserving fdt memory region failed (addr=95700000 size=100000 flags=4)
ERROR: Failed to allocate 0x40c7c bytes below 0x90000000.
device tree - allocation error
FDT creation failed!
resetting ...
Any ideas?
Hi @pocketnc_john which image is doing that? (date stamp)…
Regards,
So i see… with: am57xx-debian-10.13-console-armhf-2023-05-03-1gb.img.xz
U-Boot 2022.04-ge0d31da5 (Aug 23 2022 - 19:11:21 +0000)
CPU : DRA752-GP ES2.0
Model: BeagleBoard.org BeagleBone AI
Board: BeagleBone AI REV A
DRAM: 1 GiB
Core: 60 devices, 16 uclasses, devicetree: separate
MMC: no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
mmc@480d1000 - probe failed: -110
OMAP SD/MMC: 0, OMAP SD/MMC: 1no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
Loading Environment from nowhere... OK
BeagleBone Cape EEPROM: no EEPROM at address: 0x54
BeagleBone Cape EEPROM: no EEPROM at address: 0x55
BeagleBone Cape EEPROM: no EEPROM at address: 0x56
BeagleBone Cape EEPROM: found EEPROM at address: 0x57
BeagleBone Cape EEPROM: debug part_number field:[BBORG_FAN�������]
BeagleBone Cape EEPROM: debug part_number field HEX:[42424f52475f46414e]
BeagleBone Cape EEPROM: debug version field HEX:[4130ffff]
BeagleBone Cape EEPROM: 0x57 BBORG_FAN-A000.dtbo
Net: eth2: ethernet@48484000
Press SPACE to abort autoboot in 1 seconds
switch to partitions #0, OK
mmc0 is current device
Partition Map for MMC device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 8192 1835008 a6b3a970-01 83 Boot
Scanning mmc device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
1395 bytes read in 4 ms (339.8 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt ...
debug: [uname_r=4.19.94-ti-r73] ...
loading /boot/vmlinuz-4.19.94-ti-r73 ...
10170880 bytes read in 440 ms (22 MiB/s)
loading /boot/dtbs/4.19.94-ti-r73/am5729-beagleboneai.dtb ...
253052 bytes read in 16 ms (15.1 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
uboot_overlays: loading /boot/dtbs/4.19.94-ti-r73/overlays/BBORG_FAN-A000.dtbo ...
526 bytes read in 7 ms (73.2 KiB/s)
uboot_overlays: [uboot_detected_capes=BBORG_FAN,] ...
loading /boot/initrd.img-4.19.94-ti-r73 ...
7411271 bytes read in 322 ms (21.9 MiB/s)
debug: [console=ttyS0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait uboot_detected_capes=BBORG_FAN, coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet] ...
debug: [bootz 0x82000000 0x88080000:711647 88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x9b3200 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f8ee000, end 8ffff647 ... OK
ERROR: reserving fdt memory region failed (addr=95700000 size=100000 flags=4)
Loading Device Tree to 8f84d000, end 8f8edfff ... OK
Starting kernel ...
[ 0.003404] /cpus/cpu@0 missing clock-frequency property
[ 0.003428] /cpus/cpu@1 missing clock-frequency property
[ 0.568645] omap-mailbox 4a0f4000.mailbox: no available mbox devices found
[ 0.568716] omap-mailbox 4883a000.mailbox: no available mbox devices found
[ 0.568782] omap-mailbox 4883c000.mailbox: no available mbox devices found
[ 0.568847] omap-mailbox 4883e000.mailbox: no available mbox devices found
[ 0.569510] omap-mailbox 48844000.mailbox: no available mbox devices found
[ 0.569577] omap-mailbox 48846000.mailbox: no available mbox devices found
[ 0.569644] omap-mailbox 4885e000.mailbox: no available mbox devices found
[ 0.569709] omap-mailbox 48860000.mailbox: no available mbox devices found
[ 0.569773] omap-mailbox 48862000.mailbox: no available mbox devices found
[ 0.569867] omap-mailbox 48864000.mailbox: no available mbox devices found
[ 0.569932] omap-mailbox 48802000.mailbox: no available mbox devices found
[ 1.161605] sdhci-omap 4809c000.mmc: failed to set system capabilities
[ 1.168890] sdhci-omap 480b4000.mmc: failed to set system capabilities
[ 1.370968] dwc3 488d0000.usb: Failed to get clk 'ref': -2
[ 1.451465] omap_voltage_late_init: Voltage driver support not added
[ 1.546456] sdhci-omap 4809c000.mmc: no pinctrl state for ddr_1_8v mode
[ 1.553141] sdhci-omap 4809c000.mmc: no pinctrl state for ddr_3_3v mode
[ 1.559815] sdhci-omap 4809c000.mmc: no pinctrl state for hs200_1_8v mode
[ 1.651011] dwc3 48890000.usb: Failed to get clk 'ref': -2
[ 1.665742] OF: graph: no port node found in /ocp/ocp2scp@4a080000/phy@4a084000
[ 1.674097] dwc3 488d0000.usb: Failed to get clk 'ref': -2
[ 1.703212] omapdss error: HDMI I2C Master Error
[ 2.752924] omapdss error: HDMI I2C Master Error
[ 4.718750] systemd[1]: System cannot boot: Missing /etc/machine-id and /etc is mounted read-only.
[ 4.727802] systemd[1]: Booting up is supported only when:
[ 4.733369] systemd[1]: 1) /etc/machine-id exists and is populated.
[ 4.739743] systemd[1]: 2) /etc/machine-id exists and is empty.
[ 4.745710] systemd[1]: 3) /etc/machine-id is missing and /etc is writable.
[ 10.178593] remoteproc remoteproc0: request_firmware failed: -2
[ 10.193660] remoteproc remoteproc1: request_firmware failed: -2
[ 10.208955] remoteproc remoteproc2: request_firmware failed: -2
[ 10.222779] remoteproc remoteproc3: request_firmware failed: -2
Debian GNU/Linux 10 beaglebone ttyS0
BeagleBoard.org Debian Buster Console Image 2023-05-03
Support: https://bbb.io/debian
default username:password is [debian:temppwd]
beaglebone login:
the ERROR: reserving fdt memory region failed (addr=95700000 size=100000 flags=4) is concering…
Ah…without the cape plugged in:
Checking if uname_r is set in /boot/uEnv.txt ...
debug: [uname_r=4.19.94-ti-r73] ...
loading /boot/vmlinuz-4.19.94-ti-r73 ...
10170880 bytes read in 441 ms (22 MiB/s)
loading /boot/dtbs/4.19.94-ti-r73/am5729-beagleboneai.dtb ...
253052 bytes read in 17 ms (14.2 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
loading /boot/initrd.img-4.19.94-ti-r73 ...
7411271 bytes read in 322 ms (21.9 MiB/s)
debug: [console=ttyS0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet] ...
debug: [bootz 0x82000000 0x88080000:711647 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x9b3200 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f8ee000, end 8ffff647 ... OK
ERROR: reserving fdt memory region failed (addr=95700000 size=100000 flags=4)
ERROR: Failed to allocate 0x40c7c bytes below 0x90000000.
device tree - allocation error
FDT creation failed!
resetting ...
U-Boot 2022.04-ge0d31da5 (Aug 23 2022 - 19:11:21 +0000)
Regards,
So your BBAI booted? Mine got into a reset loop and wouldn’t ever allow me to login.
Sorry, updated in mid post, when i have a cape installed, it boots okay’ish… but with no cape, it reboots… (All my bbai’s have a fan cape, so now to git bisect…)…
Regards,
Ah, gotcha! Yeah, that’s the behavior I’m seeing. Thanks for looking into it!
Oh lovely! Bullseye version work’s… (same git source) U-Boot 2022.04-ge0d31da5 (Aug 23 2022 - 19:11:21 +0000)
U-Boot 2022.04-ge0d31da5 (Aug 23 2022 - 19:11:21 +0000)
CPU : DRA752-GP ES2.0
Model: BeagleBoard.org BeagleBone AI
Board: BeagleBone AI REV A
DRAM: 1 GiB
Core: 60 devices, 16 uclasses, devicetree: separate
MMC: no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
mmc@480d1000 - probe failed: -110
OMAP SD/MMC: 0, OMAP SD/MMC: 1no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
Loading Environment from nowhere... OK
BeagleBone Cape EEPROM: no EEPROM at address: 0x54
BeagleBone Cape EEPROM: no EEPROM at address: 0x55
BeagleBone Cape EEPROM: no EEPROM at address: 0x56
BeagleBone Cape EEPROM: no EEPROM at address: 0x57
Net: eth2: ethernet@48484000
Press SPACE to abort autoboot in 1 seconds
switch to partitions #0, OK
mmc0 is current device
Partition Map for MMC device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 8192 3678208 5f08c263-01 83 Boot
Scanning mmc device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
1368 bytes read in 3 ms (445.3 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt ...
debug: [uname_r=5.10.168-ti-r61] ...
loading /boot/vmlinuz-5.10.168-ti-r61 ...
10539520 bytes read in 456 ms (22 MiB/s)
loading /boot/dtbs/5.10.168-ti-r61/am5729-beagleboneai.dtb ...
344176 bytes read in 19 ms (17.3 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
loading /boot/initrd.img-5.10.168-ti-r61 ...
6509902 bytes read in 283 ms (21.9 MiB/s)
debug: [console=ttyS0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet] ...
debug: [bootz 0x82000000 0x88080000:63554e 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0xa0d200 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f9ca000, end 8ffff54e ... OK
Loading Device Tree to 8f972000, end 8f9c906f ... OK
Starting kernel ...
[ 7.032684] reg-fixed-voltage fixedregulator-vtt: Failed to register regulator: -517
[ 11.103729] sdhci-omap 4809c000.mmc: failed to set system capabilities
[ 11.116119] sdhci-omap 480b4000.mmc: failed to set system capabilities
[ 11.167663] omap_voltage_late_init: Voltage driver support not added
[ 11.226074] reg-fixed-voltage fixedregulator-vtt: Failed to register regulator: -517
[ 11.361206] omapdss error: HDMI I2C Master Error
[ 11.425598] OF: graph: no port node found in /ocp/interconnect@4a000000/segment@0/target-module@80000/ocp2scp@0/phy@4000
[ 11.453063] sdhci-omap 4809c000.mmc: no pinctrl state for sdr104 mode
[ 11.459991] sdhci-omap 4809c000.mmc: no pinctrl state for ddr50 mode
[ 11.466461] sdhci-omap 4809c000.mmc: no pinctrl state for sdr50 mode
[ 11.473083] sdhci-omap 4809c000.mmc: no pinctrl state for sdr25 mode
[ 11.479492] sdhci-omap 4809c000.mmc: no pinctrl state for sdr12 mode
[ 11.485900] sdhci-omap 4809c000.mmc: no pinctrl state for ddr_1_8v mode
[ 11.485900] sdhci-omap 4809c000.mmc: no pinctrl state for ddr_3_3v mode
[ 11.485931] sdhci-omap 4809c000.mmc: no pinctrl state for hs mode
[ 11.485931] sdhci-omap 4809c000.mmc: no pinctrl state for hs mode
[ 11.485931] sdhci-omap 4809c000.mmc: no pinctrl state for hs200_1_8v mode
[ 12.440917] omapdss error: HDMI I2C Master Error
[ 19.253356] remoteproc remoteproc2: request_firmware failed: -2
[ 19.260406] remoteproc remoteproc3: request_firmware failed: -2
[ 19.272949] remoteproc remoteproc0: request_firmware failed: -2
[ 19.279205] remoteproc remoteproc1: request_firmware failed: -2
[ 25.311920] vpe 489d0000.vpe: couldn't get firmware
Debian GNU/Linux 11 BeagleBone ttyS0
BeagleBoard.org Debian
So let’s install 4.19.94-ti-r73 into bullseye to see if it’s kernel or u-boot build…
debian@BeagleBone:~$ sudo apt install linux-image-4.19.94-ti-r73
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
linux-image-4.19.94-ti-r73
0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded.
Need to get 28.6 MB of archives.
After this operation, 49.0 MB of additional disk space will be used.
Get:1 http://repos.rcn-ee.com/debian bullseye/main armhf linux-image-4.19.94-ti-r73 armhf 1bullseye [28.6 MB]
Fetched 28.6 MB in 10s (2758 kB/s)
Selecting previously unselected package linux-image-4.19.94-ti-r73.
(Reading database ... 24490 files and directories currently installed.)
Preparing to unpack .../linux-image-4.19.94-ti-r73_1bullseye_armhf.deb ...
Unpacking linux-image-4.19.94-ti-r73 (1bullseye) ...
Setting up linux-image-4.19.94-ti-r73 (1bullseye) ...
update-initramfs: Generating /boot/initrd.img-4.19.94-ti-r73
zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.19.94-ti-r73]
debian@BeagleBone:~$
There we go:
U-Boot 2022.04-ge0d31da5 (Aug 23 2022 - 19:11:21 +0000)
CPU : DRA752-GP ES2.0
Model: BeagleBoard.org BeagleBone AI
Board: BeagleBone AI REV A
DRAM: 1 GiB
Core: 60 devices, 16 uclasses, devicetree: separate
MMC: no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
mmc@480d1000 - probe failed: -110
OMAP SD/MMC: 0, OMAP SD/MMC: 1no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
Loading Environment from nowhere... OK
BeagleBone Cape EEPROM: no EEPROM at address: 0x54
BeagleBone Cape EEPROM: no EEPROM at address: 0x55
BeagleBone Cape EEPROM: no EEPROM at address: 0x56
BeagleBone Cape EEPROM: no EEPROM at address: 0x57
Net: eth2: ethernet@48484000
Press SPACE to abort autoboot in 1 seconds
switch to partitions #0, OK
mmc0 is current device
Partition Map for MMC device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 8192 31108063 5f08c263-01 83 Boot
Scanning mmc device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
1367 bytes read in 3 ms (444.3 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt ...
debug: [uname_r=4.19.94-ti-r73] ...
loading /boot/vmlinuz-4.19.94-ti-r73 ...
10142208 bytes read in 440 ms (22 MiB/s)
loading /boot/dtbs/4.19.94-ti-r73/am5729-beagleboneai.dtb ...
253052 bytes read in 17 ms (14.2 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
loading /boot/initrd.img-4.19.94-ti-r73 ...
6904302 bytes read in 300 ms (21.9 MiB/s)
debug: [console=ttyS0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet] ..
.
debug: [bootz 0x82000000 0x88080000:6959ee 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x9ac200 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f96a000, end 8ffff9ee ... OK
ERROR: reserving fdt memory region failed (addr=95700000 size=100000 flags=4)
ERROR: Failed to allocate 0x40c7c bytes below 0x90000000.
device tree - allocation error
FDT creation failed!
resetting ...
U-Boot 2022.04-ge0d31da5 (Aug 23 2022 - 19:11:21 +0000)
CPU : DRA752-GP ES2.0
Model: BeagleBoard.org BeagleBone AI
Board: BeagleBone AI REV A
DRAM: 1 GiB
Core: 60 devices, 16 uclasses, devicetree: separate
MMC: no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
mmc@480d1000 - probe failed: -110
OMAP SD/MMC: 0, OMAP SD/MMC: 1no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
Loading Environment from nowhere... OK
BeagleBone Cape EEPROM: no EEPROM at address: 0x54
BeagleBone Cape EEPROM: no EEPROM at address: 0x55
BeagleBone Cape EEPROM: no EEPROM at address: 0x56
BeagleBone Cape EEPROM: no EEPROM at address: 0x57
Net: eth2: ethernet@48484000
Press SPACE to abort autoboot in 1 seconds
=>
Regards,
v4.19.x includes cmem: #include "am57xx-cmem.dtsi"
voodoo@hestia:/opt/github/buildscripts/bb.org/4.19.x/BeagleBoard-DeviceTrees/src/arm$ cat ./am57xx-cmem.dtsi
/* https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/plain/recipes-kernel/linux/files/dra7xx/cmem-am5729-beagleboneai.dtsi?h=dunfell */
/* 0x0c000000 -> 0x18000000 for tild */
/ {
reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
cmem_block_mem_0: cmem_block_mem@a0000000 {
reg = <0x0 0xa0000000 0x0 0x18000000>;
no-map;
status = "okay";
};
cmem_block_mem_1_ocmc3: cmem_block_mem@40500000 {
reg = <0x0 0x40500000 0x0 0x100000>;
no-map;
status = "okay";
};
};
cmem {
compatible = "ti,cmem";
#address-cells = <1>;
#size-cells = <0>;
#pool-size-cells = <2>;
status = "okay";
cmem_block_0: cmem_block@0 {
reg = <0>;
memory-region = <&cmem_block_mem_0>;
cmem-buf-pools = <1 0x0 0x18000000>;
};
cmem_block_1: cmem_block@1 {
reg = <1>;
memory-region = <&cmem_block_mem_1_ocmc3>;
};
};
};
This is needed for TI TIDL… which we never got working on v4.19.x… (only v4.14.x)… do we trash cmem, and get the memory back??
root@BeagleBone:~# uname -r ; free -h
4.19.94-ti-r73
total used free shared buff/cache available
Mem: 577Mi 51Mi 451Mi 4.0Mi 74Mi 509Mi
Swap: 0B 0B 0B
root@BeagleBone:~# uname -r ; free -h
5.10.168-ti-r61
total used free shared buff/cache available
Mem: 989Mi 51Mi 867Mi 4.0Mi 70Mi 909Mi
Swap: 0B 0B 0B
Regards,
Hi @pocketnc_john so the big question… this has been broken for over a year an no one noticed! (or reported)…
Do we drop cmem, and grab the memory back for something we can’t even use on v4.19.x?
Regards,
I vote for that! I certainly don’t use TIDL. We don’t update our build scripts often, but it certainly seems like a good idea to get to the latest snapshot before looking into updating to Debian 11 or 12.
Okay, this looks better:
U-Boot 2022.04-ge0d31da5 (Aug 23 2022 - 19:11:21 +0000)
CPU : DRA752-GP ES2.0
Model: BeagleBoard.org BeagleBone AI
Board: BeagleBone AI REV A
DRAM: 1 GiB
Core: 60 devices, 16 uclasses, devicetree: separate
MMC: no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
mmc@480d1000 - probe failed: -110
OMAP SD/MMC: 0, OMAP SD/MMC: 1no pinctrl state for default mode
omap_hsmmc_init_setup: timedout waiting for cc2!
Loading Environment from nowhere... OK
BeagleBone Cape EEPROM: no EEPROM at address: 0x54
BeagleBone Cape EEPROM: no EEPROM at address: 0x55
BeagleBone Cape EEPROM: no EEPROM at address: 0x56
BeagleBone Cape EEPROM: no EEPROM at address: 0x57
Net: eth2: ethernet@48484000
Press SPACE to abort autoboot in 1 seconds
switch to partitions #0, OK
mmc0 is current device
Partition Map for MMC device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 8192 31108063 5f08c263-01 83 Boot
Scanning mmc device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
1369 bytes read in 3 ms (445.3 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt ...
debug: [uname_r=4.19.94-ti-r73.3] ...
loading /boot/vmlinuz-4.19.94-ti-r73.3 ...
10179072 bytes read in 441 ms (22 MiB/s)
loading /boot/dtbs/4.19.94-ti-r73.3/am5729-beagleboneai.dtb ...
252439 bytes read in 17 ms (14.2 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
loading /boot/initrd.img-4.19.94-ti-r73.3 ...
6907694 bytes read in 301 ms (21.9 MiB/s)
debug: [console=ttyS0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet] ...
debug: [bootz 0x82000000 0x88080000:69672e 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x9b5200 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f969000, end 8ffff72e ... OK
Loading Device Tree to 8f928000, end 8f968a16 ... OK
Starting kernel ...
test with:
wget -cO - https://git.beagleboard.org/RobertCNelson/ti-linux-kernel-dev/-/jobs/11796/artifacts/download > deploy.zip
unzip deploy.zip
sudo dpkg -i deploy/linux-image-4.19.94-ti-r73.3_1xross_armhf.deb
I’ll start a full build and have new images for July 1st…
Regards,
Thanks Robert! I’ll probably wait and test the July 1st image. I appreciate you looking into this.
Hi @pocketnc_john please test: Index of /rootfs/snapshot/2023-06-27/buster-console-armhf these will be staged for July 1st, if they are good…
Regards,
That one booted for me no problem. Thanks Robert!
One of the reasons I started looking into the latest BBAI image was because of another issue I was having with our older image and wanted to see if something may have gotten fixed in the latest console image. It seems to exhibit the same behavior, though. I started another thread for that issue here: Some microSD cards aren't readable on BBAI: mmc0: error -110 whilst initialising SD card