This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F28035: questions for Flash_Erase(Uint16 SectorMask, FLASH_ST *FEraseStat)

Part Number: TMS320F28035

In the given flash_programming example of F2803x, for the below function, customer have several questions:

Status = Flash_Erase((SECTORB|SECTORC|SECTORD|SECTORE|SECTORF|SECTORG|SECTORH),&FlashStatus);

1) Are Sector B, SECTORC, etc erased one by one with this order? 

2) If status returns 0, could you please help list all the possible reasons?

Thank you.

  • Aki,

    I'm referring to the Flash2803x_API_Quickstart.pdf here: https://dev.ti.com/tirex/explore/node?node=AEiIpUxZu423YUsC6AClyQ__gYkahfz__LATEST

    1)On Page 30 it states: On the F2803x the specified sectors are erased in order Sector H – Sector A., so in the example above Sector H would be erased first and Sector B would be erased last.

    2)Page 39 has the Erase Status Messages:

    There is also a structure *FEraseStat that is defined in the API_Library.h file as:

    typedef struct {
    Uint32 FirstFailAddr;
    Uint16 ExpectedData;
    Uint16 ActualData;
    }FLASH_ST;

    Note: For erase, only the FirstFailAddr of this structure is currently
    used.

    Best,

    Matthew