TCP/IP stack is optimized for automotive use

April 10, 2019 //By Christoph Hammerschmidt
TCP/IP stack is optimized for automotive use
Everywhere, the automotive industry is in the process of transplanting standard technologies from commercial IT into cars. However, a 1:1 adoption of these technologies is not always feasible - not all IT standards, for example, take functional safety into account. Example TCP/IP stack: In order for this absolutely ubiquitous protocol stack to be integrated in the vehicle in IT, it must be adapted accordingly. The software provider HCC Embedded (Budapest) has addressed this problem.

HCC Embedded (HCC), an expert in software components for deeply embedded systems with particular high quality requirements, is setting a new bar for the industry with its Safety Elements out of Context (SEooC) approach to developing reusable software components that can be integrated with systems engineered to meet stringent requirements for safety, quality, and portability. HCC has created the processes and environment to build reusable SEooCs and today introduced its first Element: the HCC SafeTCPIP network stack for use in automotive systems.

Future releases will map the standard ISO26262 V-model process to other safety-critical standards such as in aerospace, industrial, and medical device markets.

“Safety standards promote the reuse of proven software elements; however, reusing software in a safety context introduces complex challenges, such as how to do full lifecycle maintenance on essentially off-the-shelf components,” said HCC Embedded CEO Dave Hughes. “HCC has built the full lifecycle to be a manageable part of our customers’ safety development.”

Originating in ISO 26262-10, SEooC is defined as a method for using software or hardware components in a vehicle that were not originally designed for that specific project. A software SEooC is developed to a safety standard, in this case ISO 26262, which means that it is developed with all the processes of a full software safety lifecycle and within the design constraints of a safety system. The software components are developed “out of context” to provide a specific function with no awareness of how the component will be used in the target system. The “Element” indicates that this is a unit or module with a specific range of functionality; “safety” indicates that this module is specifically developed in the context of a set of safety requirements. HCC is the first embedded software module vendor to use the SEooC approach to build commercial software Elements, beginning with its SafeTCPIP product.

Vous êtes certain ?

Si vous désactivez les cookies, vous ne pouvez plus naviguer sur le site.

Vous allez être rediriger vers Google.