Re: memory allocation for nk.bin

From: Jack <unseen_coder@xxxxxxxxxxx>
Date: Fri, 24 Oct 2008 01:58:54 -0700 (PDT)

what you physically consume depends if you are using pageing or not
(check the ROMFLAGS for this).

the nb0 file size is exactly what you define with the ROMSIZE (in your
config.bib file), which reflects the total size of your OS image. the
more modules and files you add to your os design, the closer the sizes
of your bin and nb0 files get (the *.bin file size increases the more
modules you add).

when the bootloader loads the bin file it actually creates the nb0
file while "uncompressing" the bin file.
.

References:
- memory allocation for nk.bin
  - From: daniel
- Re: memory allocation for nk.bin
  - From: Chris Tacke, eMVP
- Re: memory allocation for nk.bin
  - From: daniel

Prev by Date: Re: display problem
Next by Date: Re: GPS Control panel Application
Previous by thread: Re: memory allocation for nk.bin
Next by thread: Sharing data between driver and application
Index(es):
- Date
- Thread

Relevant Pages

Re: Programming an Image into flash
... Location information is not contained in the nb0 file, ... Your thought of programming the .bin file directly is probably ... There are a few boot methods in the various BSPs, ...
(microsoft.public.windowsce.platbuilder)
Re: About the NK.bin and the NK.nb0
... The .bin file has a structured format - table of contents, and a collection of data records. ... The .nb0 does include pTOC and ROMPTR, but they are now "just" raw data bytes in the .nb0 file. ... (Head and record information) ...
(microsoft.public.windowsce.platbuilder)
Re: About XIP.NB0
... NB0 file is a flat image that has no record/address information. ... be space gaps between the records in the bin file, ... > I built XIP OS image successfully. ...
(microsoft.public.windowsce.platbuilder)