Hi team,
Here's an issue from the customer may need your help:
Regarding SPI boot, the entire boot process has been done.
However, when generating a multicore burned image file, the multicore uses the same project and requires a different cmd file as well. To resolve this issue, the customer wrote a program that found the address of each section to the btbl file generated by Hex6x and then regenerated the new btbl file by modifying it to the global address according to the nuclear number. Because the format of program storage in the btbl file is fixed, it should be byte-length, destination-address, and byte-length data. The addresses of each program section can be found by traversing the entire file in this fixed format.
While it found that only some of the files could generate the correct burn files. Troubleshooting the cause of the error found that the length of the btbl file section generated using the Hex6x tool does not match the length of the section shown in the map file.
The .const section in the .out file of the project is 0x1326 long in the map file, but the actual text in the generated btbl file is 0x1328 long, with two more bytes, resulting in a new btbl file error generated.
The RMD text used to call hex6x is as follows:
core0.out
-a
-boot
-e _c_int00
-map core0.map
ROMS
{
FLASH: org = 0x0C000000, length = 0x100000, memwidth = 32, romwidth = 32
files = {core0.btbl}
}
Could you help check this case? Thanks.
Best Regards,
Cherry
