- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- Wireless Connectivity
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- MCUXpresso Training Hub
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
-
- Home
- :
- General Purpose Microcontrollers
- :
- Kinetis Microcontrollers
- :
- Kinetis controller in secure state
Kinetis controller in secure state
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm working with the Kinetis K60 tower system, IAR EWB and built-in OSJTAG debugger. During a 'download and debug' I inadvertently put the controller in the 'secure' state. I believe I had the wrong configuration file selected. I know have all of the original working setting restored and am no longer able to interface with the controller. How do I get the controller out of the secure state?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Do you know exactly which settings were configured?
The Kinetis has a protection mode which blocks a mass erase, which is unrecoverable. The goal of this protection mode is to ensure that it is not possible to program any further software to a protected device - this avoids the possibility of programming a software containing a trojian (or similar) into a device that has shipped (in this state) as part of a product.
This is quite an extreme protection mechanism which may be of interest in a few applications but developers have to be very careful not to accidently set it, otherwise it will be necessary to replace the device to be able to continue with development. When developing small pieces of new code it is useful to work from SRAM (since the K60 has enough for quite interesting things). When programming to FLASH one has to be careful what is at the addresses 0x400..0x40f - Rowely Crossworks (for example) doesn't program this area by default and so protects against inadvertently setting a configuration that may be critical.
Regards
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One solution that worked for me:
The tools J-Link/J-Trace have a special 'commander mode' command 'unlock kinetis' that does the job!
Earl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Earl,
As per the IAR site (link below) It works only if the device is configured with "Flash Security enabled", if "Mass Erase is disabled" device can not be recovered from locked state.
http://supp.iar.com/Support/?note=77989
If there is any other alternative, please suggest.
d2v0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Do you know exactly which settings were configured?
The Kinetis has a protection mode which blocks a mass erase, which is unrecoverable. The goal of this protection mode is to ensure that it is not possible to program any further software to a protected device - this avoids the possibility of programming a software containing a trojian (or similar) into a device that has shipped (in this state) as part of a product.
This is quite an extreme protection mechanism which may be of interest in a few applications but developers have to be very careful not to accidently set it, otherwise it will be necessary to replace the device to be able to continue with development. When developing small pieces of new code it is useful to work from SRAM (since the K60 has enough for quite interesting things). When programming to FLASH one has to be careful what is at the addresses 0x400..0x40f - Rowely Crossworks (for example) doesn't program this area by default and so protects against inadvertently setting a configuration that may be critical.
Regards
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you Mark,
It looks like I ended up writing to the register that blocks mass erase. It just so happens that the data written to that location was just right to set it in that mode. I'm currently working toward replacing the controller on the TWR-K60N512 dev. board I'm working with. Thank you for the tip on using RAM during the development cycle. This is my first foray into using Freescale controllers, ARM and highly integrated 32-bit devices. It's been quite the learning curve. Thank you
