On Wed, Apr 8, 2015 at 4:36 AM, Steve Osselton <steve.ossel...@prismtech.com> wrote: > Hi, > > I have two pretty much identical blacks that I regularly update using the > update_kernel.sh script. > Have just updated from v3.14.35-ti-r56 to v3.14.37-ti-r57. The first bone > rebooted as normal, whereas the > second now hangs (output from serial console), anyone any ideas what might > have gone wrong? > > SD/MMC found on device 0 > reading uEnv.txt > 681 bytes read in 3 ms (221.7 KiB/s) > Loaded environment from uEnv.txt > Importing environment from mmc ... > Running uenvcmd ... > 349 bytes read in 23 ms (14.6 KiB/s) > 7065064 bytes read in 1182 ms (5.7 MiB/s) > 3878256 bytes read in 662 ms (5.6 MiB/s) > 87125 bytes read in 105 ms (809.6 KiB/s) > ## Flattened Device Tree blob at 80f80000 > Booting using the fdt blob at 0x80f80000 > Loading Ramdisk to 9ee84000, end 9f236d70 ... OK > Using Device Tree in place at 80f80000, end 80f98454
Looks like things went off the edge ^^, lets first look at uEnv.txt and double check: loadaddr=0x82000000 fdtaddr=0x88000000 rdaddr=0x88080000 debug: [bootz 0x82000000 0x88080000:38a2f4 0x88000000] ... Kernel image @ 0x82000000 [ 0x000000 - 0x6c49f8 ] ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Ramdisk to 8fc75000, end 8ffff2f4 ... OK Loading Device Tree to 8fc5c000, end 8fc74454 ... OK 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
