Now go back to the DAQ menu, check the status, and you should see that your DAQ path is ready to go!

Setup Clock

When checking the status of you uHTR, a list of the clocks are reported (for both front and back). These reported clocks should be consistent with the expected clock (see below). Inconsistencies may indicate that you will need to setup clocks.

This page contains some uHTRTool software procedures which are useful to an AMC13 debugger and developer.

Line: 158 to 158

Module Id : 0 (0x0) BC Offset : 0

Added:

>>

Setup Clock

When checking the status of you uHTR, a list of the clocks are reported (for both front and back). These reported clocks should be consistent with the expected clock (see below). Inconsistencies may indicate that you will need to setup clocks.

Send uHTR Local Triggers

The following procedure assumes that the backplane link sees Bc0s running both ways between the uHTR and the AMC13. It's also worth saying that the following procedure is from Jeremy, and that upon it's initial test, it did not work. We are not sure what the problem is yet, but this list of command may need to be modified.

This page contains some uHTRTool software procedures which are useful to an AMC13 debugger and developer.

Line: 160 to 160

Send uHTR Local Triggers

Changed:

<<

The following procedure assumes that the backplane link sees Bc0s running both ways between the uHTR and the AMC13. It's also worth saying that the following procedure is from Jeremy, and that upon it's initial test, it did not work. We are not sure what the problem is yet, but this list of command may need to be modified. (EDIT: recipe below seems to be working)

>>

The following procedure assumes that the backplane link sees Bc0s running both ways between the uHTR and the AMC13. It's also worth saying that the following procedure is from Jeremy, and that upon it's initial test, it did not work. We are not sure what the problem is yet, but this list of command may need to be modified.

This page contains some uHTRTool software procedures which are useful to an AMC13 debugger and developer.

Line: 160 to 160

Send uHTR Local Triggers

Changed:

<<

The following procedure assumes that the backplane link sees Bc0s running both ways between the uHTR and the AMC13. It's also worth saying that the following procedure is from Jeremy, and that upon it's initial test, it did not work. We are not sure what the problem is yet, but this list of command may need to be modified.

>>

The following procedure assumes that the backplane link sees Bc0s running both ways between the uHTR and the AMC13. It's also worth saying that the following procedure is from Jeremy, and that upon it's initial test, it did not work. We are not sure what the problem is yet, but this list of command may need to be modified. (EDIT: recipe below seems to be working)

Program uHTR Flash

The uHTR consists of two FPGAs, a 'front' and a 'back'. You can find the firmware files for each chip here

Make sure that the firmware files you want to program into the module are located in the current directory.

Start uHTRtool.exe, giving it the IP address of the uHTR you want to reprogram. NOTE! If using IPbus Software Suite 2.0 or greater, you need to use teh -u option for the time being, as ControlHub is not yet working

> flash
FLASH target: BACK
FPGA Toggle which FPGA to target
READ Read the flash contents into a file
PROG Reprogram the flash from an MCS file
VERIFY Verify the flash contents against an existing MCS file
RELOAD Reload the FPGA from FLASH
QUIT Back to top menu
>

Toggle to the FPGA you want to program by using the FPGA command. Notice that BACK is the default

Select the PROG option from the menu

FLASH target: BACK
FPGA Toggle which FPGA to target
READ Read the flash contents into a file
PROG Reprogram the flash from an MCS file
VERIFY Verify the flash contents against an existing MCS file
RELOAD Reload the FPGA from FLASH
QUIT Back to top menu
> prog

Enter the path of the MCS file you want to program into the FPGA. If you followed step 1, this should just be the file name, since it sits in the current directory. MAKE SURE YOU PROGRAM THE CORRECT MCS FILE INTO THE CHOSEN FPGA! DON'T GO PUTTING A 'FRONT' FIRMWARE FILE INTO THE 'BACK' FPGA OR VICE VERSA!

If no errors are reported, then you are ready to reload the FPGA from flash using the RELOAD command

FLASH target: BACK
FPGA Toggle which FPGA to target
READ Read the flash contents into a file
PROG Reprogram the flash from an MCS file
VERIFY Verify the flash contents against an existing MCS file
RELOAD Reload the FPGA from FLASH
QUIT Back to top menu
> reload
Initiating reload from flash (requires ~10 seconds)...

Now go back to the main menu, check the status, and see that your firmware version has been successfully updated

Congratulations! The BACK FPGA on your uHTR has been updated! The process for the FRONT FPGA is identical, only that you need to toggle to the FRONT and program the chip with a front MCS file.

Enable uHTR DAQ Path

Start uHTRtool.exe, giving it the IP address of the uHTR you want to reprogram. NOTE! If using IPbus Software Suite 2.0 or greater, you need to use teh -u option for the time being, as ControlHub is not yet working

Send uHTR Local Triggers

The following procedure assumes that the backplane link sees Bc0s running both ways between the uHTR and the AMC13. It's also worth saying that the following procedure is from Jeremy, and that upon it's initial test, it did not work. We are not sure what the problem is yet, but this list of command may need to be modified.