Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 258 to 256 | ||||||||
lt 5 would generate 5 bursts) but it does not start to run | ||||||||
Changed: | ||||||||
< < | continuously unless you enter lt e . To stop continuous triggers, enter lt d . | |||||||
> > | continuously unless you enter lt c . To stop continuous triggers, enter lt d . | |||||||
rg (general reset) | ||||||||
Line: 508 to 500 | ||||||||
dump (wu): dump registers in Mr. Wu's format to .txt file with a status (st) command at the end Usage: | ||||||||
Changed: | ||||||||
< < | wu OR wu | |||||||
> > | wu OR wu | |||||||
NOTE: as of this writing (2021-10-05) the command silently fails if the current directory is not writeable. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 200 to 201 | ||||||||
| ||||||||
Deleted: | ||||||||
< < | ||||||||
The burst parameter is ignored in random mode. The maximum rate which can be specified is about 1MHz but the trigger rules limit it to less than that unless they are disabled (see below). The low 4 bits of the specified rate are ignored (use value is divided by 16, written to a register, and then multiplied by 16 in the firmware). | ||||||||
Changed: | ||||||||
< < | Note that CMS "standard" trigger rules are applied. Individual rules may be disabled, see Local_L1A_Generator. | |||||||
> > | Note that CMS "standard" trigger rules are applied. Individual rules may be disabled, see Local_L1A_Generator. | |||||||
| ||||||||
Line: 503 to 508 | ||||||||
dump (wu): dump registers in Mr. Wu's format to .txt file with a status (st) command at the end Usage: | ||||||||
Changed: | ||||||||
< < | wu OR wu | |||||||
> > | wu OR wu | |||||||
-- EricHazen - 18 Oct 2014 \ No newline at end of file |
Line: 1 to 1 | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||
Line: 207 to 207 | |||||||||||||||||||||
Note that CMS "standard" trigger rules are applied. Individual rules may be disabled, see Local_L1A_Generator. | |||||||||||||||||||||
Added: | |||||||||||||||||||||
> > |
| ||||||||||||||||||||
setOcrCommand (set orbit count reset TTC command)Specify the TTC command to use for orbit count reset. Note that the low |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 51 to 52 | ||||||||
A script file may be created with a list of AMC13Tool2 commands. A script may be executed in two ways: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
After executing a script the tool will normally return to interactive mode. If you wish the tool to exit (e.g. so you can run scripts from within a shell script) just terminate the script with the command quit. | ||||||||
Line: 60 to 61 | ||||||||
Interactive ModeThe tool will enter interactive mode after executing any scripts specified. A &Launcher::AMC13VerifyFlashHeader, | ||||||||
Changed: | ||||||||
< < | "*>* prompt is displayed. Type h for a list of commands. Type h <command> for detailed help, or h * for detailed | |||||||
> > | "*>* prompt is displayed. Type h for a list of commands. Type h <command> for detailed help, or h * for detailed | |||||||
help on all commands. Generally, interactive commands consist of a command word followed by | ||||||||
Line: 75 to 76 | ||||||||
Tab completion is particularly useful for command words and address table entries. Wildcards are permitted in address table entries in certain cases. | ||||||||
Changed: | ||||||||
< < | For example, the command readT1 stat*ttc*err* will read and | |||||||
> > | For example, the command readT1 stat*ttc*err* will read and | |||||||
display all address table entries matching the expression with wildcards. | ||||||||
Changed: | ||||||||
< < | Wildcards are simple shell-style by default, where * matches any string. | |||||||
> > | Wildcards are simple shell-style by default, where * matches any string. | |||||||
An argument may be preceded with the string perl: to force full perl-style regular expression matching. | ||||||||
Line: 111 to 112 | ||||||||
List all connected AMC13 modules with firmware version, serial number and IP addresses. The module currently accepting commands is marked | ||||||||
Changed: | ||||||||
< < | with a - character. | |||||||
> > | with a - character. | |||||||
For example: | ||||||||
Changed: | ||||||||
< < |
>list | |||||||
> > | >list | |||||||
Connected AMC13s *0: SN: 86 T1v: 0211 T2v: 0021 cf: 192.168.1.82 1: SN: 82 T1v: 4007 T2v: 0021 cf: 192.168.1.90 | ||||||||
Line: 158 to 156 | ||||||||
Will correctly reset the T1 board.
i (en) <inputs> <options> (initialize AMC13 for data taking) | ||||||||
Changed: | ||||||||
< < |
i (en) : Initialize AMC13 | |||||||
> > | i (en) : Initialize AMC13 | |||||||
Usage: | ||||||||
Changed: | ||||||||
< < | i | |||||||
> > | i | |||||||
inputs: list of inputs e.g. '1-12' '*' enables all inputs which show AMC link ready options: T to enable loop-back TTC on TTS output fiber | ||||||||
Line: 172 to 168 | ||||||||
Using "F" will cause fake data of size determined by the T1 register CONF.AMC.FAKE_DATA_SIZE ( addr 0x18 ) to appear to come from the AMC slots given in the list of inputs. The list of inputs is comma delimited with no spaces, and you can use single numbers( 2,7,10 ), inclusive ranges indicated with a hyphen ( 1-7 ), or a combination of the two ( 1-3,5,7,9-12). | ||||||||
Changed: | ||||||||
< < | When using multiple event builders ( >daq 2 for example ), you must enable at least one AMC slot for each SFP channel. See the daq command for more info. | |||||||
> > | When using multiple event builders ( >daq 2 for example ), you must enable at least one AMC slot for each SFP channel. See the daq command for more info. | |||||||
daq <config> (configure DAQ fiber output) | ||||||||
Line: 185 to 181 | ||||||||
| ||||||||
Changed: | ||||||||
< < | Enter 'L' after number of DAQs to enable local mode (using local triggers). Example: >daq 2 L . | |||||||
> > | Enter 'L' after number of DAQs to enable local mode (using local triggers). Example: >daq 2 L . | |||||||
When initializing AMCs, at least one AMC from each SFP channel must be initialized. | ||||||||
Line: 205 to 201 | ||||||||
| ||||||||
Added: | ||||||||
> > | The burst parameter is ignored in random mode. | |||||||
Added: | ||||||||
> > | The maximum rate which can be specified is about 1MHz but the trigger rules limit it to less than that unless they are disabled (see below). The low 4 bits of the specified rate are ignored (use value is divided by 16, written to a register, and then multiplied by 16 in the firmware). Note that CMS "standard" trigger rules are applied. Individual rules may be disabled, see Local_L1A_Generator. | |||||||
setOcrCommand (set orbit count reset TTC command) | ||||||||
Line: 224 to 224 | ||||||||
This command sets the parameters for capture of selected events in the SDRAM
buffer for readout over IPBus using the commands re and df or other means. | ||||||||
Changed: | ||||||||
< < |
mode: 0 for simple prescale (record every n events, n from 1...0x10000) | |||||||
> > | mode: 0 for simple prescale (record every n events, n from 1...0x10000) | |||||||
1 to match EvN with n low bits =0 where n from 5..20 factor: if mode=0, 1...0x10000 if mode=1, 5..20 | ||||||||
Line: 275 to 272 | ||||||||
Option "D" provides debugging output. For example: | ||||||||
Changed: | ||||||||
< < |
>nodes t1 *ttc*error* | |||||||
> > | >nodes t1 *ttc*error* | |||||||
9 nodes matched 0: STATUS.TTC.BCNT_ERROR chip_type: specifies firmware file suffix denoting T2 chip type (addr=00000000 mask=00000040) r 1: STATUS.TTC.BCNT_ERRORS_HI (addr=00000045 mask=0000ffff) r | ||||||||
Line: 288 to 283 | ||||||||
6: STATUS.TTC.SGL_BIT_ERROR (addr=00000000 mask=00000080) r 7: STATUS.TTC.SGL_BIT_ERRORS_HI (addr=00000041 mask=0000ffff) r 8: STATUS.TTC.SGL_BIT_ERRORS_LO (addr=00000040 mask=ffffffff) r | ||||||||
Changed: | ||||||||
< < | > | |||||||
> > | > | |||||||
Verbose option to display descriptions: | ||||||||
Changed: | ||||||||
< < |
>nodes t1 status*tts_state v | |||||||
> > | >nodes t1 status*tts_state v | |||||||
2 nodes matched 0: STATUS.AMC_TTS_STATE (addr=00000019 mask=001f0000) r encoded TTS from enabled AMCs 1: STATUS.T1_TTS_STATE (addr=00000019 mask=0000f000) r Current T1 overall TTS state | ||||||||
Changed: | ||||||||
< < | > | |||||||
> > | > | |||||||
re <all> (read/display event from SDRAM) | ||||||||
Line: 324 to 317 | ||||||||
The file format is defined as a list of 64-bit words in little-endian byte order as follows. See AMC13CommonFirmwareProposal for detailed description of AMC13 payload format. | ||||||||
Changed: | ||||||||
< < |
badc0ffeebadcafe magic number present at start of each event | |||||||
> > | badc0ffeebadcafe magic number present at start of each event | |||||||
cccccccccccccccc size of event in 64-bit words 510000781f412308 CMS common data format header 104101401a540110 AMC13 header, specifying 4 AMCs | ||||||||
Line: 337 to 328 | ||||||||
ttc <options> (control TTC history capture) | ||||||||
Changed: | ||||||||
< < |
Usage: | |||||||
> > | Usage: | |||||||
ttc h on - ttc history enable ttc h off - ttc history disable ttc h clr - ttc history clear | ||||||||
Changed: | ||||||||
< < | ttc h d | |||||||
> > | ttc h d - ttc history display items or all | |||||||
ttc f on - ttc filter enable ttc f off - ttc filter disable ttc f clr - ttc filter clear | ||||||||
Changed: | ||||||||
< < | ttc f s ! | |||||||
> > | ttc f s ! ! - set TTC filter list item is item 0-15 to set is value to match for filtering commands is bits to ignore when filtering commands | |||||||
ttc f list - list currently-defined filters | ||||||||
Changed: | ||||||||
< < | ttc f ena | |||||||
> > | ttc f ena - enable specific filter by number ttc f dis - disable specific filter by number | |||||||
The TTC history capture must be enabled with ttc h on . Using the default settings (no filters) the history will fill with BC0 commands. To set up a filter to ignore BC0, use the following command: | ||||||||
Changed: | ||||||||
< < |
> ttc f s 1 0xfe | |||||||
> > | > ttc f s 1 0xfe | |||||||
For example: | ||||||||
Changed: | ||||||||
< < |
[hazen@cms4 amc13]$ AMC13Tool2.exe -c 192.168.1.176 | |||||||
> > | [hazen@cms4 amc13]$ AMC13Tool2.exe -c 192.168.1.176 | |||||||
... | ||||||||
Changed: | ||||||||
< < | >en 1-4 f t | |||||||
> > | >en 1-4 f t | |||||||
parsed list "1-4" as mask 0xf Enabling fake data Enabling TTS as TTC for loop-back AMC13 out of run mode AMC13 is back in run mode and ready | ||||||||
Changed: | ||||||||
< < | >ttc h on (turn on TTC history) >ttc h d 5 (display 5 commands) | |||||||
> > | >ttc h on (turn on TTC history) >ttc h d 5 (display 5 commands) | |||||||
History buffer has 512 entries NOTE: TTC history capture disabled before readout Cmd --Orbit- BcN --EvN- | ||||||||
Line: 383 to 368 | ||||||||
2: 01 0003cf50 dea 000001 3: 01 0003cf51 dea 000001 4: 01 0003cf52 dea 000001 | ||||||||
Changed: | ||||||||
< < | >ttc f s 0 0x01 0xfe (set filter item 0 to 0x01 with mask 0xfe) >ttc f on (turn on filtering) >ttc h clr (clear the history) >ttc h on (turn history back on) >ttc h d 5 (display 5 entries) | |||||||
> > | >ttc f s 0 0x01 0xfe (set filter item 0 to 0x01 with mask 0xfe) >ttc f on (turn on filtering) >ttc h clr (clear the history) >ttc h on (turn history back on) >ttc h d 5 (display 5 entries) | |||||||
History buffer has 0 entries | ||||||||
Changed: | ||||||||
< < | >ttc h on (turn history back on) >wv ACTION.LOCAL_TRIG.SEND_OCR (send OcR command) >wv ACTION.LOCAL_TRIG.SEND_OCR (twice for fun) >ttc h d 5 (display 5 entries) | |||||||
> > | >ttc h on (turn history back on) >wv ACTION.LOCAL_TRIG.SEND_OCR (send OcR command) >wv ACTION.LOCAL_TRIG.SEND_OCR (twice for fun) >ttc h d 5 (display 5 entries) | |||||||
History buffer has 2 entries NOTE: TTC history capture disabled before readout Cmd --Orbit- BcN --EvN- 0: 28 00021c6b a17 000001 1: 28 000203d5 b65 000001 | ||||||||
Changed: | ||||||||
< < | >ttc f list (list the items being filtered) | |||||||
> > | >ttc f list (list the items being filtered) | |||||||
Item Ena CMD Mask
| ||||||||
Changed: | ||||||||
< < | > | |||||||
> > | > | |||||||
The detailed documentation for the following commands hasn't been written yet, but in general they should be used only by expert users. | ||||||||
Changed: | ||||||||
< < |
vfh : verify flash header -- vfh OR vfh | |||||||
> > | vfh : verify flash header -- vfh OR vfh <chip_type> vbs : verify flash golden -- vbs OR vbs <chip_type> vs : verify flash spartan -- vs OR vs <chip_type> vv (vk) : verify flash virtex/kintex -- vv OR vv <chip_type> pfh : program flash header -- pfh OR pfh <chip_type> pbs : program flash golden -- pbs OR pbs <chip_type> ps : program flash spartan -- ps OR ps <chip_type> pv (pk) : program flash virtex/kintex -- pv OR pv <chip_type> | |||||||
status (st) : Display AMC13 Status usage: | ||||||||
Changed: | ||||||||
< < | status | |||||||
> > | status table_name | |||||||
level from 1..9 with 1 being least verbose (99 displays everything) table_name limits the display to the table named statusHTML : Display AMC13 status in basic HTML format usage: | ||||||||
Changed: | ||||||||
< < | statusHTML | |||||||
> > | statusHTML table_name | |||||||
level from 1..9 with 1 being least verbose (99 displays everything) table_name limits the display to the table named openStatusFile : Open a text file to stream status info to | ||||||||
Line: 453 to 437 | ||||||||
vfh: verify flash header
Usage:
vfh OR vfh | ||||||||
Changed: | ||||||||
< < | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
> > | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
vbs (Verify Backup Spartan, e.g. Golden)vbs: verify flash backup spartan (golden) \n" \ Usage: vbs OR vbs <chip_type> | ||||||||
Changed: | ||||||||
< < | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
> > | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
vs (Verify Spartan, e.g. T2)vs: verify flash spartan Usage: vs OR vs <chip_type> | ||||||||
Changed: | ||||||||
< < | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
> > | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
vk (or vv) (Verify Kintex/Virtex, e.g. T1)vv: verify flash virtex/kintex Usage: vv OR vv <chip_type> | ||||||||
Changed: | ||||||||
< < | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
> > | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
pfh (Program Flash Header)pfh: program flash header\n" \ Usage:\n" \ pfh OR pfh <chip_type>\n" \ | ||||||||
Changed: | ||||||||
< < | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
> > | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
pbs (Program Backup Spartan, e.g. Golden)pbs: program flash backup spartan (golden) Usage: pbs OR pbs <chip_type> | ||||||||
Changed: | ||||||||
< < | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
> > | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
ps (Program Spartan, e.g. T2)ps: program flash spartan Usage: ps OR ps <chip_type> | ||||||||
Changed: | ||||||||
< < | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
> > | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
pk (or pv) (Program Kintex/Virtex, e.g. T1)pv: program flash virtex/kintex Usage: pv OR pv <chip_type> | ||||||||
Changed: | ||||||||
< < | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
> > | chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
reconfigureFPGAs (reconfigure FPGAs from flash)Troubleshooting | ||||||||
Line: 512 to 488 | ||||||||
dump (wu): dump registers in Mr. Wu's format to .txt file with a status (st) command at the end Usage: | ||||||||
Changed: | ||||||||
< < | wu OR wu | |||||||
> > | wu OR wu | |||||||
-- EricHazen - 18 Oct 2014 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 347 to 347 | ||||||||
ttc f on - ttc filter enable ttc f off - ttc filter disable ttc f clr - ttc filter clear | ||||||||
Changed: | ||||||||
< < | ttc f s | |||||||
> > | ttc f s ! | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 170 to 170 | ||||||||
N to leave AMC13 out of run mode after initialization | ||||||||
Added: | ||||||||
> > | Using "F" will cause fake data of size determined by the T1 register CONF.AMC.FAKE_DATA_SIZE ( addr 0x18 ) to appear to come from the AMC slots given in the list of inputs. The list of inputs is comma delimited with no spaces, and you can use single numbers( 2,7,10 ), inclusive ranges indicated with a hyphen ( 1-7 ), or a combination of the two ( 1-3,5,7,9-12).
When using multiple event builders ( >daq 2 for example ), you must enable at least one AMC slot for each SFP channel. See the daq command for more info. | |||||||
daq <config> (configure DAQ fiber output)This command sets the configuration for the DAQ fiber (aka S-Link express, DAQLSC) outputs. | ||||||||
Line: 183 to 187 | ||||||||
Enter 'L' after number of DAQs to enable local mode (using local triggers). Example: >daq 2 L .
| ||||||||
Added: | ||||||||
> > | When initializing AMCs, at least one AMC from each SFP channel must be initialized. | |||||||
Note: recommend doing 'rd' (daq reset) after changing configuration
fed <link_no> <id> |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 500 to 500 | ||||||||
reconfigureFPGAs (reconfigure FPGAs from flash) | ||||||||
Added: | ||||||||
> > | Troubleshootingdump (wu) (dump register values in Mr. Wu's format)dump (wu): dump registers in Mr. Wu's format to .txt file with a status (st) command at the end Usage: wu OR wu <filename> OR wu <status_verbosity_level> OR wu <filename> <status_verbosity_level> | |||||||
-- EricHazen - 18 Oct 2014 |
Line: 1 to 1 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Line: 12 to 12 | ||||||||||
| ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
Startup | ||||||||||
Line: 26 to 26 | ||||||||||
Use the -c argument to specify AMC13 modules to communicate with. | ||||||||||
Changed: | ||||||||||
< < | IP Address | |||||||||
> > | IP Address or Serial Number | |||||||||
The argument after -c may be a numeric I/P address, in the standard form e.g. 192.168.1.120 , or simply the serial number e.g. 67 . | ||||||||||
Changed: | ||||||||||
< < | To specify the control hub protocol, append /c e.g. 192.168.1.120/c (67/c ). Always specify the T2 board (lower) IP address or serial number. The tool will automatically connect to the address specified + 1 for T1. | |||||||||
> > | To specify the control hub protocol, append /c e.g. AMC13Tool2.exe -c 192.168.1.120/c (AMC13Tool2.exe -c 67/c ). Always specify the T2 board (lower) IP address or serial number. The tool will automatically connect to the address specified + 1 for T1. | |||||||||
If you specify an IP address, you must also tell the tool where to find the IPBus address tables.
You can either set the environment variable AMC13_ADDRESS_TABLE_PATH or use | ||||||||||
Line: 179 to 179 | ||||||||||
| ||||||||||
Added: | ||||||||||
> > |
>daq 2 L . | |||||||||
Note: recommend doing 'rd' (daq reset) after changing configuration |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 182 to 182 | ||||||||
Note: recommend doing 'rd' (daq reset) after changing configuration | ||||||||
Added: | ||||||||
> > | fed <link_no> <id>Set Source_ID or FED number for link 0-3. | |||||||
localL1A <mode> <burst> <rate> (Configure local L1A generator) |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 465 to 465 | ||||||||
chip_type: specifies firmware file suffix denoting T2 chip type
pfh (Program Flash Header) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | pfh: program flash header\n" \ Usage:\n" \ pfh OR pfh <chip_type>\n" \ chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
pbs (Program Backup Spartan, e.g. Golden) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | pbs: program flash backup spartan (golden) Usage: pbs OR pbs <chip_type> chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
ps (Program Spartan, e.g. T2) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ps: program flash spartan Usage: ps OR ps <chip_type> chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
pk (or pv) (Program Kintex/Virtex, e.g. T1) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | pv: program flash virtex/kintex Usage: pv OR pv <chip_type> chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
reconfigureFPGAs (reconfigure FPGAs from flash)-- EricHazen - 18 Oct 2014 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 29 to 29 | ||||||||
IP Address
The argument after -c may be a numeric I/P address, in the standard form e.g. 192.168.1.120 , or simply the serial number e.g. 67 . | ||||||||
Changed: | ||||||||
< < | To specify the control hub protocol, append /c e.g. 192.168.1.120/c (67/c ). Specify the T2 board (lower) IP address. The tool will automatically connect to the address specified + 1 for T1. | |||||||
> > | To specify the control hub protocol, append /c e.g. 192.168.1.120/c (67/c ). Always specify the T2 board (lower) IP address or serial number. The tool will automatically connect to the address specified + 1 for T1. | |||||||
If you specify an IP address, you must also tell the tool where to find the IPBus address tables.
You can either set the environment variable AMC13_ADDRESS_TABLE_PATH or use | ||||||||
Line: 59 to 59 | ||||||||
Interactive Mode | ||||||||
Changed: | ||||||||
< < | The tool will enter interactive mode after executing any scripts specified. A > prompt is displayed. | |||||||
> > | The tool will enter interactive mode after executing any scripts specified. A &Launcher::AMC13VerifyFlashHeader, "*>* prompt is displayed. | |||||||
Type h for a list of commands. Type h <command> for detailed help, or h * for detailed help on all commands. | ||||||||
Line: 266 to 267 | ||||||||
>nodes t1 *ttc*error* 9 nodes matched | ||||||||
Changed: | ||||||||
< < | 0: STATUS.TTC.BCNT_ERROR (addr=00000000 mask=00000040) r | |||||||
> > | 0: STATUS.TTC.BCNT_ERROR chip_type: specifies firmware file suffix denoting T2 chip type (addr=00000000 mask=00000040) r | |||||||
1: STATUS.TTC.BCNT_ERRORS_HI (addr=00000045 mask=0000ffff) r 2: STATUS.TTC.BCNT_ERRORS_LO (addr=00000044 mask=ffffffff) r 3: STATUS.TTC.MULT_BIT_ERROR (addr=00000000 mask=00000100) r | ||||||||
Line: 436 to 437 | ||||||||
For detailed recipe for updating firmware follow this link: Firmware Update Recipe
vfh (Verify Flash Header) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | vfh: verify flash header Usage: vfh OR vfh <chip_type> chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
vbs (Verify Backup Spartan, e.g. Golden) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | vbs: verify flash backup spartan (golden) \n" \ Usage: vbs OR vbs <chip_type> chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
vs (Verify Spartan, e.g. T2) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | vs: verify flash spartan Usage: vs OR vs <chip_type> chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
vk (or vv) (Verify Kintex/Virtex, e.g. T1) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | vv: verify flash virtex/kintex Usage: vv OR vv <chip_type> chip_type: specifies firmware file suffix denoting T2 chip type | |||||||
pfh (Program Flash Header)pbs (Program Backup Spartan, e.g. Golden) |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 28 to 28 | ||||||||
IP Address | ||||||||
Changed: | ||||||||
< < | The argument after -c may be a numeric I/P address, in the standard form e.g. 192.168.1.120 .
To specify the control hub protocol, append /c e.g. 192.168.1.120/c . Specify the T2 board (lower) IP address. The tool will automatically connect to the address specified + 1 for T1. | |||||||
> > | The argument after -c may be a numeric I/P address, in the standard form e.g. 192.168.1.120 , or simply the serial number e.g. 67 .
To specify the control hub protocol, append /c e.g. 192.168.1.120/c (67/c ). Specify the T2 board (lower) IP address. The tool will automatically connect to the address specified + 1 for T1. | |||||||
If you specify an IP address, you must also tell the tool where to find the IPBus address tables.
You can either set the environment variable AMC13_ADDRESS_TABLE_PATH or use | ||||||||
Line: 103 to 103 | ||||||||
connect <module_id> | ||||||||
Changed: | ||||||||
< < | Connect to an AMC13 using the specified IP address or connection file. | |||||||
> > | Connect to an AMC13 using the specified IP address, serial number, or connection file. | |||||||
See section above for details on the syntax.
list (fv) |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 29 to 29 | ||||||||
IP Address
The argument after -c may be a numeric I/P address, in the standard form e.g. 192.168.1.120 . | ||||||||
Changed: | ||||||||
< < | To specify the control hub protocol, append /c e.g. 192.168.1.120/c . _Specify the T2 board (lower)
IP address._ The tool will automatically connect to the address specified + 1 for T1. | |||||||
> > | To specify the control hub protocol, append /c e.g. 192.168.1.120/c . Specify the T2 board (lower) IP address. The tool will automatically connect to the address specified + 1 for T1. | |||||||
If you specify an IP address, you must also tell the tool where to find the IPBus address tables.
You can either set the environment variable AMC13_ADDRESS_TABLE_PATH or use |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 344 to 344 | ||||||||
ttc f dis | ||||||||
Added: | ||||||||
> > | The TTC history capture must be enabled with ttc h on . Using the default settings (no filters) the history will fill with BC0 commands. To set up a filter to ignore BC0, use the following command:
> ttc f s 1 0xfe | |||||||
For example:
| ||||||||
Line: 389 to 395 | ||||||||
> | ||||||||
Added: | ||||||||
> > | The detailed documentation for the following commands hasn't been written yet, but in general they should be used only by expert users. | |||||||
vfh : verify flash header -- vfh OR vfh |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 252 to 252 | ||||||||
start (Enable run mode)stop (Disable run mode) | ||||||||
Changed: | ||||||||
< < | nodes {T1|T2} <regex> (list address table nodes) | |||||||
> > | nodes {T1|T2} <regex> <options> (list address table nodes) | |||||||
This traverses the IPBus address table for either T1 or T2 board and displays all items matching the specified regular expression. The regular expression format is rather simple; '*' matches any string. | ||||||||
Added: | ||||||||
> > | Option "V" will display a description of each item. Option "D" provides debugging output. | |||||||
For example:
| ||||||||
Line: 274 to 279 | ||||||||
> | ||||||||
Added: | ||||||||
> > | Verbose option to display descriptions:
>nodes t1 status*tts_state v 2 nodes matched 0: STATUS.AMC_TTS_STATE (addr=00000019 mask=001f0000) r encoded TTS from enabled AMCs 1: STATUS.T1_TTS_STATE (addr=00000019 mask=0000f000) r Current T1 overall TTS state > | |||||||
re <all> (read/display event from SDRAM)This command will read the next event from the SDRAM and display |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 403 to 403 | ||||||||
selectFileTest : test function for MCS file parsing -- selectFileTest file | ||||||||
Added: | ||||||||
> > | Flash Programming Commands (for firmware updates, etc.)Flash programming commands uses the board's serial number to identify the relevant firmware chip-type for the user indicated flash region. It then looks for matching mcs files in the current directory and lists them for the user to pick from. Once the user selects the mcs file to use, the flash action (verify or program) will be carried out. When reprogramming, once the flash has been programmed, load the new firmware using 'reconfigureFPGAs' For detailed recipe for updating firmware follow this link: Firmware Update Recipevfh (Verify Flash Header)vbs (Verify Backup Spartan, e.g. Golden)vs (Verify Spartan, e.g. T2)vk (or vv) (Verify Kintex/Virtex, e.g. T1)pfh (Program Flash Header)pbs (Program Backup Spartan, e.g. Golden)ps (Program Spartan, e.g. T2)pk (or pv) (Program Kintex/Virtex, e.g. T1)reconfigureFPGAs (reconfigure FPGAs from flash) | |||||||
-- EricHazen - 18 Oct 2014 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 193 to 193 | ||||||||
| ||||||||
Added: | ||||||||
> > |
setOcrCommand (set orbit count reset TTC command)Specify the TTC command to use for orbit count reset. Note that the low two bits must be zero as they have predefined meanings (bit 0=BcR; bit 1=EcR)setOrbitGap <start> <end> (set orbit gap for local triggers)Triggers generated by the local L1A generator will not occur in this range of BCN. <start> must be in the range 0-3562 <end> must be in the range 1-3563prescale <mode> <factor> (set local event capture mode/prescale)This command sets the parameters for capture of selected events in the SDRAM buffer for readout over IPBus using the commandsre and df or other means.
mode: 0 for simple prescale (record every n events, n from 1...0x10000) 1 to match EvN with n low bits =0 where n from 5..20 factor: if mode=0, 1...0x10000 if mode=1, 5..20 | |||||||
lt <mode/count> (Enable/disable local L1A generator)If <mode/count> is an integer, send that many bursts of triggers | ||||||||
Line: 210 to 237 | ||||||||
enabled (e.g. lt 5 would generate 5 bursts) but it does not start to run
continuously unless you enter lt e . To stop continuous triggers, enter lt d . | ||||||||
Deleted: | ||||||||
< < | prescale : set prescale mode and factor Usage: prescale | |||||||
rg (general reset)Reset most AMC13 logic. For firmwares before 0x20f/0x4006 this resets DAQ links too. After this version, use 'rd' to reset DAQ separately | ||||||||
Line: 238 to 249 | ||||||||
DAQ Link reset (firmware 0x20f/0x4006 and above) | ||||||||
Added: | ||||||||
> > | start (Enable run mode)stop (Disable run mode)nodes {T1|T2} <regex> (list address table nodes)This traverses the IPBus address table for either T1 or T2 board and displays all items matching the specified regular expression. The regular expression format is rather simple; '*' matches any string. For example:>nodes t1 *ttc*error* 9 nodes matched 0: STATUS.TTC.BCNT_ERROR (addr=00000000 mask=00000040) r 1: STATUS.TTC.BCNT_ERRORS_HI (addr=00000045 mask=0000ffff) r 2: STATUS.TTC.BCNT_ERRORS_LO (addr=00000044 mask=ffffffff) r 3: STATUS.TTC.MULT_BIT_ERROR (addr=00000000 mask=00000100) r 4: STATUS.TTC.MULT_BIT_ERRORS_HI (addr=00000043 mask=0000ffff) r 5: STATUS.TTC.MULT_BIT_ERRORS_LO (addr=00000042 mask=ffffffff) r 6: STATUS.TTC.SGL_BIT_ERROR (addr=00000000 mask=00000080) r 7: STATUS.TTC.SGL_BIT_ERRORS_HI (addr=00000041 mask=0000ffff) r 8: STATUS.TTC.SGL_BIT_ERRORS_LO (addr=00000040 mask=ffffffff) r > re <all> (read/display event from SDRAM)This command will read the next event from the SDRAM and display the first 10 words and last 5 words of the event. If the argument all is given, the entire event is displayed. The read pointer is advanced to the next event.rev (read/display event using new vector interface)This command is equivalent to re except that it uses (tests) the new vector-based function to read events.df <file> <count> (read events to file)This command reads events from the SDRAM buffer and writes them to a binary file. The file argument specifies the file to write. The count argument specifies the number of events (default is 1). The file format is defined as a list of 64-bit words in little-endian byte order as follows. See AMC13CommonFirmwareProposal for detailed description of AMC13 payload format.badc0ffeebadcafe magic number present at start of each event cccccccccccccccc size of event in 64-bit words 510000781f412308 CMS common data format header 104101401a540110 AMC13 header, specifying 4 AMCs 0f00040300010000 ... c62b8d9c000781f4 AMC13 trailer with CRC a0001014c3590000 CMS command data format trailer ttc <options> (control TTC history capture)Usage: ttc h on - ttc history enable ttc h off - ttc history disable ttc h clr - ttc history clear ttc h dFor example: [hazen@cms4 amc13]$ AMC13Tool2.exe -c 192.168.1.176 ... >en 1-4 f t parsed list "1-4" as mask 0xf Enabling fake data Enabling TTS as TTC for loop-back AMC13 out of run mode AMC13 is back in run mode and ready >ttc h on (turn on TTC history) >ttc h d 5 (display 5 commands) History buffer has 512 entries NOTE: TTC history capture disabled before readout Cmd --Orbit- BcN --EvN- 0: 01 0003cf4e dea 000001 (these are all Bc0 and uninteresting) 1: 01 0003cf4f dea 000001 2: 01 0003cf50 dea 000001 3: 01 0003cf51 dea 000001 4: 01 0003cf52 dea 000001 >ttc f s 0 0x01 0xfe (set filter item 0 to 0x01 with mask 0xfe) >ttc f on (turn on filtering) >ttc h clr (clear the history) >ttc h on (turn history back on) >ttc h d 5 (display 5 entries) History buffer has 0 entries >ttc h on (turn history back on) >wv ACTION.LOCAL_TRIG.SEND_OCR (send OcR command) >wv ACTION.LOCAL_TRIG.SEND_OCR (twice for fun) >ttc h d 5 (display 5 entries) History buffer has 2 entries NOTE: TTC history capture disabled before readout Cmd --Orbit- BcN --EvN- 0: 28 00021c6b a17 000001 1: 28 000203d5 b65 000001 >ttc f list (list the items being filtered) Item Ena CMD Mask 0 On 01 fe 1 Off 00 00 ... 15 Off 00 00 > | |||||||
Deleted: | ||||||||
< < | start : Enable run mode
stop : Disable run mode
nodes : List address table nodes -- list {T1|T2} | |||||||
vfh : verify flash header -- vfh OR vfh | ||||||||
Line: 259 to 381 | ||||||||
pbs : program flash golden -- pbs OR pbs | ||||||||
Deleted: | ||||||||
< < | devstatus (dst) : Display AMC13 Status
usage:
status | |||||||
status (st) : Display AMC13 Status
usage:
status | ||||||||
Line: 276 to 393 | ||||||||
table_name limits the display to the table named openStatusFile : Open a text file to stream status info to closeStatusFile : Close the text file | ||||||||
Added: | ||||||||
> > | printFlash : print flash data for testing only verifyFlash : verify flash data from file -- verifyFlash file address programFlash : program flash data from file -- programFlash file address reconfigureFPGAs : reconfigure FPGAs from flash verifyFlashFile : verify flash data from file -- verifyFlash file programFlashFile : program flash data from file -- programFlash file selectFileTest : test function for MCS file parsing -- selectFileTest file | |||||||
-- EricHazen - 18 Oct 2014 \ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 75 to 75 | ||||||||
Tab completion is particularly useful for command words and address table entries. Wildcards are permitted in address table entries in certain cases. | ||||||||
Changed: | ||||||||
< < | For example, the command *readT1 stat*ttc*err* will read and | |||||||
> > | For example, the command readT1 stat*ttc*err* will read and | |||||||
display all address table entries matching the expression with wildcards. Wildcards are simple shell-style by default, where * matches any string. |
Line: 1 to 1 | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
Line: 183 to 183 | |||||||||
Note: recommend doing 'rd' (daq reset) after changing configuration | |||||||||
Changed: | |||||||||
< < | localL1A <mode> <burst> <rate> (Configure local L1A generator) | ||||||||
> > | localL1A <mode> <burst> <rate> (Configure local L1A generator) | ||||||||
| |||||||||
Line: 193 to 193 | |||||||||
| |||||||||
Added: | |||||||||
> > | lt <mode/count> (Enable/disable local L1A generator)If <mode/count> is an integer, send that many bursts of triggers (typically you would want to set the burst size to 1 using the localL1A command if using this feature). If <mode/count> is a letter, perform one of these functions:
lt 5 would generate 5 bursts) but it does not start to run
continuously unless you enter lt e . To stop continuous triggers, enter lt d . | ||||||||
prescale : set prescale mode and factor Usage: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 188 to 188 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
prescale : set prescale mode and factor |
Line: 1 to 1 | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
Line: 170 to 170 | ||||||||||||||||
N to leave AMC13 out of run mode after initialization | ||||||||||||||||
Changed: | ||||||||||||||||
< < | daq <config> | |||||||||||||||
> > | daq <config> (configure DAQ fiber output)This command sets the configuration for the DAQ fiber (aka S-Link express, DAQLSC) outputs. Options:
localL1A <mode> <burst> <rate> (Configure local L1A generator)
| |||||||||||||||
| ||||||||||||||||
Deleted: | ||||||||||||||||
< < | daq : Enable DAQ outputs
Usage:
daq 1|2|3 d
1 - enable SFP0 (top) DAQ fiber for AMC1-AMC12 readout
2 - enable SFP0 for AMC1-AMC6, SFP1 for AMC7-AMC12
3 - enable SFP0 for AMC1-AMC4, SFP1 for AMC5-AMC8, SFP2 for AMC9-AMC12
d - disable all fibers
| |||||||||||||||
prescale : set prescale mode and factor
Usage:
prescale |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 157 to 157 | ||||||||
Will correctly reset the T1 board. | ||||||||
Added: | ||||||||
> > | i (en) <inputs> <options> (initialize AMC13 for data taking) | |||||||
i (en) : Initialize AMC13 Usage: | ||||||||
Line: 166 to 168 | ||||||||
options: T to enable loop-back TTC on TTS output fiber F to generate fake events in AMC13 N to leave AMC13 out of run mode after initialization | ||||||||
Added: | ||||||||
> > |
daq <config> | |||||||
daq : Enable DAQ outputs Usage: daq 1|2|3 d | ||||||||
Line: 195 to 202 | ||||||||
lt e enable trigger generator lt d disable trigger generator lt c enable continuous mode (configure with localL1A) | ||||||||
Changed: | ||||||||
< < | rg : General reset For firmwares before 0x20f/0x4006 this resets DAQ links too After this version, use 'rd' to reset DAQ separately rc : Counter reset rd : DAQ Link reset (firmware 0x20f/0x4006 and above) | |||||||
> > |
rg (general reset)Reset most AMC13 logic. For firmwares before 0x20f/0x4006 this resets DAQ links too. After this version, use 'rd' to reset DAQ separatelyrc (counter reset)Reset AMC13 counters.rd (DAQ reset)DAQ Link reset (firmware 0x20f/0x4006 and above) | |||||||
start : Enable run mode
stop : Disable run mode
nodes : List address table nodes -- list {T1|T2} |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 143 to 143 | ||||||||
All displayed values are in hex. | ||||||||
Added: | ||||||||
> > | writeT1 (wv) <address> [<data>]writeT2 (ws) <address> [<data>]Write to an address on T1 or T2 board. Address may be numeric or an address table item. Data must be numeric. Data may be omitted in which case a special masked write is performed. This is typically used for address table items with names starting with ACTION.. For example:wv ACTION.RESETS.GENERAL
Will correctly reset the T1 board. | |||||||
Deleted: | ||||||||
< < | writeT1 (wv) : Write from AMC13 T1 board writeT2 (ws) : Write from AMC13 T2 board | |||||||
i (en) : Initialize AMC13
Usage:
i |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Added: | ||||||||
> > |
| |||||||
Usage:AMC13Tool2.exe [-p | ||||||||
Line: 19 to 21 | ||||||||
interactive mode without establishing communication with any AMC13. Typically the first interactive command would then be "connect" to attach an AMC13. | ||||||||
Changed: | ||||||||
< < | Specifying AMC13 Modules | |||||||
> > | Specifying AMC13 ModulesUse the -c argument to specify AMC13 modules to communicate with. IP Address | |||||||
Changed: | ||||||||
< < | Use the -c argument to specify AMC13 modules to communicate with. The argument may be a numeric
I/P address or the name of a uHAL connection file (see Tutorial![]() | |||||||
> > | The argument after -c may be a numeric I/P address, in the standard form e.g. 192.168.1.120 .
To specify the control hub protocol, append /c e.g. 192.168.1.120/c . _Specify the T2 board (lower)
IP address._ The tool will automatically connect to the address specified + 1 for T1.
If you specify an IP address, you must also tell the tool where to find the IPBus address tables.
You can either set the environment variable AMC13_ADDRESS_TABLE_PATH or use
the -p option on the command line to do this. The path must be the name of a directory containing
the two files AMC13_T1.xml and AMC13_T2.xml. (In the standard source distribution these are symlinks
in the directory ...amc13/etc/amc35 below the top level. In the RPM distribution they are in /opt/cactus/etc/amc13 ).
Connection File
Alternatively you may specify the name of a connection file.
See Cactus Tutorial![]() Running ScriptsA script file may be created with a list of AMC13Tool2 commands. A script may be executed in two ways:
Interactive ModeThe tool will enter interactive mode after executing any scripts specified. A > prompt is displayed. Type h for a list of commands. Type h <command> for detailed help, or h * for detailed help on all commands. Generally, interactive commands consist of a command word followed by optional arguments. The command words are case-sensitive. Each command may have aliases (alternative names) given in parenthesis in the help. Numeric arguments are interpreted as decimal unless prefixed with 0x in which case they are interpreted as hexadecimal. Tab completion and history editing are provided by the GNU readline library. Tab completion is particularly useful for command words and address table entries. Wildcards are permitted in address table entries in certain cases. For example, the command *readT1 stat*ttc*err* will read and display all address table entries matching the expression with wildcards. Wildcards are simple shell-style by default, where * matches any string. An argument may be preceded with the string perl: to force full perl-style regular expression matching.Detailed Command Listhelp (h)Display list of commands. A command name may be given for a longer description of a particular command.quit (q, exit)Exit the program.echoEcho the arguments after the command to the terminal (useful in scripts)sleepDelay execution for the specified time in seconds. Decimal values may be used.connect <module_id>Connect to an AMC13 using the specified IP address or connection file. See section above for details on the syntax.list (fv)List all connected AMC13 modules with firmware version, serial number and IP addresses. The module currently accepting commands is marked with a - character. For example:>list Connected AMC13s *0: SN: 86 T1v: 0211 T2v: 0021 cf: 192.168.1.82 1: SN: 82 T1v: 4007 T2v: 0021 cf: 192.168.1.90 sel <number>Select an AMC13 to accept commands. Specify a number as shown in the output of the list command.readT1 (rv) <address> [<count>]readT2 (rs) <address> [<count>]Read from a register on the T1 or T2 board. <address> may be any of the following:
writeT1 (wv) : Write from AMC13 T1 board writeT2 (ws) : Write from AMC13 T2 board i (en) : Initialize AMC13 Usage: i | |||||||
-- EricHazen - 18 Oct 2014 |
Line: 1 to 1 | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Added: | ||||||||||||||||||
> > |
Usage:AMC13Tool2.exe [-p
StartupThe tool make be started with no command-line options, in which case it will immediately enter interactive mode without establishing communication with any AMC13. Typically the first interactive command would then be "connect" to attach an AMC13. Specifying AMC13 Modules Use the -c argument to specify AMC13 modules to communicate with. The argument may be a numeric I/P address or the name of a uHAL connection file (see Tutorial![]() |