Hot Swap Kernel Update Selective Peripheral Reset
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-boot memory architectures, hot swapping program code is time-consuming due to the need for resetting various resources like the stack, heap, SRAM, and peripherals, which is problematic for applications requiring minimal downtime.
Innovation Solution
A method that identifies and resets only those peripherals and system components that require reinitialization, using configuration bits or software registers to determine which components need resetting, allowing the new code to execute without a system-wide reset.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a system reset is performed before switchover to new code, then reliability of code execution is improved, but switchover time increases
Solution Approach 1:
The patent segments the reset operation from a system-wide reset to a selective peripheral reset. Instead of resetting all system components, the invention identifies and resets only those specific peripherals that require reinitialization after code switchover, thereby reducing switchover time while maintaining execution reliability.
Solution Approach 2:
The patent performs preliminary identification of which peripherals need resetting before the actual switchover occurs. By using configuration bits or software registers to pre-determine the reset requirements, the system prepares the minimal necessary reset actions in advance, avoiding unnecessary delays during the critical switchover window.
2Stability of the object's composition
If all system components are reset during hot swap, then system stability is improved, but productivity decreases
Solution Approach 1:
The patent applies local quality by differentiating the reset requirements of individual peripherals rather than applying a uniform system-wide reset. Each peripheral is evaluated independently, and only those with specific reset requirements are reset, maintaining system stability where needed while enabling faster updates elsewhere.
Solution Approach 2:
The patent performs a partial reset action, resetting only the necessary subset of peripherals rather than all system components. This partial action is sufficient to maintain system stability for the updated code while significantly reducing the time and resources required compared to a complete system reset.
3Ease of operation
If configuration bits are used to identify peripherals requiring reset, then device complexity increases, but ease of operation improves
Solution Approach 1:
The patent implements self-service by having the new code automatically identify which peripherals require resetting through configuration bits or software registers. The system autonomously determines its own reset requirements without external intervention, simplifying the hot swap operation while the configuration structure manages the complexity internally.
Data Source
Figure 1~3
Figure 2
Figure 4A~5
AI summary
A method for hot swapping an operating system kernel in a system, wherein the system comprises a central processing unit, one or more system components and a program memory including an old kernel and a new kernel, the method comprising: - configuring, by the old kernel, the system to boot from the new kernel by branching into a suitable entry point in the new kernel; - identifying, by the new kernel, one or more system components which require a reinitialization or reset; - further executing the new kernel in order to reinitialize or reset the one or more system components.