{"id":16940,"date":"2022-02-18T14:34:15","date_gmt":"2022-02-18T19:34:15","guid":{"rendered":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/?p=16940"},"modified":"2026-03-27T08:48:47","modified_gmt":"2026-03-27T12:48:47","slug":"fpga-retargeting","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/2022\/02\/18\/fpga-retargeting\/","title":{"rendered":"FPGA Retargeting"},"content":{"rendered":"\n<p>FPGA retargeting is an essential element of supply\u2013chain agility in a world without traditional second\u2013sourcing. Since the 1980s, second\u2013sourcing has disappeared to improve supply chain efficiency. Today&#8217;s highly\u2013optimized supply chain has worked well. That is until the pandemic disrupted it.<\/p>\n\n\n\n<p>FPGA retargeting is one response to supply\u2013chain difficulties. By creating new versions of a board using different FGPAS, engineers deliver the flexibility to navigate supply\u2013chain issues. The challenge is retargeting the design to a new FPGA without changing its behavior.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"fpga-retargeting-is-more-than-resynthesizing\"><a>FPGA retargeting is more than resynthesizing<\/a><\/h2>\n\n\n\n<p>Retargeting FPGAs would be easy if designers used only RTL. In that case, we&#8217;d retarget resynthesizing in a different vendor&#8217;s tool flow. However, FPGA designers usually take advantage of vendor\u2013supplied design IP by dragging and dropping blocks into a schematic and connecting them with custom RTL.<\/p>\n\n\n\n<p>Design IP tied to a specific FPGA vendor or a specific FPGA model means that we cannot simply resynthesize a design. We must create a new version of the design using a new library of IP and then connect our custom RTL to it. How do you verify that the two designs are identical?<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"fpga-retargeting-verification-goal\">FPGA retargeting verification goal<\/h2>\n\n\n\n<p><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Ensure that the netlist matches the original RTL.<\/li><li>Modify the RTL using the new chip&#8217;s design IP.<\/li><li>Ensure that the new RTL matches the new netlist.<\/li><\/ul>\n\n\n\n<figure class=\"wp-block-image size-large is-style-default\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"506\" src=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/54\/2022\/02\/fpga-retargeting-1024x506.png\" alt=\"FPGA retargeting flow\" class=\"wp-image-16959\" srcset=\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/54\/2022\/02\/fpga-retargeting-1024x506.png 1024w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/54\/2022\/02\/fpga-retargeting-600x296.png 600w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/54\/2022\/02\/fpga-retargeting-768x379.png 768w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/54\/2022\/02\/fpga-retargeting-1536x758.png 1536w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/54\/2022\/02\/fpga-retargeting-2048x1011.png 2048w, https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/54\/2022\/02\/fpga-retargeting-900x444.png 900w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption>FPGA retargeting verification<\/figcaption><\/figure>\n\n\n\n<p>One approach to solving this problem is to assume that the RTL and the netlists match and run the RTL against a simulation testbench. This assumes that the testbench has complete coverage and that its stimulus addresses all corner cases. Simulation is a good verification solution, but it doesn&#8217;t provide gap\u2013free assurance that both FPGAs match.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"fpga-retargeting-verification-1\">FPGA retargeting verification webinar<\/h2>\n\n\n\n<p>Another approach to verifying a retargeted design is to prove that the netlists are identical to the RTL and then prove that RTL for each FPGA delivers identical functionality.<\/p>\n\n\n\n<p>The webinar <em>Overcoming Today\u2019s Verification, Supply Chain, and Legacy Technology Challenge Associated with FPGA\u2013based Designs<\/em> will show you how to deliver gap\u2013free FPGA retargeting verification.<\/p>\n\n\n\n<p>The webinar will outline the verification solutions and retargeting solutions that deliver a solution to deal with FPGA supply chain issues and to extend the life of legacy designs powered by old or obsolete FPGAs. A workflow and methodology will be provided for each scenario, along with real\u2013world case studies.<\/p>\n\n\n\n<p><strong>What You Will Learn:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>The challenges facing FPGA\u2013based designers<\/li><li>Mitigating FPGA supply chain shortages and legacy design dilemma<\/li><li>The verification strategies to ensure FPGA\u2013based designs have zero bug escapes<\/li><\/ul>\n\n\n\n<p><strong>Who Should Attend:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Design and Verification Engineers and Managers using FPGAs<\/li><li>Program Managers and Systems Developers<\/li><\/ul>\n\n\n\n<p><h4><strong>The webinar recording is now available <a href=\"https:\/\/verificationacademy.com\/sessions\/overcoming-todays-verification-supply-chain-and-legacy-technology-challenges-associated-fpga-based-designs\" target=\"_blank\" rel=\"noopener\">on-demand<\/a><\/strong>.<\/h4><\/p>\n","protected":false},"excerpt":{"rendered":"<p>FPGA retargeting is an essential element of supply\u2013chain agility in a world without traditional second\u2013sourcing. Since the 1980s, second\u2013sourcing has&#8230;<\/p>\n","protected":false},"author":74314,"featured_media":16945,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[],"industry":[],"product":[],"coauthors":[947],"class_list":["post-16940","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"featured_image_url":"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/54\/2022\/02\/Futuristic-Chip-on-Board.jpg","_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/16940","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/users\/74314"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/comments?post=16940"}],"version-history":[{"count":5,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/16940\/revisions"}],"predecessor-version":[{"id":16986,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/16940\/revisions\/16986"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/media\/16945"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/media?parent=16940"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/categories?post=16940"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/tags?post=16940"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/industry?post=16940"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/product?post=16940"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/coauthors?post=16940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}