IO Block Power Retention During System Reset for Board Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional electronic systems shut down IO blocks during reset sequences to conserve power, interfering with board-level testing that requires all components to be powered, and implementing internal switching for IO block testing is expensive and difficult.
Innovation Solution
The system utilizes added firmware hooks to override reset and power-wakeup signals, maintaining power to IO blocks by stalling the shutdown process and entering a reduced power mode, such as semi-sleep, allowing for platform testing without complete power removal.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If the system shuts down IO blocks during reset sequence to conserve power, then power consumption is reduced, but board testing capability is lost
Solution Approach 1:
The system dynamically adjusts the power state of IO blocks based on operational context. During normal operation, IO blocks are shut down to save power. During board testing mode, the system dynamically maintains IO blocks in a powered state by stalling the reset sequence, allowing the same hardware to adapt to different operational requirements without physical modification.
Solution Approach 2:
The invention changes the temporal parameter of the reset sequence by introducing a stall condition. Instead of allowing the reset sequence to complete (which would shut down IO blocks), the system modifies the timing and progression of the reset sequence to pause at a critical point, thereby changing the power state parameters from 'shutdown' to 'maintained' for testing purposes.
2Adaptability or versatility
If internal switching is added to enable IO block testing, then testing capability is improved, but device complexity and manufacturing cost increase
Solution Approach 1:
Instead of adding physical internal switching hardware to control IO block power states, the invention creates a software copy or simulation of switching functionality through firmware hooks. These hooks replicate the control function of physical switches in software, allowing the system to simulate different power states without the physical complexity of additional switching components.
Solution Approach 2:
The invention replaces the mechanical/hardware switching system with a software-based control mechanism. Instead of using physical switches or complex internal routing hardware to control IO block power states, the system uses firmware logic and reset sequence manipulation to achieve the same functional outcome, thereby eliminating the need for additional physical components.
3Productivity
If a complete reset sequence is executed, then system initialization is complete, but IO blocks are shut down preventing testing
Solution Approach 1:
The system performs preliminary actions by stalling the reset sequence before it reaches the point where IO blocks would be shut down. By pausing the initialization process at a strategic point in the reset sequence, the system prepares the hardware in a state suitable for testing while avoiding the subsequent shutdown action, effectively performing the testing preparation in advance.
Solution Approach 2:
The invention extracts or removes the IO block shutdown step from the complete reset sequence by introducing a stall condition. Instead of allowing the reset sequence to proceed through all its stages including the final shutdown phase, the system takes out or excludes the shutdown portion by pausing earlier in the sequence, thereby separating the testing-capable state from the complete initialization process.
Data Source
AI summary
Embodiments are generally directed to maintaining IO block operation in electronic systems for board testing. An embodiment of a system includes a processor; a power management block for the system; a plurality of IO (input/output) blocks; a read only memory for storage of firmware for the processor. The system is to provide support for a board-level test of the system including testing of one or more IO blocks of the plurality of IO blocks; and the firmware includes elements to stall a reset sequence of the system including the system branching to a mode that maintains power to the one or more IO blocks.