MCUXpresso IDEのトピックRe: when I use mcuxpresso to debug FRDMK64 report error:&quot;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 erro https://community.nxp.com/t5/MCUXpresso-IDE/when-I-use-mcuxpresso-to-debug-FRDMK64-report-error-quot-op/m-p/763400#M2177 <HTML><HEAD></HEAD><BODY><P>does it caused by MPU ?</P></BODY></HTML> Mon, 29 Jan 2018 05:32:05 GMT leilovelei100 2018-01-29T05:32:05Z 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 - https://community.nxp.com/t5/MCUXpresso-IDE/when-I-use-mcuxpresso-to-debug-FRDMK64-report-error-quot-op/m-p/763399#M2176 <HTML><HEAD></HEAD><BODY><P><span class="lia-inline-image-display-wrapper" image-alt="error info.png"><img src="https://community.nxp.com/t5/image/serverpage/image-id/30463iD47FF6B20016BF1E/image-size/large?v=v2&amp;px=999" role="button" title="error info.png" alt="error info.png" /></span></P></BODY></HTML> Mon, 29 Jan 2018 04:39:41 GMT https://community.nxp.com/t5/MCUXpresso-IDE/when-I-use-mcuxpresso-to-debug-FRDMK64-report-error-quot-op/m-p/763399#M2176 leilovelei100 2018-01-29T04:39:41Z Re: 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 erro https://community.nxp.com/t5/MCUXpresso-IDE/when-I-use-mcuxpresso-to-debug-FRDMK64-report-error-quot-op/m-p/763400#M2177 <HTML><HEAD></HEAD><BODY><P>does it caused by MPU ?</P></BODY></HTML> Mon, 29 Jan 2018 05:32:05 GMT https://community.nxp.com/t5/MCUXpresso-IDE/when-I-use-mcuxpresso-to-debug-FRDMK64-report-error-quot-op/m-p/763400#M2177 leilovelei100 2018-01-29T05:32:05Z Re: 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 erro https://community.nxp.com/t5/MCUXpresso-IDE/when-I-use-mcuxpresso-to-debug-FRDMK64-report-error-quot-op/m-p/763401#M2178 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>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.</P><P></P><P>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.</P><P></P><P>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.</P><P></P><P><span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"><img src="https://community.nxp.com/t5/image/serverpage/image-id/33615iF427501C6D731865/image-size/large?v=v2&amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /></span></P><P></P><P>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.</P><P></P><P>In both of these cases all data on the flash will be erased.</P><P></P><P>I hope this helps,</P><P></P><P>Yours,</P><P></P><P>MCUXpresso IDE Support</P></BODY></HTML> Tue, 30 Jan 2018 12:29:22 GMT https://community.nxp.com/t5/MCUXpresso-IDE/when-I-use-mcuxpresso-to-debug-FRDMK64-report-error-quot-op/m-p/763401#M2178 lpcxpresso_supp 2018-01-30T12:29:22Z