Tool/software:
Ran into the same issue as this poster:
A close look at the build output shows that the linker couldn't find a location for the .init_array section. This is the array of constructor function calls for c++ objects that need to be created at launch time. By default, the linker.cmd file doesn't include that section in any of the lists, so it gets placed in RAM by the linker as a fall back. Unfortunately, since it was just defaulted to RAM and not loaded into a flash area that's copied to RAM, it never gets initialized. Thus, the caller of the constructors ends up calling a random address from RAM.
The fix is to add an entry for .init_array to one of the flash sections. It's constant anyway, pointing to functions in flash, so flash is a fine spot for it.
Example:
GROUP {
.reserved: { . += 0x101C; } (NOLOAD)
.padding : fill = 0xFFFFFFFF { . += 0x00E4; }
.resetVecs: {} palign(4) /* This is where code resides */
.cram: {} palign(4)
.text: {} palign(4) /* This is where code resides */
.rodata: {} palign(4) /* This is where const's go */
.cinit: {} palign(4)
.init_array {} palign(4)
} > FLASH_NON_SECURE
This will fix the crash and allow use of C++ objects that are created at system startup.
