From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Babic Date: Fri, 30 Jul 2010 09:44:15 +0200 Subject: [U-Boot] How to handle binary data file in u-boot In-Reply-To: <1AE74F652ECB1440B73DD7C2C20842D1BA42DB@zch01exm27.fsl.freescale.net> References: <1AE74F652ECB1440B73DD7C2C20842D1BA42DB@zch01exm27.fsl.freescale.net> Message-ID: <4C5282CF.1090207@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Lv Terry-R65388 wrote: > Hi Experts, > > We have implemented an display utilty in u-boot and this utlity > needs a waveform file. > > We are planning to release this display utility, but we don't know > how to do with the waveform file. The file is as large as 800KB. > > Now we just put the waveform file on mmc and read it out in boot. > > Is there any better way to deliver this binary waveform file as part > of the bootloader? > How is this case typically handled? Because the file is raw data, it is normally not linked to u-boot code. I mean, you can convert the data in a C-array and link it to the bootloader, but is it worth ? The same issue is for images used as splashscreen in u-boot, in some case quite huge (but not so big as yours). They are often saved in different areas (or after the bootloader), but not linked together. You could easier concatenate u-boot and your waveform data in a single file using "cat", padding bytes if you need to reserve some areas, and probably you reach easier the same goal, if you want only to deliver a single file containing both bootloader and data. Best regards, Stefano Babic -- ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de =====================================================================