Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does hex6x (Hex utility) give the warning message,”WARNING: Can convert RAM-model .cinit with -image”?

0
Posted

Why does hex6x (Hex utility) give the warning message,”WARNING: Can convert RAM-model .cinit with -image”?

0

ISA: C6000, All CCS versions: When linked with the -cr option, the loader uses the data in the .cinit section to auto initialize all the global variables. The .cinit section is marked with the COPY flag, which means that the auto-initialization data exists in the .out file, but does not take up any space in the memory defined with the MEMORY linker directive. In the memory map, the user will find that the .cinit section has been overlapped with ome other section that actually takes up space in the memory. Since the .cinit section is marked with the COPY attributes, and it is technically overlapping other sections, the hex utility does not include it when run with the -image option. The user probably should link their code with the -c option in this case.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.