Configurable Data Integrity Logic for Flexible CRC Boundary Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data integrity checking methods in integrated circuits lack flexibility and adaptability, particularly in handling data streams with varying starting addresses and chunk boundaries, which can lead to errors and inefficiencies in data transmission and reception.
Innovation Solution
The implementation of an integrated circuit device with configurable CRC modes, including floating and fixed boundary CRC modes, that uses data integrity logic to parse and compute CRC codes, allowing for flexible identification of chunk boundaries based on configuration data, thereby enhancing data integrity checking across different ecosystems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If fixed boundary CRC mode is used, then data integrity checking is simplified and standardized, but adaptability to varying data stream boundaries is reduced
Solution Approach 1:
The patent implements a configurable CRC boundary identification mechanism that can dynamically switch between fixed boundary mode and floating boundary mode based on configuration data. The boundary identification logic is made adjustable, allowing the CRC checking device to adapt its behavior to different data stream formats without requiring multiple dedicated hardware circuits for each mode.
Solution Approach 2:
The patent introduces configuration data that contains parameters defining the CRC chunk boundaries, such as starting addresses and chunk sizes. By changing these parameters, the system can adapt to different data stream formats. The configuration data enables the CRC logic to flexibly interpret where chunks begin and end, resolving the contradiction between fixed simplicity and floating adaptability.
2Adaptability or versatility
If floating boundary CRC mode is used, then flexibility in handling varying data streams is improved, but complexity in identifying chunk boundaries increases
Solution Approach 1:
The patent employs configuration data that is prepared in advance to define the floating boundary parameters. The starting address and chunk size information are predetermined and stored, allowing the CRC logic to quickly identify chunk boundaries without performing complex real-time calculations. This preliminary preparation of boundary information simplifies the detection process while maintaining floating boundary flexibility.
3Adaptability or versatility
If configurable CRC modes are implemented, then compatibility with different data integrity ecosystems is enhanced, but device complexity increases
Solution Approach 1:
The patent designs a universal CRC checking device that can operate in multiple modes (fixed boundary and floating boundary) through a single configurable hardware structure. The same CRC logic circuit can serve different data integrity ecosystems by interpreting configuration data differently, eliminating the need for separate dedicated circuits for each mode and reducing overall device complexity despite enhanced compatibility.
Data Source
AI summary
An integrated circuit device can comprise addressable memory, and a receiver. Data integrity logic can be coupled to the input data path and configured to receive a data stream having a reference address, and a plurality of data chunks with data integrity codes. Also, the data integrity logic can include a configuration store to store configuration data for the data integrity checking. Also, the integrated circuit can include logic to parse the data chunks and the data integrity codes from the data stream, and logic to compute computed data integrity codes of data chunks in the received data stream, and compare the computed data integrity codes with received data integrity codes to test for data errors in the received data stream. The data integrity logic includes logic responsive to the configuration data that control the data integrity logic. In one aspect, the data integrity data indicates a floating boundary data integrity mode or a fixed boundary data integrity mode.