From: Simon Kagstrom Date: Fri, 4 Sep 2009 08:30:03 +0200 Subject: [U-Boot] [PATCH v3 4/4] tools: mkimage: Add: Kirkwood Boot Image support (kwbimage) In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202E5D0E9F2@SC-VEXCH1.marvell.com> References: <20090903140002.3d2cbfce@marrow.netinsight.se> <73173D32E9439E4ABB5151606C3E19E202E5D0E9F2@SC-VEXCH1.marvell.com> Message-ID: <20090904083003.3f7f0d1f@marrow.netinsight.se> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Prafulla! I see the complications and understand that it might be difficult to get it running. On Thu, 3 Sep 2009 07:15:48 -0700 Prafulla Wadaskar wrote: > > I think it could also be useful to be able to produce just the boot > > header without the U-boot image. For example if you want to place > > U-boot at some other location on the flash or (as a developer) > > frequently re-flash U-boot, but don't want to write to the first block > > all the time (you only need to rewrite it when moving U-boot). > > This is not possible. > Boot Header is a part of Kirkwood boot image, > Header contains u-boot imagesize so for this, first block need to be written each time. Understandable. On the other hand, it should be possible to pad the U-boot image to some specific size to keep the size constant. Typically to the erase size. > Secondly u-boot header is of 512bytes only whereas minimum sector size could be 4kbytes (typical), > so rest part of first sector will be a waste. I'd be prepared to waste a couple of bytes :-) > Also at the end of boot image checksum need to be calculated on entire image including header. This is not how I read the documentation. I thought the 32-bit checksum is for the image only, not the headers? Anyway, if it does include the headers, then I see why this would be impossible. Thanks for the explanation! // Simon