How to debug with CCS, when ECC enable.

please upgrade to CCS 6.
the download capability includes an auto-ecc generation so it will program ECC for you automatically whenever you download your code.
the compiler also offers you a alternative method - you can generate ECC directly during linking.

So the extra step outside the build flow where you use nowECC is no longer necessary.
We only provide nowECC in case you are not using CCS or the TI ARM compiler.

Thank you for reply !

I'll try to use CCS 6. But  our project decided to use CCS v5.5.

Is there a way to debug with CCS v5.5 when ECC enbale?

If answer is no, should we debug with CCS v5.5 on condition that (Flash) ECC function is disabled?

I solved the problem by myself.
I found Auto ECC Gen Setting in CCS v5.5.
Project Properties → Debug → Flash Settings　→　chaeck [Auto ECC Generation]

I have a new Question.

Where can I find Auto gen ECC file(binary)?
just can read from Memory Browser in debug mode?

Super.

There is no ecc file when you use auto-generated ECC. The ECC is computed on the device on the fly during programming and is programmed into the ECC array at the same time the data array is programmed.

If you want ECC in a file, you need to use the linker to generate ECC.

Thank you for the quick response.

I understand Auto ECC Generator in CCS don't generate ECC file.

Sorry to ask many question,

Q1.
 >If you want ECC in a file, you need to use the linker to generate ECC.

I found a Wiki page.

<processors.wiki.ti.com/.../Linker_Generated_ECC ECC&tisearch=Search-JP-Everything>

 ・Linker Generated ECC

Is this wiki page what you had to say?

If this page is not, please can you show me a reference.

Q2.

If I use the linker to generate ECC, should I uncheck  [Auto ECC Generation] in CCS v5.5?

([Auto ECC Generation] ：　Project Properties → Debug → Flash Settings)

I think that, Auto ECC generation function in CCS will overwrite ECC generated by linker.

Thank a lot !
I could burn ECC generated by linker and debug !
My next task is emulation faults in ECC function.

Thank you!

There's a dedicated piece of memory in your controller with a deliberate error, to test the ECC.

Here's a piece of test code (lifted from the Hercules Safety Demos):

void ATCM_Correctable_Error(void) {
	unsigned int Single_Bit_Err_Loc;

    /** - 0xF00803F4 is TI OTP location which has corrupted data "0x9ABCDEF1" */
	unsigned int * Single_Bit_Err_Loc_ptr = (unsigned int *)(0xF00803F4);
	
    /** - Setup Flash ECC  
    *     - Error Detection / Correction Enable
    *     - Errors from OTP memory regions unblocked
    *     - Correctable Interrupt Enabled
    */
	flashWREG->FEDACCTRL1 = 0x20D;

    /** Enable Flash ECC in Cortex R4*/
	_coreEnableFlashEcc_();

    /** - Read data from the Single Bit Error location 
	 *	  - ESM error will be triggered after this read
	 *	  - Data will be corrected and stored in the variable Single_Bit_Err_Loc
	 */
	Single_Bit_Err_Loc = * Single_Bit_Err_Loc_ptr;

    /** - Verify that corrected data is stored in the variable
     *  - Transmit back 0x0000000 to PC incase of failure
     */
	if(Single_Bit_Err_Loc != 0x9ABCDEF0) 	{
//    sciSend_32bitdata(scilinREG, FAIL); // todo make this relevant to educational boosterpack
	}

    /** - Clear the Flash Single Bit error Flag */
	flashWREG->FEDACSTATUS = 2;

    /** - Disable Flash Error Detection / Correction */
	flashWREG->FEDACCTRL1 = 0x005;

    /** Disable Flash ECC in Cortex R4*/
	_coreDisableFlashEcc_();

}