• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 27 subscribers
  • Views 425 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Flash Program APIs

Hiroaki Tanikoshi
Intellectual 675 points
Other Parts Discussed in Thread: DLPC200

Dear Sir,

Regarding the Flash programming, Can we use DLP_FlashProgram_EraseParallelFlash() API before using DLP_FlashProgram_ProgramParallelFlash() API?

Are there any conserns for this routin?

Now there is a difference of about 5minites Flash writing time between the routins.

When we erase the parallel Flash in advance, uploading time is shorter than that we don't erase it in advance.

Please let me know why the uproding time difference occures in that case.

 

Best regards,

Hiroaki

 

 

  • 0
    TI__Mastermind 30875 points

    Hello Hiroaki,

    Good question.

    There is no concerns. You should be fine this approach.

    Please let me know why the uploading time difference occurs in that case.

    [Sanjeev]

    DLP_FlashProgram_ProgramParallelFlash() - When this API is called, the DLPC200 finds which area in the flash the programming is requested, then it will first erase, impacted sectors in the flash and then program the content.

    Now, DLP_FlashProgram_EraseParallelFlash() - This API simply erase the requested area, as you know, once the sector is erased, then next-time erasing takes almost no time. 

    So, in your new approach, since you have called DLP_FlashProgram_EraseParallelFlash() API, so all the sectors are erased and bits are programmed to set value in the flash.  After this calling DLP_FlashProgram_EraseParallelFlash(), the erase step in this function takes almost no time and directly get into the programming mode. This will save the time.

    Regards,

    Sanjeev