FPGA, CPLD, and ASIC solutions from Altera
  • Download Center
  • Literature
Sign in/register
myAltera Account
Welcome
  •   myAltera
  •   Logout
  • Products
    • Devices
    • Design Software
    • Intellectual Property
    • Development Kits/Cables
    • Design & Support Services
    • Literature
  • End Markets
    • Automotive
    • Broadcast
    • Computer & Storage
    • Consumer
    • Industrial
    • Medical
    • Military
    • Test & Measurement
    • Wireless
    • Wireline
  • Technology
    • DSP
    • External Memory
    • Embedded Processing
    • Transceivers
    • Parallel I/O
    • Signal Integrity
    • System Integration
  • Training
    • Training Courses
    • University Program
    • Webcasts & Videos
    • Demonstrations
    • Events Calendar
  • Support
    • Design & Support Resources
    • Knowledge Database
    • Devices
    • Design Software
    • Intellectual Property
    • Development Kits/Cables
    • Design Examples
    • Downloads
    • User Communities/Forums
    • mySupport
  • About Altera
    • About Us
    • Environmental
    • Customer Successes
    • Partners
    • Newsroom
    • Investor Relations
    • Jobs
    • Contact Us
  • Buy Online
    • Devices
    • Design Software
    • Development & Education Kits
    • Cables & Programming Hardware
    • Intellectual Property
  • Entire Site
  • Part Number
  • Knowledge Database
  • Support & Technical Docs
  • Forums & Wiki
Username:  
Password:  
 
Forgot my username or password
Don't have myAltera account? Register Now.
Enter your email address:


Home > Support > Knowledge Database > Support Solution

Solution ID: rd01262005_839
Last Modified: Jul 17, 2007
Product Category: Devices
Product Area: Configuration (FPGA)
Product Sub-area: JTAG

Problem

Why was the CONFIG_IO JTAG instruction introduced in Quartus II programmer version 4.2 when attempting to configure the FPGA over JTAG and are there any consequences with this change?

Solution

Beginning in Quartus® II software version 4.2, the programmer issues the CONFIG_IO instruction before attempting to JTAG configure an FPGA device.

Upon power up, the FPGA attempts to configure from the configuration device. If the configuration fails the FPGA will reset and retry configuration. If configuration continues to fail this will again reset the device and the FPGA will enter an infinite reconfiguration loop.

The only way to break this loop is to shift in the CONFIG_IO instruction over JTAG. The side effect of shifting CONFIG_IO is that it asserts the nCONFIG signal low causing nSTATUS to transition low which could cause a system failure if there is another configuration scheme on the board.

When you use Jam, it does not issue the CONFIG_IO instruction. Jam can be used with the Quartus II programmer in a similar manner as adding a POF file for JTAG.

Related Solutions

  • What is CONFIG_IO?


Feedback

     This solution answers my question:
Strongly Disagree
   
Strongly Agree
 
  1 2 3 4 5  
     This solution was easy to find:          
Strongly Disagree
   
Strongly Agree
 
  1 2 3 4 5  

    Please provide additional feedback to improve support solutions:


Altera does not warrant that this solution will work for the customer's intended purpose and disclaims all liability for use of or reliance on the solution.


  • Altera Troubleshooters
    • Overview
    • Licensing
    • Simulating with ModelSim
    • Timing Analysis
    • PLL Loss of Lock
    • FPGA Configuration
    • JTAG Config & ISP
    • PFL Troubleshooter
    • Jam, JBC and SVF
    • Usage Guidelines
    • Optimization Advisor
    Please Give Us Feedback
    Products | End Markets | Technology | Training | Support | About Altera | Buy Online
    Jobs | Investor Relations | Contact Us | Site Map | Privacy | Legal Notice
    Copyright © 1995-2010 Altera Corporation. All Rights Reserved.
    Altera Forum
    Altera
    Forum
    Twitter
    Twitter
    RSS
    RSS
    Facebook
    Facebook
    Flickr
    Flickr
    YouTube
    YouTube
    Email Updates
    Email
    Updates