Analysis

What can a pre-certified RTOS prove on a zonal controller?

ST and WITTENSTEIN’s Stellar G3 demonstration puts software with different safety requirements on the same MCU. The more revealing test is how it behaves when those applications want the same resources.
Circuit board inside an automotive control unit (illustrative).

A task can stay within its own memory and still make a neighbouring control loop miss a deadline. If both use the same peripheral, or one generates enough interrupts to hold up the other, memory isolation has done its job while the system has failed a different test. The question for the Stellar G3 demonstration from STMicroelectronics and WITTENSTEIN is how the control workload behaves when the display and user interface get busy.

The two companies announced the demonstration for electronica, combining real-time control, visualisation and user interaction on a Stellar G3 microcontroller with SAFERTOS. WITTENSTEIN says the operating system is pre-certified to ISO 26262, while ST’s product information lists hardware virtualisation on the Stellar G3 family. Together they provide tools and evidence for separating applications, but a vehicle programme still has to show how its own software, I/O and timing budgets hold up in that arrangement.

If the display task issues a burst of updates while the control function has to respond to an input, how long can the peripheral stay occupied before it affects the deadline? The next thing to check is what the safety supervisor sees when that deadline is missed. An answer would need measurements on the integrated controller, with the loads and fault cases defined. The demonstration shows how the applications can be arranged; it does not publish results from those contention tests.

Sources: WITTENSTEIN and ST demonstration announcement; ST Stellar SR6G3C4 product information; image source (CC BY-SA 3.0)

Continue reading