Re: nk.bin and nk.nb0

The thread should be "findable" in the Platform Builder newsgroup. It got
quite a number of responses from Barry Bond, me, and Steve Maillet.

Paul T.

"Greg Prier (Microsoft Corp.)" <gprier@xxxxxxxxxxxxx> wrote in message
news:uwcTtbbNHHA.5012@xxxxxxxxxxxxxxxxxxxxxxx
Trying to reply to the post below, but it appears to be deleted. Creating
a new post with the answers.
1. NB0 size is controlled by the ROMSIZE variable in config.bib. It should
almost always be larger than BIN size because it's a bit-for-bit
representation of flash, whereas the BIN file is a series of records
wrapping actual data. NB0s fill in the zero-padding around the actual
data.


2. It was likely inserted by ROMImage.exe - it contains some
initialization code (which, at least on ARM, is just a jump instruction to
the nk.exe entry point) and some pointers to the TOC (both a virtual
address and a physical offset)


3. Yes. The NB0 is the complete representation of the image as it is laid
out on flash, so it contains everything in the BIN file, but in a flat
file instead of a record-based file.


Greg Prier [ms]

"starry night" <timetohug@xxxxxxxxxxx> wrote in message
news:<1165470505.617369.107150@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>...
Hello, everyone.
There are some questions about NK.bin and NK.nb0.

(1) As far as I see, nk.nb0 is a plain binary.
So the nk.nb0 doesn't contain the information that nk.bin does.
(Head and record information)
Anyway, I translated nk.bin to nk.nb0.
I expected that the size of nk.nb0 would be smaller than the
nk.bin.
Actually but nk.nb0 was bigger than nk.bin.
Why?

(2) I set the address of NK as 0x802F 0000 in the config.bib.
But I found that the start address of nk.bin was 0x802F 1000 by
using "viewbin" command.
Was this 4KB region inserted by the linker?
If so, is this region the jump page related to the vector table?

(3) nk.bin contains the ROMHDR and pTOC.
Does nk.nb0 not have those?


Thanks in advance.

Jang.






.