TMS320F280025C: Flash API Fapi_doVerify problem

Tomas Lehotsky

Hi,

I am working with the TMS320F280025C device and I have met a very strange problem. I have developed the bootloader for erase/program/verify the content of the flash. I can successfuly program the device and erase it but not able to verify the flash. My bootloader is loaded directly to RAM(via parallel boot mode) and run from this location. Everything works fine to the step, when the flash start to verify...

My code looks like this(in accordance with driverlib example):

        for(i=0, u32Index = Address;
                (u32Index < (Address + WORDS_IN_FLASH_BUFFER));
                i+= 8, u32Index+=8)
        {
            EALLOW;
            oReturnCheck = Fapi_issueProgrammingCommand((uint32 *)u32Index,Buffer+i,8,0,0,Fapi_AutoEccGeneration);
            // Wait until FSM is done with actual operation
            while(Fapi_checkFsmForReady() == Fapi_Status_FsmBusy);

            if(oReturnCheck != Fapi_Status_Success){
                break;
            }

            oFSM_stat = Fapi_getFsmStatus();
            if(oFSM_stat != 0)
            {
                oReturnCheck = Fapi_Error_FeatureNotAvailable;
                break;
            }

            //verify
            oReturnCheck = Fapi_doVerify((uint32 *)u32Index, 4, Buffer32+(i/2), &oFlashStatusWord);
            if(oReturnCheck != Fapi_Status_Success){
                break;
                }
            EDIS;
        }

The oReturnCheck = Fapi_doVerify exits with the Fapi_Error_Fail and I don't know why. The strange is, when I debug this code from CCS (CCS 10.2.0.00009 ) the code works well. But after loading the generated hex file(from out file) and load to RAM and run, the verify is not working. I have tried the BOOT ROM flash API(FlashAPI_ROM_F28002x_FPU32.lib) and also the software flash API(FlashAPI_F28002x_FPU32), but the result is always the same - the verify is still not working.

Can someone explain, why program and erase works well but the verify not? IS the

Thank you!

Best regards,

Tomas

over 5 years ago

0 Vamsi Gudivada over 5 years ago

TI__Guru* 87155 points

Tomas,

When it failed, what is the info returned in the oFlashStatusWord? Please check and see if that failing location has valid data or not. We can analyze further based on that.

Thanks and regards,

Vamsi

0 Tomas Lehotsky over 5 years ago in reply to Vamsi Gudivada

Expert 1025 points

Hi Vamsi,

this is very strange situation, because it seems, that from some reason I am not able to obtain the data from this status word. For an example, when I comapre the burned data with blank data (0xFFFF), algo can identifying it and show the compared with burned value. But when I try to verify the burned data with some random data, in this case the returned value is completely irrelevant with no meaninig - the returned oFlashStatusWord don't throw the expected data and readed data. It seems, like some exception has start or something similar. And it is very hard to simulate because in debug mode, the algo works.

Thanks,

Tomas

0 Vamsi Gudivada over 5 years ago in reply to Tomas Lehotsky

TI__Guru* 87155 points

Tomas,

Maybe the application is ending up in an NMI - I would suggest to check for ECC errors.

Also, do you have watchdog enabled? If yes, are you servicing it as needed?

In case of debug mode, gel file disables watchdog and ECC.

Thanks and regards,
Vamsi

0 Vamsi Gudivada over 5 years ago in reply to Vamsi Gudivada

TI__Guru* 87155 points

Tomas,

Do you have any update on this?

Thanks and regards,
Vamsi

0 Vamsi Gudivada over 5 years ago in reply to Vamsi Gudivada

TI__Guru* 87155 points

Tomas,

I am closing this post since I did not hear back from you in the last two weeks. Hope the issue is closed based on our suggestions.

Thanks and regards,
Vamsi

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMS320F280025C: Flash API Fapi_doVerify problem