TMS320F2800155-Q1: Issue with Flash-API

Hi Jens,

We will take a look and get back to you.

Customer can use F280013x Flash API meanwhile if needed.

Thanks and regards,
Vamsi

Hi Jens,

Is the customer able to compile and execute the flash API example successfully?  We are able to successfully build and execute the example from the web package.

Did they include the file flash_programming_f280015x.h as shown in the example?  

It has the definition of "FlashTech_CPU0_BASE_ADDRESS".  Constants.h file is not needed for this definition.  Constants.h file is left for the migration reasons (we will decide on whether or not to remove it at RTM).  F280013x and F280015x APIs will be merged at RTM.

Thanks and regards,
Vamsi

Hi Jens,

Please note:  I am out of office until February 23rd.  Please reply on February 23rd if you have further questions.  

Thanks and regards,

Vamsi

Customer has also issues with FlashAPI, hence I put it in your thread.

"When using the Fapi_issueProgrammingCommand(), we see it requires uint16 *pu16DataBuffer, after reading from flash memory we see the flash driver writing only one byte from each buffer entry.

Is it a mistake in the documentation about the input buffer type? As from what we can see it writes 8 bytes not 16 bytes.

Our expectation from the FlashAPI documentation is that 16 bytes would be written in flash memory in one go. We made sure that the buffer address is 16 bytes aligned."

Hi Martin,

Flash API can write 128-bits at once - there should not be any issue.  Did the customer review the flash programming example provided in the C2000Ware?

Buffer type is described correctly in the guide.  

Thanks and regards,

Vamsi

Please provide the folder + file-name of the example.

Martin,

Here is the path: ti\c2000\C2000Ware_4_03_00_00\driverlib\f280015x\examples\flash\flashapi_ex1_programming.c

Thanks and regards,

Vamsi

Hello Vamsi,

customer tested the FlashAPI library based on the examples provided in flashapi_ex1_programming.c.

The test was made on sector 15 of the F2800157 controller.

First the sector is erased using the following function:

After erase the 16bit 1024 element buffer (as in example) is populated in the following way:

And the flashing is done:

After flashing, the flash is dumped and I get the following:

Per cycle I can only flash 64 bits not 128. Is there something that I am not doing right?

Hi Martin,

Did the customer try the flash API example as-is?  Did it show the same behavior?

Thanks and regards,

Vamsi

Hi Martin,

Is there any update from the customer on this?  

Can I assume that this issue is resolved?

Thanks and regards,

Vamsi

Hi Martin,

I am closing this post since I did not hear back from you.

If needed, please open a new post.

Thanks and regards,

Vamsi