Hello,
I’m trying to bootup BBAI-64 board. I have tried everything mentioned in this forum. When I got the package, only the power LED as ON. Tried to update the image via the SD card, ts not helping. Finally with an old image I was getting the following error.
That’s the mcu/wake port, use the other serial port for u-boot messages…
Regards,
Thank you. Now I’m getting the proper serial logs after using the other port.
Bootup_Msg_BBAI64.txt (48.3 KB)
I’ve attached the serial logs. I see couple of errors in this logs but not sure those that might prevent a successful bootup. The attachment contains 1 set of log and this repeats.
Can anyone decode and let me know what could be the failure causing the boot-up to run in loop? (the full log is attached in the above comment). The last few lines were:
[ 13.033647] k3-dsp-rproc 4d81800000.dsp: local reset is deasserted for device
[ 13.041666] remoteproc remoteproc13: 4d81800000.dsp is available
[ 13.059372] pvrsrvkm: loading out-of-tree module taints kernel.
[ 13.069891] k3-dsp-rproc 64800000.dsp: assigned reserved memory node vision-apps-c71-dma-memory@aa000000
[ 13.084556] k3-dsp-rproc 64800000.dsp: configured DSP for remoteproc mode
[ 13.094385] remoteproc remoteproc14: 64800000.dsp is available
[ 13.112941] remoteproc remoteproc12: powering up 4d80800000.dsp
[ 13.118954] remoteproc remoteproc12: Booting fw image vision_apps_eaik/vx_app_rtos_linux_c6x_1.out, size 1461044
.
.
And then it reboots back…
It’s the r5’s we fixed this maybe a year ago… in the ti-vision-apps-eaik-firmware-8.2 there was a race condition where the r5’s could get stuck on bootup (when loading the r5 firmware on kernel bootup)… So we moved loading of the firmware from the kernel to user space… Today this script takes care of loading the firmware…
If you want to restore the “edgeai” demo image, grab the flasher from here, Index of /rootfs/release/2023-10-07/bullseye-xfce-edgeai-arm64 pretty sure that’s still my best one for edgeai…
If you don’t care about edgeai, just grab any: ARM64 - Debian 11.x (Bullseye) - Monthly Snapshots - 2023-10-07
Regards,
Hello @RobertCNelson
Case 1:
Tried all the images you provided above. If I try to boot from SD card or flash via the eMMC flasher (through UART0), I get the following error and it reboots:
[ 1.092822] am65-cpsw-nuss c000000.ethernet: /bus@100000/ethernet@c000000/ethernet-ports/port@1 error retrieving port phy: -19
However, I have not connected any Ethernet cables.
Case 2
If I use the old SD card image from here, I get the following error and it keeps rebooting:
[ 2.268054] davinci_mdio 46000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
[ 2.280576] davinci_mdio 46000f00.mdio: phy[0]: device 46000f00.mdio:00, driver TI DP83867
[ 2.288891] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA00101, cpsw version 0x6BA80100 Ports: 2 quirks:00000000
[ 2.303139] am65-cpts 310d0000.cpts: CPTS ver 0x4e8a010a, freq:200000000, add_val:4 pps:0
[ 2.315456] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
Case 3
If I do not insert any SD card and try to boot from the existing eMMC, it throws a Kernel Panic. Last few lines below:
[ 1.144523] am65-cpsw-nuss c000000.ethernet: /bus@100000/ethernet@c000000/ethernet-ports/port@1 error retrieving port phy: -19
[ 2.293777] spi-nor spi11.0: unrecognized JEDEC id bytes: ff ff ff ff ff ff
[ 3.012719] debugfs: Directory ‘pd:27’ with parent ‘pm_genpd’ already present!
[ 3.019977] debugfs: Directory ‘pd:26’ with parent ‘pm_genpd’ already present!
[ 3.028556] debugfs: Directory ‘pd:242’ with parent ‘pm_genpd’ already present!
[ 3.035875] debugfs: Directory ‘pd:241’ with parent ‘pm_genpd’ already present!
[ 3.043197] debugfs: Directory ‘pd:240’ with parent ‘pm_genpd’ already present!
[ 3.050512] debugfs: Directory ‘pd:239’ with parent ‘pm_genpd’ already present!
run-init: can’t execute ‘/sbin/init’: No such file or directory
Target filesystem doesn’t have requested /sbin/init.
run-init: can’t execute ‘/sbin/init’: No such file or directory
run-init: can’t execute ‘/etc/init’: No such file or directory
run-init: can’t execute ‘/bin/init’: No such file or directory
run-init: can’t execute ‘/bin/sh’: Exec format error
[ 5.665483] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 5.677780] SMP: stopping secondary CPUs
[ 5.681697] Kernel Offset: disabled
[ 5.685173] CPU features: 0x08240022,20006008
[ 5.689516] Memory Limit: none
[ 5.692564] —[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]—
Excuse my ignorance, how do I copy the magic script? Should I be creating a *.sh file and placing it on the SD card root folder?
Regards,
That’s fine, it’s just the 2nd port…
voodoo@bbai64-02:~$ dmesg | grep cpsw
[ 1.046078] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA00101, cpsw version 0x6BA80100 Ports: 2 quirks:00000000
[ 1.046130] am65-cpsw-nuss 46000000.ethernet: initialized cpsw ale version 1.4
[ 1.046133] am65-cpsw-nuss 46000000.ethernet: ALE Table size 64
[ 1.046633] am65-cpsw-nuss 46000000.ethernet: CPTS ver 0x4e8a010a, freq:500000000, add_val:1 pps:0
[ 1.226327] am65-cpsw-nuss c000000.ethernet: initializing am65 cpsw nuss version 0x6BA01901, cpsw version 0x6BA80101 Ports: 9 quirks:00000000
[ 1.226342] am65-cpsw-nuss c000000.ethernet: /bus@100000/ethernet@c000000/ethernet-ports/port@1 error retrieving port phy: -19
[ 1.534119] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA00101, cpsw version 0x6BA80100 Ports: 2 quirks:00000000
[ 1.534174] am65-cpsw-nuss 46000000.ethernet: initialized cpsw ale version 1.4
[ 1.534177] am65-cpsw-nuss 46000000.ethernet: ALE Table size 64
[ 1.534646] am65-cpsw-nuss 46000000.ethernet: CPTS ver 0x4e8a010a, freq:500000000, add_val:1 pps:0
[ 1.536074] am65-cpsw-nuss 46000000.ethernet: set new flow-id-base 48
[ 6.270816] am65-cpsw-nuss 46000000.ethernet eth0: PHY [46000f00.mdio:00] driver [TI DP83867] (irq=POLL)
[ 6.270830] am65-cpsw-nuss 46000000.ethernet eth0: configuring for phy/rgmii-rxid link mode
[ 10.374070] am65-cpsw-nuss 46000000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
voodoo@bbai64-02:~$ uname -r
5.10.168-ti-arm64-r113
voodoo@bbai64-02:~$ sudo beagle-version
eeprom:[BBONEAI-64-B0-B0007801B00001643422BBBBBB2230]
model:[BeagleBoard.org_BeagleBone_AI-64]
dogtag:[BeagleBoard.org Debian Bullseye Minimal Image 2022-11-01]
bootloader:[/dev/mmcblk0boot0]:[tiboot3.bin]:[U-Boot SPL 2021.01-gea96725b (Aug 19 2023 - 01:11:20 +0000)]
bootloader:[/dev/mmcblk0]:[/boot/firmware/tiboot3.bin]:[U-Boot SPL 2021.01-gea96725b (Aug 19 2023 - 01:11:20 +0000)]
bootloader:[/dev/mmcblk0]:[/boot/firmware/tispl.bin]:[U-Boot SPL 2021.01-gea96725b (Aug 19 2023 - 01:11:20 +0000)]
bootloader:[/dev/mmcblk0]:[/boot/firmware/u-boot.img]:[U-Boot 2021.01-gea96725b (Aug 19 2023 - 01:11:20 +0000)]
UBOOT: Booted Device-Tree:[k3-j721e-beagleboneai64-no-shared-mem.dts]
kernel:[5.10.168-ti-arm64-r113]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-u-boot-beagleboneai64]:[2021.10.20230216.14-0~bookworm+20231201]
pkg:[bb-customizations]:[1.20231201.0-0~bookworm+20231201]
pkg:[bb-usb-gadgets]:[1.20230922.1-0~bookworm+20230925]
WARNING:pkg:[bb-wl18xx-firmware]:[NOT_INSTALLED]
cmdline:[console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 root=/dev/nvme0n1p1 ro rootfstype=ext4 rootwait net.ifnames=0 quiet]
ti-sci:
Nov 09 18:25:41 bbai64-02 kernel: ti-sci 44083000.dmsc: ABI: 3.1 (firmware rev 0x0008 '8.6.3--v08.06.03 (Chill Capybar')
optee:
Nov 09 18:25:41 bbai64-02 kernel: optee: revision 3.22 (001ace66)
dmesg | grep remote
[ 4.750668] remoteproc remoteproc0: b034000.pru is available
[ 4.750861] remoteproc remoteproc1: b004000.rtu is available
[ 4.751043] remoteproc remoteproc2: b00a000.txpru is available
[ 4.751446] remoteproc remoteproc3: b038000.pru is available
[ 4.751623] remoteproc remoteproc4: b006000.rtu is available
[ 4.753146] remoteproc remoteproc5: b00c000.txpru is available
[ 4.753336] remoteproc remoteproc6: b134000.pru is available
[ 4.753503] remoteproc remoteproc7: b104000.rtu is available
[ 4.753650] remoteproc remoteproc8: b10a000.txpru is available
[ 4.753783] remoteproc remoteproc9: b138000.pru is available
[ 4.753938] remoteproc remoteproc10: b106000.rtu is available
[ 4.754080] remoteproc remoteproc11: b10c000.txpru is available
[ 7.317554] k3-dsp-rproc 4d80800000.dsp: configured DSP for remoteproc mode
[ 7.387009] remoteproc remoteproc12: 4d80800000.dsp is available
[ 7.388471] remoteproc remoteproc12: Direct firmware load for j7-c66_0-fw failed with error -2
[ 7.388481] remoteproc remoteproc12: powering up 4d80800000.dsp
[ 7.388505] remoteproc remoteproc12: Direct firmware load for j7-c66_0-fw failed with error -2
[ 7.388510] remoteproc remoteproc12: request_firmware failed: -2
[ 7.404444] k3-dsp-rproc 4d81800000.dsp: configured DSP for remoteproc mode
[ 7.467559] remoteproc remoteproc13: 4d81800000.dsp is available
[ 7.467872] remoteproc remoteproc13: Direct firmware load for j7-c66_1-fw failed with error -2
[ 7.467879] remoteproc remoteproc13: powering up 4d81800000.dsp
[ 7.467897] remoteproc remoteproc13: Direct firmware load for j7-c66_1-fw failed with error -2
[ 7.467901] remoteproc remoteproc13: request_firmware failed: -2
[ 7.481693] k3-dsp-rproc 64800000.dsp: configured DSP for remoteproc mode
[ 7.488608] remoteproc remoteproc14: 64800000.dsp is available
[ 7.488965] remoteproc remoteproc14: Direct firmware load for j7-c71_0-fw failed with error -2
[ 7.488973] remoteproc remoteproc14: powering up 64800000.dsp
[ 7.488988] remoteproc remoteproc14: Direct firmware load for j7-c71_0-fw failed with error -2
[ 7.488992] remoteproc remoteproc14: request_firmware failed: -2
[ 8.091679] remoteproc remoteproc15: 41000000.r5f is available
[ 8.091733] remoteproc remoteproc15: attaching to 41000000.r5f
[ 8.098595] remoteproc15#vdev0buffer: assigned reserved memory node r5f-dma-memory@a0000000
[ 8.098682] remoteproc15#vdev0buffer: registered virtio0 (type 7)
[ 8.098686] remoteproc remoteproc15: remote processor 41000000.r5f is now attached
[ 8.970480] platform 5c00000.r5f: configured R5F for remoteproc mode
[ 9.108359] remoteproc remoteproc16: 5c00000.r5f is available
[ 9.108704] remoteproc remoteproc16: Direct firmware load for j7-main-r5f0_0-fw failed with error -2
[ 9.108714] remoteproc remoteproc16: powering up 5c00000.r5f
[ 9.108736] remoteproc remoteproc16: Direct firmware load for j7-main-r5f0_0-fw failed with error -2
[ 9.108741] remoteproc remoteproc16: request_firmware failed: -2
[ 9.129816] platform 5d00000.r5f: configured R5F for remoteproc mode
[ 9.279149] remoteproc remoteproc17: 5d00000.r5f is available
[ 9.279925] remoteproc remoteproc17: Direct firmware load for j7-main-r5f0_1-fw failed with error -2
[ 9.279937] remoteproc remoteproc17: powering up 5d00000.r5f
[ 9.279971] remoteproc remoteproc17: Direct firmware load for j7-main-r5f0_1-fw failed with error -2
[ 9.279975] remoteproc remoteproc17: request_firmware failed: -2
[ 9.377407] platform 5e00000.r5f: configured R5F for remoteproc mode
[ 9.517694] remoteproc remoteproc18: 5e00000.r5f is available
[ 9.517882] remoteproc remoteproc18: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
[ 9.517890] remoteproc remoteproc18: powering up 5e00000.r5f
[ 9.517908] remoteproc remoteproc18: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
[ 9.517913] remoteproc remoteproc18: request_firmware failed: -2
[ 9.558236] platform 5f00000.r5f: configured R5F for remoteproc mode
[ 9.710325] remoteproc remoteproc19: 5f00000.r5f is available
[ 9.710838] remoteproc remoteproc19: Direct firmware load for j7-main-r5f1_1-fw failed with error -2
[ 9.710849] remoteproc remoteproc19: powering up 5f00000.r5f
[ 9.710867] remoteproc remoteproc19: Direct firmware load for j7-main-r5f1_1-fw failed with error -2
[ 9.710872] remoteproc remoteproc19: request_firmware failed: -2
dmesg | grep pru
[ 4.750668] remoteproc remoteproc0: b034000.pru is available
[ 4.751043] remoteproc remoteproc2: b00a000.txpru is available
[ 4.751446] remoteproc remoteproc3: b038000.pru is available
[ 4.753146] remoteproc remoteproc5: b00c000.txpru is available
[ 4.753336] remoteproc remoteproc6: b134000.pru is available
[ 4.753650] remoteproc remoteproc8: b10a000.txpru is available
[ 4.753783] remoteproc remoteproc9: b138000.pru is available
[ 4.754080] remoteproc remoteproc11: b10c000.txpru is available
dmesg | grep pinctrl-single
[ 0.674346] pinctrl-single 4301c000.pinctrl: 94 pins, size 376
[ 0.674605] pinctrl-single 11c000.pinctrl: 173 pins, size 692
dmesg | grep gpio-of-helper
lsusb
Bus 002 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lspci
00:00.0 PCI bridge: Texas Instruments Device b00d
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
END
As far as Case 2 and Case 3, those usually are caused by a mismatched version of u-boot. Early on with the BBAI64 we made some mistakes in u-boot on bringup, as things we tested we got better…
Regards,
I’m finally able to get my board to boot up. The issue was with the 5V barrel-type power socket. Maybe it’s damaged? (not sure). Instead, I used the USB type C port. I was able to boot from SD Card with the below image:
https://rcn-ee.net/rootfs/debian-arm64-12-bookworm-minimal-v6.1-ti/2023-12-24/
Also able to reflash the eMMC now with the latest build.