when I use mcuxpresso to debug FRDMK64 report error:"op EraseSector (0x0, 0x0, 0x4) status 0x1 - driver reported driver error - INTKFMM driver rc 16 - Flash protection violation op EraseSector (0x0, 0x0, 0x4) status 0x1 - driver reported driver error -

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

when I use mcuxpresso to debug FRDMK64 report error:"op EraseSector (0x0, 0x0, 0x4) status 0x1 - driver reported driver error - INTKFMM driver rc 16 - Flash protection violation op EraseSector (0x0, 0x0, 0x4) status 0x1 - driver reported driver error -

2,052件の閲覧回数
leilovelei100
Contributor II

error info.png

ラベル(1)
0 件の賞賛
返信
2 返答(返信)

1,776件の閲覧回数
lpcxpresso_supp
NXP Employee
NXP Employee

Hi,

Firstly, it is possible to accidentally attempt to flash a project for one MCU onto a different MCU - this can lead to errors from the flash driver. The correct flash driver for the K64 MCU is called FTFE_4K - you can check the debug log to see which flash driver is being used.

Assuming there was no error as described above, I would suggest you attempt to mass erase this part. This process is described in the User Manual for the IDE.

First location the LinkServer GUI Flash Programmer Icon from the ToolBar (it looks like a small MCU). Then be sure to select the Erase flash memory tab, and check the Mass erase radio button as below. Then click OK.

pastedImage_1.png

If this also fails, I would next try the third tab 'Resurrect locked Kinetis device'. To use this feature, simply select this tab and click OK.

In both of these cases all data on the flash will be erased.

I hope this helps,

Yours,

MCUXpresso IDE Support

1,776件の閲覧回数
leilovelei100
Contributor II

does it caused by MPU ?

0 件の賞賛
返信