- 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
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- 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
- S32Z/E
-
- 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
- Generative AI & LLMs
-
- 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
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2365786_en-US
2365786_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2365786_en-US
2365786_en-US
Hello NXP Team,
Our team is currently developing a controller using the S32K312 MCU. For the production phase, we are implementing Secure Debug and Configuration Lock features.
We have observed that when Cybersecurity is active, executing the S32_SDAP_WRITE.cmm script (provided by NXP) or entering the Secure Debug password allows temporary debugger access.
We are requesting detailed information regarding the specific changes in memory addresses and register values when the device transitions from a "Cybersecurity Enabled" state to a "Temporary Secure Debug Access" state.
Specifically, we would like to know which registers or memory-mapped locations reflect this transition. For example:
Cybersecurity Active State: e.g., Address 0x40000000 = 1 / HSM Secure Debug Register = 1
Temporary Debug Enabled State: e.g., Address 0x40000000 = 0 / HSM Secure Debug Register = 0
Could you provide a list of the relevant registers (such as those in the HSE (Hardware Security Engine) or Register Status) that indicate whether the Secure Debug session is currently authenticated and active?
Best regards,
Hi @jeongwoo
Section 82.5.7 of the S32K3xx Reference Manual (Rev. 12) describes the debug authentication sequence in detail.
Additionally, there is a dedicated application note that explains the procedure to follow in order to unlock the device. This document can be downloaded from the S32K3 product webpage under Documentation → Secure Files → S32K3xx Secure Debug Enablement Guide.
BR, VaneB