element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Ultrazed Hardware Design Programming FPGA problem- bitstream is not compatible with the target revision
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 340 subscribers
  • Views 5779 views
  • Users 0 members are here
Related

Programming FPGA problem- bitstream is not compatible with the target revision

pgielmuda
pgielmuda over 8 years ago

Hi,

I'm doing UltraZed PCIe Carrier Card Tutorial on Vivado V2017.2. Everything went pretty well. I've generated bitsream with vivado and run all off programs till I stucked on 9.3 chapter where I need to program FPGA with generated bitstream. In the SDK there is an error:


09:49:27 ERROR : bitstream is not compatible with the target revision, use -no-revision-check to allow programming

 

When I've tried to program the device with Vivado and I got such error:

 

ERROR: [Labtools 27-3303] Incorrect bitstream assigned to device. Bitstream was generated for part xczu3eg-sfva625-1-i-es1, target device (with IDCODE revision 1) is compatible with production revision bitstreams.
To allow the bitstream to be programmed to the device, use "set_param xicom.use_bitstream_version_check false" tcl command.
 
What does it mean and how to solve it. 
  • Sign in to reply
  • Cancel
  • pgielmuda
    0 pgielmuda over 8 years ago

    Ok, I've managed to program the device with the Vivado. I used proposed tcl command:
    set_param xicom.use_bitstream_version_check false

    and then program the device with the bitstream.

    Now in the SDK I do not program the FPGA and just run the software. The first run of software gives reasonable outcome. I get proper messages from COM port. However if I want to:
    - run the software second time there is an error:

    Error while launching program: 
    Memory write error at 0x0. Cannot read sctlr_el3. Cannot read r0. Instruction transfer timeout
     
    - program the FPGA with vivado there is an error:
    ERROR: [Labtools 27-3165] End of startup status: LOW
    I need to reset whole board to get proper outcome of software another time.  
     
     
    Based on that I have few questions:
    1. do usage of tcl command: set_param xicom.use_bitstream_version_check false is justified, safe and do not influence proper work of MPSoC?
    2. how to apply this command to SDK so that I could program the FPGA from SDK?
    3. should I worry about errors which are in this post above?
    4. is there a way to set up environment (SDK or Vivado) to not encounter all of this problems in the future (to solve the reason of it not just apply the path command)? 
     
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 8 years ago

    Looks like you have a PCIe Carrier Card with production ULtraZed-EG SOM, however, when you followed the tutorial instructions, you created the design for the UltraZed-EG SOM with ES1 silicon. I would suggest the following:

    1) Make sure you have installed the 2017.2 Board Definition Files. These file sets support both the UltraZed-EG SOM with ES1 silicon as well as the UltraZed-EG SOM with the production silicon.

    2) When following the tutorial instructions to create your design, please use the PCIe Carrier Card with Production SOM Board Definition Files (this is documented on page 6 of the tutorial PDF).

    3) Once you complete the above steps, you should not need any TCL commands to configure the device in SDK.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
  • pgielmuda
    0 pgielmuda over 8 years ago

    Yes you are right. However the reason of problem was associated with the board definition that you give with tutorial packs. The are only ES versions. I used them as default input and didn't know that there are any production version definition board. Maybe it is worth to add all of those board definition to tutorial pack? For people who starts their work with these boards it could be much easier to find appropriate one  :). 

    Regards. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube