Variable in L2 SRAM will be reseted to zero after calling adi_rcu_ControlSystemReset() even though the variable are allocated in "no_init" L2 region

Question

Hello, 
 I used "#pragma section("seg_l2_noinit_data", NO_INIT)" to allocate variable to "no_init" L2 SRAM, but it has still been reset to zero after calling adi_rcu_ControlSystemReset() API, 
 How do I fix this, since I want to keep the variable value unchanged after the system software reset? 
 Thansk, and looking forward your reply.

Divya.P · Accepted Answer

Hi Jay Lee, 
 Apologies for the delay in response. 
 When linking an executable file that contains large uninitialized variables, use the NO_INIT or ZERO_INIT section qualifier to reduce the file size. The NO_INIT qualifier directs the linker to omit data for that section from the output file. 
 No data initialization is used for NO_INIT memory section. The purpose of NO_INIT and NOMEMINIT are different. 
 The Memory Initialization process is enabled by default and optionally bypassed by setting RCU_BCODE.NOMEMINIT.

Setting RCU_BCODE bit 4 (NOMEMINIT) avoids the writing of the rom space and leaves us with the L2 Memory space not initialized. 
 Set the bit RCU_BCODE.NOMEMINIT in your application before issuing a reset. 
 Note : The variable can be declared as global in the L2 memory section but should not be defined while using NOMEMINIT. 
 Please let us know if you need any further assistance. 
 Regards, Divya.P)

Partner Forums

Partner Libraries

Products Mentioned

Variable in L2 SRAM will be reseted to zero after calling adi_rcu_ControlSystemReset() even though the variable are allocated in "no_init" L2 region

Thread Notes