5744 emulation EE system swap problem

[liujinhang]

hi every body, i need some help for the emulation EE system's swap problem.

as we know that in the emulation EE system, a full flash block will be erased when the useful data are all recorded at a new flash block. in my opinion, the old flash block must be erased after marking the new block valid flag. but actually i found in few times , the old flash block was erased but the new flash block has not been marked valid. this phenomenon will make data lost.

i used the DRIVER is v1.2.0, and i don't know if other body saw this problem in this version driver module. now i also want to know the reason of this problem.

any body help me please.

[lukaszadrapa]

Hi,

after swapping, the block is marked as COPY_DOWN in FSL_BlockSwapping function:

... and then it is erased. The block is then marked as active in  FSL_MainFunction or in FSL_InitEeprom.

I would recommend to download the latest version 1.3.0 which fixes some unrecoverable brownout cases.

http://www.nxp.com/files/run_time_software/device_driver/MPC5xxx_EEE_DRIVER.exe

Regards,

Lukas

[liujinhang]

could you help me to find the reason why the new block has not been marked valid flag in FSL_BlockSwapping function in EEE_DRIVER version 1.2.0?

[lukaszadrapa]

Hi,

are you able to reproduce the scenario? Could you share some simple project to be able to reproduce the issue? If you test it using version 1.3.0, is it working?

The drivers thoroughly tested before publishing, so I need something to move forward.

Regards,

Lukas

[liujinhang]

TKS for your response.

发件人: lukaszadrapa

发送时间: 2016年8月30日 15:28

收件人: liu jinhang

主题: Re: - 5744 emulation EE system swap problem

<https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg> NXP Community

5744 emulation EE system swap problem

reply from Lukas Zadrapa <https://community.nxp.com/people/lukaszadrapa?et=watches.email.thread> in MPC5xxx - View the full discussion <https://community.nxp.com/message/826934?commentID=826934&et=watches.email.thread#comment-826934>