- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Original question:
MCU-PLUS-SDK-AM243X: LTS1.3.1-linker problems which produce undefined aborts
Hello,
we are loading some sw-parts dynamically via the copy-tables from the linker TABLE-operator. For this we use copy_in. It works nice so far but I noticed that all the .data-section is not initialized at all. it's just all 0xAAAAAAAA. Also I need to mention that the copied-in .data-sections are the .data-sections of a previous created relocatable output module.
The final linking for this uses the ram_model-option and the relocatable output module itself does not use any of the ram/rom_model-options when partial linking, since the manual recommends to not use it.
So I am not sure whether the problem is the initialization after copy_in or the initialization of the .data-section in the relocatable output module beforehand.
I noticed that even in the load-address the data is already 0xAAAAAAAA. so it seems the relocatable module already initialized it with those values? Is there a way to prevent this?
Edit: I may add that most of the symbols in the relocatable output modules are hidden via --make_static. Does this affect the initialization of those variables?
The data must be initialized at least with their default values, else the application crashes.
Compiler is LTS 2.1.2
Best regards
Felix
