S32K is NXP's general-purpose automotive MCU platform. S32K1 and S32K3 are both programmed over SWD, but what needs watching in production differs between the two generations: the flash security byte and FlexNVM partitioning on S32K1, the UTEST sector and the HSE life cycle on S32K3.

NXP S32K is a platform of 32-bit Arm® Cortex®-M microcontrollers for general-purpose automotive applications. S32K1 uses a Cortex®-M0+ core (S32K11x) or a Cortex®-M4F core (S32K14x); S32K3 uses Cortex®-M7 cores and integrates the HSE-B hardware security engine for secure boot and key storage.

S32K in the device list

As of November 2026 the device list has 368 S32K-related entries, all programmed over SWD:

  • 33 microcontrollers: S32K116, S32K118, S32K142, S32K144, S32K146 and S32K148 in the S32K1xx family; 20 S32K3 parts (S32K310 to S32K396) in the S32K3xx family, together with five MWCT2xxx parts that SMH files there; S32M274 and S32M276 in the S32 S32K3xx family.
  • 335 combinations of S32K144 with an external serial flash: the external SPI flash on the board is programmed through the S32K144 (part numbers such as S32K144_W25Q128JV). This is indirect programming through an MCU, explained in Direct programming versus indirect programming through an MPU/MCU.
Programmer 33 microcontrollers 335 external-flash combinations
FlashRunner 2.0 / 2.0 HS / 2.0 NXG 33, all available now 335 (3 available now, the rest with the algorithm delivered within 10 days of order)
WriteNow! 30 (not S32K341, S32M274 or S32M276) —

Memory regions to program

  • S32K1: FLASH (program flash, 128 KB to 1.5 MB), the FlexNVM data area (32 KB to 512 KB) and FlexRAM (2 KB or 4 KB).
  • S32K3: FLASH (768 KB to about 8 MB), DATAFLASH (64 KB or 128 KB), UTEST and OTP.

Where production goes wrong

S32K1: the flash security byte. The S32K1 flash configuration field is at 0x400–0x40F, and the FSEC byte at 0x400 decides whether the device is secured. NXP’s application note AN12130 warns that a device secured with both mass erase and backdoor key access disabled can no longer be programmed, and that after a mass erase the part comes back secured at the next reset unless the unsecured value is written again. Make sure the content of 0x400–0x40F in your image is set on purpose.

S32K1: FlexNVM partitioning. EEPROM emulation needs the partition command. It erases the whole FlexNVM, works over SWD/JTAG only while the device is unsecured, and repartitioning loses the stored data. Have the script read the partition state first and partition only when needed.

S32K3: UTEST and life cycle. According to NXP, once the UTEST sector’s seal value is written you can only append to it, not erase it; installation of the HSE firmware is triggered by a flag in UTEST; and the life cycle can only move forward (CUST_DEL → OEM_PROD → IN_FIELD), never back. Decide before production starts which step installs the HSE and advances the life cycle, and rehearse it on samples.

Line integration

FlashRunner 2.0 (4 to 16 channels, extendable to 32), 2.0 HS (up to 32 channels), 2.0 NXG (1 to 4 channels) and WriteNow! (1 to 8 sites) all fit in the fixture, connect to ATE or ICT over LAN, USB or a dedicated control interface, and report a result per channel. SWD needs only a handful of signals (clock, data, reset and power), which suits panels programmed on many channels in parallel.

Questions and answers

What are the S32K144 + external flash entries? They mean FlashRunner can program an external serial flash connected to the S32K144 on the board, without a separate programming connection for the flash.

Can the S32K3 HSE firmware be written in the same programming step? HSE installation follows a procedure defined by NXP, involving the UTEST flag and the image location. Tell us your project’s security scheme and we will confirm the programming steps.

Why are S32M274 and S32M276 in the S32 S32K3xx family? That is how SMH’s data files them. All three FlashRunner models list them as available now.

Can one programmer serve a line building both S32K1 and S32K3 boards? Yes. Both generations use SWD; set up a separate project for each product on the same programmer.