Method and device for processing data associated with a software component for a product

Abstract

The invention relates to a method, for example a computer-implemented method, for processing data associated with a software component for a product, comprising: generating redundant software code for the software component in an intermediate representation, and, optionally, transforming the redundant software code into, for example redundant, machine-specific software code.

Description

[0001] Description

[0002] title

[0003] Method and apparatus for processing data associated with a software component for a product

[0004] State of the art

[0005] The disclosure relates to a method for processing data associated with a software component for a product.

[0006] The disclosure also relates to a device for processing data associated with a software component for a product.

[0007] Disclosure of the invention

[0008] Some examples refer to a method, such as a computer-implemented method, for processing data associated with a software component for a product, comprising: generating redundant software code for the software component in an intermediate representation, and, optionally, transforming the redundant software code into, for example, redundant, machine-specific software code. In some examples, this allows for increased safety, for example, against hardware errors, such as during the execution of the machine-specific software code.

[0009] In some examples, the software component is characterized by or is at least one of the following elements: a) source code, for example in a high-level language such as C or C++, or b) bytecode, for example virtual bytecode, or c) for example platform-independent representation, for example intermediate representation, for example according to the LLVM Project, e.g. www.llvm.org, or d) machine-specific code, for example machine code.

[0010] In some examples, the generation of redundant software code includes at least one of the following elements: a) generating the redundant software code using at least one frontend of a development environment for the software component, for example, using at least one compiler of the at least one frontend, or b) generating at least one redundant function for the software component, for example, using at least one frontend of a development environment for the software component.

[0011] In some examples, the transformation involves: transforming the redundant software code using at least one backend of a development environment for the software component.

[0012] In some examples, the method has at least one of the following aspects: a) providing the, for example, redundant, machine-specific software code for at least one component of a chiplet system, for example, storing the, for example, redundant, machine-specific software code for the at least one component of a chiplet system; b) executing the, for example, redundant, machine-specific software code by at least one component of a chiplet system; or c) verifying the execution of the, for example, redundant, machine-specific software code by at least one component of a chiplet system; or f) providing a monitoring function for verifying the execution of the, for example, redundant, machine-specific software code by at least one component of a chiplet system.of the chiplet system.

[0013] Some examples relate to a device for carrying out the method according to the disclosure. Some examples relate to a computer-readable storage medium comprising instructions which, when executed by a computer, cause it to carry out the method according to the disclosure.

[0014] Some examples relate to a computer program, comprising instructions that, when executed by a computer, cause it to perform the procedure according to the disclosure.

[0015] Some examples refer to a data carrier signal that characterizes and / or transmits the computer program according to the disclosure.

[0016] Some examples refer to a procedure for a chiplet system, comprising: providing, for example, loading, a, for example, redundant, machine-specific software code for at least one component of the chiplet system, executing the, for example, redundant, machine-specific software code by the at least one component of the chiplet system, and, optionally, verifying the execution of the, for example, redundant, machine-specific software code.

[0017] In some examples, the procedure involves: providing a monitoring function for checking the execution of the, for example, redundant, machine-specific software code, for example by at least one component of the chiplet system, and, optionally, checking the execution of the, for example, redundant, machine-specific software code using the monitoring function.

[0018] In some examples, the checking involves: comparing the results of the execution of, for example, redundant, machine-specific software code, and, optionally, initiating an error response based on the comparison, where, for example, initiating the error response involves resetting at least one component of the chiplet system.

[0019] Some examples relate to a device for a chiplet system for carrying out the method according to the disclosure. Some examples relate to a product comprising at least one device according to the disclosure.

[0020] Some examples refer to a computer-readable storage medium for a chiplet system, comprising instructions which, when executed by a computer, cause it to perform the procedure according to the disclosure.

[0021] Some examples relate to a computer program for a chiplet system, comprising instructions that, when the computer program is executed by a computer, cause it to perform the procedure according to the disclosure.

[0022] Some examples refer to a data carrier signal for a chiplet system that characterizes and / or transmits the computer program according to the disclosure.

[0023] Some examples relate to a use of the method according to the disclosure and / or the device according to the disclosure and / or the computer-readable storage medium according to the disclosure and / or the computer program according to the disclosure and / or the data carrier signal according to the disclosure and / or the product according to the disclosure for at least one of the following elements: a) enabling redundancy in the execution of software code, or b) integrating at least one aspect of the coded processing into a development environment, for example, a modular one, such as a compiler infrastructure, or c) enabling, for example, comparatively large diagnostic coverage, for example, for single and / or multiple faults, such as hardware faults, or d) enabling diverse implementation, for example, for fault-tolerant systems, for example, for driver assistance, for example, according to SAE L3+.or e) providing software components for chiplet systems.

[0024] Further features, applications, and advantages will become apparent from the following description of aspects and examples illustrated in the figures of the drawing. All described or illustrated features, individually or in any combination, constitute the subject matter of the disclosure, irrespective of their compilation in the claims or their cross-reference, and irrespective of their formulation or representation in the description or in the drawing.

[0025] The drawing shows:

[0026] Fig. 1 schematically shows a simplified flowchart,

[0027] Fig. 2 schematically shows a simplified block diagram,

[0028] Fig. 3 schematically shows a simplified block diagram,

[0029] Fig. 4 schematically shows a simplified flowchart,

[0030] Fig. 5A schematically shows a simplified block diagram,

[0031] Fig. 5B schematically shows a simplified block diagram,

[0032] Fig. 6 schematically shows a simplified block diagram,

[0033] Fig. 7 schematically shows a simplified block diagram,

[0034] Fig. 8 schematically shows a simplified flowchart,

[0035] Fig. 9 schematically shows a simplified flowchart,

[0036] Fig. 10 schematically shows aspects of uses.

[0037] Some examples, see Fig. 1, 2, refer to a method, for example a computer-implemented method, for processing data associated with a software component SW-KOMP for a product 1, 10, comprising: generating 100 redundant software code SC, SC for the software component SW-KOMP in an intermediate representation ZR, for example, and, optionally, transforming 102 the redundant software code SC, SC into, for example, redundant, machine-specific software code MS-SC, MS-SC, see also the dashed block arrow A1 according to Fig. 2. In some examples, this makes it possible to increase safety, for example against hardware errors, for example during the execution of the machine-specific software code MS-SC, MS-SC.

[0038] In some examples, Fig. 2, the software component SW-KOMP is characterized by or is at least one of the following elements: a) source code SRC, for example in a high-level language such as C or C++, or b) bytecode BC, for example virtual bytecode, or c) for example platform-independent representation PUR, for example intermediate representation, for example according to the LLVM Project, see www.llvm.org, or d) machine-specific code MC, for example machine code. In some examples, Fig. 2, the software component SW-KOMP is intended, for example, for a chiplet system CS.

[0039] In some examples, Fig. 1, 3, the generation 100 of the redundant software code includes at least one of the following elements: a) Generation 100a of the redundant software code SC, SC using at least one frontend FE-1 of a development environment EU for the software component SW-KOMP, for example using at least one compiler of the at least one frontend FE-1, or b) Generation 100b of at least one redundant function F, F' for the software component SW-KOMP, for example using at least one frontend FE-1 of a development environment EU for the software component SW-KOMP.

[0040] In some examples, Fig. 1, 3, the transformation 102 shows: Transformation 102a of the redundant software code SC, SC using at least one backend BE-1 of a development environment EU for the software component SW-KOMP.

[0041] In some examples, Fig. 3, the development environment EU has, for example, one or more frontends FE-1, ... that transform source code from various programming languages ​​into at least one intermediate representation ZR. For this purpose, the one or more frontends FE-1, ... can include corresponding compilers (not shown). In some examples, Fig. 3, the development environment EU has, for example, one or more backends BE-1, ... that transform the intermediate representation ZR into machine-specific software code.

[0042] In some examples, Fig. 3, the development environment EU can be designed according to or based on the LLVM Project.

[0043] In some examples, Fig. 4, the method has at least one of the following aspects: a) Providing 110 of the, for example redundant, machine-specific software code SC, SC for at least one component CS-K (Fig. 2) of a chiplet system CS, for example storing 110a of the, for example redundant, machine-specific software code SC, SC for the at least one component CS-K of a chiplet system CS (e.g. such that the machine-specific software codes SC, SC are loadable and / or executable by the at least one component CS-K of the chiplet system CS), e.g. also the dashed block arrow A2 according to Fig. 2, b) Executing 112 of the, for example redundant, machine-specific software code SC, SC by at least one component CS-K of a or of the chiplet system CS, or c) Checking 114 of a (or(a) execution 112 of the, for example redundant, machine-specific software code SC, SC, for example by at least one component of a chiplet system, or (b) providing 116 a monitoring function MF, for example monitoring function, for checking 114 of the execution of the, for example redundant, machine-specific software code, for example by at least one component of a chiplet system.

[0044] In some examples, Fig. 2, the chiplet system CS e.g. has several components CS-K, CS-K', ..., e.g. several chiplets, and is designed for applications in the automotive sector, for example for a control unit or a vehicle computer 1 , for example for a motor vehicle 10.

[0045] Fig. 5A schematically shows a simplified block diagram with aspects of a development environment EU' for the software component SW-KOMP, where aspects can be used according to the examples. For example, the development environment EU according to Fig. 3 can have a configuration EU' according to Fig. 5A.

[0046] Element E1 according to Fig. 5A symbolizes a frontend, for example, an LLVM frontend, which in some examples may be part of the development environment EU for software components, e.g., including an LLVM compiler system. Element E2 symbolizes further optional frontends, for example, of type AST or Clang, etc. Element E3a symbolizes an intermediate representation (see also element ZR according to Fig. 2) (e.g., a low-level intermediate language), for example, an intermediate representation IR, such as an LLVM IR, which is associated with frontend E1. Element E3b symbolizes another optional intermediate representation, such as an intermediate representation IR, such as an LLVM IR, which is associated with frontend(s) E2. Elements E4 and E5 each symbolize aspects of corresponding backends.

[0047] Element E6 symbolizes input data for the frontend E1, e.g., in the form of code, represented, for example, in a programming language for computers, e.g., C or C++. Similarly, element E7 symbolizes input data for at least one further frontend E2.

[0048] Element E8 symbolizes a program code, for example machine code, as can be formed in some examples by the backend E4, e.g. based at least on the input data E6.

[0049] Element E9 symbolizes a program code, for example machine code, as can be formed in some examples by the optional backend(s) E5, e.g. based at least on the input data E7.

[0050] In some examples, Fig. 5A, the development environment EU' is configured to generate the redundant software code SC, SC (Fig. 2) for the software component SW-KOMP in the intermediate representation ZR, for example (for example using at least one frontend E1 , E2), and, optionally, to transform the redundant software code SC, SC into, for example, redundant, machine-specific software code MS-SC, MS-SC (for example using at least one backend E3, E4).

[0051] Figure 5B schematically shows a verification device MFE for performing a check, for example, in accordance with block 114 of Figure 4. In some examples, the verification device MFE checks the execution of, for example, the redundant machine-specific software code MS-SC, MS-SC by a computing device E9a (Figure 5B), which is, for example, a component CS-K of the chiplet system CS (Figure 2). Data communication between the components MFE and E9a is symbolized in Figure 5B by block arrow A3. Optionally, the verification device MFE can reset the computing device E9a, for example, as indicated by arrow A4, e.g., if the check of the execution of, for example, the redundant machine-specific software code MS-SC, MS-SC has resulted in an error (e.g., a discrepancy between the results of the execution of the redundant machine-specific software code MS-SC, MS-SC by a computing device E9a).

[0052] In some examples, at least some aspects 100, 102, 110, 112 according to Fig. 1 and / or 4 can be carried out, for example, during or before the manufacture of the chiplet system CS and / or a product 1, 10 comprising the chiplet system CS.

[0053] In some examples, at least some aspects 114, 116 according to Fig. 4 can be carried out, for example, during or after the manufacture of the chiplet system CS and / or a product 1 , 10 comprising the chiplet system CS.

[0054] Fig. 6 schematically shows a simplified block diagram of a chiplet system CS' according to some examples. For instance, at least some aspects of the software component SW-KOMP (Fig. 2) can be executed, at least temporarily, by at least one component of the chiplet system CS'.

[0055] Element E10 according to Fig. 6 symbolizes a first component of the chiplet system CS', e.g., a so-called base die, which is configured, for example, to perform management functions and / or to connect further components, e.g., chiplets and / or storage devices E11, E12, E13, E14. For example, element E11 is a computing device, e.g., a central processing unit (CPU), e.g., a CPU chiplet. For example, element E12 is a graphics computing device, e.g., a graphics processing unit (GPU), e.g., a GPU chiplet. For example, element E13 is a storage device, e.g., main memory (RAM). For example, element E14 is a computing device for aspects of artificial intelligence (e.g., AI), e.g., machine learning (ML), e.g., an AI processor or accelerator device for AI, e.g., ML, e.g., an AI / ML chiplet.

[0056] The elements E15a, E15b, E15c, E15d, E15e, and E15f symbolize interfaces of the E10 base, for example, for connecting the aforementioned chiplets and / or memory devices. These interfaces can be of various types, such as D2D and / or memory interface and / or UCIe and / or PCIe, etc.

[0057] In some examples, Fig. 6, the monitoring function MF is implemented in the base E10, and it monitors the execution of redundant machine-specific software codes MS-SC, MS-SC according to the disclosure, in this case for example by the GPU chiplet E12.

[0058] Some examples, Fig. 7, refer to a device 200 for carrying out the method according to the disclosure.

[0059] In some examples, Fig. 7, the device 200 is provided to have: a computing device ("computer") 202 having at least one processing core 202a, a storage device 204 associated with the computing device 202 for at least temporary storage of at least one of the following elements: a) data DAT (e.g., data associated with the software component SW-KOMP and / or data associated with the redundant software codes SC, SC or the, for example, redundant, machine-specific software code MS-SC, MS-SC, and / or data associated with the development environment EU, EU'), b) a computer program PRG, for example, for executing the method according to the disclosure. In further examples, Fig. 7, the storage device 204 has volatile memory (e.g., main memory (RAM)) 204a, and / or non-volatile (NVM) memory (e.g., Flash EEPROM) 204b, or a combination thereof or with other memory types not explicitly mentioned.

[0060] Some examples, Fig. 7, refer to a computer-readable storage medium SM, comprising instructions PRG which, when executed by a computer 202, cause it to execute the method according to the disclosure, e.g. according to at least one of blocks 100, 102, 110, ... of Fig. 1 or 4.

[0061] Some examples, Fig. 7, refer to a computer program PRG, comprising instructions which, when the computer program PRG is executed by a computer 202, cause it to execute the method according to the disclosure, e.g. according to at least one of blocks 100, 102, 110, ... of Fig. 1 or 4.

[0062] Some examples, Fig. 7, refer to a data carrier signal DCS that characterizes and / or transmits the computer program PRG according to the disclosure. The data carrier signal DCS is, for example, exchangeable (transmittable and / or receiveable) via an optional data interface 206 of the device 200.

[0063] Element 12 according to Fig. 7 symbolizes optional aspects of a development environment EU, e.g., one or more frontends 12a and / or one or more backends 12b, as they can be used in some examples for processing data associated with the software component SW-KOMP. In some examples, at least some aspects of Element 12 can be implemented, at least temporarily, by the device 200.

[0064] Some examples, Fig. 8, relate to a method for a chiplet system CS, CS' (see Fig. 2, 6), comprising: providing 150, for example loading 150a, of, for example redundant, machine-specific software code SC, SC for at least one component CS-K, E12, of the chiplet system CS, CS', executing 152 of the, for example redundant, machine-specific software code by the at least one component CS-K, E12 of the chiplet system, and, optionally, checking 154 the execution 152 of the, for example redundant, machine-specific software code SC, SC.

[0065] In some examples, Fig. 9, the method includes: providing 160 a monitoring function MF, for example, for checking the execution of the, for example, redundant, machine-specific software code SC, SC, for example by at least one component CS-K, E12 of the chiplet system CS, CS', and, optionally, checking 162 the execution of the, for example, redundant, machine-specific software code by means of the monitoring function MF.

[0066] In some examples, Fig. 9, the checking 162 includes: comparing 162a results of the execution of, for example, redundant, machine-specific software code SC, SC, and, optionally, based on the comparison 162a, initiating 162b an error response FR, wherein, for example, initiating the error response includes resetting 162b' at least one component of the chiplet system.

[0067] Some examples, Fig. 7, relate to a device 200' for a chiplet system CS, CS' for carrying out the method according to the disclosure, for example at least some aspects according to Fig. 8, 9. For example, the device 200' or a corresponding functionality can be integrated into the chiplet system CS, CS'.

[0068] In some examples, device 200' has a configuration identical or similar to device 200.

[0069] Some examples, Fig. 7, relate to a computer-readable storage medium SM' for a chiplet system CS, CS', comprising instructions PRG' which, when executed by a computer 202, cause it to execute the method according to the disclosure, e.g. according to at least one of blocks 150, 152, 160, ... of Fig. 8 or 9.

[0070] Some examples, Fig. 7, refer to a computer program PRG' for a chiplet system CS, CS', comprising instructions which, when the computer program is executed by a computer 202, cause it to execute the method according to the disclosure, e.g. according to at least one of blocks 150, 152, 160, ... of Fig. 8 or 9.

[0071] Some examples, Fig. 7, refer to a data carrier signal DCS' for a chiplet system CS, CS', which characterizes and / or transmits the computer program PRG' according to the disclosure.

[0072] Some examples, Fig. 2, relate to a product 1, 10 comprising at least one device 200, 200' according to the disclosure. For example, the product 1, 10 comprises at least one chiplet system CS, CS'.

[0073] Some examples, Fig. 10, relate to a use 300 of the method according to the disclosure and / or the device 200, 200' according to the disclosure and / or the computer-readable storage medium SM, SM' according to the disclosure and / or the computer program PRG, PRG' according to the disclosure and / or the data carrier signal DCS, DCS' according to the disclosure and / or the product 1, 10 according to the disclosure for at least one of the following elements: a) enabling 301 redundancy in the execution of software code SC, SC, or b) integrating 302 at least one aspect of the coded processing into a development environment EU, EU', for example, a modular development environment, such as a compiler infrastructure, or c) enabling 303 comparatively large diagnostic coverage, for example, for single and / or multiple faults, such as hardware faults, or d) enabling 304 diverse implementation, for example, for fault-tolerant systems.for example for a driver assistance system, for example according to SAE L3+, or e) providing 305 software components SW-KOMP for chiplet systems CS, CS'.,

[0074] In some examples, diverse implementation is a concept that can be applied particularly in the context of functional safety and / or system reliability. Some examples of diverse implementation involve the development and use of several different implementations of the same functionality, for example, to reduce the probability of systematic errors. In some examples, the software component SW-KOMP can be used for ADAS (Advanced Driver Assistance Systems). In some examples, the software component SW-KOMP can be used for IVI (in-vehicle infotainment). In some examples, the software component SW-KOMP can be used for both ADAS and IVI.

[0075] In some examples, the principle according to the disclosure can be used, for example, for the provision and / or execution of the software component SW-KOMP for ADAS central control units and / or vehicle computers.

[0076] In some examples, the principle according to the disclosure can be used, for example, for automotive applications that can be implemented using chiplet technology, i.e., using the chiplet system CS, CS'.

[0077] In some examples, the principle according to the disclosure can be used to reduce the development effort of control units 1 and / or to enable the use of chiplets E12, E14 e.g. from a consumer sector, while simultaneously implementing safety requirements e.g. according to ISO26262.

[0078] In some examples, the principle as disclosed can be used to fulfill at least some of the requirements of ISO 26262 for hardware, such as diagnostic coverage. According to ISO 26262, this is 99% for single-bit errors in the case of ASIL-D. For multiple-bit errors (e.g., latent errors), a required detection rate is 90%; see, for example, ISO 26262-5:2018, section 8.4. In some examples, these metrics are achieved by chiplet systems CS and CS' as disclosed and / or by applying the principle as disclosed.

[0079] In some examples, the principle according to the disclosure can be used to achieve, for example, safety objectives according to ASIL-C and / or ASIL-D, without, for example, requiring hardware redundancy as is necessary with some conventional approaches. Instead, in some examples, the safety objectives according to ASIL-C and / or ASIL-D can be achieved, for example, by means of the process 100, 102 according to Fig. 1 and, optionally, by appropriate verification, for example, at runtime of the redundant software codes SC, SC, e.g., on a chiplet system CS, CS'.

Claims

Claims 1. Method, for example a computer-implemented method, for processing data associated with a software component (SW-KOMP) for a product (1 , 10), comprising: generating (100) redundant software code (SC, SC) for the software component (SW-KOMP) in an intermediate representation (ZR), for example intermediate representation, and, optionally, transforming (102) the redundant software code (SC, SC) into, for example redundant, machine-specific software code (MS-SC, MS-SC).

2. The method of claim 1, wherein the software component (SW-KOMP) characterizes at least one of the following elements: a) source code (SRC), for example in a high-level language such as C or C++, or b) bytecode (BC), for example virtual bytecode, or c) for example platform-independent representation (PUR), for example intermediate representation, for example according to the LLVM Project, or d) machine-specific code (MC), for example machine code.

3. A method according to at least one of the preceding claims, wherein the generation (100) of the redundant software code (SC, SC) comprises at least one of the following elements: a) generation (100a) of the redundant software code (SC, SC) by means of at least one frontend (FE-1) of a development environment (EU) for the software component (SW-KOMP), for example by means of at least one compiler of the at least one frontend (FE-1), or b) generation (100b) of at least one redundant function (F, F') for the software component (SW-KOMP), for example by means of at least one frontend (FE-1) of a development environment (EU) for the software component (SW-KOMP).

4. Method according to at least one of the preceding claims, wherein the transformation (102) comprises: transformation (102a) of the redundant Software codes (SC, SC) using at least one backend (BE-1) of a development environment (EU) for the software component (SW-KOMP).

5. A method according to at least one of the preceding claims, comprising at least one of the following aspects: a) providing (110) the, for example redundant, machine-specific software code (MS-SC, MS-SC) for at least one component (CS-K; E12) of a chiplet system (CS; CS'), for example storing (110a) the, for example redundant, machine-specific software code (MS-SC, MS-SC) for the at least one component (CS-K; E12) of a chiplet system (CS; CS'), b) executing (112) the, for example redundant, machine-specific software code (MS-SC, MS-SC) by at least one component (CS-K; E12) of a chiplet system (CS; CS'), or c) verifying (114) an execution (112) of the, for example redundant, machine-specific software code (MS-SC, MS-SC), for example by at least one component (CS-K; E12) of a chiplet system (CS; CS').of the chiplet system (CS; CS'), or f) providing (116) a monitoring function (MF), for example, a monitoring function, for checking (114) the execution (112) of the, for example, redundant, machine-specific software code (MS-SC, MS-SC), for example, by at least one component (CS-K; E12) of a chiplet system (CS; CS').

6. Device (200) for carrying out the method according to at least one of the preceding claims.

7. Computer-readable storage medium (SM) comprising instructions (PRG) which, when executed by a computer (202), cause it to execute the method according to at least one of claims 1 to 5.

8. Computer program (PRG) comprising instructions which, when the computer program (PRG) is executed by a computer (202), cause it to execute the method according to at least one of claims 1 to 5.

9. Data carrier signal (DCS) that characterizes and / or transmits the computer program (PRG) according to claim 8.

10. Method for a chiplet system (CS; CS'), comprising: providing (150), for example loading (150a), a, for example redundant, machine-specific software code (MS-SC, MS-SC) for at least one component (CS-K; E12) of the chiplet system (CS; CS'), executing (152) of the, for example redundant, machine-specific software code (MS-SC, MS-SC) by the at least one component (CS-K; E12) of the chiplet system (CS; CS'), and, optionally, checking (154) the execution (152) of the, for example redundant, machine-specific software code (MS-SC, MS-SC).

11. Method according to claim 10, comprising: providing (160) a monitoring function (MF), for example, for checking (154) the execution (152) of the, for example, redundant, machine-specific software code (MS-SC, MS-SC), for example, by at least one component (CS-K; E12) of the chiplet system (CS; CS'), and, optionally, checking (154; 162) the execution (152) of the, for example, redundant, machine-specific software code (MS-SC, MS-SC) by means of the monitoring function (MF).

12. Method according to claim 11, wherein the checking (162) comprises: comparing (162a) results of the execution of the, for example redundant, machine-specific software code (MS-SC, MS-SC), and, optionally, based on the comparison (162a), initiating (162b) a fault response (FR), wherein, for example, the initiation (162b) of the fault response (FR) comprises a reset (162b') of at least one component (CS-K; E12) of the chiplet system (CS; CS').

13. Device (200') for a chiplet system (CS; CS') for carrying out the method according to at least one of claims 10 to 12.

14. Product (1 , 10) comprising at least one device (200') according to claim 13.

15. Computer-readable storage medium (SM') for a chiplet system (CS; CS'), comprising instructions (PRG) which, when executed by a computer (202), cause it to execute the method according to at least one of claims 10 to 12.

16. Computer program (PRG') for a chiplet system (CS; CS'), comprising instructions which, when the computer program (PRG') is executed by a computer (202), cause it to execute the method according to at least one of claims 10 to 12.

17. Data carrier signal (DCS') for a chiplet system (CS; CS') that characterizes and / or transmits the computer program (PRG) according to claim 15.

18. Use (300) of the method according to at least one of claims 1 to 5 or 10 to 12 and / or the device (200; 200') according to claim 6 or 13 and / or the computer-readable storage medium (SM; SM') according to claim 7 or 15 and / or the computer program (PRG; PRG') according to claim 8 or 16 and / or the data carrier signal (DCS; DCS') according to claim 9 or 17 and / or the product (1, 10) according to claim 14 for at least one of the following elements: a) Enabling (301) redundancy in the execution of software code (SC, SC;MS-SC, MS-SC), or b) Integrate (302) at least one aspect of coded processing into a development environment (EU, EU'), for example a modular development environment (e.g. a compiler infrastructure), or c) Enable (303) a comparatively large diagnostic coverage, for example for single and / or multiple faults, for example hardware faults, or d) Enable (304) a diverse implementation, for example for fault-tolerant systems, for example for driver assistance, for example according to SAE L3+, or e) Provide (305) software components (SW-KOMP) for chiplet systems (CS; CS').;

Images