presto_en.pdf - 第91页
Page 91 RUNTEST timing multiply (both SVF and XSVF): 25% RUNTEST w ith run_count and no timing (both SVF and XSVF): int erpret as R UNTEST min_ time with scale 1MHz VPP P RESTO / P FORTE pin usage while running test (fi…
Page 90
• The RUNTEST command containing run_count and
specifying min_time is executed at the currently
running TCK frequency. Therefore the command can
take much more time than what is specified in
min_time.
• The RUNTEST command containing run_count and
specifying max_time is executed at the currently
running TCK frequency. As the programmer cannot
respect the “deadline” specified in the max_time
parameter, this parameter is ignored.
8.2.6 VPP PRESTO / P
FORTE pin usage
while running test
(file) / after test
completion
The selection of the VPP / P pin function: TRST or SCK as
described in the SVF file or user-defined output levels.
(This is useful to keep the device in the reset state during
file execution.)
8.2.7 Default Settings
The JTAG Player features several default settings intended
primarily for use in connection with FORTE, but not with
PRESTO. Feel free to change these settings if the default
values do not suit your application.
Default Settings for FPGAs
Default TCK frequency: 15MHz; Ignore FREQUENCY
commands
Fast Clock Option (FORTE only): 5MHz and above
RUNTEST without run_count (SVF only): default
speed clock on TCK
RUNTEST timing multiply (both SVF and XSVF): 0%
RUNTEST with run_count and no timing (both SVF
and XSVF): interpret as RUNTEST min_time with scale
1MHz
VPP PRESTO / P FORTE pin usage while running test
(file): Tristate
VPP PRESTO / P FORTE pin usage after test
completion: Tristate
Default Settings for XC9500
Default TCK frequency: 5MHz; Ignore FREQUENCY
commands
Fast Clock Option (FORTE only): 5MHz and above
RUNTEST without run_count (SVF only): slow clock
on TCK (~100kHz)
RUNTEST timing multiply (both SVF and XSVF):
100%
RUNTEST with run_count and no timing (both SVF
and XSVF): interpret as RUNTEST min_time with scale
1MHz
VPP PRESTO / P FORTE pin usage while running test
(file): Tristate
VPP PRESTO / P FORTE pin usage after test
completion: Tristate
Default Settings for AVR:
Default TCK frequency: 1MHz; Ignore FREQUENCY
commands
Fast Clock Option (FORTE only): 5MHz and above
RUNTEST without run_count (SVF only): default
speed clock on TCK
Page 91
RUNTEST timing multiply (both SVF and XSVF):
25%
RUNTEST with run_count and no timing (both SVF
and XSVF): interpret as RUNTEST min_time with scale
1MHz
VPP PRESTO / P FORTE pin usage while running test
(file): Tristate
VPP PRESTO / P FORTE pin usage after test
completion: Tristate
8.3
Running JTAG Player
from Command Line
SVF & XSVF JTAG Player can be run from the command
line for more comfort especially during debugging. The
following parameters apply:
jtagplay.exe [-p] [-f filename] [-i inifile] [-
c] [-cc] [-s serial]
-p automatically executes the file specified in
the -f filename parameter
-f filename specifies SVF / XSVF file to be executed
-i inifile ini file containing settings
-c closes the program if the file has been
executed without errors
-cc closes the program even if the file has been
executed with error(s)
-s serial uses PRESTO or FORTE programmer of the
specified serial number, when instead of
the serial number there is the "-" (dash)
sign, it will use any connected programmer
regardless of its serial number
-forte uses FORTE, not PRESTO
Return Codes
The jtagplay.exe program returns the following return
codes:
0 execution of the last file had no errors
1 an error occurred during execution of the
last file
2 execution of the last file could not be
started
Page 92
9
MultiUP
MultiUP is utility usable for programming with up to 4
ASIX programmers at once. MultiUP uses program UP.
The utility is installed together with the UP program.
MultiUP can simply, using one button, run programming
of selected task, which is deffined with the UP program
project and other settings.
To increase speed the utility loads the programming data
only once, it is suitable for using in production.
9.1
Programming settings
In the "Options/Programming settings" it is possible to
select programmers to be used, UP program project to be
programmed, whether they will program the common
way or using the differential programming and the
memories to be programmed.
To improve clarity it is possible to select a name for each
of the programmers.
Each of the programmers can program a different project
or all of them can be the same project.
All of the programmers do not have to be of the same
type (PRESTO, FORTE), but the selected project have to
use the same type of the programmer.
In the Options it is also possible to select Keyboard
shortcuts for running work of the praticular programmers
and to set the console saving during the program closing.
The parameters configured in the Options can be used
once or they can be saved to MPPR file for other using.
9.2
Programming
For programming of predefined tasks it is advisable to
open MultiUP project file in menu "File/Open MPPR file".
The project can be crated in the "Options" menu.
Afterwards the particular programmings can be run
separately using the "Run" button on the appropriate
programmer panel or all the active programmings can be
run at once using the "Run all" button, eventually the
associated keyboard shortcuts can be used.
9.3
CommandLine
It is possible to provide the MPPR project path on the
commandline, it will be loaded on the utility start.
Example:
multiup.exe C:\data\project.mppr