On 16 November 2015 at 16:03, Robert Nelson <[email protected]> wrote: > On Mon, Nov 16, 2015 at 9:39 AM, Taceant Omnes <[email protected]> wrote: >> On 16 November 2015 at 15:20, Robert Nelson <[email protected]> wrote: >> >>>> My previous kernel, that worked very well, was 4.1.10-bone16. >>>> >>>> Any ideas? >>> >>> What rootfs and distro? >>> >>> cat /etc/dogtag >> >> This is from a previous email, as now it does not boot: >> >> root@beaglebone:~# cat /etc/dogtag >> BeagleBoard.org Debian Image 2015-09-13 > > I don't have that version local, but i do have the week after: > > debian@beaglebone:~$ cat /etc/dogtag > BeagleBoard.org Debian Image 2015-09-20 > > https://paste.debian.net/333066/ > > That leaves: u-boot? > > yours: > > U-Boot SPL 2014.04-00015-gb4422bd (Apr 22 2014 - 13:24:29) > > What shipped with 2015-09-20: (based on the build date, 2015-09-13 had > the same version) > > U-Boot SPL 2015.10-rc3-00001-gfb375b5 (Sep 10 2015 - 10:07:48) > bad magic > > > U-Boot 2015.10-rc3-00001-gfb375b5 (Sep 10 2015 - 10:07:48 -0500), > Build: jenkins-github_Bootloader-Builder-222 > > Watchdog enabled > I2C: ready > DRAM: 512 MiB > Reset Source: Global warm SW reset has occurred. > Reset Source: Power-on reset has occurred. > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > Using default environment > > Net: <ethaddr> not set. Validating first E-fuse MAC > cpsw > Hit any key to stop autoboot: 0 > gpio: pin 53 (gpio 53) value is 1 > switch to partitions #0, OK > mmc0 is current device > gpio: pin 54 (gpio 54) value is 1 > Checking for: /uEnv.txt ... > reading uEnv.txt > 1179 bytes read in 5 ms (229.5 KiB/s) > gpio: pin 55 (gpio 55) value is 1 > Loaded environment from uEnv.txt > Importing environment from mmc ... > Checking if uenvcmd is set ... > gpio: pin 56 (gpio 56) value is 1 > Running uenvcmd ... > 1661 bytes read in 39 ms (41 KiB/s) > debug: [/boot/vmlinuz-4.1.13-ti-r30] ... > 8260280 bytes read in 497 ms (15.9 MiB/s) > debug: [/boot/initrd.img-4.1.13-ti-r30] ... > 4414791 bytes read in 290 ms (14.5 MiB/s) > debug: [/boot/dtbs/4.1.13-ti-r30/am335x-boneblack.dtb] ... > 59295 bytes read in 72 ms (803.7 KiB/s) > debug: [console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p2 > rootfstype=ext4 rootwait fixrtc coherent_pool=1M quiet] ... > debug: [bootz 0x82000000 0x88080000:435d47 0x88000000] ... > Kernel image @ 0x82000000 [ 0x000000 - 0x7e0ab8 ] > ## Flattened Device Tree blob at 88000000 > Booting using the fdt blob at 0x88000000 > Using Device Tree in place at 88000000, end 8801179e > > So what happens when you force it to boot with the microSD, thus > forcing the 2015.10-rc3 u-boot?
I am using now a newish rev. C BBB that I got a few weeks ago. I did what you suggested and pressed the boot button on the BBB to force the BBB to used the uboot in the MicroSD card instead of the uboot in the eMMC. However I still got the same problem as before, i. e., it hangs at the last line of the log with the asterisks moving and the time being incremented. I am also puzzled why your boot log looks so different from mine. For example I get the message below and you don't, and I don't get any timestamp starting at [ 0.000000]: [FAILED] Failed to start Load Kernel Modules. Boot log: https://paste.debian.net/333095/ Any ideas? Maybe you have something in uEnv.txt that I don't? Mine is unchanged. /rootfs/uEnv.txt https://paste.debian.net/333104/ /rootfs/boot/uEnv.txt https://paste.debian.net/333106/ -- 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]. For more options, visit https://groups.google.com/d/optout.
