Hi Robert, Thanks for your answer! Here is the output of the console:
U-Boot SPL 2017.07-00002-gd316f5106c (Jul 11 2017 - 10:43:17) Trying to boot from MMC2 U-Boot 2017.07-00002-gd316f5106c (Jul 11 2017 - 10:43:17 -0500), Build: jenkins-github_Bootloader-Builder-585 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 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 13 Card did not respond to voltage select! mmc_init: -95, time 12 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 2171 bytes read in 15 ms (140.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.4.145-bone23 ... 8263240 bytes read in 549 ms (14.4 MiB/s) loading /boot/dtbs/4.4.145-bone23/am335x-boneblack.dtb ... 51343 bytes read in 51 ms (982.4 KiB/s) uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to enable... loading /boot/initrd.img-4.4.145-bone23 ... 5935511 bytes read in 404 ms (14 MiB/s) debug: [console=ttyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet consoleblank=0 fbcon=rotate:1 omap_wdt.nowayout=0 root=/dev/mmcblk0p1 root=/dev/mmcblk0p1] ... debug: [bootz 0x82000000 0x88080000:5a9197 0x88000000] ... ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Ramdisk to 8fa56000, end 8ffff197 ... OK Loading Device Tree to 8fa46000, end 8fa5588e ... OK Starting kernel ... [ 0.000690] clocksource_probe: no matching clocksources found [ 4.085697] omap-sham 53100000.sham: initialization failed. [ 4.104156] omap_voltage_late_init: Voltage driver support not added Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) I see that problems started already here, even before loading the kernel : Card did not respond to voltage select! mmc_init: -95, time 13 If I understand correctly it can't detect eMMC device. Do you have any idea why? Thanks again! Best, Olex пятница, 10 апреля 2020 г., 21:12:38 UTC+2 пользователь RobertCNelson написал: > > On Fri, Apr 10, 2020 at 2:02 PM <[email protected] <javascript:>> wrote: > > > > Hi everyone! > > > > I'm looking for some enlightenment to solve the problem I have with my > BBB. > > It was running fine until I tried to follow this guide for setting up > the WiFi dongle. > > > https://learn.adafruit.com/setting-up-wifi-with-beaglebone-black?view=all > > > > One of the steps suggested to do the following: > > > > cd /opt/scripts/tools/ > > ./update_kernel.sh > > > > I did and it worked (well, it didn't show error messages). But after the > reboot nothing happens :( It starts double-blinking with one of the user > LEDs and that's it, no network, no image on the screen. > > Any idea how to revert that upgrade of repair it? > > I can get to the filesystem by booting with fresh image on uSD card but > I'm sure what to do with it... My experience with Linux doesn't go that far > :( > > Do you have a usb-serial adapter to plug into J1? > > https://elinux.org/Beagleboard:BeagleBone_Black_Serial > > Using that, it would be useful to see what the board is doing on > bootup, to help assist you to fix it. > > 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/35a8e08d-15cd-4c80-bd25-1cf1d9a97d7c%40googlegroups.com.
