Well, I tried again with the latest image (bbx15-debian-9.3-console-armhf-2018-02-11-1gb.img) and a different SD card, and it was able to boot and is now flashing.
> On Feb 16, 2018, at 17:32 , Rick Mann <rm...@latencyzero.com> wrote: > > Thanks, Joerg. I tried to flash it, too, but ran into the same error (after a > long string of lines about flashing). I'll try it again in a few hours and > post the actual output. > > >> On Feb 16, 2018, at 07:50 , j...@ib-weinhardt.de wrote: >> >> Hi, >> I had the same problem with a current >> bbx15-debian-9.3-iot-armhf-2018-02-11-4gb.img.xz Image. >> Flashing the SD Card to the onboard eMMC works for me (uncomment the last >> line at /boot/uEnv.txt on the SD Card file system + boot again with SD Card >> inserted). >> >> Joerg >> >> On Saturday, February 10, 2018 at 1:31:27 AM UTC+1, Rick M wrote: >> I downloaded the stretch-console for x15 and imaged an 8GB SD Card on macOS >> using Etcher. I put this in the x15 and powered it on. It gets partway >> through the boot process, and appears to be booting from the SD card (the >> installed kernel on the MMC is -r44, and the log shows -r96), but then it >> gets stuck. There's a fairly long delay after "mmc0: error -110 whilst >> initialising SD card." Console log below: >> >> https://pastebin.com/Y5pX3uBW >> >> >> � >> 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_Bootloader-Builder-592 >> >> CPU : DRA752-GP ES2.0 >> Model: TI AM5728 BeagleBoard-X15 >> Board: BeagleBoard X15 REV C.00 >> 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: beagle_x15_revc >> 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 29 ms (14.6 KiB/s) >> Loaded environment from /boot/uEnv.txt >> Checking if uname_r is set in /boot/uEnv.txt ... >> debug: [uname_r=4.9.79-ti-r96] ... >> loading /boot/vmlinuz-4.9.79-ti-r96 ... >> 9961120 bytes read in 461 ms (20.6 MiB/s) >> loading /boot/dtbs/4.9.79-ti-r96/am57xx-beagle-x15-revc.dtb ... >> 153258 bytes read in 84 ms (1.7 MiB/s) >> loading /boot/initrd.img-4.9.79-ti-r96 ... >> 5756938 bytes read in 281 ms (19.5 MiB/s) >> debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 >> rootwait coherent_pool=1M net.ifnames=0 quiet] ... >> debug: [bootz 0x82000000 0x88080000:57d80a 0x88000000] ... >> ## Flattened Device Tree blob at 88000000 >> Booting using the fdt blob at 0x88000000 >> Loading Ramdisk to 8fa82000, end 8ffff80a ... OK >> Loading Device Tree to 8fa59000, end 8fa816a9 ... OK >> >> Starting kernel ... >> >> [ 0.074308] /cpus/cpu@0 missing clock-frequency property >> [ 0.074332] /cpus/cpu@1 missing clock-frequency property >> [ 2.410682] dra7-pcie 51000000.pcie: phy link never came up >> [ 2.671093] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode >> [ 2.686786] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode >> [ 2.759464] omap_voltage_late_init: Voltage driver support not added >> [ 3.760897] omap_hsmmc 4809c000.mmc: card busy >> [ 3.810275] 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! >> (initramfs) >> >> >> -- >> Rick Mann >> rm...@latencyzero.com >> >> >> >> -- >> 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/e3dfb1a8-5bf4-4362-ba73-53fa3363b2ef%40googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > Rick Mann > rm...@latencyzero.com > > > -- > 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/02D50C5E-E084-4D69-B08F-2A7D10F4CD66%40latencyzero.com. > For more options, visit https://groups.google.com/d/optout. -- Rick Mann rm...@latencyzero.com -- 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/22A42700-A490-48D0-9EE4-1A5E8D9BBE45%40latencyzero.com. For more options, visit https://groups.google.com/d/optout.