Mercury Device Configuration
Configuration Scheme Overview
MercuryTM devices support the following configuration schemes:
- Serial - To Conserve Pins
- Passive Serial (PS)
- Uses an external intelligent host such as a PC, an enhanced configuration (EPC) device (PDF), or a microprocessor to control the configuration process synchronously and suppy the configuration data serially to a Mercury device.
- JTAG
- Configures the Mercury device via the IEEE Standard 1149.1 interface.
- Parallel - For Faster Configuration
- Passive Parallel Synchronous(PPS)
- Uses an external intelligent host, such as a PC or microprocessor to control the configuration process synchronously and supply the configuration data in a parallel manor to the Mercury device. Each configuration data byte requires eight
DCLK cycles. The configuration time in the PPS scheme is similar to the configuration time in the PS scheme provided the DCLK frequencies for both schemes are the same.
- Passive Parallel Asynchronous (PPA)
- Uses an external intelligent host, such as a PC or microprocessor, to control the configuration process asynchronously and supply the configuration data in a parallel manor to the Mercury device.
How to Configure Mercury Devices
- For Prototyping or Debugging
- Using Altera Programming Cables
- The Quartus® II programmer supports configuring Mercury devices directly using PS or JTAG interfaces via Altera® programming cables.
- In the Field
Frequently Asked Questions Regarding Mercury Configuration
- What are the configuration file sizes of the EP1M350 and EP1M120 devices?
- Which Altera JTAG-compliant devices offer the optional JTAG IDCODE command?
- How many times can I reprogram or reconfigure an Altera device?
- How can I create a Chain Description File (.cdf) for JRunner use in the Quartus II software?
- What input files are needed by JRunner?
- What are the I/O characteristics of an unconfigured APEXTM-E or Mercury device during boundary-scan test (BST)?
|
Literature
> 
