TSN Network Debugging for Synchronized MCU Trace Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional debugging subsystems in computer-controlled systems require specialized connectors and communication protocols, making debugging operations cumbersome, especially for MCUs in difficult-to-access locations, and synchronization of local clocks across MCUs is challenging, complicating the diagnosis of complex bugs involving multiple MCUs.

Innovation Solution

Implementing a Time Sensitive Networking (TSN) Ethernet protocol for synchronized communication among MCUs, using a real-time packet-switched networking protocol to synchronize local clocks and enable efficient debugging and tracing operations through a network-aware debugging subsystem, with features like precision time protocol (PTP) and IEEE standards for time synchronization and traffic management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional debugging subsystems use specialized connectors and protocols, then debugging functionality is provided, but debugging operations become cumbersome and difficult for MCUs in difficult-to-access locations

Engineering Contradiction:
Improvedebugging operation easeVSAvoidconnector and protocol complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent applies universality by enabling the debugging subsystem to communicate through standard Ethernet network ports that can handle multiple protocols (UART, SPI, I2C, CAN) over a single network interface. This eliminates the need for specialized debug connectors and makes the same physical port usable for both network communication and debugging operations, significantly improving ease of operation for remotely located MCUs

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

Solution Approach 2:

The patent replaces mechanical/debugging-specific connectors with electronic network-based communication. Instead of using physical debug ports and cables, the system uses Ethernet network packets to transmit debugging data, traces, and control commands through the existing network infrastructure, eliminating the need for specialized mechanical connectors

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

2Reliability

If conventional debugging subsystems are used, then debugging functionality is achieved, but synchronization of local clocks across MCUs is challenging

Engineering Contradiction:
Improveclock synchronization reliabilityVSAvoidsynchronization complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the clock synchronization function with the existing Ethernet network communication infrastructure. By using the same network packets that carry debugging data to also convey timing and synchronization information, the system achieves reliable clock synchronization across distributed MCUs without adding separate synchronization hardware or protocols

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces a network-based timing intermediary that uses standard Ethernet protocols to distribute synchronized timing information across the system. The Ethernet network acts as an intermediary carrier for both data and timing signals, using protocol-based timestamping and synchronization mechanisms to coordinate clocks across multiple MCUs

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If specialized debugging connectors are used, then debugging access is provided, but accessing MCUs in difficult-to-access locations becomes particularly challenging

Engineering Contradiction:
Improvedebugger access easeVSAvoidphysical accessibility constraints
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent replaces mechanical connector-based debugging access with wireless or network-based Ethernet communication. Debugging data and control signals are transmitted through the existing network infrastructure, allowing developers to access and debug MCUs located in physically difficult-to-reach positions without needing to physically connect specialized debug probes to the target device

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

Data Source

PatentUS20260081861A1Debugging using a packet-based networking protocol
Publication Date: 2026.03.19 INFINEON TECHNOLOGIES AG
  • US20260081861A1 patent drawing
  • US20260081861A1 patent drawing
  • US20260081861A1 patent drawing

AI summary

Some aspects of the present disclosure relate to an integrated-circuit (IC) microcontroller (MCU) having a debug subsystem, a classifier module, and a network port. The debug system is configured to generate trace data in response to a trace trigger and provide the generated trace data to the classifier. The network port is configured to: receive network frames in accordance with a time-sensitive packet-switched networking protocol, encapsulate received payloads to generate network frames in accordance with the time-sensitive packet-switched networking protocol, transmit the generated network frames in accordance with the time-sensitive packet-switched networking protocol, generate timing information in accordance with the time-sensitive packet-switched networking protocol, and provide the timing information to the classifier. The classifier is configured to generate trace-data payloads based on the received trace data and the received timing information and provide the generated trace-data payloads to the network port.