Other Parts Discussed in Thread: HALCOGEN
Project is based on HalCoGen 04.06.01. Startup sequence is :
_coreInitRegisters_()->_coreInitStackPointer_()->_memoryInit_()->_coreEnableEventBusExport_()->VIMInit()->__TI_auto_init()
The project once worked pretty well, after adding some application layer codes, it cracked. While in __TI_auto_init, imprecise abort will occur and once clear CPSR.A, dataentry will entered. If CPSR.A clear before __TI_auto_init executes, dataentry will enter immediately inside __TI_auto_init function call.
I'v read through other questions posted on forum about __TI_auto_init abort issue, and mainly there are two possible root cause.
1). ECC auto generate in CCS not selected. (https://e2e.ti.com/support/microcontrollers/hercules/f/312/p/602078/2287967) I assume its not my case as the project worked before and indeed, the option in CCS is selected.
2). map file error. (https://e2e.ti.com/support/microcontrollers/hercules/f/312/t/554272 ) Possible but not sure how should I test it.
Another thing worth mention is I'm currenlly using Thumb mode for compiling and RTS involved is rtsv7R4_T_be_v3D16_eabi.lib. Should I use ARM mode instead?
