mkuboot was recently changed to be able to handle "bsd" files directly. If you're still on an older mkuboot, it's possible that you need to do objcopy before, so you can get it out of it's (iirc) ELF container.
\Patrick Am 25.08.2013 um 13:27 schrieb Stefan Sperling <s...@openbsd.org>: > On Sun, Aug 25, 2013 at 12:01:57PM +0200, Stefan Sperling wrote: >> I've tried updating a beagle bone black using bsd.rd, but couldn't >> get it to boot. Is there a way of doing this? I ended up reinstalling >> from scratch since the system was mostly using a stock config and >> I had to jump over the time_t bump. But in the future I'd like to >> have a mechanism to update to a newer snapshot without reinstalling. >> >> After converting bsd.rd to bsd.umg, using the command >> >> mkuboot -a arm -o linux -e 0x80300000 -l 0x80300000 bsd.rd bsd.umg >> > > Even worse, using the above with a self-compiled /bsd kernel > and trying to boot it from the MSDOS partition results in > an ubootable system that keep resetting itself: > > Importing environment from mmc ... > Running uenvcmd ... > reading bsd.umg > 2831184 bytes read in 327 ms (8.3 MiB/s) > ## Booting kernel from Legacy Image at 82800000 ... > Image Name: boot > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2831120 Bytes = 2.7 MiB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > Loading Kernel Image ... data abort > > MAYBE you should read doc/README.arm-unaligned-accesses > > pc : [<9ff94f78>] lr : [<9ff656d0>] > sp : 9fe42a40 ip : 00000000 fp : 9fe4a020 > r10: 00000000 r9 : 82ab3350 r8 : 9fe42f40 > r7 : 82800000 r6 : 00000000 r5 : 9fe42a84 r4 : 00000000 > r3 : 00000000 r2 : 002b3310 r1 : 82800040 r0 : 00000000 > Flags: Nzcv IRQs off FIQs on Mode SVC_32 > Resetting CPU ... > > resetting ...
