SoC Microcontroller Remote Debugging via Network Stack
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current SoC debugging methods require physical access and specialized equipment, making remote debugging expensive and impractical, especially when the SoC has security restrictions or malware infections prevent software execution, and debugging is limited to post-boot scenarios.
Innovation Solution
Incorporating a microcontroller with a network stack that allows remote access to the Test Access Port (TAP) of IP blocks within the SoC, enabling virtual JTAG debugging even when the OS doesn't boot or malware suppresses notifications, and allowing Field Programmable Fuses (FPFs) to be modified for feature control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If physical access and specialized equipment are required for debugging, then debugging can be performed on SoCs with security restrictions or malware infections, but debugging costs increase and practicality decreases
Solution Approach 1:
The patent introduces a microcontroller as an intermediary component within the SoC that provides a secure debugging interface. This microcontroller acts as a mediator between external debugging tools and the internal IP blocks, allowing remote debugging without requiring physical access to the SoC hardware. The microcontroller maintains security restrictions while enabling authorized remote access through network communication.
Solution Approach 2:
The patent replaces the mechanical/physical debugging approach (requiring physical access and specialized equipment like JTAG) with a software-based network communication approach. The microcontroller implements a network stack that enables debugging commands to be transmitted remotely over a network, substituting the need for physical connection and specialized hardware interfaces.
2Ease of operation
If remote debugging is enabled without physical access, then debugging costs and complexity are reduced, but security restrictions and malware infections may prevent proper debugging
Solution Approach 1:
The patent implements preliminary security measures by incorporating authentication mechanisms within the microcontroller before allowing remote debugging access. The microcontroller verifies the identity and authorization of remote debugging attempts, preventing unauthorized access even when the main processor is compromised by malware. This preliminary security check ensures debugging authenticity before enabling remote access.
3Device complexity
If debugging is limited to post-boot scenarios with OS execution, then software-based debugging is simpler to implement, but debugging cannot be performed when OS fails to boot or malware suppresses notifications
Solution Approach 1:
The patent implements preliminary action by having the microcontroller maintain independent debugging capabilities that operate before and during the boot process, independent of the main processor and operating system. The microcontroller can capture and report debugging information even when the OS fails to boot or when malware attempts to suppress notifications, ensuring comprehensive debugging scenario coverage without significantly increasing overall system complexity.
Data Source
AI summary
Techniques for secure remote debugging of SoCs are described. The SoC includes an intellectual property (IP) block, a microcontroller, and a fabric coupled to the IP block and the microcontroller. The IP block transmits, via the fabric, information regarding events within the IP block to the microcontroller. The microcontroller executes firmware including a network stack and a remote debugger program. Using the firmware, the microcontroller provides the event information to a device external to the SoC.