Tool/software:
I integrated the HSM encryption function under the SBL_QSPI project, and the signature generated file failed, showing that the file was too large, as shown below:
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
I integrated the HSM encryption function under the SBL_QSPI project, and the signature generated file failed, showing that the file was too large, as shown below:
hi,、
The first picture is the generated file without adding HSM function, and the second picture is the generated file after adding HSM function, which is far less than 960K from the.timage file type. What is the reason for the error?
Hi,
The script runs on the .bin file.
I see that sbl_can_uds_am263x.bin on the left is 104KB, whereas it is a very huge file on the right side. Please check why this is happening at your end.
Regards,
Nikhil Dasan
Hi,
Please compare the generated .map file for both the binaries and check which region or variable is taking up more space.
Regards,
Nikhil Dasan
hi,
On the left, the.map file is normally compiled to generate an executable file, and on the right, the abnormal comparison found no problems.
Can you share both the map files and the linker files?
Wanted to check if you have missed any "(NOLOAD)" in bss section which could possibly increase the binary size
Regards,
Nikhil
I tried this linker file at my end, but didn't see an issue in the generated .bin file size.
Also, I see that the .out file from which your .bin file is created is also of valid size.
Can you share me this project here?
Regards,
Nikhil Dasan