- 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
- :
- 1949764_en-US
1949764_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
1949764_en-US
1949764_en-US
Hi,
We are developing a solution in which we need to enable CSEc strict mode.
When we do, by using the boot flavor '00' in the command CMD_BOOT_DEFINE, everything works fine.
However, after rebooting, if we update our boot loader and we try to define a new BOOT_SIZE, the command fails with code 0x800.
Even if we try to update with the same BOOT_SIZE, the command fails, no matter the Boot Flavor we use in the command. If we ignore the error and reboot, the part is bricked (even using the same BOOT_SIZE and updating the MAC appropriately).
The same process works without issue if the Sequential Boot Method is selected. The documentation states that Strict mode is OTP, but that BOOT_SIZE can be changed.
How can we update BOOT_SIZE in Strict mode?
Thank you very much!
Thank you very much for clarifying this.
Best regards,
Carlos
Hi @sinixtek
the result is that the SIZE cannot be updated. The sentence in the manual is confusing, I asked to update it.
Thanks for pointing this out.
Regards,
Lukas
Hi @lukaszadrapa ,
Thank you very much for your support, let's see what they say.
Best regards,
Carlos
Hi @sinixtek
That's a good question, I have never tried this use-case. It looks like you are the first one who is trying to change the BOOT_SIZE in strict boot mode. Please give me more time to clarify this. I will probably need to discuss this with another team, so it may take some time. At a glance, my guess is that it's not supported even if the documentation says something different. But let's wait for the result.
Regards,
Lukas