Re: What to do with nb0 and nb1 files?

From: Sujith (sujithss_at_hotmail.com)
Date: 07/30/04 

Date: Fri, 30 Jul 2004 17:41:20 +0530

hi,
check out with your ROMSTART, ROMSIZE and ROMWIDTH, with your actual memory
map. it could solve the problem
Regards
Sujith
"Ten" <anonymous@tentechnologies.com> wrote in message
news:u6Nt4tidEHA.216@TK2MSFTNGP11.phx.gbl...
> ROMWIDTH is already set at 32. Any other suggestions?
>
> Thanks,
> Nick.
>
>
> "Sujith" <sujithss@hotmail.com> wrote in message
> news:OH2qUCidEHA.644@tk2msftngp13.phx.gbl...
> > hi,
> > use your ROMWIDTH = 32, which makes the Rominage.exe to make the
romimage
> > into a single file, nk.nb0, if it is 16 it makes twofiles, also if it is
8
> > it makes 4 files, all are dame in size.
> >
> > Regards
> > Sujith
> > "Ten" <anonymous@tentechnologies.com> wrote in message
> > news:%23WT63zadEHA.712@TK2MSFTNGP09.phx.gbl...
> > > I've researched this and can't find the answer. I have a platform
that
> > > creates nk.bin that is about 16 MB. I also get nk.nb0 and nk.nb1 each
> > > exactly 16 MB (16 * 1024 * 1024). When I burn these to the FLASH, I'm
> > > guessing that I need to burn nb0 starting at offset 0, and nb1
starting
> at
> > > 0x8000. Is this right?
> > >
> > > Thanks,
> > > Nick.
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: boot loader build error
    ... IF IMGFLASH! ... > waht is the beginning adress of your ramimage ?? ... > in most case you only need to set the ROMSTART, ROMSIZE and ROMWIDTH ...
    (microsoft.public.windowsce.platbuilder)
  • Re: nk.nb0 and nk.nb1
    ... well, if the ROMWIDTH is 32, the only reason to get this is your ROMSIZE is ... get a single image ok NK.NB0 but make sure, the ROMSIZE will not cross the ... RAM start+size size RAM ...
    (microsoft.public.windowsce.platbuilder)
  • Re: boot loader build error
    ... IF IMGFLASH! ... > waht is the beginning adress of your ramimage ?? ... > in most case you only need to set the ROMSTART, ROMSIZE and ROMWIDTH ...
    (microsoft.public.windowsce.embedded)