Sorry i don’t understand what do you mean with “Visual Studio sepatar leave”.
You should sign nk.bin and then regenerate the nb0 file.
As far as I know, the license code is added to the bin file header and this is then placed in memory.
Can you try to create the nb0 with romimage without signing it first? Does it boot and matches the original one? (I am trying to figure out if there is an issue with romimage).
sorry, my fault, I mixed up the two tools. ROMIMAGE.EXE builds the .bin file, CVRTBIN is the one you have to use.
But if you use CVRTBIN with the same addresses you have in ce.bib:
Dear @Saphymo
Valter is out of the office for some time. I try to take over the ticket, even though I don’t know the platform as well as Valter.
Did I get you right: You were able to license the nk.bin successfully?
Do you want to download your licensed image through platform builder?
If I am right, downloading through platform builder only supports the nk.bin (not the nk.nb0).
The message “No valid kernel signature!” refers to a corrupted OS image file, not to a missing license.
For using the UpdateTool you might need the nk.nb0 file.
Hi @Saphymo
I talked to the T30 BSP developer: As long as you are using our BSP and workspace, the whole build process is set up to stamp (license) the NK.bin and NK.nb0 - by default with the Toradex WinCE license. To use your own license code, all you need to do is enter your license code into the file lic.txt.
For details, of the process, refer to the batch file PostMakeImg.bat.
The NK.nb0 does not need to be stamped again. When you convert a stamped nk.bin, the license is automatically forwarded into the generated NK.nb0 file.
Hi @Saphymo
The license we include is the C13Entry which we negotiated to be also valid for C7NR (plus 2 features). Please refer to the licensing article on our developer website for details about the included components.
Regards, Andy