- 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
- :
- 2417527_en-US
2417527_en-US
2417527_en-US
2417527_en-US
Hi NXP Team,
We are planning to implement SWUpdate-based OTA with A/B root filesystem and rollback on the i.MX 95 platform using Yocto Linux.
Could you please confirm:
Is SWUpdate officially supported/recommended for i.MX 95?
What is the recommended A/B partition and U-Boot rollback implementation?
What are the recommended steps for secure/signed SWUpdate packages and Secure Boot integration?
Please share the latest application notes, documentation, Yocto layers/recipes, reference implementation, and example configuration for i.MX 95 SWUpdate.
We would also appreciate any step-by-step guide recommended by NXP for a production implementation.
Thanks.
Hello,
Take a look on the i.MX 95 SWUpdate enablement through AN13872 and the meta-swupdate-imx Yocto layer.
You can use boot_a/rootfs_a and boot_b/rootfs_b, update the inactive slot, and let U-Boot manage bootslot, bootcount, bootlimit, and a “confirmed-good” flag using redundant persistent environment storage. See AN13872.
Recommended references are AN13872, i.MX Yocto User’s Guide UG10164, meta-imx, meta-swupdate-imx, swupdate-scripts, and the NXP Security Reference Design layer.