topic Re: "Device is secure. Erase to ensecure?". in Kinetis Microcontrollers

"Device is secure. Erase to ensecure?".

arturoarteaga — Tue, 07 Mar 2017 09:20:27 GMT

Hi,

I would like to reprogram a MK20DX64VLH7 microcontroller that I have in a board with , but I haven´t been able to download the new firmware and erase a previous firmware that I´ve just download before succesfully. In the monitor it appears the next message: "Device is secure. Erase to ensecure?". I repetedly choose "Yes" but without any success, until the next message appears: "Launching LED Debug (4) has encountered a problem. Error in services launch sequence". In details appears written: "Error in services launch sequence Timed out trying to launch GDB Server."

I use KDS application, and "Debug Configuration" Option and GDB PEMicro with "Multilink Universal" programmer.

I´ve followed the KDS User Guide in order to set Debug Configurations.

Maybe there is one problem with the secure configuration of microcontroller, but I don´t know.

How can I erase the flash memory to reprogramm again?

I didn´t program the 0x40C address related to "NV_SEC" because I´ve only done the tutorial from Processor Expert, but I don´t know if this application program this address (0x40C) by default when I choose "Generate Processor Expert Code".

Anyway I tell you that it appears in this this address in my application:

NV_SEC (Address: 0x40C):

Init. value. 7E
After reset. FF

whose bits are:

KEYEN bits:
Init. value. 01
After reset. 11

MEEN bits:
Init. value. 11
After reset. 11

FSLACC bits:
Init. value. 11
After reset. 11

SEC bits:
Init. value. 10
After reset. 11

I don´t know how I can access to these registers by the "Processor Expert Application".

I would like to know how I could erase the firmware loaded in the MK20DX64VLH7 microcontroller to be able to reprogram it, as well as reprogramming in unsecure mode in order not to have this problems again. Or to program a firmware erasing the firmware loaded before. Do you know if there are any application to manage this. I have used "pe_gdb_server" and "multilink_universal" applications before but without any success.

Moreover I didn´t check a box to secure. The security boxes from the flash are disable by default and Protection regions are unprotected in Component Inspector Properties in the "Processor Expert Application" in KDS.

According to this I think there shouldn´t be any problem with accesses related to security.

I will continue researching.

Thanks previouslly for your answer.

your sincerelly,

Arturo Arteaga

Re: "Device is secure. Erase to ensecure?".

kerryzhou — Wed, 08 Mar 2017 03:24:18 GMT

Hi Arturo Arteaga,

About the secure, please read this document at first:

https://community.nxp.com/servlet/JiveServlet/download/857127-1-396709/Kinetis%20Lock%20issue%20analysis%20and%20unlock%…

If you have the JLINK, I suggest you to use the JLINK to unlock it in the JLINK commander window.

If you don't have JLINK, try to use mass erase in the KDS:

Please try it at first, if you still have problem, please let me know!

Have a great day,
Kerry

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Wed, 08 Mar 2017 09:18:38 GMT

Hi Kerry,

Firstly I would like to thank you because of your answer.

Unfortunately I don´t use JLINK, here we only use “Multilink Universal” from PE Micro. I have just done your proposed solution that I should check the “Emergency Kinetis device Recovery by chip erase” box but it wasn´t satisfactory as well. When I debug the chip, instead of receiving the message “Device is secure. Erase to unsecure?”, I receive the message that I´m attaching in this mail (“An error occurred while connecting to the interface hardware….”) and next another message (“Launching LED debug” has encountered a problem. Error in services launch sequence…). (see “Debug fail” image attached)

I have read carefully your “*.pdf” document. Maybe in my case the error root could be that when I managed to debug, I have chosen “Disconnect” option in the “GDB Trace” in KDS Application instead of having chosen “Terminate” option previously, or perhaps I have pulsed the Reset button in my target. I don’t know if when it happens this coincidences, it is that the chip is in “secure state”.

Sometimes I have managed to erase the chip with P&E GDB Server for Kinetis application when I had chosen “Allways mass erase on connect”, but then after I have managed to reprogram successfully later I can´t reprogram again because it is in “secure state” because of coincidences that I don´t know.

Also I have used “Multilink universal” software application, but without any success result.

I´ve seen to the CPU registers, that every FSEC bit changes to “1” after RESET (I have attached these registers in the application), I think that with SEC bits in “11”, maybe the chip enters in “secure state”. In MK20DX256VH7 datasheet you can read that the microcontroller enters in this secure state if you have these “11” values in SEC values. (See “NV_FSEC” image attached)

I want to know if there is an application that I manage to erase the chip, in order to manage to get out from “secure state”.

Another solution is, if there is a development firmware that you can erase or initialize the microcontroller in order to reprogram microcontroller from KDS application.

Or also if I can develop a new firmware that I can set a new configuration for the CPU, thus I can manipulate the CPU inside bits that erase the before firmware. Do you know what bits you can manipulate to erase the chip? I have seen MDM-AP register that it is mentioned in *.pdf. The 0 bit from MDM-AP register (Flash Erase Mass in progress), it appears that It is only cleared by hardware after mass erase operation completes. I think this operation I´ve just manipulate with P&E GDB Server for Kinetis application that I mentioned before. Do you Know if there is another way to erase by another bit? Or if you can access to this MDM-AP register by CPU configuration somehow. I haven´t seen this register in CPU peripheral registers. (See “MDM-AP” image attached).

Thanks again for your help,

Regards,

Arturo Arteaga

De: kerryzhou

Enviado el: miércoles, 08 de marzo de 2017 4:25

Para: Arturo Arteaga

Asunto: Re: - Re: "Device is secure. Erase to ensecure?".

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

Re: "Device is secure. Erase to ensecure?".

reply from Kerry Zhou <https://community.nxp.com/people/kerryzhou?et=watches.email.thread> in Kinetis Microcontrollers - View the full discussion <https://community.nxp.com/message/884677?commentID=884677&et=watches.email.thread#comment-884677>

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Wed, 08 Mar 2017 09:52:26 GMT

Sorry but didn´t appear the images in the previous message. I attach the images related to the previous image.

Thanks,

Regards.

Re: "Device is secure. Erase to ensecure?".

kerryzhou — Thu, 09 Mar 2017 05:17:54 GMT

Hi Arturo Arteaga,

If your software code didn't lock the chip, your problem should be caused by the hardware.

Please check your hardware about these points:

1. Reset pin should have 4.7k to 10K pull-up resistor, and 0.1uf capacitor to ground.

2. NMI pin should have external pull up

3. SWD_DIO should have 4.7k to 10K pull up resistor.

The above is the basic board design.

But if the device security is caused by the power up sequence: if the reset pin power up earlier than VDD, it will lock the chip and hard to recover.

I suggest you find a JLINK, and use the JLINK commander input: unlock kinetis at first.

If the JLINK still can't unlock it, your chip maybe difficult to unsecure, just like the power up sequence problem.

Please also use short debugger cable which is mentioned in the document which I give you before.

Please check your hardware again, you also can find another board, make sure the hardware is meet the demand, and download the code which is in unsecure mode again.

Have a great day,
Kerry

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Thu, 09 Mar 2017 17:14:17 GMT

Hi Kerry,

Thanks of your last answer.

I have made the changes that you have suggested me, in our case it was to put a new capacitor of 100 nF in the RESET pin to ground.

Some hours it has worked although it was locked when we switched off the power, and later we managed to unlock the chip with the “PE GDB for KINETIS” with the “mass erase on connect” functionality and then later we downloaded the program several times.

But although this success, we have had the chip locked and now we haven´t been able to unlocked again. I don´t know why.

I have done a captured image from the oscilloscope between the VDD signal and RESET signal. In the image you can see a green curve and a pink curve. Green curve is the VDD signal and pink signal is the RESET signal. You can see that RESET signal isn´t before as VDD signal, and we haven’t problems with the frequency and levels of signals.

I hope you have known something more than what happen.

Thanks a lot for all of your help.

Regards,

Arturo Arteaga

De: kerryzhou

Enviado el: jueves, 09 de marzo de 2017 6:19

Para: Arturo Arteaga

Asunto: Re: - Re: "Device is secure. Erase to ensecure?".

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

Re: "Device is secure. Erase to ensecure?".

reply from Kerry Zhou <https://community.nxp.com/people/kerryzhou?et=watches.email.thread> in Kinetis Microcontrollers - View the full discussion <https://community.nxp.com/message/884975?commentID=884975&et=watches.email.thread#comment-884975>

Re: "Device is secure. Erase to ensecure?".

kerryzhou — Mon, 13 Mar 2017 10:19:09 GMT

Hi Arturo Arteaga,

Could you tell me how many board on your side have this problem?

Did you check any other board?

Maybe you can try to solider your chip again with the temperature at max 270, just to exclude the bad pin connection problem.

Please also check the debugger interface, whether the wire have the bad connection problem.

Have a great day,
Kerry

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Thu, 16 Mar 2017 17:14:36 GMT

Hi Kerry,

Thanks for your help, we have managed to program the board correctly. We have solved these problems by taking off some pull-ups and downs connected wrongly to SWD. I have connected also a pull-up to CS pin. Occasionally it faults again but I erase the program with “GDB for kinnetis application”.

I have a question, I haven´t managed to stop running the application with breakpoints except in main fuction that it´s selected by default in “Debug Configuration” in “Start up” tab. I don’t know why, because I have configured ok the breakpoints and they are enable and with a blue circle,

Perhaps, should I install some pluggin?? Another configuration that I don´t know?

Thanks a lot again,

Arturo Arteaga

De: kerryzhou

Enviado el: lunes, 13 de marzo de 2017 11:20

Para: Arturo Arteaga

Asunto: Re: - Re: "Device is secure. Erase to ensecure?".

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

Re: "Device is secure. Erase to ensecure?".

reply from Kerry Zhou <https://community.nxp.com/people/kerryzhou?et=watches.email.thread> in Kinetis Microcontrollers - View the full discussion <https://community.nxp.com/message/886010?commentID=886010&et=watches.email.thread#comment-886010>

Re: "Device is secure. Erase to ensecure?".

kerryzhou — Fri, 17 Mar 2017 05:28:09 GMT

Hi Arturo Arteaga,

You don't need to install the plugin to add the breakpoints.

When you add the breakpoints, just with the tick sign, it is the useful break points:

Please check it on your side.

Have a great day,
Kerry

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Fri, 17 Mar 2017 07:40:34 GMT

Hi,

Sorry Kerry, I have tried to add the tick sign, but I haven´t managed it. I don´t see how you can get tick signs, I know how to get circle blue sign at the left side from the code however although I read and read I don´t see where I can get tick sign or checkmark overlay as it´s mentioned in the help from KDS. Should I configure some parameters? Is there in any option from one of the menu windows? Maybe any option from the “breakpoints perspective view”? or perhaps some commands that I have to write in “Debug configuration? Or any kind of configuration of debug?

I would be great grateful again for your help.

Have a nice day too,

Arturo Arteaga

De: kerryzhou

Enviado el: viernes, 17 de marzo de 2017 6:29

Para: Arturo Arteaga

Asunto: Re: - Re: "Device is secure. Erase to ensecure?".

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

Re: "Device is secure. Erase to ensecure?".

reply from Kerry Zhou <https://community.nxp.com/people/kerryzhou?et=watches.email.thread> in Kinetis Microcontrollers - View the full discussion <https://community.nxp.com/message/887918?commentID=887918&et=watches.email.thread#comment-887918>

Re: "Device is secure. Erase to ensecure?".

kerryzhou — Fri, 17 Mar 2017 07:57:58 GMT

Hi Arturo Arteaga,

Please enter the debug mode at first, then put the break point.

Don't put too much break points.If you still not OK, please give me some pictures from your side, I will help you to investigate it.

Have a great day,
Kerry

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Fri, 17 Mar 2017 08:26:10 GMT

Ok thanks, in some minutes I´ll send you.

De: kerryzhou

Enviado el: viernes, 17 de marzo de 2017 8:59

Para: Arturo Arteaga

Asunto: Re: - Re: "Device is secure. Erase to ensecure?".

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

Re: "Device is secure. Erase to ensecure?".

reply from Kerry Zhou <https://community.nxp.com/people/kerryzhou?et=watches.email.thread> in Kinetis Microcontrollers - View the full discussion <https://community.nxp.com/message/888026?commentID=888026&et=watches.email.thread#comment-888026>

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Fri, 17 Mar 2017 09:29:47 GMT

Hi kerry,

Hi Kerry again,

I haven’t managed to get tick signs again. After debugging I have put the breakpoint in the left side of one line the code, however I have only one blue circle. I send you two captured images. One it´s from the “Debug configuration” (Breakpoints GDB Multilink_Universal image), where you can find in the bottom from “Startup” tab something related on debugging step by step, and my dude it´s if I have to modify this default configuration. Another image is Debug perspective View (Debug_Breakpoints image), where I show you breakpoints view (red rectangle), the breakpoint by default in main file (blue rectangle), the breakpoint that I’ve chosen (orange rectangle), explanation from the help that it’s mentioned about checkmark overlay (pink rectangle), and in the bottom console explanation after debugging that you can read about breakpoints (green rectangle).

For more information for you, I have managed to debug with another board, with the FRDM-KL25Z board with OpenSDA and I haven’t any problem to see the breakpoints with tick signs in the left side of the code from the beginning. For this reason I think perhaps I need some kind of plugin because I actually I’m debugging with Multilink Universal with my actual board with MK20dx256vlh7 microcontroller.

I hope this serve you to find the solution. Thanks a lot for your help.

Regards,

Arturo Arteaga

De: kerryzhou

Enviado el: viernes, 17 de marzo de 2017 8:59

Para: Arturo Arteaga

Asunto: Re: - Re: "Device is secure. Erase to ensecure?".

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

Re: "Device is secure. Erase to ensecure?".

reply from Kerry Zhou <https://community.nxp.com/people/kerryzhou?et=watches.email.thread> in Kinetis Microcontrollers - View the full discussion <https://community.nxp.com/message/888026?commentID=888026&et=watches.email.thread#comment-888026>

Re: "Device is secure. Erase to ensecure?".

kerryzhou — Fri, 17 Mar 2017 09:53:46 GMT

Hi Arturo Arteaga,

What the KDS version you are using?

If your version is below KDS3.2, please download the newest version and try again:

Kinetis® Design Studio Integrated Development Environment (IDE)|NXP

If your anther board can use the breakpoints, please check you code, make sure the break point position can be executed.

Have a great day,
Kerry

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Fri, 17 Mar 2017 11:06:59 GMT

Hi Kerry,

The KDS version is 3.2.0. I have made sure that the program has executed break point position, because it´s only a toggle function executed on the led and I’ve seen how the led is toggled but without stopping in the breakpoint.

On the other hand, I’ve read that exists some commands for setting the breakpoints I’ve wrote these commands in the GDB window in Debug tab and Startup tab, however It doesn´t work on. I don´t know if some commands I should write before debugging and where or in which place I should write.

These are the linkers in KDS to this information about breakpoints.

file:///C:/Freescale/KDS_v3/Toolchain/share/doc/gcc-arm-none-eabi/html/gdb/Set-Breaks.html#Set-Breaks <file:///C:\Freescale\KDS_v3\Toolchain\share\doc\gcc-arm-none-eabi\html\gdb\Set-Breaks.html#Set-Breaks>

file:///C:/Freescale/KDS_v3/Toolchain/share/doc/gcc-arm-none-eabi/html/gdb/Maintenance-Commands.html#maint%20info%20breakpoints <file:///C:\Freescale\KDS_v3\Toolchain\share\doc\gcc-arm-none-eabi\html\gdb\Maintenance-Commands.html#maint%20info%20breakpoints>

Do you know something about these commands?? This is the source of the problem??

Thanks Kerry for your help.

Regards,

Arturo

De: kerryzhou

Enviado el: viernes, 17 de marzo de 2017 10:55

Para: Arturo Arteaga

Asunto: Re: - Re: "Device is secure. Erase to ensecure?".

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

Re: "Device is secure. Erase to ensecure?".

reply from Kerry Zhou <https://community.nxp.com/people/kerryzhou?et=watches.email.thread> in Kinetis Microcontrollers - View the full discussion <https://community.nxp.com/message/888032?commentID=888032&et=watches.email.thread#comment-888032>

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Fri, 17 Mar 2017 12:17:47 GMT

Hi again Kerry,

Do you know where I can find a more extended user guide than one that I send you attached in this mail? I think this is very short and It don’t explain anything about breakpoints and another issues like register view, debug…. or other issues. I have been finding information about another user guide.

I need a more complete user guide to work with this develop tool, because there are a lot of issues to manipulate.

Thank you very much at all.

Regards,

Arturo Arteaga

De: kerryzhou

Enviado el: viernes, 17 de marzo de 2017 10:55

Para: Arturo Arteaga

Asunto: Re: - Re: "Device is secure. Erase to ensecure?".

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

Re: "Device is secure. Erase to ensecure?".

reply from Kerry Zhou <https://community.nxp.com/people/kerryzhou?et=watches.email.thread> in Kinetis Microcontrollers - View the full discussion <https://community.nxp.com/message/888032?commentID=888032&et=watches.email.thread#comment-888032>

Re: "Device is secure. Erase to ensecure?".

kerryzhou — Mon, 20 Mar 2017 05:45:00 GMT

Hi Arturo Arteaga,

You post this picture before:

Please write these code

before

You add break point in for{;;}, are you sure your while(AS1_GetTxCompleteStatur(..)==false) is executed?

I just want to make sure your code is not blocking before your break points.

Have a great day,
Kerry

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Mon, 20 Mar 2017 09:24:30 GMT

Hi Kerry,

The application don’t let me put the “for{;;}” line before

https://community.nxp.com/servlet/JiveServlet/showImage/2-888387-179660/pastedImage_4.png

It tell me there’s a problem.

this “for{;;}” line is put me after by default.

Another lines although I can put before

https://community.nxp.com/servlet/JiveServlet/showImage/2-888387-179660/pastedImage_4.png

These lines aren’t executed when they are before:

https://community.nxp.com/servlet/JiveServlet/showImage/2-888387-179659/pastedImage_3.png

The application stops in a line inside the GPIO function, but I haven´t decided to put a breakpoint inside this function. I don’t know why.

Why can´t I executed these lines? Why can´t I stop in the breakpoints lines? Have I to install something more? Have I to repair something wrong? Are there similar errors by another users?

The project is very simple to start to work. Why don’t work?

Thanks for your help

Have a nice day too,

Arturo Arteaga

De: kerryzhou

Enviado el: lunes, 20 de marzo de 2017 6:46

Para: Arturo Arteaga

Asunto: Re: - Re: "Device is secure. Erase to ensecure?".

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

Re: "Device is secure. Erase to ensecure?".

reply from Kerry Zhou <https://community.nxp.com/people/kerryzhou?et=watches.email.thread> in Kinetis Microcontrollers - View the full discussion <https://community.nxp.com/message/888387?commentID=888387&et=watches.email.thread#comment-888387>

Re: "Device is secure. Erase to ensecure?".

kerryzhou — Mon, 20 Mar 2017 10:00:07 GMT

Hi Arturo Arteaga,

Send me your test project, I will help you to check it when I am free.

I think this method will be the fastest way to get you out.

Have a great day,
Kerry

Re: "Device is secure. Erase to ensecure?".

arturoarteaga — Mon, 20 Mar 2017 10:28:42 GMT

Ok thanks, I´ll send you my test Project attached.

In “mein file there are 2 for{;;} loops:

One before,

https://community.nxp.com/servlet/JiveServlet/showImage/2-888387-179660/pastedImage_4.png

that I don’t know if I have to put here.

And another one, after previous lines mentioned, that it´s develop by default.

I keep waiting for your check.

Thank you very much for your help again,

Arturo Arteaga

De: kerryzhou

Enviado el: lunes, 20 de marzo de 2017 11:01

Para: Arturo Arteaga

Asunto: Re: - Re: "Device is secure. Erase to ensecure?".

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

Re: "Device is secure. Erase to ensecure?".

reply from Kerry Zhou <https://community.nxp.com/people/kerryzhou?et=watches.email.thread> in Kinetis Microcontrollers - View the full discussion <https://community.nxp.com/message/888554?commentID=888554&et=watches.email.thread#comment-888554>