{"id":3069,"date":"2026-01-30T00:00:00","date_gmt":"2026-01-29T23:00:00","guid":{"rendered":"https:\/\/kunden.weissblaumedia.de\/microconsult\/2017\/03\/28\/ip-multicore-mikrocontroller-2\/"},"modified":"2026-02-09T10:26:46","modified_gmt":"2026-02-09T09:26:46","slug":"ip-multicore-microcontroller-2","status":"publish","type":"post","link":"https:\/\/www.microconsult.de\/en\/ip-multicore-mikrocontroller-2\/","title":{"rendered":"Multicore Microcontrollers Part 2: Which safety and security requirements are important when choosing an MCU?"},"content":{"rendered":"

The first part of the article series on choosing the right multicore processor dealt with the... <\/strong>Determining the requirements regarding computing power and their <\/strong>Evaluation for the project. As a second step, we will now consider the <\/strong>Requirements regarding functional safety and data security.<\/strong><\/p>\n

<\/p>\n

When safety and security requirements come into play in an application, a comprehensive requirements analysis for these aspects is crucial. For example, to achieve ASIL level C, it is required that the results of the main core program be compared with the results of the program processed at a later time in the lockstep\/checker core.<\/p>\n

This is necessary to detect temporary errors in the Safety Core's result calculation. In response to detected errors, the system must be able to generate appropriate error responses.<\/p>\n

In specific cases, an error response without software intervention must be able to bring the system to a safe state. This requires a safety hardware module (Safety Management Unit) that automatically generates a user-selected or predefined error response for each detected error, such as an exception\/trap routine, reset, CPU idle state, or an external error signal.<\/p>\n

\"\"<\/p>\n

Figure 7: Work steps in project development for safety-relevant systems<\/em><\/p>\n

To determine the requirements that must be considered in safety-relevant applications, an analysis of the possible hazards and an assessment of the risks must first be carried out.<\/p>\n

The required safety level then determines, for example, which safety hardware must be included in a microcontroller so that the system ensures the required level of safety.<\/p>\n

\"\"<\/p>\n

Figure 8: Example of safety requirements for ASIL-B and ASIL-C<\/em><\/p>\n

A similar approach applies to the security issue:<\/p>\n

\"\"<\/p>\n

Figure 9: Security \u2013 Security systems for controllers<\/em><\/p>\n

The security goals and attack vectors that could make a system a target must be identified and investigated. Furthermore, it should be assessed whether these potential attacks have an impact on system security and integrity, or whether user privacy needs to be protected by additional measures.<\/p>\n

Examples of this include the following aspects:<\/p>\n