TMS570LS3137: SYSESR Register is not working as intended while observing reset source in debug mode

I noticed that 

void _c_int00(void)

    /* check for power-on reset condition */
    /*SAFETYMCUSW 139 S MR:13.7 <APPROVED> "Hardware status bit read check" */
    if ((SYS_EXCEPTION & POWERON_RESET) != 0U)

On the other hand, WATCHDOG_RESET behaves like POWERON_RESET. It goes high at startup and is cleared in _c_int00 function and never triggered after that till power up event happens once again.

Btw, Loading Code into the uC should be trigger POWERON_RESET right ?

Hi Ismail,

The power-on-reset is only triggered by power cycling the device or pulling the nPORRST pin to LOW then HIGH. Loading code into the uC will not trigger Power-on-reset.

You can top the code execution before the SYSESR is cleared, then read the real value of SYSESR register.

After power-on-reset, the code will stop at while(adc==0). Connect the JTAG emulator to target, and read the SYSESR value from the register window:

Hi Mr. Wang, I defined a global variable and assigned SysEsr Content to this variable but, When the program jumped to Main Function the  after completed startup issues, my global variable content is reset due to the resetting ram-rom operations before exit startup.

What is the best approach to save SysEsr content ? Someone has advised to use FLASHBANK7, in this case, I wonder that where is the best place to insert "the  code that program flashbank7" in startup function, this is important because if I insert the code where a necessary thing did not initialize may cause error.

I tried to program flashbank7 in startup but I got failed. I uploaded the code where I inserted. I just tried a dummy bytes to write  Fbank7 start address.

code is stucked where query the state of FMdlStat register in FlashWrapper if I am right.

FMdlStat  value is 0x00000410(hex). This means 10. and 4. bit are set. 

10.bit says

Erase Verify
When set, indicates that a sector is not successfully erased after the maximum allowed number of
erase pulses are given for erase operation. During Erase verify command, this flag is set
immediately if a bit is found to be 0.

What I have to do ? 

We use crystal osc at 16MHz and convert it 160Mhz via PLL.

This code block work in main well.

Finally, this code only works after __TI_auto_init function is executed.

Sir Wang, I reviewed the example,

TI_Fee_WriteSync(BlockNumber, &SpecialRamBlock[0]);

Hi Ismail,

From HALOCGen FEE configuration windows, you define the number of blocks, and size of each block. When you call the FEE APIs, using the block number as the function argument is enough.

Hmm now it's okey. One more question, In that example there is a piece of code 

	do
	{
		TI_Fee_MainFunction();
		delay();
		Status=TI_Fee_GetStatus(0);
	}
	while(Status!=IDLE);

Is this code necessary to call after each erase or program function called ?

The TI_Fee_MainFunction() is used to finish the flash or data operations initiated by erase/write functions. It should be called at regular intervals.

I call this function after calling erase/program (async) function

Thank you Sir Wang, I will try these api functions in sys_startup to save SYSESR content and will give feedback about results.