Question for "Card did not respond to voltage select!"


#1

Hello,

I follow the following link to make image for beaglebone black Rev C.

After I copy microSD card to eMMC with script bbb-eMMC-flasher-eewiki-ext4.sh, I met the error of “Card did not respond to voltage select!” during u-boot,but there is no such error if booting from microSD card.

I found the difference between booting from microSD and flash, that the booting device from microSD is mmcblk0 while booting from flash is mmcblk1. I am not sure whether this is root cause and how to fix it. I attach the booting log for your reference.

https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Setuname_rin/boot/uEnv.txt.

Looking forward for your reply and thanks so much for your help!

whole boot log as below

U-Boot SPL 2018.09-dirty (Dec 25 2018 - 09:19:49 +0800)
Trying to boot from MMC2
Loading Environment from EXT4… Card did not respond to voltage select!

U-Boot 2018.09-dirty (Dec 25 2018 - 09:19:49 +0800)

CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
No match for driver ‘omap_hsmmc’
No match for driver ‘omap_hsmmc’
Some drivers were not found
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4… Card did not respond to voltage select!
Board: BeagleBone Black
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
Model: SeeedStudio BeagleBone Green:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x54:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x55:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x56:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net: eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[BBG1] …
Card did not respond to voltage select!
Card did not respond to voltage select!
Card did not respond to voltage select!
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
Card did not respond to voltage select!
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1…
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
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
315 bytes read in 6 ms (50.8 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.9.146-bone-rt-r12 …
8855328 bytes read in 565 ms (14.9 MiB/s)
debug: [enable_uboot_overlays=1] …
debug: [enable_uboot_cape_universal=] …
debug: [uboot_base_dtb_univ=am335x-boneblack-uboot.dtb] …
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] …
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb …
loading /boot/dtbs/4.9.146-bone-rt-r12/am335x-boneblack-uboot.dtb …
54055 bytes read in 20 ms (2.6 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] …
uboot_overlays: loading /lib/firmware/M-BB-BBG-00A0.dtbo …
277 bytes read in 135 ms (2 KiB/s)
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo …
1440 bytes read in 105 ms (12.7 KiB/s)
uboot_overlays: uboot loading of [/lib/firmware/BB-ADC-00A0.dtbo] disabled by /boot/uEnv.txt [disable_uboot_overlay_adc=1]…
uboot_overlays: add [enable_uboot_cape_universal=1] to /boot/uEnv.txt to enable…
loading /boot/initrd.img-4.9.146-bone-rt-r12 …
5964115 bytes read in 382 ms (14.9 MiB/s)
debug: [console=ttyO0,115200n8 quiet lpj=4980736 root=UUID=cf91e354-04fe-4f2d-b13d-2bf5a4c3a6a3 ro rootfstype=ext4 rootwait] …
debug: [bootz 0x82000000 0x88080000:5b0153 88000000] …

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fa4f000, end 8ffff153 … OK
reserving fdt memory region: addr=88000000 size=6e000
Loading Device Tree to 8f9de000, end 8fa4efff … OK

Starting kernel …

[ 0.000523] clocksource_probe: no matching clocksources found
[ 2.401269] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 2.673152] omap_voltage_late_init: Voltage driver support not added
[ 2.796395] bone_capemgr bone_capemgr: slot #0: No cape found
[ 2.825209] bone_capemgr bone_capemgr: slot #1: No cape found
[ 2.855705] bone_capemgr bone_capemgr: slot #2: No cape found
[ 2.886196] bone_capemgr bone_capemgr: slot #3: No cape found
BEAGLEBONE: clean, 40091/233392 files, 315757/932864 blocks
[ TIME ] Timed out waiting for device dev-ttyS0.device.
[DEPEND] Dependency failed for Serial Getty on ttyS0.
Starting Create Volatile Files and Directories…
[ OK ] Started udev Kernel Device Manager.
[ OK ] Started Create Volatile Files and Directories.
Starting Update UTMP about System Boot/Shutdown…
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Started udev Coldplug all Devices.
[ OK ] Reached target System Initialization.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
[ OK ] Started Regular background program processing daemon.
[ OK ] Started D-Bus System Message Bus.
Starting Connection service…
Starting Login Service…
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Timers.
Starting Generic Board Startup…
[ OK ] Started Connection service.
[ OK ] Started Login Service.
[ OK ] Reached target Network.
Starting OpenBSD Secure Shell server…
Starting Permit User Sessions…
[ OK ] Started Permit User Sessions.
[ OK ] Started Getty on tty1.
[ OK ] Reached target Login Prompts.
Starting Hostname Service…
[FAILED] Failed to start OpenBSD Secure Shell server.
See ‘systemctl status ssh.service’ for details.
[FAILED] Failed to start Hostname Service.
See ‘systemctl status systemd-hostnamed.service’ for details.
[ OK ] Stopped OpenBSD Secure Shell server.
Starting OpenBSD Secure Shell server…
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[FAILED] Failed to start OpenBSD Secure Shell server.
See ‘systemctl status ssh.service’ for details.
[ OK ] Stopped OpenBSD Secure Shell server.
Starting OpenBSD Secure Shell server…
[ OK ] Started Generic Board Startup.
[ OK ] Started OpenBSD Secure Shell server.
[ OK ] Reached target Multi-User System.
Starting Update UTMP about System Runlevel Changes…
[ OK ] Started Update UTMP about System Runlevel Changes.


#2

Nah, this is u-boot trying to read from the microSD that “isn’t” in the microSD slot… Standard “informational” message… :wink:

Regards,


#3

Thanks for your quick reply.
But this would cause another problem that when I try to run saven in u-boot shell, it failed either. How to tell the u-boot to init from flash instead of microSD? Or can we change the flash disk name mmcblk1 to mmcblk0?


#4

Well, sadly today u-boot only supports saveenv in one location and one file system type.

If you want to force it for eMMC for your design, you’ll need to patch u-boot, in the file configs/am335x_evm_defconfig

Change:

CONFIG_ENV_EXT4_INTERFACE="mmc"
CONFIG_ENV_EXT4_DEVICE_AND_PART="0:1"
CONFIG_ENV_EXT4_FILE="/boot/uboot.env"

to:

CONFIG_ENV_EXT4_INTERFACE="mmc"
CONFIG_ENV_EXT4_DEVICE_AND_PART="1:1"
CONFIG_ENV_EXT4_FILE="/boot/uboot.env"

0 = microSD
1 = eMMC

(untested, but should work…)

Regards,