Triggered Remote Function Calls for Slave MCU Hardware Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Master/host-slave systems face limitations in configuring and controlling slave-side hardware function blocks due to communication protocol incompatibilities and slow data transfer rates, making it difficult to handle real-time requests and reconfigure hardware function blocks.

Innovation Solution

A triggered remote function call methodology is introduced, where a master issues trigger-function signals to a slave MCU, which executes pre-loaded software functions with associated parameters from memory, using a trigger conditioning block to service these signals as IRQs, enabling faster and more flexible control of slave-side hardware functionality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If standardized communication buses (SPI, I2C) are used for master-slave communication, then communication protocol compatibility is maintained, but real-time control capability and data transfer speed deteriorate

Engineering Contradiction:
Improvecommunication protocol compatibilityVSAvoiddata transfer speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent segments the control functionality into two parts: time-critical control signals are handled by dedicated hardware blocks with direct physical connections, while non-time-critical data communication continues to use the standardized SPI/I2C buses. This segmentation allows real-time control without compromising protocol compatibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary hardware blocks (such as state machines, pulse generators, or dedicated control logic) that act as mediators between the master controller and slave devices. These intermediaries receive commands from the master via standard buses and generate the necessary real-time control signals locally, eliminating the bottleneck of using slow buses for real-time control.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If slave-side hardware function blocks are used for real-time control, then real-time response capability is improved, but reconfigurability and adaptability deteriorate

Engineering Contradiction:
Improvereal-time response capabilityVSAvoidreconfigurability
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic reconfigurability by allowing the master controller to programmatically configure and reconfigure the slave-side hardware function blocks through register writes or control sequences sent via the communication bus. This enables the system to adapt to different real-time control requirements while maintaining fast response capability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent enables reconfiguration of hardware function blocks by changing their operational parameters through software control. The master can modify configuration registers, timing parameters, and control logic states to adapt the hardware blocks to different functions while maintaining their real-time performance characteristics.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If interrupt service routines are used for handling slave requests, then software flexibility is maintained, but response time and processing efficiency deteriorate

Engineering Contradiction:
Improvesoftware flexibilityVSAvoidresponse time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent replaces the software-based interrupt service routine mechanism with hardware-based automatic response mechanisms. Dedicated hardware blocks detect events and automatically generate responses or trigger interrupts with predetermined handling logic, eliminating the overhead of software interrupt context switching and improving response time while retaining configurability.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10140229B2Wired communication with remote function calls
Publication Date: 2018.11.27 TEXAS INSTRUMENTS INC
  • US10140229B2 patent drawing

AI summary

Triggered remote function calls can be used in master-slave systems to trigger slave-side software functions pre-loaded by a master into slave MCU memory, with associated parameters pre-loaded into a slave function interface memory. A master issues trigger-function signals (such as rising/falling edges or signal levels) over a trigger-function signal line. The slave includes a trigger conditioning block that in response issues a trigger-function request to the slave MCU, which calls/executes the associated software function, including accessing the associated trigger-function parameters from function interface memory. A slave can include a hardware function block with functionality configurable by a pre-loaded software configuration function (with associated parameters). A master can include a hardware function block configured to issue trigger-function signals. The slave (trigger conditioning block) can be configured to service trigger-function signals as an IRQ (interrupt request) to the MCU, which executes an ISR (interrupt service routine) as a triggered function call.