On Sat, Aug 22, 2020 at 5:15 PM Hartley Sweeten <[email protected]> wrote:
>
> Hi Robert,
>
> Quick background on this.
>
> I have a "standard" image I use that is based on the Console Debian 9 image. 
> I usually keep it pretty up-to-date but have not updated it since Debian 9.9.
>
> I was trying to update it to the latest Debian 9.13 using apt update/upgrade. 
> This has always worked in the past.
>
> But going from 9.9 to 9.13 I can no longer get the BeagleBone Black to boot. 
> This has happened on 2 different BeagleBone Black's so far.
>
> Here is the serial log:
>
> ---
>
> U-Boot SPL 2018.01-00002-g9aa111a004 (Jan 20 2018 - 12:45:29)
> Trying to boot from MMC2
>
>
> U-Boot 2018.01-00002-g9aa111a004 (Jan 20 2018 - 12:45:29 -0600), Build: 
> jenkins-github_Bootloader-Builder-32
>
> 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.
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Using default environment
>
> Board: BeagleBone Black
> <ethaddr> not set. Validating first E-fuse MAC
> BeagleBone Black:
> BeagleBone: cape eeprom: i2c_probe: 0x54:
> BeagleBone: cape eeprom: i2c_probe: 0x55:
> BeagleBone: cape eeprom: i2c_probe: 0x56:
> BeagleBone: cape eeprom: i2c_probe: 0x57:
> Net:   eth0: MII MODE
> cpsw, usb_ether
> Press SPACE to abort autoboot in 2 seconds
> board_name=[A335BNLT] ...
> board_rev=[00C0] ...
> Card did not respond to voltage select!
> mmc_init: -95, time 12
> Card did not respond to voltage select!
> mmc_init: -95, time 13
> Card did not respond to voltage select!
> mmc_init: -95, time 13
> 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!
> mmc_init: -95, time 13
> Card did not respond to voltage select!
> mmc_init: -95, time 13
> 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
> 2190 bytes read in 15 ms (142.6 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.105-ti-r114 ...
> 9818560 bytes read in 636 ms (14.7 MiB/s)
> uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...
> uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb ...
> loading /boot/dtbs/4.9.105-ti-r114/am335x-boneblack-uboot.dtb ...
> 61638 bytes read in 44 ms (1.3 MiB/s)
> uboot_overlays: [fdt_buffer=0x60000] ...
> uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
> 1584 bytes read in 219 ms (6.8 KiB/s)
> uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
> 4915 bytes read in 64 ms (74.2 KiB/s)
> uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
> 867 bytes read in 204 ms (3.9 KiB/s)
> uboot_overlays: unable to find [mmc 1:1 
> /lib/firmware/univ-bbb-EVA-00A0.dtbo]...
> loading /boot/initrd.img-4.9.105-ti-r114 ...
> 5790384 bytes read in 380 ms (14.5 MiB/s)
> debug: [console=ttyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 
> rootwait coherent_pool=1M net.ifnames=0 quiet] ...

Want to remove "quiet" so we can see what really failed?

Regards,

-- 
Robert Nelson
https://rcn-ee.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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiN0dU2pz14oRgSEdN-UnLVf1UXi4aEYEmJ8ZAdLOiF1A%40mail.gmail.com.

Reply via email to