Book-Keeping work in progress

Reddy Pratap Gandrajula, Mark Cooke & Ana Ovcharova

Iowa group meeting

March 20th 2012

03/20/12 Book keeping work in progress 2

OutLine

● New variables to hold the counting of FMT Link reset/Module reconfiguration attempts in QuickStatusInfo structure

● Trouble in reading same FPGA register addresses twice, one in quickStatus and other in PixDSPMonitorTask

●Alternative Solution

03/20/12 Book keeping work in progress 3

Brief remainder

03/20/12 Book keeping work in progress 4

New Variables in QuickStatusInfo

QuickStatusMode: A string in IS that holds the quickStatus mode. e.g quickStatus running is one possible mode (For more Info refer to Ana's Todays Talk)

nRST: An UINT32 to count the number of FMT Link reset attempts

nCFG: An UINT32 to count the number of module reconfiguration attempts

QSDisabled: An UINT32 that holds the Info of disabled module link that doesn't recovered after certain Reset/Reconfigure attempts (for how many modules)

03/20/12 Book keeping work in progress 5

Trouble in reading FPGA registers twice

● In the attempt of reconfiguring the auto-disabled modules, we are reading the FMT register addresses to know about the Error states such as FMT_TIMEOUT_ERR and FMT_ROD_BUSY_ERR in quickStatus (in NewDsp)which runs at every 0.4 mSec

● Once we read the values at FPGA register, that register memory gets cleared.

● Currently,for general ROD status Monitoring, we are reading all FPGA (FMT, EFB,Router,RCF) registers via mdspBlockread in PixDSPMonitorTask (in host) at a slower rate every 5 sec.

03/20/12 Book keeping work in progress 6

Trouble ...Continue

So, when we read the FPGA registers in quickStatus (at 0.4 mSec),we are clearing the respective memory and is now not available for the PixDSPMonitorTask to read at later time (after 5 sec)

So we can only read FPGA registers once either through quickStatus or through PixDSPMonitorTask to Monitor ROD status

03/20/12 Book keeping work in progress 7

What's currently There:

FPGA Registers (FMT,EFB,Router,RCF)

holding Status Info

Read only the FMT status registers Info and fill in

QuickStatusInfo structure

We exported the QuickStatusInfo to

PixDSPMonitorTask and publish the Info in it to IS

Read all FPGA registers and store in vector V and

dump it into IS

Reading through quickStatus

Parse the vector v for error states (D,T,B,O,H)

and publish this Info to IS

Reset the module/FMT link status according to

this parsed info and convey to

PixModuleGroup

Reading through PixDspMonitorTask

03/20/12 Book keeping work in progress 8

Now we know only one reading is Possible:Choose reading via quickStatus

FPGA Registers (FMT,EFB,Router,RCF)

holding Status Info

Read only the FMT status registers Info and fill in

QuickStatusInfo structure

We exported the QuickStatusInfo to

PixDSPMonitorTask and publish the Info in it to IS

Read all FPGA registers and store in vector V and

dump it into IS

Reading through quickStatus

Parse the vector v for error states (D,T,B,O,H)

and publish this Info to IS

Reset the module/FMT link status according to

this parsed info and convey to

PixModuleGroup

Reading through PixDspMonitorTask

Parse QuickStatusInfo for error states (D,T,B,O,H) and publish this Info to Is

analogous to existing method

Convey to PixModuleGroup

03/20/12 Book keeping work in progress 9

Monitoring the ROD actions: RodMon

Two step process:

Step 1: publish the Info to ISStep 2:Monitor and display the Info in RodMOn

03/20/12 Book keeping work in progress 10

Publishing nRST ,nCFG To Information Service:

03/20/12 Book keeping work in progress 11

Displaying nRST in RodMon

03/20/12 Book keeping work in progress 12

Ana's Work: QuickStatus Modes

03/20/12 Book keeping work in progress 13

Displaying the QS Modes in RodMon:

03/20/12 Book keeping work in progress 14

E.G user decides to change the Mode:Ana's QSManager

03/20/12 Book keeping work in progress 15

Displaying the QS Modes in Rod Mon

03/20/12 Book keeping work in progress 16

Nest Steps

We are requesting a permanent storage location in a Data base to store nRST, nCFG and Module info for further analysis (E.g to see the pattern of

auto disable modules)