Desktop Error Verification System for Embedded Software

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for detecting errors in embedded systems are inefficient, particularly when dealing with complex hardware and software combinations, and often require significant time to identify and stabilize application errors, especially in environments lacking exception handling support across various development languages and operating systems.

Innovation Solution

A desktop error verification system that uses API wrappers to replace error detection syntax and perform exception handling independently of development languages and operating systems, allowing for automatic error detection and logging, and enabling error verification and reuse across different OS environments without modification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional error detection methods are used in embedded systems, then error detection capability is provided, but the time required to detect and stabilize errors increases significantly

Engineering Contradiction:
Improveerror detection capabilityVSAvoidtime to detect and stabilize errors
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces a desktop error verification system as an intermediary between the embedded system and the developer. This system includes API wrappers that translate embedded system-specific error detection APIs into desktop OS-compatible calls, enabling error detection in a controlled desktop environment before deployment to the embedded system, thereby reducing the time needed to identify and stabilize errors.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary error detection by allowing developers to verify applications on a desktop system before deploying to the embedded system. The error verification system performs error detection in advance on the desktop, where the development environment is more robust and easier to debug, thereby reducing the time required to detect and stabilize errors in the final embedded deployment.

Inventive Principle:
Principle #10Preliminary action

2Extent of automation

If exception handling functions are supported in development languages, then automatic error detection is enabled, but compatibility across different operating systems becomes difficult

Engineering Contradiction:
Improveautomatic error detectionVSAvoidcross-operating system compatibility
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The patent uses API wrappers as an intermediary layer between the desktop error verification system and the embedded operating system. These wrappers translate exception handling calls from the desktop environment into the specific API calls required by different embedded OSs, enabling automatic error detection while maintaining cross-platform compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal error verification system that can operate across multiple operating systems by providing a unified interface through API wrappers. The same desktop-based error detection code can verify applications for different embedded OSs (Windows CE, Linux, etc.) without modification, achieving both automation and versatility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If error detection syntax is inserted in application code, then error detection function is provided, but code complexity and number of source lines increases

Engineering Contradiction:
Improveerror detection functionVSAvoidcode complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses API wrappers as an intermediary that handles error detection logic externally to the application code. Instead of embedding error detection syntax throughout the application, the wrappers provide a clean interface that calls the error verification system, keeping the application code simple while maintaining comprehensive error detection capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If hardware problems occur in embedded systems, then system functionality is maintained, but error identification and stabilization becomes time-consuming

Engineering Contradiction:
Improvesystem functionalityVSAvoiderror identification and stabilization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent enables preliminary error detection on a desktop system before deploying to the embedded system. By performing error verification in advance on the more capable desktop environment, developers can identify and stabilize errors before they manifest in the embedded system, reducing the time needed for error identification and stabilization in the final deployment.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8589889B2Apparatus and method of detecting errors in embedded software
Publication Date: 2013.11.19 SAMSUNG ELECTRONICS CO LTD
  • US8589889B2 patent drawing
  • US8589889B2 patent drawing
  • US8589889B2 patent drawing

AI summary

A method and apparatus for detecting errors in an application software of an embedded system are provided. The method of detecting errors in an application software includes determining a development language of the application software and an operating system on which the application software is executed; replacing an error detection syntax inserted in order to examine an error in a predetermined function of the application software, with an error detection syntax according to the result of the determination; and performing exception handling for an error occurring in the function according to the result of the replacement, and logging error information according to the exception handling. According to the method and apparatus, an error can be automatically detected and logged irrespective of a development language and an operating system.