8–4 Chapter 8: Configuration and Remote System Upgrades in Cyclone IV Devices
Configuration
Cyclone IV Device Handbook, May 2013 Altera Corporation
Volume 1
Power-On Reset (POR) Circuit
The POR circuit keeps the device in reset state until the power supply voltage levels
have stabilized during device power up. After device power up, the device does not
release nSTATUS until V CCINT, V CCA , and V CCIO (for I/O banks in which the
configuration and JTAG pins reside) are above the POR trip point of the device.
V CCINT and V CCA are monitored for brown-out conditions after device power up.
1 V CCA is the analog power to the phase-locked loop (PLL).
In some applications, it is necessary for a device to wake up very quickly to begin
operation. Cyclone IV devices offer the fast POR time option to support fast wake-up
time applications. The fast POR time option has stricter power-up requirements when
compared with the standard POR time option. You can select either the fast option or
the standard POR option with the MSEL pin settings.
1 If your system exceeds the fast or standard POR time, you must hold nCONFIG low
until all the power supplies are stable.
f For more information about the POR specifications, refer to the Cyclone IV Device
Datasheet.
f For more information about the wake-up time and POR circuit, refer to the Power
Requirements for Cyclone IV Devices chapter.
Power Up
If the device is powered up from the power-down state, V CCINT, V CCA , and V CCIO (for
the I/O banks in which the configuration and JTAG pins reside) must be powered up
to the appropriate level for the device to exit from POR.
Reset
After power up, Cyclone IV devices go through POR. POR delay depends on the MSEL
pin settings, which correspond to your configuration scheme. During POR, the device
resets, holds nSTATUS and CONF_DONE low, and tri-states all user I/O pins (for PS and
FPP configuration schemes only).
1 To tri-state the configuration bus for AS and AP configuration schemes, you must tie
nCE high and nCONFIG low.
The user I/O pins and dual-purpose I/O pins have weak pull-up resistors, which are
always enabled (after POR) before and during configuration. When the device exits
POR, all user I/O pins continue to tri-state. While nCONFIG is low, the device is in
reset. When nCONFIG goes high, the device exits reset and releases the open-drain
nSTATUS pin, which is then pulled high by an external 10-k pull-up resistor. After
nSTATUS is released, the device is ready to receive configuration data and the
configuration stage starts.
f For more information about the value of the weak pull-up resistors on the I/O pins
that are on before and during configuration, refer to the Cyclone IV Device Datasheet
chapter.
Configuration
Configuration data is latched into the Cyclone IV device at each DCLK cycle. However,
the width of the data bus and the configuration time taken for each scheme are
different. After the device receives all the configuration data, the device releases the
open-drain CONF_DONE pin, which is pulled high by an external 10-kpull-up resistor.
A low-to-high transition on the CONF_DONE pin indicates that the configuration is
complete and initialization of the device can begin.
Chapter 8: Configuration and Remote System Upgrades in Cyclone IV Devices 8–7
Configuration
May 2013 Altera Corporation Cyclone IV Device Handbook,
Volume 1
You can begin reconfiguration by pulling the nCONFIG pin low. The nCONFIG pin must
be low for at least 500 ns. When nCONFIG is pulled low, the Cyclone IV device is reset.
The Cyclone IV device also pulls nSTATUS and CONF_DONE low and all I/O pins are
tri-stated. When nCONFIG returns to a logic-high level and nSTATUS is released by the
Cyclone IV device, reconfiguration begins.
Configuration Error
If an error occurs during configuration, Cyclone IV devices assert the nSTATUS signal
low, indicating a data frame error and the CONF_DONE signal stays low. If the
Auto-restart configuration after error option (available in the Quartus II software in
the General tab of the Device and Pin Options dialog box) is turned on, the
Cyclone IV device releases nSTATUS after a reset time-out period (a maximum of
230 s), and retries configuration. If this option is turned off, the system must monitor
nSTATUS for errors and then pulse nCONFIG low for at least 500 ns to restart
configuration.
Initialization
In Cyclone IV devices, the initialization clock source is either the internal oscillator or
the optional CLKUSR pin. By default, the internal oscillator is the clock source for
initialization. If you use the internal oscillator, the device provides itself with enough
clock cycles for proper initialization. When using the internal oscillator, you do not
have to send additional clock cycles from an external source to the CLKUSR pin during
the initialization stage. Additionally, you can use the CLKUSR pin as a user I/O pin.
You also have the flexibility to synchronize initialization of multiple devices or to
delay initialization with the CLKUSR option. The CLKUSR pin allows you to control
when your device enters user mode for an indefinite amount of time. You can turn on
the Enable user-supplied start-up clock (CLKUSR) option in the Quartus II software
in the General tab of the Device and Pin Options dialog box. When you turn on the
Enable user supplied start-up clock option (CLKUSR) option, the CLKUSR pin is the
initialization clock source. Supplying a clock on the CLKUSR pin does not affect the
configuration process. After the configuration data is accepted and CONF_DONE goes
high, Cyclone IV devices require 3,192 clock cycles to initialize properly and enter
user mode.
1 If you use the optional CLKUSR pin and the nCONFIG pin is pulled low to restart
configuration during device initialization, ensure that the CLKUSR pin continues to
toggle when nSTATUS is low (a maximum of 230 s).
На это похоже?
Auto-restart configuration after error option (available in the Quartus II software in
the General tab of the Device and Pin Options dialog box) is turned on, the
Cyclone IV device releases nSTATUS after a reset time-out period (a maximum of
230 s), and retries configuration. If this option is turned off, the system must monitor
nSTATUS for errors and then pulse nCONFIG low for at least 500 ns to restart
configuration
в конце концов, раз уж всё уже меняли, попробуйте подкинуть другой генератор..
HantekMaster
新手上路
|
Go to Page No.
1#
Edited by HantekMaster at 2017-5-2 03:26
Hello there, I bought a DSO5102P that came with firmware 3.40.0(161227.0) and tried to do a self calibration. I ‘ve got the following error message at step 29/38: Self calibration failed, error: 0x10802 I upgraded the firmware to the latest version 3.40.0(170318.0) and getting the same error message. HW version: 1010xffff8108 Any idea what the problem could be? Thanks Related collections:
|
|||
|
||||
Reply
Use magic Report |
||||
ramazzot2009@ho
新手上路
|
7#
Good afternoon. Translated by Google Translate |
|||
Reply Support Not support Use magic Report |
||||
HANTEK DSO5102P |
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
|
|
Все права на контент принадлежат участникам создавшим его. Частичное копирование возможно, только со ссылкой на первоисточник !!!
Статистика сайта
Последние темы | Читаемые темы | Лучшие пользователи | Новые пользователи | ||||||||||
Новые Файлы | Новые Прошивки | Новые Статьи, Блоги | Счетчики для пользователей | ||||||||||
|
|||||||||||||
Новые сайты | Новые Мастера в Вашем городе | Последние Новости | Участники прошедшие тест | ||||||||||
Attached information
Application software
Driver
User’s manual
The latest firmware
SDK
DPO6004B(C)/MPO6004D Firmware
2022-11-19
DSO2000 Firmware
2022-11-14
DPO6002B(C)/MPO6002D Firmware
2022-02-12
DSO4004B Firmware
2021-12-13
DSO4004C Firmware
2021-12-13
DSO5072P Firmware
2021-02-25
DSO5102P Firmware
2021-02-25
DSO5202P Firmware
2021-02-25
DSO4072C Firmware
2020-07-22
DSO4102C Firmware
2020-07-22
DSO4202C Firmware
2020-07-22
DSO5202B Firmware
2013-04-07
DSO5102B Firmware
2013-04-07
DSO5062B Firmware
2013-04-07
DSO5202BM Firmware
2013-04-07
DSO5102BM Firmware
2013-04-07
- < First
- < Prev
- 1
- 2
- Next >
- Last >