TMS320F28379D: flash erase/write busy bit is not set

but what could be the reason for a timeout in case of serveral erase procedures.

Vamsi,
sorry, I was on vacation the last to weeks.

Here the code snippet:

      EALLOW;
      eAPIResult = Fapi_issueAsyncCommandWithAddress (Fapi_EraseSector, (SMX_U32 *) u32SectorStartAddress);
      EDIS;

      SMX_U32 *pu32AddrPtr, u32val;
      pu32AddrPtr = (SMX_U32 *) 0x5F82A;
      u32val = *pu32AddrPtr;
      DB_PRINTF(("FMSTAT (0x5F82A) = 0x%04x%04x\r\n", (SMX_U16) (u32val >> 16), (SMX_U16) (u32val)));
      u32val = *pu32AddrPtr;
      DB_PRINTF(("FMSTAT (0x5F82A) = 0x%04x%04x\r\n", (SMX_U16) (u32val >> 16), (SMX_U16) (u32val)));
      u32val = *pu32AddrPtr;
      DB_PRINTF(("FMSTAT (0x5F82A) = 0x%04x%04x\r\n", (SMX_U16) (u32val >> 16), (SMX_U16) (u32val))); 

Printf-output:
0x8405 MEMORY ERASE
FMSTAT (0x5F82A) =0x00000000
FMSTAT (0x5F82A) =0x00000000
FMSTAT (0x5F82A) =0x00000000

Regards, Holger

Holger,

I don't see customer waiting for the FSM operation to complete. As shown in the Flash API guide and mentioned in the Flash API wiki, application should wait for the FSM to complete the erase operation as shown below using Fapi_checkFsmForReady() function.

oReturnCheck = Fapi_issueAsyncCommandWithAddress(Fapi_EraseSector, Sector Address);

while (Fapi_checkFsmForReady() != Fapi_Status_FsmReady) { }

Please ask customer to make this change and see if that helps.

Thanks and best regards,

Vamsi

Hello Vamsi,
he uses these functions. It works when erasing one section but erasing more sections there will be errors. Btw, how long would be the busy flag set?

Here the code he uses in production:

RESULT TMS320_F2837x_FLASHEraseSector (SMA_U32 u32SectorStartAddress, SMA_U32 u32TimeoutIterations)
{
   RESULT Result = BSP_ERROR;
   Fapi_StatusType eAPIResult;
   boolean bAbort = false;
   SMA_U8 u8WaitLoop; 

   /* set active flash bank */
   EALLOW;
   eAPIResult = Fapi_setActiveFlashBank (Fapi_FlashBank0);
   EDIS;

    /* initiate erase command */
   if (Fapi_Status_Success == eAPIResult)
   {
      EALLOW;
      eAPIResult = Fapi_issueAsyncCommandWithAddress (Fapi_EraseSector, (SMA_U32 *) u32SectorStartAddress);
      EDIS; 

      /* WORKAROUND: For unknown reasons function Fapi_checkFsmForReady     *
       * does not return a busy flag while writing is active. Thus we       *
       * stay here for the time given by spec (max. 55ms for a 32KW sector) */

       #define WAIT_ERASE_MS 55u 

      for (u8WaitLoop = 0u; WAIT_ERASE_MS > u8WaitLoop; u8WaitLoop++)
      {
         (void) bsp2_HWDTrigger (BSP_CHANNEL_0);
         TMS320_CPUDelay_us (1000);
      }

      /* End of WORKAROUND */ 

      /* wait until erase process has finished */
      while ((0UL != u32TimeoutIterations) && (false == bAbort))
      {
         if (Fapi_Status_FsmReady == Fapi_checkFsmForReady())
         {
            bAbort = true;
         }
         else
         {
            u32TimeoutIterations--;

             if (0UL == (u32TimeoutIterations % 100UL))
              (void) bsp2_HWDTrigger (BSP_CHANNEL_0)
         }
     }

      if (0UL != u32TimeoutIterations)
      {
         if (Fapi_Status_Success == eAPIResult)
         {
            Result = BSP_OK;
         }
      }

      else
         Result = BSP_ERR_FLASH_TIMEOUT;
   }
   return Result;
}

Regards, Holger

Holger,

Erase times are provided in Table 5-20. Flash Parameters of datasheet.

Are you saying that erase is taking more than 55ms for a 32KW sector?

How many write/erase cycles did the device go through?

Instead of above timeout procedure, if they simply wait on FSM using Fapi_checkFsmForReady(), does it ever complete erasing? OR is it stuck in the loop?

while (Fapi_checkFsmForReady() != Fapi_Status_FsmReady) { }

Thanks and regards,
Vamsi

Hello Vamsi,
the problem is that it runs to fast through Fapi_checkFsmForReady() like the busy bit is not set. For one cycle it is no problem but if you do several erase cycles then it runs into problem. 

Regards, Holger