MPC5605B DFLASH issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MPC5605B DFLASH issue

1,035 Views
曾经怀念
Contributor II

Hi,

 

   pastedImage_1.png

  

From the data sheet, it seem i have to wait for 300~500ms when erase DFLASH.

What is the risk if i open the external interrupts after enable EHV , or non-blocking

0 Kudos
6 Replies

867 Views
davidtosenovjan
NXP TechSupport
NXP TechSupport

Hi, it does not mean user would have to set up this wait time manually. After starting erase operation application polls MCR[DONE] bit.
However erase time may differ from piece-to-piece and it is also given by aging of flash memory.

0 Kudos

867 Views
曾经怀念
Contributor II

Hi David,

      

as usually:close external interrupts => EHV=1 => waiting for DONE => EHV=0 => open external interrupts

change     :close external interrupts => EHV=1 => open external interrupts=> polls MCR[DONE] => EHV=0

We need to assess the risk of change

0 Kudos

867 Views
davidtosenovjan
NXP TechSupport
NXP TechSupport

Hi, there is a risk of read-while-write operation in case user software wants to read from the memory during erase/program. It would lead either in bus error or execution stall (according to RWWC, on this device stalls by default).

A solution is to have interrupt vector table and interrupt/exception service routine placed in SRAM.

0 Kudos

867 Views
malekben
Contributor II

Even if interrupt/exception service routine are placed in FLASH that would be in the CFlash not in teh DFlash ...

0 Kudos

867 Views
davidtosenovjan
NXP TechSupport
NXP TechSupport

Yes, you are right. I have somehow forgot we are talking about DFLASH. In case case it should be OK unless interrupt service routine does not access DFLASH.

0 Kudos

867 Views
曾经怀念
Contributor II

Hi David,

      in this p time need to pay attention to what?

     Is there a special document to introduce this?

Thanks!

0 Kudos