SPRUJ27C November 2022 – November 2023 TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1
Verifies region specified against supplied data
Synopsis
Fapi_StatusType Fapi_doVerify(
uint32 *pu32StartAddress,
uint32 u32Length,
uint32 *pu32CheckValueBuffer,
Fapi_FlashStatusWordType *poFlashStatusWord)
Parameters
pu32StartAddress [in] | start address for region to verify | |
u32Length [in] | length of region in 32-bit words to verify | |
pu32CheckValueBuffer [in] | address of buffer to verify region against. Data buffer should be 128-bit aligned. | |
poFlashStatusWord [out] | returns the status of the operation if result is not Fapi_Status_Success | |
->au32StatusWord[0] | address of first verify failure location | |
->au32StatusWord[1] | data read at first verify failure location | |
->au32StatusWord[2] | value of compare data | |
->au32StatusWord[3] | N/A |
Description
This function verifies the device against the supplied data starting at the specified address for the length of 32-bit words specified. If a location fails to compare, these results will be returned in the poFlashStatusWord parameter.
Restrictions
None
Return Value
On the F28003x device, the zones get locked when the corresponding new programmed password locations in the Bank 0 User configurable DCSM OTP are read. This could cause further erase/program operations to fail. Hence, it is not suggested to do verify (Fapi_doVerify()) for the User configurable DCSM OTP Bank 0 locations.