Beaglebone AI booting from SD card issue.

RE: Beaglebone AI booting from SD card issue.

xiachao — Thu, 17 Sep 2020 03:42:35 GMT

I was trapped in the exactly same problem for one week.

Finally, I found out that the key of the problem is the device tree(.dtb). I didn't study very deep into the .dts files provided by official website, because there is too many files.

So, I converted the am5729-beagleboneai.dtb to xx.dts using "dtc". Then, I found out mmc1 node (mmc@4809c000), and modify some places as follows:

1. compatible = "ti,dra7-sdhci"; >>>>> compatible = "ti,dra7-sdhci", "ti,omap4-hsmmc";

2. add: vmmc_aux-supply = <0xd0>; (same node with vqmmc-supply)

3. max-frequency = <0xb71b000>; >>>>> max-frequency = <0x16e3600>; (to lower the frequency of mmc)

Save and exit, then convert the .dts file to am5729-beagleboneai.dtb, replace the old one.

Then, I booted debian from my SD card successfully! And, when I booted debian form emmc(modify the .dts inside as listed above), there was no error log "mmc0: error -110 whilst initialising SD card" when plug in sd card, and I can see my sd card using "lsblk", and also can mount it successfully.

However, some error log still there as follows when poweron.

U-Boot 2019.07-rc4-00001-g607b5b738b (Jul 06 2019 - 21:01:15 -0500), Build: jenkins-github_Bootloader-Builder-127

CPU : DRA752-GP ES2.0

Model: BeagleBoard.org BeagleBone AI

Board: BeagleBone AI REV A

DRAM: 1 GiB

MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1

CTRL_CORE_PAD_I2C1_SDA: 0x00060000

CTRL_CORE_PAD_I2C1_SCL: 0x00060000

CTRL_CORE_PAD_GPMC_A0: 0x00060007

CTRL_CORE_PAD_GPMC_A1: 0x00060007

CTRL_CORE_PAD_VIN2A_D4: 0x0005000f

CTRL_CORE_PAD_VIN2A_D5: 0x0005000f

CM_L4PER_GPIO7_CLKCTRL: 0x00000001

CM_L4PER_I2C1_CLKCTRL: 0x00000002

CM_L4PER_I2C4_CLKCTRL: 0x00000002

CM_L4PER_L4_PER1_CLKCTRL 0x00000001

PM_L4PER_I2C1_WKDEP 0x0000b000

RM_L4PER_I2C1_CONTEXT 0x00000002

PM_L4PER_I2C4_WKDEP 0x0000b000

RM_L4PER_I2C4_CONTEXT 0x00000001

BeagleBone: cape eeprom: i2c_probe: 0x54

Checking (ret 1 bus works) I2C1 bus. ret 1

Checking (ret 1 bus works) I2C4 bus. ret 1

BeagleBone: cape eeprom: i2c_probe: 0x55

Checking (ret 1 bus works) I2C1 bus. ret 1

Checking (ret 1 bus works) I2C4 bus. ret 1

BeagleBone: cape eeprom: i2c_probe: 0x56

Checking (ret 1 bus works) I2C1 bus. ret 1

Checking (ret 1 bus works) I2C4 bus. ret 1

BeagleBone: cape eeprom: i2c_probe: 0x57

Checking (ret 1 bus works) I2C1 bus. ret 1

Checking (ret 1 bus works) I2C4 bus. ret 1

Net:

Warning: ethernet@48484000 using MAC address from ROM

eth0: ethernet@48484000

Press SPACE to abort autoboot in 1 seconds

usb_boot is currently disabled

scsi_boot is currently disabled

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 7364608 f7146e7c-01 83 Boot

Scanning mmc device 0

Checking for: /uEnv.txt ...

Checking for: /boot/uEnv.txt ...

657 bytes read in 2 ms (320.3 KiB/s)

Loaded environment from /boot/uEnv.txt

Checking if uname_r is set in /boot/uEnv.txt ...

debug: [uname_r=4.14.108-ti-r113] ...

loading /boot/vmlinuz-4.14.108-ti-r113 ...

9929216 bytes read in 864 ms (11 MiB/s)

loading /boot/dtbs/4.14.108-ti-r113/am5729-beagleboneai.dtb ...

103182 bytes read in 11 ms (8.9 MiB/s)

uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to enable...

loading /boot/initrd.img-4.14.108-ti-r113 ...

4642997 bytes read in 406 ms (10.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:46d8b5 0x88000000] ...

## Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000

Loading Ramdisk to 8fb92000, end 8ffff8b5 ... OK

Loading Device Tree to 8fb75000, end 8fb9130d ... OK

Starting kernel ...

[ 0.002420] /cpus/cpu@0 missing clock-frequency property

[ 0.002444] /cpus/cpu@1 missing clock-frequency property

[ 0.560313] omap-mailbox 4a0f4000.mailbox: no available mbox devices found

[ 0.560383] omap-mailbox 4883a000.mailbox: no available mbox devices found

[ 0.560448] omap-mailbox 4883c000.mailbox: no available mbox devices found

[ 0.560511] omap-mailbox 4883e000.mailbox: no available mbox devices found

[ 0.561155] omap-mailbox 48844000.mailbox: no available mbox devices found

[ 0.561224] omap-mailbox 48846000.mailbox: no available mbox devices found

[ 0.561288] omap-mailbox 4885e000.mailbox: no available mbox devices found

[ 0.561353] omap-mailbox 48860000.mailbox: no available mbox devices found

[ 0.561416] omap-mailbox 48862000.mailbox: no available mbox devices found

[ 0.561478] omap-mailbox 48864000.mailbox: no available mbox devices found

[ 0.561540] omap-mailbox 48802000.mailbox: no available mbox devices found

[ 1.008948] tpd12s015 encoder@0: failed to find video source

[ 1.014950] connector-hdmi connector@0: failed to find video source

[ 1.137172] dwc3 488d0000.usb: failed to initialize core

[ 1.158946] sdhci-omap 4809c000.mmc: failed to set system capabilities

[ 1.166177] sdhci-omap 480b4000.mmc: failed to set system capabilities

[ 1.189399] omap_voltage_late_init: Voltage driver support not added

[ 25.420732] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

Debian GNU/Linux 9 beaglebone ttyS0

BeagleBoard.org Debian Image 2019-08-03

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

beaglebone login:

RE: Beaglebone AI booting from SD card issue.

gdstew — Thu, 14 Nov 2019 16:33:50 GMT

My experience has been that dd will report an error if it runs out of space when writing to "of" if it is a block device.

RE: Beaglebone AI booting from SD card issue.

cstanton — Thu, 14 Nov 2019 14:06:12 GMT

I discovered with other single board computers that not all microSD cards are created equal, there's variable sizes even among the 4gB and 8gB, and even 16gB ranges, sometimes by only a few bytes, sometimes by more.

'dd', the linux command, will just dump data at the destination until it can't write to it anymore (I think) and ends up in situations like this.

'dd' can be useful in that way, and sometimes not useful,

RE: Beaglebone AI booting from SD card issue.

clem57 — Thu, 14 Nov 2019 13:36:55 GMT

It verified all it could. and No More!!!

RE: Beaglebone AI booting from SD card issue.

Sean_Miller — Thu, 14 Nov 2019 03:27:00 GMT

My bad...didn't know the 4 gig image would have burned without a verification error. Live and learn. I'll add that into my "Survival guide".

RE: Beaglebone AI booting from SD card issue.

chkvsk — Thu, 14 Nov 2019 03:12:10 GMT

Good news. Everything is working no. I used 8GB SD card instead of 4GB. Solution was simple, but not obvious. (Or I just missed something...)
Thank you for your help.

RE: Beaglebone AI booting from SD card issue.

cstanton — Mon, 11 Nov 2019 10:28:29 GMT

Have you tried using an SDCard larger than 4gB?

RE: Beaglebone AI booting from SD card issue.

Sean_Miller — Sun, 10 Nov 2019 14:45:55 GMT

Did you ever boot and use it from the flash storage without the card installed?

Here's a post that describes /dev/mmcblk…:

https://devtalk.nvidia.com/default/topic/1022062/jetson-tx1/is-there-any-information-about-dev-mmcblk1p1-and-mmcblk0p1-/

If you didn't boot into flash and make any tweaks, my only thought left would be to be absolutely sure the card is seated. After try that, I'd have to assume there's a pin broken in the SD slot.

See ya',

Sean

RE: Beaglebone AI booting from SD card issue.

chkvsk — Sun, 10 Nov 2019 01:58:34 GMT

I've tried maybe 5 different (iot and lxqt) Images with no success. As I mentioned above, had no issues with flashing BBBs and BBGs before and now.

RE: Beaglebone AI booting from SD card issue.

chkvsk — Sat, 09 Nov 2019 21:45:48 GMT

Ok, tried am57xx-debian-9.11-iot-armhf-2019-11-02-4gb.img.xz.
No luck so far...

Starting kernel ...

[ 0.002525] /cpus/cpu@0 missing clock-frequency property

[ 0.002549] /cpus/cpu@1 missing clock-frequency property

[ 0.565444] omap-mailbox 4a0f4000.mailbox: no available mbox devices found

[ 0.565516] omap-mailbox 4883a000.mailbox: no available mbox devices found

[ 0.565582] omap-mailbox 4883c000.mailbox: no available mbox devices found

[ 0.565647] omap-mailbox 4883e000.mailbox: no available mbox devices found

[ 0.566341] omap-mailbox 48844000.mailbox: no available mbox devices found

[ 0.566408] omap-mailbox 48846000.mailbox: no available mbox devices found

[ 0.566473] omap-mailbox 4885e000.mailbox: no available mbox devices found

[ 0.566537] omap-mailbox 48860000.mailbox: no available mbox devices found

[ 0.566600] omap-mailbox 48862000.mailbox: no available mbox devices found

[ 0.566663] omap-mailbox 48864000.mailbox: no available mbox devices found

[ 0.566727] omap-mailbox 48802000.mailbox: no available mbox devices found

[ 0.996874] tpd12s015 encoder@0: failed to find video source

[ 1.002876] connector-hdmi connector@0: failed to find video source

[ 1.122231] dwc3 488d0000.usb: failed to initialize core

[ 1.142741] sdhci-omap 4809c000.mmc: failed to set system capabilities

[ 1.149990] sdhci-omap 480b4000.mmc: failed to set system capabilities

[ 1.173101] omap_voltage_late_init: Voltage driver support not added

[ 1.320221] sdhci-omap 4809c000.mmc: no pinctrl state for ddr_1_8v mode

[ 1.326891] sdhci-omap 4809c000.mmc: no pinctrl state for hs200_1_8v mode

[ 1.468036] mmc0: error -110 whilst initialising SD card

Gave up waiting for root file system device. Common problems:

- Boot args (cat /proc/cmdline)

- Check rootdelay= (did the system wait long enough?)

- Missing modules (cat /proc/modules; ls /dev)

ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell!

BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)

Enter 'help' for a list of built-in commands.

RE: Beaglebone AI booting from SD card issue.

chkvsk — Sat, 09 Nov 2019 20:54:36 GMT

I've tried this:

On Beaglebone Black and Green I have no issues with firmware updates.

RE: Beaglebone AI booting from SD card issue.

chkvsk — Sat, 09 Nov 2019 20:52:45 GMT

I have about a dozen Beaglebone Black and Green. Had no issues updating firmware on BB and BBG. Every time using same brand 4GB SD cards something like this: microSDmicroSD

First time I had this issue when I was trying to update firmware on X15. Debian 8 updating was working fine, but Debian 9 updates - no success.

Same issue I have with AI.

RE: Beaglebone AI booting from SD card issue.

crisdeodates — Sat, 09 Nov 2019 20:38:12 GMT

Your snapshot says 'missing modules'. It might be a bad image. Try flashing the latest image again.

PS: In case your image that is pre-flashed iìon the eMMC is one of recent, you might only have to update it manually without going through the hurdle of flashing again.

RE: Beaglebone AI booting from SD card issue.

jissdeodates — Sat, 09 Nov 2019 20:32:27 GMT

chkvsk, I would suggest you use this image (https://debian.beagleboard.org/images/am57xx-debian-9.9-lxqt-armhf-2019-08-03-4gb.img.xz ) for the BB-AI as Sean_Miller suggested. This is available here (https://beagleboard.org/latest-images ) the official webpage of Beaglebone.

RE: Beaglebone AI booting from SD card issue.

mp2100 — Sat, 09 Nov 2019 19:54:30 GMT

Make sure you are using the BB AI image (not the BB Black image). The BB AI image file name starts with am57xx

(use the link that Sean gave)

RE: Beaglebone AI booting from SD card issue.

Sean_Miller — Sat, 09 Nov 2019 14:51:30 GMT

I successfully used this image a couple of times now: https://www.element14.com/community/external-link.jspa?url=https%3A%2F%2Fdebian.beagleboard.org%2Fimages%2Fam57xx-debian…

It's from here: https://beagleboard.org/latest-images

I found a lot more is needed to get it rolling as a fully functioning microcontroller with GPIO - for instance, your filesystem may need to grow to meet your SD card capacity. So, I wrote it all down here:

BeagleBone AI Survival Guide V3.18: PWM, I2C, Analog/Digital Read/Write, Vision AI, Video Text Overlays, Audio, & Hardware

See ya',

Sean

RE: Beaglebone AI booting from SD card issue.

clem57 — Sat, 09 Nov 2019 09:33:01 GMT

Either a bad SD card or a bad image. chkvsk What software did you use to build the image with?