Hello NXP Team,
We are using a custom i.MX95-based board (not the FRDM-i.MX95 EVK) and have connected an Ara240 M.2 module through the PCIe M-Key interface.
After reviewing the Ara240 Runtime SDK documentation, we understand the normal runtime flow where the Ara240 device is enumerated over PCIe and initialized by the Runtime SDK during system boot.
We would like to understand the requirements related to first-time module provisioning/programming for manufacturing and production support.
Could you please clarify the following:
Any guidance or documentation related to first-time provisioning, firmware recovery, or production deployment would be greatly appreciated.
The Ara240 M.2 module is normally shipped pre‑programmed, with the Runtime SDK handling initialization at boot, but if the onboard flash is blank or corrupted, recovery requires re‑flashing the firmware using the SDK tools and provisioning steps outlined in NXP’s manufacturing guide. Typically only base firmware is programmed once during production, while runtime components load automatically at each boot. For custom i.MX95 boards, the same provisioning flow applies as with the FRDM‑i.MX95, though you may need to adapt board‑specific PCIe and power sequencing. Official provisioning and recovery documentation from NXP is the recommended reference for manufacturing support.