Generating Nk.nb0

hi to all,

I know that to generate a NK.nb0 file at the end of build process we have to
specify the ROMSTART, ROMWIDTH, ROMSIZE in config.bib file.

When ROMSIZE is less than to be than NK.nb1 is generated. If ROMSIZE is
bigger than the ROM size then padded with zeros.

I want to generate Nk.nb0 file not constant size ROMSIZE instead autosize
like NK.bin.

Can anybody know how to generate autosized Nk.nb0 files by configuring
config.bib?

Best regards...

Valter
Mon Feb 05 12:18:02 CST 2007

=?Utf-8?B?U2Vya2Fu?= <Serkan@discussions.microsoft.com> wrote in
news:B86008FB-3C49-4D30-A677-5E4B7A23E453@microsoft.com:

> hi to all,
>
> I know that to generate a NK.nb0 file at the end of build process
> we have to specify the ROMSTART, ROMWIDTH, ROMSIZE in config.bib
> file.
>
> When ROMSIZE is less than to be than NK.nb1 is generated. If
> ROMSIZE is bigger than the ROM size then padded with zeros.
>
> I want to generate Nk.nb0 file not constant size ROMSIZE instead
> autosize like NK.bin.
>
> Can anybody know how to generate autosized Nk.nb0 files by
> configuring config.bib?

nb0 are supposed to be a "flat" image of your memory that could be
written straight to the flash of your device and so you should know in
advance that size.
If you need to reduce the amount of data written you can set the size
to the maximum available flash amount and write a simple app that will
be executed in the post-build .bat script that will open the file, scan
it backwards until it find a word (32 bit) that is not 0. Then you can
truncate your file considering that all the exceeding flash should be
set to 0.
The intel utility used to write flash does that and ask something like:
the last 13% of your file is made by zeros, do you want to truncate it?

--
Valter Minute
(the reply address of this message is invalid)
(l'indirizzo di reply di questo messaggio non è valido)