ST's automotive microcontrollers run from the SPC5 families to the new Stellar platform. The two use different programming interfaces, and the newer the device, the more regions, such as UTEST, DCF and HSM, need handling on the line.
STMicroelectronics’ SPC5 is a family of 32-bit automotive microcontrollers in three generations, SPC56, SPC57 and SPC58; SPC58 includes the Chorus, Eiger and Bernina lines. Stellar is ST’s new automotive platform: Stellar SR6 uses Arm® Cortex®-R52/R52+ cores for domain and zone controllers, with up to 20 MB of phase-change memory (PCM) on the P and G series; Stellar SR5 E1 uses two Cortex®-M7 cores for electrification applications such as on-board chargers, DC/DC converters and traction inverters.
SPC5 and Stellar in the device list
As of November 2026 the device list has 90 parts:
| Family | Parts | FlashRunner 2.0 / 2.0 HS / 2.0 NXG | WriteNow! |
|---|---|---|---|
| SPC56 (Bolero, Pictus, Monaco, Andorra, Leopard and others) | 39 | 39, JTAG | 21, JTAG |
| SPC57 (K2, Lavaredo, Sphaero, Velvety) | 8 | 8, JTAG | 3, JTAG |
| SPC58 (Chorus, Eiger, Bernina) | 33 | 33, JTAG | 20, JTAG |
| Stellar (SR5E1, SR6G7, SR6P3) | 10 | 10, SWD | — |
Of the 90 FlashRunner parts, 84 are available now, 4 have the algorithm delivered within 10 days of order and 2 within 20 days. In the device list you can search for SPC58 or for SR6, or open family pages such as SPC58 Chorus4M and SR5E1.
Memory regions to program
The regions in FlashRunner’s data grow with each generation:
- SPC56: code flash (CODEFLASH, up to 4 MB), data flash and the SHADOW area (16 KB or 32 KB), plus OTP on some parts.
- SPC57: code flash, data flash and UTEST.
- SPC58: code flash (up to 10 MB), data flash and UTEST; every line except Chorus 1M also has separate HSM code and HSM data regions.
- Stellar: FLASH (19.5 MB on SR6G7), data flash, HSM code and data, UTEST and DCF, with BCS, HSM_UTEST and further regions on SR6.
Where production goes wrong
UTEST and DCF records. ST’s technical note TN1356 explains that SPC58 keeps device parameters as DCF records in the UTEST area, an OTP flash that the device reads while reset is still asserted. User DCF records can make flash blocks OTP, protect flash blocks with passwords and configure self-tests, and ST notes that settings enabled in UTEST cannot be cancelled by software afterwards. DCF content should therefore be validated on samples before it goes into the production image, and written once.
HSM regions. On SPC58 and Stellar the HSM code and data are separate regions in the data and can be programmed in the same project as the main flash. Confirm the HSM firmware version and the programming order beforehand.
SHADOW area. The SPC56 SHADOW area is listed as a region of its own; check its content against the device reference manual before writing it.
Line integration
SPC5 uses JTAG and Stellar uses SWD, so the fixture interface has to be designed for each. FlashRunner 2.0 (4 to 16 channels, extendable to 32), 2.0 HS (up to 32 channels) and 2.0 NXG (1 to 4 channels) cover both interfaces on one platform; WriteNow! (1 to 8 sites) currently covers SPC5. All of them connect to ATE or ICT through a control interface or LAN and report a result per channel.
Questions and answers
Can Stellar be programmed with WriteNow!? At present the Stellar parts in the device list are listed for FlashRunner 2.0, 2.0 HS and 2.0 NXG only.
Are SPC56 and NXP MPC56 the same chips? The device list files them as parts of different vendors (NXP’s MPC56 and MPC57 families have their own entries), so look up the exact part number on your board.
Can a wrong UTEST entry be corrected? UTEST is OTP: once written it cannot be erased, and new records can only go into unused locations. Treat writing UTEST as a one-time operation.