Skip to content

Commit daf25e3

Browse files
committed
Update README.md with CRORC docs
1 parent 6c65d4e commit daf25e3

File tree

1 file changed

+29
-12
lines changed

1 file changed

+29
-12
lines changed

README.md

Lines changed: 29 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ In order to run ALF a DIM Nameserver has to be up and running. For performance r
99
## Usage
1010

1111
### o2-alf
12-
o2-alf is the binary of the ALF server. The only option it expects is the address of the DIM Nameserver. It can be passed either as a command-line argument or as an environmental variable.
12+
o2-alf is the binary of the ALF server. It expects the address of the DIM Nameserver, which can be passed either as a command-line argument or as an environmental variable.
1313

1414
`
1515
o2-alf --dim-dns-node thedimdns.cern.ch
@@ -20,18 +20,18 @@ DIM_DNS_NODE=thedimdns.cern.ch
2020
`
2121

2222
### o2-alf-client
23-
o2-alf-client is the binary of an ALF client used solely for testing purposes. On top of the DIM Nameserver it expects the hostname of the node hosting the ALF server, the CRU's sequence number and the link number as command-line arguments. Different arguments to test different types of services are available.
23+
o2-alf-client is the binary of an ALF client used solely for testing purposes. On top of the DIM Nameserver it expects the hostname of the node hosting the ALF server, the card's sequence number and the link number as command-line arguments. Different arguments to test different types of services are available (run with `--help`).
2424

2525
`
26-
o2-alf-client --dim-dns-node thedimdns.cern.ch --alf-id thealfserver --cru-sequence 0 --link 4
26+
o2-alf-client --dim-dns-node thedimdns.cern.ch --alf-id thealfserver --card-sequence 0 --link 4
2727
`
2828

2929
## Services
3030

3131
Service names are identified by the server's hostname, the card's sequence number (as reported during ALF's startup) and the link, as follows:
3232

3333
`
34-
ALF_[hostname]/SERIAL_[cru_sequence_number]/LINK_[link]/[service_name]
34+
ALF_[hostname]/SERIAL_[card_sequence_number]/LINK_[link]/[service_name]
3535
`
3636

3737
### DIM RPC services
@@ -44,8 +44,9 @@ The services are DIM RPC services. Every RPC is called with a string and expects
4444
* An exception is made for SWT words which are 76-bit unsigned integers. (e.g. 0x0000000000badc0ffee)
4545
* Input needs to be prefixed with "0x" but not necessarily with leading zeros.
4646
* Lines prefixed with `#` are disregarded as comments.
47-
48-
#### REGISTER_READ
47+
48+
#### CRU
49+
##### REGISTER_READ
4950
* Parameter:
5051
* Register address
5152
* Returns:
@@ -55,7 +56,7 @@ The services are DIM RPC services. Every RPC is called with a string and expects
5556
* DIM input: `0x0000f00d`
5657
* DIM output: `0x0000beef`
5758

58-
#### REGISTER_WRITE
59+
##### REGISTER_WRITE
5960
* Parameters:
6061
* Register address
6162
* Register value
@@ -66,7 +67,7 @@ The services are DIM RPC services. Every RPC is called with a string and expects
6667
* DIM input: `0x0000f00d,0x0000beef`
6768
* DIM output: ` `
6869

69-
#### SCA_SEQUENCE
70+
##### SCA_SEQUENCE
7071
* Parameters:
7172
* Sequence of SCA operations as follows:
7273
* Operations may be:
@@ -79,7 +80,7 @@ The services are DIM RPC services. Every RPC is called with a string and expects
7980
* DIM input: `0x00000010,0x00000011\n3\n0x000000020,0x00000021`
8081
* DIM output: `0x00000010,0x00000111\n3\n0x00000020,0x00000221\n`
8182

82-
#### SWT_SEQUENCE
83+
##### SWT_SEQUENCE
8384
* Parameters:
8485
* Sequence of SWT word and operation pairs as follows:
8586
* Operations may be:
@@ -96,7 +97,7 @@ The services are DIM RPC services. Every RPC is called with a string and expects
9697
* DIM input `reset\n0x0000000000badc0ffee,write\nread\n0xbadf00d,write\n4,read`
9798
* DIM output `0\n0x0000000000badc0ffee\n0\n0x000000000000badf00d\n`
9899

99-
#### IC_SEQUENCE
100+
##### IC_SEQUENCE
100101

101102
* Parameters:
102103
* Sequence of IC operations as follows:
@@ -112,7 +113,7 @@ The services are DIM RPC services. Every RPC is called with a string and expects
112113
* DIM input: `0x54,0xff,write\n0x54,read`
113114
* DIM output: `0x000000ff\n0x000000ff\n`
114115

115-
#### IC_GBT_I2C_WRITE
116+
##### IC_GBT_I2C_WRITE
116117

117118
* Parameters:
118119
* Value
@@ -124,7 +125,7 @@ The services are DIM RPC services. Every RPC is called with a string and expects
124125
* DIM input `0x3\n`
125126
* DIM output ` `
126127

127-
#### PATTERN_PLAYER
128+
##### PATTERN_PLAYER
128129

129130
* Parameters
130131
* Sync Pattern
@@ -145,3 +146,19 @@ The services are DIM RPC services. Every RPC is called with a string and expects
145146
* Example:
146147
* DIM input `0x23456789abcdef123456\n0x5678\n0x9abc\n42\n0\n53\n30\n29\n#a comment\nfalse\ntrue\nfalse`
147148
* DIM output ` `
149+
150+
#### CRORC
151+
152+
##### REGISTER_SEQUENCE
153+
* Parameters:
154+
* Operations may be:
155+
* `write` with address and value (e.g. `0x0000f00d,0x0000beef`)
156+
* `read` with address (e.g `0x0000cafe`)
157+
158+
* Returns:
159+
* `write` always retuns `0`
160+
* `read` returns the value read from the register
161+
162+
* Example:
163+
* DIM input `0xf00d\n0x0000f00d, 0x0000beef\n0x0000f00d`
164+
* DIM output `0xcafe\n0\n0xbeef\n`

0 commit comments

Comments
 (0)