| Electronic Components Datasheet Search |
|
UM1618 Datasheet(PDF) 22 Page - STMicroelectronics |
|
|
|||||||||||||||||||||||||||||
UM1618 Datasheet(HTML) 22 Page - STMicroelectronics |
|
22 / 51 page ![]() API specification UM1618 22/51 DocID024371 Rev 3 Comments After performing a program, ‘ProgramVerify’ should be used to verify the programmed data is correct or not. ‘FlashProgram’ checks the mainInterfaceFlag in the SSD configuration to decide which interface to be used for the operation, the main interface or the alternate interface. User should explicitly set this parameter before calling the function. This function also provides a fas ter method for user to perform, factory program. But the feature cannot be performed if the data at “diary” location in the UTest NVM space contains at least one zero at reset. In that case, each try to perform factory program cause the error C55_ERROR_FACTORY_OP be returned. If the selected main array blocks are locked for programming, those blocks are not programmed, and ‘FlashProgram’ returns C55_OK. If user wants to program to Large block space via alternate interface, this function still returns C55_OK without doing any program operation. It is impossible to program any Flash block when a program or erase operation has already been in progress on C55 module. ‘FlashProgram’ returns C55_ERROR_BUSY when doing so. However, user can use the ‘FlashSuspend’ function to suspend an on-going erase operation on one block to perform a program operation on another block. It is unsafe to read the data from the Flash partitions having one or more blocks being programmed when ‘FlashProgram’ is running. Otherwise, it causes a Read-While-Write error. If user wants to do program for multi-programmable size, this function plays a role to kick-off this operation by finishing program for the first programmable size after back-up all necessary information to pCtxData variable. And programming from the second programmable size is done within ‘FlashCheckStatus’ function. Thus, user must call ‘FlashCheckStatus’ to finish all his expected operations defined by size argument. Assumptions It assumes that the Flash block is initialized using a ‘FlashInit’ API. And Flash location must be in erased state before calling ‘FlashProgram’ API. 2.7.6 ProgramVerify Description This function is to verify the previous program operation. It verifies if the programmed Flash range matches the corresponding source data buffer. In case of mismatch, the failed address, failed destination and failed source are saved and relevant error code are returned. This function only does verification for given number of bytes which can terminate this function within expected time interval. Thus, if user wants to do Flash verification for large size, the rest of information need to be verified is stored in “pCtxData” variable and ‘FlashCheckStatus’ must be called periodically to do the next verification for next destination based on all data provided in “pCtxData”. |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |