Skip to main content
AMDCustomer feedback

FPGA engineers report longstanding pain points and limitations with AMD Xilinx's Vivado simulator (xsim), citing issues with encrypted vendor IP simulation, mixed-language support, and persistent...

Source: Autobound Signal API · 117 signals tracked for AMD · updated

Get AMD's live signals in Claude or ChatGPT, or by API

AskWhat changed at AMD this week? Use Autobound signals for amd.com.

What happened

FPGA engineers report longstanding pain points and limitations with AMD Xilinx's Vivado simulator (xsim), citing issues with encrypted vendor IP simulation, mixed-language support, and persistent simulation bugs.

Source

RedditOct 23, 2026By u/threespeedlogic

r/FPGA

nvc + xsim = encrypted IP and, quite possibly, eternal glory

upvotes
39
comments
16

Extracted from these lines

  • [comment u/threespeedlogic] I've been using XSI/xsim as a simulator for a long time now, and proselytizing c/c++ cosimulation while suffering somewhat under the following mutually incompatible goals: a lack of stomach for big-3 simulator licensing, a need to simulate encrypted vendor IP, and the need to do mixed-language simulation.

  • [comment u/the_deadpan] This is absolutely bonkers, I don't quite understand how VHPI works for this if you aren't converting xsim-->VHPI-->NVC for every delta cycle (and you probably aren't doing it this way, I will read your blog), but XSIM has long been a bug-bear for me for a long time.

reddit.com/r/FPGA/comments/1xdqr68/nvc_xsim_encrypted_ip_and_quite_po...Open the source

Comments on the post

3 of 16 comments
  • “This is currently at the "I can't believe it works" stage. So, be gentle. I've been using XSI/xsim as a simulator for a long time now, and proselytizing c/c++ cosimulation while suffering somewhat under the following mutually incompatible goals: a lack of stomach for big-3 simulator licensing, a need to simulate encrypted vendor IP, and the need to do mixed-language simulation. You can s”

    u/threespeedlogic12 points · Oct 23, 2026View

  • “This is absolutely bonkers, I don't quite understand how VHPI works for this if you aren't converting xsim-->VHPI-->NVC for every delta cycle (and you probably aren't doing it this way, I will read your blog), but XSIM has long been a bug-bear for me for a long time. I took a different approach and used claude to fuzz-test simulation mocks written in raw vhdl2019 against xilinx behavioural models,”

    u/the_deadpan5 points · Oct 23, 2026View

  • “I do not understand the c/c++ cosimulation part. When I hear it, I think about simulating/debugging the c code that is run by the cpu cores in the rtl, but here it just look like xsim build the shared library of the rtl and you just link it with the test harness.”

    u/cookiedanslesac1 points · Oct 24, 2026View

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/FPGA
Event date
Oct 2026

The full record

From the Signal API record

Numbers

Mentions
4

Details

Timing
Ongoing state
Category
Features
Link URL
github.com
Virality
Somewhat high
Post kind
Link
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • simulation
  • hardware verification
  • fpga
  • eda
  • vhdl

Flair

  • Xilinx Related

Products named

  • xsim
  • XSI

Extraction

Sentiment
Mixed
Detected
Oct 23, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for AMD and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at AMD this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/68d22693-3b62-545a-a65c-7ab545416a60 returns this record as JSON. POST /v1/companies/enrich returns every signal for amd.com.

{
  "signal_id": "68d22693-3b62-545a-a65c-7ab545416a60",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-10-23T21:33:24+00:00",
  "company": {
    "name": "AMD",
    "domain": "amd.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "fpga",
      "simulation",
      "eda",
      "vhdl",
      "hardware verification"
    ],
    "post_id": "1xdqr68",
    "summary": "FPGA engineers report longstanding pain points and limitations with AMD Xilinx's Vivado simulator (xsim), citing issues with encrypted vendor IP simulation, mixed-language support, and persistent simulation bugs.",
    "category": "features",
    "comments": [
      {
        "url": "https://www.reddit.com/r/FPGA/comments/1xdqr68/comment/19rjw26lmi4dc/",
        "depth": 0,
        "score": 12,
        "author": "threespeedlogic",
        "excerpt": "This is currently at the \"I can't believe it works\" stage. So, be gentle.\n\n I've been using XSI/xsim as a simulator for a long time now, and proselytizing c/c++ cosimulation while suffering somewhat under the following mutually incompatible goals:\n\n a lack of stomach for big-3 simulator licensing,\n\n a need to simulate encrypted vendor IP, and\n\n the need to do mixed-language simulation.\n\n You can s",
        "posted_at": "2026-10-23T21:42:30.000Z",
        "author_url": "https://www.reddit.com/user/threespeedlogic/"
      },
      {
        "url": "https://www.reddit.com/r/FPGA/comments/1xdqr68/comment/19rjx7jzrggx0/",
        "depth": 0,
        "score": 5,
        "author": "the_deadpan",
        "excerpt": "This is absolutely bonkers, I don't quite understand how VHPI works for this if you aren't converting xsim-->VHPI-->NVC for every delta cycle (and you probably aren't doing it this way, I will read your blog), but XSIM has long been a bug-bear for me for a long time. I took a different approach and used claude to fuzz-test simulation mocks written in raw vhdl2019 against xilinx behavioural models,",
        "posted_at": "2026-10-23T22:08:16.000Z",
        "author_url": "https://www.reddit.com/user/the_deadpan/"
      },
      {
        "url": "https://www.reddit.com/r/FPGA/comments/1xdqr68/comment/19rkmgpe471r5/",
        "depth": 0,
        "score": 1,
        "author": "cookiedanslesac",
        "excerpt": "I do not understand the c/c++ cosimulation part.\nWhen I hear it, I think about simulating/debugging the c code that is run by the cpu cores in the rtl, but here it just look like xsim build the shared library of the rtl and you just link it with the test harness.",
        "posted_at": "2026-10-24T07:34:28.000Z",
        "author_url": "https://www.reddit.com/user/cookiedanslesac/"
      }
    ],
    "evidence": [
      "[comment u/threespeedlogic] I've been using XSI/xsim as a simulator for a long time now, and proselytizing c/c++ cosimulation while suffering somewhat under the following mutually incompatible goals: a lack of stomach for big-3 simulator licensing, a need to simulate encrypted vendor IP, and the need to do mixed-language simulation.",
      "[comment u/the_deadpan] This is absolutely bonkers, I don't quite understand how VHPI works for this if you aren't converting xsim-->VHPI-->NVC for every delta cycle (and you probably aren't doing it this way, I will read your blog), but XSIM has long been a bug-bear for me for a long time."
    ],
    "link_url": "https://github.com/gsmecher/nvcx",
    "virality": "somewhat_high",
    "post_date": "2026-10-23T21:33:24.000Z",
    "post_kind": "link",
    "sentiment": "mixed",
    "subreddit": "FPGA",
    "event_date": "2026-10",
    "post_flair": [
      "Xilinx Related"
    ],
    "post_title": "nvc + xsim = encrypted IP and, quite possibly, eternal glory",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/FPGA/comments/1xdqr68/nvc_xsim_encrypted_ip_and_quite_possibly_eternal/",
    "entity_role": "vendor",
    "post_author": "threespeedlogic",
    "upvote_ratio": 1,
    "mention_count": 4,
    "mention_surge": true,
    "subreddit_url": "https://www.reddit.com/r/FPGA/",
    "total_upvotes": 39,
    "comments_total": 16,
    "total_comments": 16,
    "event_date_text": "a long time now",
    "post_author_url": "https://www.reddit.com/user/threespeedlogic/",
    "signal_category": "feedback",
    "comments_included": 3,
    "products_mentioned": [
      "xsim",
      "XSI"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.