topic Re: MPC5605B DFLASH issue in MPC5xxx

MPC5605B DFLASH issue

曾经怀念 — Wed, 03 May 2017 13:29:43 GMT

Hi,

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

Re: MPC5605B DFLASH issue

davidtosenovjan — Wed, 03 May 2017 13:56:03 GMT

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.

Re: MPC5605B DFLASH issue

曾经怀念 — Thu, 04 May 2017 00:50:24 GMT

Hi David,

in this p time need to pay attention to what?

Is there a special document to introduce this?

Thanks!

Re: MPC5605B DFLASH issue

曾经怀念 — Thu, 04 May 2017 01:37:37 GMT

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

Re: MPC5605B DFLASH issue

davidtosenovjan — Tue, 09 May 2017 07:34:36 GMT

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.

Re: MPC5605B DFLASH issue

malekben — Thu, 11 May 2017 15:29:39 GMT

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

Re: MPC5605B DFLASH issue

davidtosenovjan — Fri, 12 May 2017 07:13:40 GMT

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.