- 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
- :
- 2420534_en-US
2420534_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2420534_en-US
2420534_en-US
On a 32K396, HSE FW 0.2.50.0 FULL_MEM is used, and the current lifetime is CUST_DEL.
Testing Process: Initially, the system ran normally. Then, the address 0x00453FF0 within the authentication range was changed from 0xFF to 0xFE, while keeping the AppBL Header, authentication tag, and IVT unchanged. The IVT bootCfgWord was set to 0x00000009. After powering off and on again, a J-Link Attach connection was used, without downloading the image, and RAM/ECC initialization during connection was disabled using an empty SetupTarget. At this point, the PC stopped at 0x2040012E. The instructions from 0x2040012C to 0x2040012E are WFI and branches that jump back to WFI, consistent with the JTAG Recovery wait loop. Currently, no user Secure Recovery application is configured.
Question: Please confirm the complete handling process and reliable criteria for this version after BSB authentication failure: Why is GPR3 bit5 still 0 even after entering the JTAG Recovery waiting loop? Is it related to the fact that this bit only indicates "SBAF boot application kernel into Recovery" and the current recovery path is triggered by HSE FW? And which status bit or error message should be used to clearly confirm that the failure is due to AppBL authentication failure?