EP2S130F1020I4 Datasheet, PDF (685/768 Pages) List of Unclassifed Manufacturers – Stratix II Device Handbook, Volume 1

Remote System Upgrades with Stratix II and Stratix II GX Devices
Tables 8–10 and 8–11 describe the input and output ports available on the
altremote_update megafunction. Table 8–12 shows the
param[2..0] bit settings.
Table 8–10. Input Ports of the altremote_update Megafunction (Part 1 of 2)
Port Name
clock
reset
reconfig
reset_timer
read_param
write_param
Require
d
Y
Y
Y
N
N
N
Source
Logic
Array
Logic
Array
Logic
Array
Logic
Array
Logic
Array
Logic
Array
Description
Clock input to the altremote_update block. All operations
are performed with respects to the rising edge of this clock.
Asynchronous reset, which is used to initialize the remote update
block. To ensure proper operation, the remote update block must
be reset before first accessing the remote update block. This
signal is not affected by the busy signal and will reset the remote
update block even if busy is logic high. This means that if the reset
signal is driven logic high during writing of a parameter, the
parameter will not be properly written to the remote update block.
When driven logic high, reconfiguration of the device is initiated
using the current parameter settings in the remote update block.
If busy is asserted, this signal is ignored. This is to ensure all
parameters are completely written before reconfiguration begins.
This signal is required if you are using the watchdog timer feature.
A logic high resets the internal watchdog timer. This signal is not
affected by the busy signal and can reset the timer even when the
remote update block is busy. If this port is left connected, the
default value is 0.
Once read_param is sampled as a logic high, the busy signal
is asserted. While the parameter is being read, the busy signal
remains asserted, and inputs on param[] are ignored. Once the
busy signal is deactivated, the next parameter can be read. If this
port is left unconnected, the default value is 0.
This signal is required if you intend on writing parameters to the
remote update block. When driven logic high, the parameter
specified on the param[] port should be written to the remote
update block with the value on data_in[]. The number of valid
bits on data_in[] is dependent on the parameter type. This
signal is sampled on the rising edge of clock and should only be
asserted for one clock cycle to prevent the parameter from being
re-read on subsequent clock cycles. Once write_param is
sampled as a logic high, the busy signal is asserted. While the
parameter is being written, the busy signal remains asserted, and
inputs on param[] and data_in[] are ignored. Once the busy
signal is deactivated, the next parameter can be written. This
signal is only valid when the Current_Configuration
parameter is factory since parameters cannot be written in
application configurations. If this port is left unconnected, the
default value is 0.
Altera Corporation
January 2008
8–25
Stratix II Device Handbook, Volume 2