Difference: AMC13Tool2Recipes (11 vs. 12)

Revision 1217 Nov 2020 - ChristopherCosby

Line: 1 to 1
 
META TOPICPARENT name="HcalDTC"
These instructions assume you have successfully installed and tested your software. See AMC13CppGettingStarted for instructions if you haven't
Line: 7 to 7
 
Fake Data Readout
Connect Multiple AMC13s
Setup one 10Gb link to cms1 FEROL
Deleted:
<
<
 For some instructions specific for Building 28 (at CERN), please go here:

Building 28 Instructions

Changed:
<
<
>
>
#UpdateFirmware
 

Update Firmware using AMC13Tool2

Added:
>
>		___________________________________________________________________

WARNING!!! (11/17/2020)

If you have recently received a new module with a SN > 384, then you must immediately

download and install the latest version of the AMC13 software (1.2.17) before attemting

to update your firmware. This is due to the fact that the new modules have a different

FLASH memory chip, which is imcompatible with the old software.

ADDITIONALLY, you must use the AMC13ToolFlash.exe tool with the option "-f pa" to

program all parts of the memory at once. This will require the below firmware MCS files

for the T2/Golden/Header. Whatever T1 version you intend to use should work fine.

Failure to follow these steps could result in corrupting the memory of your module. 

            Header: http://physics.bu.edu/~wusx/download/AMC13/AMC13T2Header_6slx45t.mcs
            Golden: http://physics.bu.edu/~cosbyc/AMC13/AMC13T2Golden_6slx45t.mcs
       T2: http://physics.bu.edu/~wusx/download/AMC13/AMC13T2v0x0033_6slx45t.mcs


___________________________________________________________________
 Make sure that you have the latest firmware files for both the Spartan and Kintex chips by downloading the latest '.mcs' files from here. To be safe, download all of the MCS files for the latest versions (the tool will pick the correct file where there is more than one choice). Put the firmware files in your current directory.

Use the pk command to program the T1 (Kintex) and ps to program the T2 (Spartan). Then use reconfigureFPGAs to force a reload from flash.

Here is an example session where we program the Kintex and Spartan and then reload:

Changed:
<
<
[ehazen@cms1 amc13_mcs]$ ../tools/bin/AMC13Tool2.exe -c ../amc13/etc/amc13/connectionSN43.xml
>
>
[ehazen@cms1 amc13_mcs]$ ../tools/bin/AMC13Tool2.exe -c ../amc13/etc/amc13/connectionSN43.xml
 Using AMC13 software ver:30757
Changed:
<
<		>fv # check current firmware versions
>
>		>fv # check current firmware versions
 Connected AMC13s *0: SN: 43 T1v: 0209 T2v: 0021 cf: ../amc13/etc/amc13/connectionSN43.xml
Changed:
<
<		>pk # program the Kintex
>
>		>pk # program the Kintex
 chip_type not specified, using default from serial number... Searching for files with T1 and 7K325T...
Line: 48 to 70
 programming flash at address 0x564700 % done = 87 programming flash at address 0x4a8f00 % done = 94
Changed:
<
<		>ps # program the Spartan
>
>		>ps # program the Spartan
 chip_type not specified, using default from serial number... Searching for files with T2, and 6SLX25T...
Line: 67 to 89
  NOTE: The most recent versions of these program commands should automatically verify the relevant flash sector against the chosen firmware file, but if it does not, use 'vk' and 'vs' respectively for verifying the T1 and T2 (upon using the command select the new firmware file to check against what is programmed in flash). Be sure to verify flash sector prior to reconfiguring or power cycling.
Changed:
<
<
>reconfigureFPGAs     # force reload from flash
>
>
>reconfigureFPGAs     # force reload from flash
 Best exit/restart tool after 10s or so
Changed:
<
<		>q
>
>		>q
 [ehazen@cms1 amc13_mcs]$ ../tools/bin/AMC13Tool2.exe -c ../amc13/etc/amc13/connectionSN43.xml Using AMC13 software ver:30757
Changed:
<
<		>fv # check versions again
>
>		>fv # check versions again
 Connected AMC13s *0: SN: 43 T1v: 020d T2v: 0021 cf: ../amc13/etc/amc13/connectionSN43.xml
Changed:
<
<		>
>
>		>
 
Changed:
<
<
>
>
#FakeDataReadout
 

Fake Data Readout

This recipe tells you how to generate fake events in the AMC13 and read them out over IPBus. Required equipment:

Line: 92 to 113
 Here's the recipe (example below is for SN 86, make sure use the IP address or connection files that correspond to your board):

1. Connect to the AMC13 either by connection file or by spartan (T2) IP address (assuming T1 IP address is 1 higher than the T2 address).

Changed:
<
<
[hazen@cms4 scripts]$ AMC13Tool2.exe -c connectionSN86.xml
>
>		 
[hazen@cms4 scripts]$ AMC13Tool2.exe -c connectionSN86.xml
 OR $ AMC13Tool2.exe -c 192.168.1.82 Address table path "/home/hazen/work/amc13/amc13/etc/amc13" set from AMC13_ADDRESS_TABLE_PATH
Line: 101 to 122
 

2. Reset AMC13 (general and counter).

Changed:
<
<
> rg
> rc
>
>		 
> rg
> rc
 

3. Enable link with fake events ('f') and TTC loopback ('t') options and start run (part of enable command by default).

Line: 109 to 130
 3. Enable link with fake events ('f') and TTC loopback ('t') options and start run (part of enable command by default).

NOTE: If we are building fake events, these are generated internally, so in this case, the actual numbers denoted are unimportant. But when building events from actual AMCs, you would denote the slot numbers corresponding to the modules you will be reading event data from.

Added:
>
>
 
http://cms1.bu.edu:33001/urn:xdaq-application:lid=12
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
Line: 117 to 139
 AMC13 out of run mode AMC13 is back in run mode and ready
Added:
>
>
 4. Set up local triggers. There are various options how you would like triggers to be sent (number of triggers per bunch, rate, etc.), for help use 'h localL1A'. In this example we will just send 1 trigger per orbit.
Changed:
<
<
>localL1A o 1 1
>
>		 
>localL1A o 1 1
 Configure LocalL1A enabled mode=0 burst=1 rate=1 rules=0
Added:
>
>
 5. Send Triggers
Changed:
<
<
>lt 5
>
>		 
>lt 5
 detected number after 'lt' Sending 5 local triggers Trigger: 4 left
Line: 133 to 157
 Trigger: 1 left Trigger: 0 left
Added:
>
>
 6. Use status command to check to see that L1As were sent+received and that events were built.
Changed:
<
<
>st
>
>		 
>st
  Board| SERIALNO| T1_VER| T2_REV| T2_SERNO| --|---------|-------|-------|---------| INFO| 0x56| 0x400A| 0x21| 0x56|
Line: 168 to 193
  --|----|----| STATE| RDY| RDY|
Added:
>
>
 7. Read out events.
Changed:
<
<
>re
>
>		 
>re
 calling readEvent...AOK Read 16400 words
0
510000011f400008
Line: 189 to 215
 16397: 7122902601001002 16398: 0f2fe8ab000011f4 16399: a0004010fc520000
Changed:
<
<		>
>
>		>
 
Deleted:
<
<
 -- EricHazen - 18 Nov 2014
Changed:
<
<
>
>
#MultiConnect
 

Connect Multiple AMC13s

This recipe tells you how to connect multiple AMC13s and how to send fake payloads from AMC13s in slots 1-12 to an AMC13 in the MCH slot. The AMC13s in slots 1-12 act as uHTRs. Required equipment:

Line: 209 to 233
  There are two ways to connect to multiple AMC13s. One is on the command line with AMC13Tool2, the other is inside AMC13Tool2:
Changed:
<
<

First way

>
>

First way

 When starting the tool:
Changed:
<
<
[cjjacob@cms4 amc] ./tools/bin/AMC13Tool2.exe -c 161 -c 303
>
>		 
[cjjacob@cms4 amc] ./tools/bin/AMC13Tool2.exe -c 161 -c 303
 use_ch false Created URI from IP address: T2: ipbusudp-2.0://192.168.2.188:50001
Line: 223 to 248
  T2: ipbusudp-2.0://192.168.3.160:50001 T1: ipbusudp-2.0://192.168.3.161:50001 Using AMC13 software ver:41103
Changed:
<
<		>
>
>		>
 
Changed:
<
<

Second Way

Inside the tool, use the command connect: 
[cjjacob@cms4 amc] ./tools/bin/AMC13Tool2.exe -c 161
>
>

Second Way

Inside the tool, use the command connect: 

[cjjacob@cms4 amc] ./tools/bin/AMC13Tool2.exe -c 161
 Address table path "/home/cjjacob/amc13/amc13/etc/amc13" set from AMC13_ADDRESS_TABLE_PATH use_ch true Created URI from IP address: T2: chtcp-2.0://localhost:10203?target=192.168.2.188:50001 T1: chtcp-2.0://localhost:10203?target=192.168.2.189:50001 Using AMC13 software ver:41103
Changed:
<
<		>connect 303
>
>		>connect 303
 use_ch false Created URI from IP address: T2: ipbusudp-2.0://192.168.3.160:50001 T1: ipbusudp-2.0://192.168.3.161:50001 Using AMC13 software ver:41103
Changed:
<
<		>
>
>		>
 
Changed:
<
<		You can see which AMC13s are connected by using the list (fv) command. This also lists their firmware versions and serial numbers. You can select the active AMC13 (the one that will execute your commands) with the selectAMC13 (sel) command.
>
>		You can see which AMC13s are connected by using the list (fv) command. This also lists their firmware versions and serial numbers. You can select the active AMC13 (the one that will execute your commands) with the selectAMC13 (sel) command.
 
Changed:
<
<
>fv
>
>
>fv
 Connected AMC13s *0: SN: 161 T1v: 0244 T2v: 002e cf: 161 1: SN: 303 T1v: 100b T2v: 002a cf: 303
Changed:
<
<		>sel 1
>
>		>sel 1
 Setting default AMC13 to 1
Line: 261 to 286
  If the AMC13 has the 0x1000 series firmware, you can control the fake payloads by setting a lower bound at register 0x18 and an upper bound at register 0x19, then performing a general reset. Example:
Changed:
<
<
>wv 0x18 0x400
>
>
>wv 0x18 0x400
 Write to address 0X18
Changed:
<
<		>wv 0x19 0x1200
>
>		>wv 0x19 0x1200
 Write to address 0X19
Changed:
<
<		>wv 0 1
>
>		>wv 0 1
 Write to address 0

if you are using HCAL firmware also write

Changed:
<
<
wv 0x17 0x80000000
>
>		 
wv 0x17 0x80000000
 

will send fake payloads between 0x400 and 0x1200 64-bit words in size.

Changed:
<
<		After you've set all the fake payload sizes, return to the AMC13 in the MCH slot with the sel command. You must now enable the AMC13s that will send fake triggers with the en command using their slot number. In this example AMC13 SN 303 is in slot 2 of the crate.
>
>		After you've set all the fake payload sizes, return to the AMC13 in the MCH slot with the sel command. You must now enable the AMC13s that will send fake triggers with the en command using their slot number. In this example AMC13 SN 303 is in slot 2 of the crate.
 
Changed:
<
<
>en 2 t
>
>
>en 2 t
 parsed list "2" as mask 0x2 Enabling TTS as TTC for loop-back AMC13 out of run mode AMC13 is back in run mode and ready
Changed:
<
<		Now, you can use the lt command to send local triggers.
>
>		Now, you can use the lt command to send local triggers.
 
Changed:
<
<
>lt 2
>
>
>lt 2
 detected number after 'lt' Sending 2 local triggers Trigger: 0 left
Line: 299 to 321
 There are now unread events in the monitor buffer.

Connect AMC13 and a single 10Gb FEROL

Changed:
<
<		 Make two connections to cms1 as the daq user, and then in both terminals, cd to the local FEROL directory.
>
>
#SingleFEDOL Make two connections to cms1 as the daq user, and then in both terminals, cd to the local FEROL directory.
  First, setup the AMC13 by using the following commands in AMC13Tool2.exe
Changed:
<
<
rg
>
>		 
rg
 rc en 1-12 f t daq 1
Line: 314 to 336
  Or you can just run "AMC13Tool2.exe -c 285/c -X amc13_script.txt" in the FEROL directory and it will run all of them for you.
Changed:
<
<		Then switch to the other terminal and type "./fedKit.py" into the terminal. It will ask you several questions, but the default values should be fine. Here is an example: 
[daq@cms1 FEROL]$ ./fedKit.py
>
>		Then switch to the other terminal and type "./fedKit.py" into the terminal. It will ask you several questions, but the default values should be fine. Here is an example: 

[daq@cms1 FEROL]$ ./fedKit.py
 Welcome to the optical FEDkit ========================= Please select the data source to be used:
Line: 328 to 348
  4 - AMC13 data source over 10Gb (L10G_SOURCE) 5 - Generator core of AMC13 over 10Gb (L10G_CORE_GENERATOR_SOURCE) 6 - SLINK data source (SLINK_SOURCE)
Changed:
<
<		=> [4]
>
>		=> [4]
 Please enter the FED id you want to read out [100]: Do you want to write the data to disk? [No]: Starting run...
Line: 336 to 356
  The program will hang here for up to a minute, but then show the following command prompt:
Changed:
<
<
Running. Point your browser to http://cms1.bu.edu:33001
>
>
Running. Point your browser to http://cms1.bu.edu:33001
  m display this Menu f# dump the next # FED fragments incl DAQ headers (default 1) e# dump the next # Events with FED data only (default 1) q stop the run and Quit

Changed:
<
<		=>
>
>		=>
 
Deleted:
<
<
 At this point you can go back to the AMC13 screen and type "lt 1" to send a trigger or two.

You can monitor the status of the link in the AMC13Tool2.exe by typing "status" and looking at the SlinkExpress table.

Changed:
<
<		You can also monitor the FEROL by going to: http://cms1.bu.edu:33000/urn:xdaq-application:lid=11 and you can see if events are being built by going to: http://cms1.bu.edu:33001/urn:xdaq-application:lid=12
>
>		You can also monitor the FEROL by going to: http://cms1.bu.edu:33000/urn:xdaq-application:lid=11 and you can see if events are being built by going to: http://cms1.bu.edu:33001/urn:xdaq-application:lid=12
  -- ColinJacob - 10 Dec 2015 \ No newline at end of file
View topic | History: r13 < r12 < r11 < r10 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback