From: NXP Technical Support <tech.support@nxp.com>
Sent: 09 April 2019 21:36
To: Chidanand Musari <chidanand@slntech.com>
Subject: Your case:00206744 is closed, your feedback is appreciated.

[Inline image name : ~WRD000.jpg]

Dear Chidanand Musari, 

Your case 00206744 has been closed, you can reopen by replying to this email.

Subject of the case: We frequently coming with the Secured of MK61FX512VMJ1 this controller can u suggest anything on this sir 

Please help us to improve our service by answering our 1 min. survey.

Your feedback is highly appreciated.

https://nxpcommunity.force.com/community/CommunityCaseSurvey?caseId=5002p000024gnF5

Best Regards,

Technical Support

NXP Semiconductor

----------------------------------------------------------------------------------------------

Your inquiry was already asked and answered …. maybe… !

Please visit the NXP Community at www.nxp.com/community

Get faster support through research in thousands of detailed 

discussions or ask NXP experts and other users. NXP 

Technical Support is actively monitoring and supporting the 

community spaces.

Case Thread Id: 

----------------------------------------------------------------------------------------------

The information contained in this message is confidential and may be legally privileged.This message is 

intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any 

use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended 

recipient, please contact the sender by return e-mail and destroy all copies of the original message.

[Inline image name : ~WRD000.jpg]

[Inline image name : ~WRD000.jpg]

[Inline image name : ~WRD000.jpg]

ref:_00D20NBgb._5002p24gnF5:ref
--------------- Original Message ---------------
From: Chidanand Musari [chidanand@slntech.com]
Sent: 4/26/2019 4:44 PM
To: tech.support@nxp.com
Subject: RE: Your case:00206744 is closed, your feedback is appreciated.

Dear Sir,

We are satisfied with response , We needed the exact solution for that ,

Thanks and Regards:

Chidanand N M

9591519820

Chidanand@slntech.com

From: NXP Tech Support <tech.support@nxp.com>
Sent: 30 April 2019 02:28
To: Chidanand Musari <chidanand@slntech.com>
Subject: RE: Your case:00206744 is closed, your feedback is appreciated.

I'm very sorry for the late replay.

The locked of the MCU could has many causes. I mention you one of this in the previous email.

Could you let me know the process your using to flash the MCU and which debugger are you using? This could help to understand better your problem

Again, very sorry for the late replay.

Best Regards,

Alexis Andalon 

--------------- Original Message ---------------
From: Chidanand Musari [chidanand@slntech.com]
Sent: 4/30/2019 6:49 AM
To: tech.support@nxp.com
Subject: RE: Your case:00206744 is closed, your feedback is appreciated.

Dear Sir,

We are regularly using the NXP  Controller -- MK61FN1M0VMJ12 ,

Since we are  faced problem that the NXP Controller goes to  secure  for regularly once its secured  , we are not able to unsecure the device since  we have replace the Controller again have to program,

This due to the reset  section I have attached the my reset section used, While without reset section it got programming fine , Once I mount the reset section it may have the possibility to go the Secure Mode Sir,

For programming we are using universal multilink J-TAG tool with the code warrior platform,

Kindly advise on this sir,

[Inline image name : image001.png] 

 

[Inline image name : image002.png]

Thanks and Regards:

Chidanand N M

9591519820

From: NXP Tech Support <tech.support@nxp.com>
Sent: 30 April 2019 21:24
To: Chidanand Musari <chidanand@slntech.com>
Subject: RE: Your case:00206744 is closed, your feedback is appreciated.

Hi Chidanand,

With the schematic you send I don't understand really well how is interconnected to your MCU. Could you send all the path of the reset signal to the MCU?

I suspect that the MultiLink can't reset the MCU, do you have any way to check the voltage in the RST pin in while the debugger is trying to reset the MCU?

Let me know your findings.

Best Regards,

Alexis Andalon

--------------- Original Message ---------------
From: Chidanand Musari [chidanand@slntech.com]
Sent: 5/1/2019 10:45 AM
To: tech.support@nxp.com
Subject: RE: Your case:00206744 is closed, your feedback is appreciated.

Dear Sir,

1.The below Mentoned Circuitary is the J-TAG Interface in which RESET_B  is directly connects to the Microcontroller Reset Pin ,

JTAG_EZP_CS_N is connected to the EZP_CS pin of the controller.

 

[Inline image name : image002.png]

 

2.The Manual Reset of Microcontroller is done by using the below mentioned circuitry ,The RESET_B  is directly connecs to the Microcontroller Reset Pin,

[Inline image name : image005.png]

These are the two ways we are using to reset the controller ,

Thanks and Regards:

Chidanand N M

9591519820

From: NXP Tech Support <tech.support@nxp.com>
Sent: 04 May 2019 03:23
To: Chidanand Musari <chidanand@slntech.com>
Subject: RE: Your case:00206744 is closed, your feedback is appreciated.

Dear Chitanda,

A few more questions about this:

Could you check if in any part of your application you're writing the FSEC register?

Also , could you check if in your application the NMI is change his default state?

Or could you try using the examples of the SDK and write it many time to know if with this examples also lock the MCU?

Let me know your findings.

Best Regards,

Alexis Andalon

--------------- Original Message ---------------
From: Chidanand Musari [chidanand@slntech.com]
Sent: 5/7/2019 1:01 PM
To: tech.support@nxp.com
Subject: RE: Your case:00206744 is closed, your feedback is appreciated.

Dear Sir,

Could you check if in any part of your application you're writing the FSEC register?
Replay: We are not  writing to the FSEC register

Also , could you check if in your application the NMI is change his default state?
Replay: NMI state we kept as default

        3. Or could you try using the examples of the SDK and write it many time to know if with this examples also lock the MCU?

Replay: Same Error

Thanks and Regards:

Chidanand N M

+91 9591519820


Attachments, pictures, and links in this message have been blocked because the sender isn't in your Safe Senders list. I trust content from tech.support@nxp.com. | Show blocked content
NXP Tech Support <tech.support@nxp.com>
Tue 5/7/2019 8:18 PM
Hi Chidanand,

Please check the image attached, this is a errata from the MCU mask.
Looks like is an error in the MCU properly, there's also a workaround attach to the image.

Please let me know if this helps you.

Best Regards,
Alexis Andalon

Attachments, pictures, and links in this message have been blocked because the sender isn't in your Safe Senders list. I trust content from chidanand@slntech.com. | Show blocked content
Chidanand Musari
Wed 5/8/2019 10:42 AM
Dear Sir,

When Controller is secured we are  not able to excess the controller through J-TAG (Universal Multilink),

Thanks and Regards:

Chidanand N M

+91 9591519820