Note: I have commented , last erase function there.

Hi Yogini,

What is the returned FMSTAT value when it did not program?

Did verify pass successfully?

Thanks and regards,

Vamsi

Hello Vamsi,

I tried to watch the return value of below function;

I always get Fapi_Status_Success.

I read after write operation and verify operation;

//
// Verify the programmed values. Check for any ECC errors.
//
oReturnCheck = Fapi_doVerify((uint32 *)u32Index,
4, Buffer32+(i/2),
&oFlashStatusWord);

Hi Yogini,

How about the FMSTAT value returned from Fapi_getFsmStatus()?

Thanks and regards,

Vamsi

returned value is zero.

Also, I have one more doubt. then values which are reflecting in map file are in words or bytes?

Hi Yogini,

Can you keep a break point after the program/verify (in the C2000Ware example code) and take a snapshot of the memory window and share here?

Thanks and regards,
Vamsi

Hello Vamsi,

Thank you for your answer.

I have one more question related to it.

from the above mentioned code , I see that flash api cannot be called from same bank.

//
// Flash API functions should not be executed from the same bank on which
// erase/program operations are in progress.
// Also, note that there should not be any access to the Flash bank on
// which erase/program operations are in progress. Hence below function
// is mapped to RAM for execution.

But our controller has only one bank. then how can we call these apis for bootloader? 

it will be difficult to map them to RAM as , when we flash application , we have both bootloader + application in the memory.  will it cause any issue?

Also,

I was trying to write the sector 6, I wrote blinky code which is mapped to sector 6. Then I added jump  instruction to sector 6 at the end. But code is going to trap after jump.

Interrupt_illegalOperationHandler()

Hi Yogini,

Please open separate threads for separate questions.  It will make it easy for us to track the issues.  

Is the original issue at the start of this thread solved now?  

Thanks and regards,
Vamsi

Okay. Previous issue is resolved