SerDes Initialization Firmware Split for Smaller On-Chip Memory
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic devices face challenges in implementing efficient and compact serializer/deserializer (SerDes) communications due to the need for large non-volatile memory to store software, which increases size and cost, and existing initialization methods are inefficient.
Innovation Solution
Implementing a programmable read-only memory to store an abbreviated version of the software for initializing SerDes communication, allowing devices to autonomously initiate communication, with a full software version stored externally and downloaded later for complete functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If large non-volatile memory is used to store software for SerDes communication, then communication functionality is complete, but device size and cost increase
Solution Approach 1:
The software is divided into two segments: an abbreviated initialization version stored in on-chip memory and a full version stored externally. This segmentation allows the device to have complete communication functionality while minimizing on-chip memory requirements, thus reducing device size.
Solution Approach 2:
The full software version is extracted from the device and stored externally, with only the essential initialization portion remaining on-chip. This extraction eliminates the need for large non-volatile memory in the device while maintaining complete functionality through external software loading.
2Adaptability or versatility
If large non-volatile memory is used to store software for SerDes communication, then communication functionality is complete, but device cost increases
Solution Approach 1:
The software is segmented into minimal initialization code and full functionality code, allowing the device to use small, inexpensive on-chip memory while storing the bulk of the software externally, thereby reducing manufacturing costs.
Solution Approach 2:
The majority of the software is extracted from the device and stored externally, eliminating the need for expensive large-capacity non-volatile memory in the device itself, thus reducing overall device cost while maintaining complete communication functionality.
3Volume of stationary object
If abbreviated software is used for initialization, then memory requirements are reduced, but communication data rate is lower
Solution Approach 1:
The abbreviated software performs preliminary initialization actions to establish basic communication functionality at lower data rates. Once initialized, the system can load and execute the full software version to achieve higher data rates, thus balancing memory constraints with performance requirements.
4Volume of stationary object
If abbreviated software is used for initialization, then device size is reduced, but functionality is limited
Solution Approach 1:
The software functionality is segmented into essential initialization operations and advanced communication operations. The abbreviated version contains only essential operations, reducing device size, while the full version provides complete functionality, accessible after external loading.
Solution Approach 2:
The abbreviated software performs preliminary initialization to establish basic communication capability with reduced device size. Subsequently, the full software is loaded to expand functionality, thus achieving both size reduction and complete adaptability through sequential software deployment.
Data Source
Figure 1
Figure 2
AI summary
The present description relates to an electronic device (102) adapted to implement a communication by serializer/deserializer comprising a first memory (1022) adapted to store a first software (10221) adapted to initialize said communication, said first software (10221) being different from a second software (1031) adapted to implement said communication.