Hello Robert, All of the verification requirements are handled within the FlashCtl APIs themselves. The verification/read mode APIs are made available to enable power users to write their own flash drivers, however it is highly recommended that the majority of users rely on the DriverLib APIs to handle all of the verification requirements and read mode transitions. As far as the timing for the mass erase function, it is very dependent on your code. The majority of this code is actually going to be executing from the MSP432's ROM. This means that there are no requirements for erasing and bank execution, however if you erase the code that the mass erase function jumps back to after completion your program counter is going to be incorrect. Could you share which version of CCS you are using as well as which version of DriverLib? Best Regards,
↧