Since we use generative AI to extract information from datasheets—which sometimes lack complete component information—we’ve implemented robust error management tools to help you. Errors act as blockers—you cannot proceed to driver or testing generation until you resolve them. The system also includes warnings, which appear in orange. These non-blocking notifications highlight potentially inconsistent elements in your Component Model.

How do I know there is an error?

When a section contains an error, a red dot appears above the chapter name. Navigate to that section to see error details.

How do I find an error inside the section?

In smaller sections (like General component information), error fields are highlighted in red.For larger sections (like Registers), we provide an error navigation menu below the Component Model chapters. This menu shows the error count and offers buttons to navigate between errors.

​
Which types of errors exist?

Warnings occur in the system when non-blocking inconsistencies are detected. These include cases where a specific register has a size larger than other registers within the same device. You don’t have to resolve this to generate testing/driver, however, we suggest to use PDF Backlink feature to doublecheck correctness.
A bit allocation overlap error occurs when two fields share overlapping bits. In most cases, this is due to an AI extraction error. To resolve this, click the ‘Show Datasheet’ button to open the relevant section in the PDF document. Then, click the field name in the error message to adjust its offset and size.
This error occurs when the datatype size is incorrect or the bit allocation contains extra fields. To resolve it, click the ‘Show Datasheet’ button to open the relevant section in the PDF document. Depending on the cause of the error, adjust the datatype size, remove extra bits, or change the datatype to an integer.
Ensure that the names of each bitfield are unique. This applies to reserved bits as well.