Tried it with a different SD card, and this time Etcher successfully verified the image. However, same result as before when booting off that SD card...
On Tuesday, April 17, 2018 at 2:26:55 PM UTC-5, Jeff Andich wrote: > > After downloading the latest image ( > bbx15-debian-9.3-lxqt-armhf-2018-01-28-4gb.img.xz) for the BB-X15 from > http://beagleboard.org/latest-images, verifying the sha256, and ripping > an SD card via Win32DiskImager (Etcher hangs on the verify step for some > reason): > > > My console on my 572xEVM Rev A3 shows the following: > > U-Boot SPL 2017.01-00360-gc604741cb3 (Aug 11 2017 - 15:47:09) > DRA752-GP ES2.0 > Trying to boot from MMC1 > > ** Unable to use mmc 0:1 for loading the env ** > Using default environment > > > > U-Boot 2017.01-00360-gc604741cb3 (Aug 11 2017 - 15:47:09 -0500), Build: > jenkins-github_Bootl2 > > CPU : DRA752-GP ES2.0 > Model: TI AM5728 BeagleBoard-X15 > Board: AM572x EVM REV A.3A > DRAM: 2 GiB > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > > ** Unable to use mmc 0:1 for loading the env ** > Using default environment > > setup_board_eeprom_env: am57xx_evm_reva3 > SCSI: SATA link 0 timeout. > AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode > flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst > scanning bus for devices... > Found 0 device(s). > Net: <ethaddr> not set. Validating first E-fuse MAC > cpsw > Press SPACE to abort autoboot in 2 seconds > usb_boot is currently disabled > scsi_boot is currently disabled > switch to partitions #0, OK > mmc0 is current device > Scanning mmc device 0 > Checking for: /uEnv.txt ... > Checking for: /boot/uEnv.txt ... > 445 bytes read in 24 ms (17.6 KiB/s) > Loaded environment from /boot/uEnv.txt > Checking if uname_r is set in /boot/uEnv.txt ... > debug: [uname_r=4.9.78-ti-r94] ... > loading /boot/vmlinuz-4.9.78-ti-r94 ... > 9960536 bytes read in 456 ms (20.8 MiB/s) > loading /boot/dtbs/4.9.78-ti-r94/am57xx-evm-reva3.dtb ... > 155403 bytes read in 127 ms (1.2 MiB/s) > loading /boot/initrd.img-4.9.78-ti-r94 ... > 6300596 bytes read in 292 ms (20.6 MiB/s) > debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 > rootwait coherent_pool. > debug: [bootz 0x82000000 0x88080000:6023b4 0x88000000] ... > ## Flattened Device Tree blob at 88000000 > Booting using the fdt blob at 0x88000000 > Loading Ramdisk to 8f9fd000, end 8ffff3b4 ... OK > Loading Device Tree to 8f9d4000, end 8f9fcf0a ... OK > > Starting kernel ... > > [ 0.073146] /cpus/cpu@0 missing clock-frequency property > [ 0.073171] /cpus/cpu@1 missing clock-frequency property > [ 2.448629] dra7-pcie 51000000.pcie: phy link never came up > [ 2.710443] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode > [ 2.726129] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode > [ 2.838825] omap_voltage_late_init: Voltage driver support not added > [ 3.512258] omap_hsmmc 4809c000.mmc: card busy > [ 3.561793] 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. > > (initramfs) > > > ?? Is this maybe a pinmux issue with MMC0 in the dev. tree ?? > > > Is anyone else having the same issue? > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f148632e-2d3a-4c66-9e99-ef645782a69b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
