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.
Hello Support team.
This question is about Flash erase using Flash API (FAPI_F28003x_COFF_v1.58.01.lib).
Could you please explain why the second argument (pu16DataBuffer) of Fapi_issueProgrammingCommand() needs to be placed in 128-bit align?
Also Could you please explain why the third argument (pu32CheckValueBuffer) of api_doVerify() needs to be placed in 128-bit align?
For example, customer is understanding that system cannot write such as the below.
Is it correct ?
Best Regards
KORO
Hi Koro,
Based on a few previous customer queries, we wanted to make it simple and hence mentioned that those data buffers have to be 128-bit aligned.
However, as long as the address of the data buffer starts on a even address, it should be fine.
The diagram that you copied from customer is good to implement - no issue with that.
Thanks and regards,
Vamsi
Hello Vamsi-san
> Based on a few previous customer queries, we wanted to make it simple and hence mentioned that those data buffers have to be 128-bit aligned.
But your answer is that an even address can be used.
if customer asked TI if TI has plan to modify this document, how we can answer it ?
Best Regards
KORO
Hi Koro,
A clarification here in this forum should be enough I hope. If not, please let them know that I wrote that guide. 128-bit alignment does not hurt - however, if the user is not able to maintain that, then an even address using ALIGN(2) should do.
Thanks and regards,
Vamsi