From: Reinhard Meyer <reinhard.meyer@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] How to handle binary data file in u-boot
Date: Thu, 29 Jul 2010 09:45:23 +0200 [thread overview]
Message-ID: <4C513193.3040408@emk-elektronik.de> (raw)
In-Reply-To: <1AE74F652ECB1440B73DD7C2C20842D1BA42DB@zch01exm27.fsl.freescale.net>
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.
>
Files that large are usually not embedded within the u-boot image.
>
> Now we just put the waveform file on mmc and read it out in boot.
>
It depends where your u-boot image is. If its in NOR flash, for example,
one would add a partition of suitable size to put the data in.
If the external location can be flexibly defined (filename for SD/MMC or
location for others) it is great.
>
> Is there any better way to deliver this binary waveform file as part
> of the bootloader?
>
As part of the bootloader (image) you'd need to convert the bytestream
into a lengthy initialized array and link it into the image. I'm not
sure the toolchain can handle that and I am sure that method is not
welcome in the repository (800kb binary --> several MB c-source)...
> How is this case typically handled?
>
Have a look at the code to handle FPGA images, you can probably even
reuse or share code with there.
Reinhard
next prev parent reply other threads:[~2010-07-29 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 3:38 [U-Boot] How to handle binary data file in u-boot Lv Terry-R65388
2010-07-29 7:45 ` Reinhard Meyer [this message]
2010-07-30 4:11 ` Lv Terry-R65388
2010-07-30 7:44 ` Stefano Babic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C513193.3040408@emk-elektronik.de \
--to=reinhard.meyer@emk-elektronik.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox