Quote:
Originally Posted by Lmiller1708
Well... I'm beginning to think that placing the tinboot at a early address does not work for all devices. I'm thinking that this will be a problem for Cotulla also.
I will try inserting it at a later location to see if that will help. Just not sure where yet?
|
Take a look at your resulting NBH files in a hex editor. You will be able to see where the tinboot code is all at (just remember it is now offset by the NBH header). I'm still thinking there is some sort of validation going on because if I take a working NBH, then edit the fatfs size to be 0 or something really small like 128 KB, it refused to boot up. All of the tinboot code was in the right place, and nothing overlapped by me just removing some of the space allocated to the fatfs partition (that I know of).
Really, it isn't that big of a deal. If you look through the resulting NBH, even if we were to perfect this thing to maximize on our space allocation, we would only be gaining back like 5-8 MB of wasted space. I think it is a good idea to have those buffers there just in case we need the extra space for initrd or the kernel.