Hi,
I am struggling to understand how to create the product header. From what I understood from the document (creation of secondary bootloader, 6.3) you need to create a text file with parameters for the image offsets etc...
Its hard to understand what needs to be in the text file to define the header. It says to enter the following parameters:
Signature: 0x70, 0x52
Version: 1234
Offset1: 00800000 (it corresponds to offset 0x8000)
Offset2: 00300100 (it corresponds to offset 0x13000)
Firstly, I think offset1 and offset2 must have mistakes as they don't correspond to what it says in the brackets. Then it says to refer to the help menu in the smart snippets toolkit for more information on how to create the product header but there is no mention of it anywhere in the user guide. I also checked the forums and there is nothing on it.
It then goes onto say :
2 Signature MagicNumber
2 Version VersionNumber
4 Offset1 Offset_image_1
4 Offset2 Offset_image_2
I have tried a few combinations and it always comes up with a reading error
I am in memory header/nvds programmer in smart snippets.
Can you clarify exactly what needs to be in the txt file? Maybe you can point me towards an example
Thanks
I don't know this issue either, but I know that offset1 and offset2 is totally right according to what is in brackets. For example, 00800000 is in byte reverse order, so the real offset is 00 00 80 00.
I found out that it is a problem with incomplete documentation - its incorrect. What it tells you to put in the secondary bootloader documentation is incorrect - which is why I assume its been taken off the resources section.
Hello gcblair - the secondary bootloader document is on the support site : can you point out the error and I will get that corrected ? BR JE_Dialog
hi, is there anyone who had solved this problem???
I have solved the problem.
2 Signature: 0x70, 0x52 MagicNumber aaa
2 Version: 1234 VersionNumber bbb
4 Offset1: 00800000 Offset_image_1 ccc
4 Offset2: 00300100 Offset_image_2 ddd
thankyou for posting the reply summer. I undersand from the development team that a new update to the document will come in 1-2 weeks.
BR JE_Dialog