Seeting SiTCP Paremeter By Hand

From my_wiki
Revision as of 01:54, 12 June 2017 by Tysaito (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Dear Takayuki, ok, I applied the solution. I will write down what I did, for reference. A good board (Italian #129) had the following:

console > rbcp ${IP} 4660
SiTCP-RBCP$ rd 0xfffffc00 128
[0xfffffc00] ff ff ff ff - ff ff ff ff
[0xfffffc08] ff ff ff ff - ff ff ff ff
[0xfffffc10] 01 ff 7c f0 - 98 01 0f e2
[0xfffffc18] 0a 01 06 1d - 00 18 00 17
[0xfffffc20] 05 b4 12 34 - 03 e8 ea 60
[0xfffffc28] 13 88 2b f2 - 01 f4 01 f4
[0xfffffc30] 00 00 00 00 - 00 00 00 00
[0xfffffc38] 00 00 00 00 - 00 00 00 00
[0xfffffc40] 83 a8 9c 99 - a6 54 54 35
[0xfffffc48] 34 45 35 38 - 66 cd 62 b2
[0xfffffc50] ff ff ff ff - ff ff ff ff
[0xfffffc58] ff ff ff ff - ff ff ff ff
[0xfffffc60] ff ff ff ff - ff ff ff ff
[0xfffffc68] ff ff ff ff - ff ff ff ff
[0xfffffc70] ff ff ff ff - ff ff ff ff
[0xfffffc78] ff ff ff ff - ff ff ff ff

The bad board (Italian #54) had the part in red missing (all "ff")

[0xfffffc00] ff ff ff ff - ff ff ff ff
[0xfffffc08] ff ff ff ff - ff ff ff ff
[0xfffffc10] 01 ff 7c f0 - 98 01 0f 97
[0xfffffc18] 0a 01 05 04 - ff ff ff ff
[0xfffffc20] ff ff ff ff - ff ff ff ff
[0xfffffc28] ff ff ff ff - ff ff ff ff
[0xfffffc30] ff ff ff ff - ff ff ff ff
[0xfffffc38] ff ff ff ff - ff ff ff ff
[0xfffffc40] 83 a8 9c 99 - a6 54 54 35
[0xfffffc48] 34 45 35 38 - d9 8a 29 0d
[0xfffffc50] ff ff ff ff - ff ff ff ff
[0xfffffc58] ff ff ff ff - ff ff ff ff
[0xfffffc60] ff ff ff ff - ff ff ff ff
[0xfffffc68] ff ff ff ff - ff ff ff ff
[0xfffffc70] ff ff ff ff - ff ff ff ff
[0xfffffc78] ff ff ff ff - ff ff ff ff

What should go there is described in this document, page 28. http://research.kek.jp/people/uchida/technologies/SiTCP/doc/SiTCP_eng.pdf

I tried to run SiTcpMpcWriter but it didn't write anything in that position... it remained all "ff". So I wrote the missing part by hand, that is (using "rbcp" program):

First, write ‘0x00’ of a byte to ‘0xFFFFFCFF’ using RBCP as written in page 29 of the mentioned document (this will enable writing).

wrb xfffffcff x00

Then, run the following commands:

wrw xfffffc1c x00180017 
wrw xfffffc20 x05b41234
wrw xfffffc24 x03e8ea60
wrw xfffffc28 x13882bf2
wrw xfffffc2c x01f401f4
wrw xfffffc30 0
wrw xfffffc34 0
wrw xfffffc38 0
wrw xfffffc3c 0

So now it looks like this,

[0xfffffc00] ff ff ff ff - ff ff ff ff
[0xfffffc08] ff ff ff ff - ff ff ff ff
[0xfffffc10] 01 ff 7c f0 - 98 01 0f 97
[0xfffffc18] 0a 01 05 04 - 00 18 00 17
[0xfffffc20] 05 b4 12 34 - 03 e8 ea 60
[0xfffffc28] 13 88 2b f2 - 01 f4 01 f4
[0xfffffc30] 00 00 00 00 - 00 00 00 00
[0xfffffc38] 00 00 00 00 - 00 00 00 00
[0xfffffc40] 83 a8 9c 99 - a6 54 54 35
[0xfffffc48] 34 45 35 38 - d9 8a 29 0d
[0xfffffc50] ff ff ff ff - ff ff ff ff
[0xfffffc58] ff ff ff ff - ff ff ff ff
[0xfffffc60] ff ff ff ff - ff ff ff ff
[0xfffffc68] ff ff ff ff - ff ff ff ff
[0xfffffc70] ff ff ff ff - ff ff ff ff
[0xfffffc78] ff ff ff ff - ff ff ff ff

I then ran QC (DAQ part) using the IP 10.1.5.4 and on my machine it took about 14 minutes, so the issue is fixed now.


Best, Andrea