... | ... | @@ -16,9 +16,27 @@ project](https://www.ohwr.org/project/mock-turtle/wikis/LHC-Instability-Trigger) |
|
|
## Q: is there any way to determine what gateware version my TDC is using?
|
|
|
|
|
|
A: Gateware in OHWR FMC modules is loaded dynamically, so you just need
|
|
|
to know which binary was loaded at boot time. FMC gateware does not
|
|
|
contain any global version tag that might be read dynamically after the
|
|
|
fact.
|
|
|
to know which binary was loaded at boot time. Recovering this
|
|
|
information from loaded gateware is a bit trickier: a synthesis record
|
|
|
is embedded in the SDB block at the very beginning of the register map.
|
|
|
If you really want to know, you need to mount
|
|
|
debugfs:
|
|
|
|
|
|
cfv-774-cdv28:FmcDelay1ns4cha-02c1$ sudo mount -t debugfs none /sys/kernel/debug/
|
|
|
cfv-774-cdv28:FmcDelay1ns4cha-02c1$ cat /sys/kernel/debug/FmcTdc1ns5cha-0200/dump_sdb
|
|
|
FMC: svec.1 (SVEC), slot 0, device FmcTdc1ns5cha-0200
|
|
|
00000651:e6a542c9 WB4-Crossbar-GSI
|
|
|
00000651:eef0b198 WB4-Bridge-GSI (bridge: 00010000)
|
|
|
00000651:e6a542c9 WB4-Crossbar-GSI
|
|
|
0000ce42:00000602 WB-Onewire.Control (00011000-00011007)
|
|
|
0000ce42:00000604 WB-TDC-Core-Config (00012000-000120ff)
|
|
|
0000ce42:00000605 WB-FMC-TDC.EIC (00013000-0001300f)
|
|
|
0000ce42:00000606 WB-I2C.Control (00014000-0001401f)
|
|
|
0000ce42:00000622 WB-TDC-TsFIFO (00015000-000150ff)
|
|
|
....
|
|
|
|
|
|
This is rather old firmware, though, and has no synthesis record, so
|
|
|
we're out of luck here.
|
|
|
|
|
|
-----
|
|
|
|
... | ... | |