Lattice Semiconductor

What's New in Lattice Help Center
Recent updates to help you submit requests faster and more accurately
Latest Update
New
MachXO5-NX CDF Request — New Submission Process
A streamlined path to submit your CDF requests
The MachXO5-NX CDF request now has a dedicated route through the Technical Support portal. Tickets are automatically routed to the appropriate engineer upon submission.
Submission Steps
1
Open the ticket creation page Use the button below to go directly to the Technical Support portal.
2
Set the Area of Inquiry field Use the drop-down menu and select:
Controlled Files
3
Set the Case Sub-Category 2 field Use the drop-down menu and select:
MachXO5-NX CDF Request
Note: Please ensure the correct target OPN is selected for the MachXO5-NX in the Device and Package field so we can provide the appropriate CDF
Nov 18, 2025
Nov 18, 2025
Controlled Files Release Forms: Software Control Pack and Existing Patch
Two new form layouts to improve clarity and routing for controlled software file requests

Dedicated forms are now available for controlled software file requests. You can submit tickets specifically for the following categories:


Software Control Pack — Guidelines
An NDA is mandatory before submission.
  • All listed control packs are publicly referenced in official Lattice documentation.
  • For unlisted packs (Early Access, Beta, or older versions): select "Others – Not Listed" for Software Product and/or Control Pack Name, then enter details in "Specify Software Version and Control Pack Name."
  • Currently supported versions:
    • Radiant: Latest + 2 previous versions
    • Diamond: Latest + 1 previous version
    • Propel: Currently one control pack; future support will include latest + 2 previous versions

Existing Software Patch — Guidelines
This form is intended only for requesting patches that already exist. Do not use this form to request patches that do not yet exist or patches for older software versions.

If such a request is critical, use the General Technical Support form and select:

Area of Inquiry: Controlled Files Case Sub-Category 2: Existing Software Patch for Old Software Version

Changes to General Technical Support Form

To avoid duplication, the following options have been removed from Case Sub-Category 2 and are now handled through the dedicated forms:

  • Product Licensing
  • Security Encryption Pack — now: Software Control Pack
  • Security HSM Script — now: Secured Document Request
  • Software and Tools Pack/Patch/Script
Nov 18, 2025
Nov 18, 2025
Software Licensing — Dedicated Ticket Form
A dedicated form to make licensing support easier to locate and submit

A dedicated ticket form for software licensing requests is now available. Select the Software Licensing category when submitting your ticket to access the new layout.

Available Request Types
New License Request
Update License Request
License Installation
Other Licensing Inquiry

Changes to General Technical Support Form

To streamline support and avoid duplication, the following option has been removed:

  • Product Licensing — now handled exclusively through the Software Licensing form
Other software concerns such as installation errors and tool crashes remain available in the General Technical Support form. Additional dedicated form layouts are in progress and will be released soon.
Oct 21, 2025
Oct 21, 2025
Controlled Document Release: Secured Documents and IBIS-AMI Model
A faster, clearer, and more secure process for requesting controlled documents

A dedicated ticket layout for controlled document requests is now live. Select the Controlled Document Release category to access the new form instead of using the general ticketing form.

An NDA with Lattice is required for all controlled document requests.
Available Document Types
Secured Document Files
Covers Application Notes, Tech Notes, User Guides, and similar controlled documentation.
IBIS-AMI Models


What's Improved
Dynamic Form Fields
Required fields are displayed based on the selected document type, reducing unnecessary input.
Secure Delivery
Approved documents are provided via a secure FTP link included in the closing email.
Rejection Handling
If declined, the requester is notified and may reply with justification to reinitiate the approval process.
Changes to General Technical Support Form

The following options have been removed from Case Sub-Category 2 and are now handled exclusively through the new layout:

  • Secured Document Files
  • IBIS-AMI Models
Other controlled files such as source codes, patches, and control packs remain available in the General Technical Support form. Dedicated layouts for these are in progress — stay tuned.
Lattice Help Center — Release Notes 4 announcements
    • Recent Articles

    • DisplayPort IP RX Intermittent Interlane Alignment Loss of Lock for TPS2

      Description: When TPS2 is used during link training, intermittent occurrences have been observed where the DisplayPort IP internal deskew logic latches onto an incorrect test pattern alignment and is unable to recover. As a result, the DisplayPort IP ...
    • Overlapping BS Between Idle to Active Video Stream Transition

      Description: There is a known issue where the BS (Blanking Start) of the idle pattern, which occurs at every 8192th symbol, overlaps with the BS of the active video stream during transition from idle to active mode. This overlap causes the IP to ...
    • DisplayPort IP RX 8.1G Unable to Achieve Interlane Alignment

      Description: DisplayPort IP(RX) operating at 8.1 Gbps may encounter an issue where the DisplayPort IP is unable to achieve interlane alignment during link training. This is due to some hardware have lane data arrives earlier than expected, resulting ...
    • DisplayPort RX IP does not support backpressure

      Description: DisplayPort RX IP does not support backpressure. The IP continues to output data even when the downstream tready signal is deasserted. Resolution: A shallow buffer will be introduced in a future IP release to handle occasional tready ...
    • DisplayPort IP symbol Transfer Unit (TU) size is capped at 63

      Description: The DisplayPort IP TU size is capped at 63 to avoid link oversubscription. Resolution: Users are required to increase to a higher link rate or lane count to avoid hitting the maximum 64-symbol TU. Users may refer to "Valid Bytes per TU" ...