Whenever we run the command romimage with one of the bib file like ce.bib then we get two images.
- nk.nb0 ( in case of ce.bib but name can vary like sam.nb0 depending on the target image name you want)
- nk.bin
So what is the difference between these two -
In case of .bin file, the following stuffs getting added one by one -
1. Image hdr "B000FF"
2. Image start address and image size.
3. Now make entry of dll/files under module sections.
4. Make entry for dll/files under FILES section in bib file here( ce.bib) in nk.bin with proper offset and entry point with allignment.
5. Allocate the space for rom header but that will be filled later after toc and other stuff. And as all information related to toc and other stuff will be ready after build process hence we will fill it after build process.
6. Now make entry in TOC about all dll.
7. Now wrtite the toc information into kernel which is available for TOC entry.
8. Write ROM Signature with it's offset.
8. Next all xip or files get entered into files. Hence depending on the need only the size of the file grows. Not like the nknb0 which takes all space allocated to OS.
Now lets give a look at nk.nb0 -
1. There no compression or ToC in nk.nb0. So it does not require support to get executed. The nk.nb0 can execute on self.
2. It's size can be determine from config.bib by getting the size of OS size. If the image is lesser then also it will consume the whole space and filled the rest of the area with zero.
This apply to both nk.nb0 or any type of .nb0.
I am planning to add more stuff here related to differences.
No comments:
Post a Comment
Please add your valuable feedback and suggestion...
Note: Only a member of this blog may post a comment.