Browse Prior Art Database

Automatic background verification of external interfaces in embedded systems

IP.com Disclosure Number: IPCOM000017255D
Original Publication Date: 2000-Apr-01
Included in the Prior Art Database: 2003-Jul-22
Document File: 1 page(s) / 13K

Publishing Venue

Siemens

Related People

Markus Senninger: AUTHOR

Abstract

In practically all cases, embedded systems must interact with external interfaces such as ASICs or I/O-ports. Usually this interaction is controlled by software drivers, which control the writing of values to (or the reading from) the desired location.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 86% of the total text.

-   97   -

Information / Kommunikation

Automatic background verification of external interfaces in embeddedsystems

Idee: Markus Senninger, Buchloe

In practically all cases, embedded systems must interact with external interfaces such asASICs or I/O-ports. Usually this interaction is controlled by software drivers, which controlthe writing of values to (or the reading from) the desired location.

Problems may arise when internal or external errors lead to a invalidation of the driverconfiguration during runtime, leading to undefined behavior of the whole embedded system.

Verifying the interface behavior conventionally requires a high effort, and in most cases it isnot viable to reach a 100 percent test coverage. Testing is performed configuration-orientedso that side effects on other parts of the external interface or the dynamics of the systemcannot be considered.

Firstly  to  automate  the  testing  process  and  secondly  to  improve  stability  againstconfiguration  loss,  electromagnetic  influences,  and  malfunction  of  the  external  interfaceitself, and thirdly to enhance the testing capabilities to cover side effects, system dynamics,and the automated rectification of misconfigurations, the following is proposed:

The whole software configuration information is mirrored in the microprocessor RAM, sothat  all  configuration  data  being  written  to  the  hardware  itself  is  also  written  to  this'hardware image'. The idle task, i.e. the task with the lowest poss...