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] ... debug: [bootz 0x82000000 0x88080000:585ab0 88000000] ... ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Ramdisk to 8fa7a000, end 8ffffab0 ... OK reserving fdt memory region: addr=88000000 size=71000 Loading Device Tree to 8fa06000, end 8fa79fff ... OK Starting kernel ... [ 0.001030] clocksource_probe: no matching clocksources found [ 1.313075] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle [ 1.487481] omap_hsmmc 481d8000.mmc: prop pinctrl-0 index 0 invalid phandle [ 1.522508] omap_voltage_late_init: Voltage driver support not added [ 1.529663] PM: Cannot get wkup_m3_ipc handle [ 1.807970] bone_capemgr bone_capemgr: slot #0: No cape found [ 1.839041] bone_capemgr bone_capemgr: slot #1: No cape found [ 1.871724] bone_capemgr bone_capemgr: slot #2: No cape found [ 1.904358] bone_capemgr bone_capemgr: slot #3: No cape found 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/mmcblk1p1 does not exist. Dropping to a shell! (initramfs) --- The first BeagleBone Black I tried this on failed the exact same way but I had a power bump so thought maybe the rootfs just got corrupted somehow. I installed my "standard" image to a new BeagleBone Black and tried the apt update/upgrade again. Now this one is doing the same thing. I also tried reflashing the first one but that failed during the uBoot stage with some error about the SD-Card not resetting. That BeagleBone Black is at work (along with my "standard" image SD-Card). On Monday I will get both the original BeagleBone Black (as long as it didn't get tossed) and the SD-Card and try reflashing them again. In the meantime I'm hoping to find a solution to get this board to boot. Thanks for any help, Hartley On Saturday, August 22, 2020 at 1:57:51 PM UTC-7 RobertCNelson wrote: > Let's see your serial boot log from j1 header to see where it's getting > stick.. > > On Sat, Aug 22, 2020, 3:35 PM jonnymo <[email protected]> wrote: > >> Could you post the strange message you are seeing regarding the uSD card? >> >> For me, going from 9.9 to 9.13 and beyond, I would just do a reflash of >> the image. >> >> Which rev of BBB do you have? Rev B or Rev C? >> >> Robert is the master of this so I would think his suggestions would clear >> the issue. >> >> Cheers, >> >> Jon >> >> On Sat, Aug 22, 2020 at 1:04 PM Hartley Sweeten <[email protected]> >> wrote: >> >>> >>> Hi Jon, >>> >>> I have already seen that post. It doesn't help since it requires >>> reflashing the board. >>> >>> I had another board that I did the same 'apt update/upgrade' on and had >>> the same problem. >>> >>> BTW, If have not been able to get that board to reflash, it keeps giving >>> me some strange error message about the SD-Card, still have not figured >>> that out. The SD-Card worked fine on a different BBB. >>> >>> I would like to know if there is a way to fix this without reflashing >>> the board. >>> >>> I guess a bigger question is - Does upgrading the console image from >>> Debian 9.9 to 9.13 actually work? >>> >>> Hartley >>> >>> On Saturday, August 22, 2020 at 11:28:22 AM UTC-7 [email protected] >>> wrote: >>> >>>> This may help: >>>> >>>> >>>> https://forum.digikey.com/t/beablebone-black-boot-issue-dev-mmcblk1p1-does-not-exist/7717 >>>> >>>> >>>> Cheers, >>>> >>>> Jon >>>> >>>> On Sat, Aug 22, 2020 at 10:47 AM Hartley Sweeten <[email protected]> >>>> wrote: >>>> >>>>> Hello all, >>>>> >>>>> I had an old Debian 9.9 console image on my BBB and did an apt upgrade >>>>> that bumped it to Debian 9.13. Now the board does not boot. >>>>> >>>>> If I hook up a serial console I see it keeps stopping at: >>>>> >>>>> Starting kernel ... >>>>> >>>>> [ 0.001033] clocksource_probe: no matching clocksources found >>>>> [ 1.312908] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc >>>>> handle >>>>> [ 1.487471] omap_hsmmc 481d8000.mmc: prop pinctrl-0 index 0 invalid >>>>> phandle >>>>> [ 1.522392] omap_voltage_late_init: Voltage driver support not added >>>>> [ 1.529573] PM: Cannot get wkup_m3_ipc handle >>>>> [ 1.807980] bone_capemgr bone_capemgr: slot #0: No cape found >>>>> [ 1.839062] bone_capemgr bone_capemgr: slot #1: No cape found >>>>> [ 1.871759] bone_capemgr bone_capemgr: slot #2: No cape found >>>>> [ 1.904436] bone_capemgr bone_capemgr: slot #3: No cape found >>>>> 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/mmcblk1p1 does not exist. Dropping to a shell! >>>>> (initramfs) >>>>> >>>>> Is there any way to fix this other than reflashing? >>>>> >>>>> Thanks >>>>> >>>>> -- >>>>> 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/960431ee-a19f-4425-b2c5-b06f4ec63229o%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/beagleboard/960431ee-a19f-4425-b2c5-b06f4ec63229o%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>> 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/a55e5f2b-e111-4624-ae1c-41419050a951n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/beagleboard/a55e5f2b-e111-4624-ae1c-41419050a951n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> 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/CAG99bkqAMNPGsruTihkOjT9cykvcUycrgc8%3DXj7zGV5yoH%2BwUA%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/beagleboard/CAG99bkqAMNPGsruTihkOjT9cykvcUycrgc8%3DXj7zGV5yoH%2BwUA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/33577d09-061d-48c8-a4f9-a7f427378d45n%40googlegroups.com.
