cmvlc interface to MVLC
At least it compiles. And is able to do a read:
daq@bridge2:~/caendaq/nurdlib.cmvlc$ bin/rwdump -m mvlc1 --addr=0x04000000 --raw-read=32
2025-01-04,16:51:51:INFO: MVLC link_ip=mvlc1. [tools/rwdump.c:211]
2025-01-04,16:51:51:INFO: Address=0x04000000. [tools/rwdump.c:250]
2025-01-04,16:51:51:INFO: Will try default cfg path='../nurdlib/cfg/default', can be set with NURDLIB_DEF_PATH. [config/config.c:206]
2025-01-04,16:51:51:INFO: Opened '../nurdlib/cfg/default/mesytec_mvlc.cfg' { [config/parser.c:319]
2025-01-04,16:51:51:INFO: Closed '../nurdlib/cfg/default/mesytec_mvlc.cfg' } [config/parser.c:331]
FW version: 0039 HW ID: 5008 daq_mode: 0
2025-01-04,16:51:55:INFO: Raw-read. [tools/rwdump.c:319]
2025-01-04,16:51:55:INFO: Value=0x14090121. [tools/rwdump.c:326]
Though, sometimes it gives abunch of errors when doing the VME speed tests (are those needed/wanted with bin/rwdump
? Should it print the results of them then?)
2025-01-04,16:51:38:INFO: MVLC link_ip=mvlc1. [tools/rwdump.c:211]
2025-01-04,16:51:38:INFO: Address=0x04000000. [tools/rwdump.c:250]
2025-01-04,16:51:38:INFO: Will try default cfg path='../nurdlib/cfg/default', can be set with NURDLIB_DEF_PATH. [config/config.c:206]
2025-01-04,16:51:38:INFO: Opened '../nurdlib/cfg/default/mesytec_mvlc.cfg' { [config/parser.c:319]
2025-01-04,16:51:38:INFO: Closed '../nurdlib/cfg/default/mesytec_mvlc.cfg' } [config/parser.c:331]
FW version: 0039 HW ID: 5008 daq_mode: 0
Data frame with wrong magic: 0x52ba13b2 != 0x52ba13b2 or 0xf3000003 != 0x59190bc0.
Data frame with wrong magic: 0x52ba13b2 != 0x402eb405 or 0xf3000003 != 0x4d95aea9.
Data frame with wrong magic: 0x2d907907 != 0x2d907907 or 0xf3000003 != 0x41e360d2.
Data frame with wrong magic: 0x2d907907 != 0x2d907907 or 0xf3000003 != 0x41e360d2.
Data frame with wrong magic: 0x5b3b96a8 != 0x5b3b96a8 or 0xf3000003 != 0x368061ad.
2025-01-04,16:51:41:INFO: Raw-read. [tools/rwdump.c:319]
2025-01-04,16:51:41:INFO: Value=0x14090121. [tools/rwdump.c:326]
Such things typically happen when something else also is accessing the VME. This is a bug in MVLC (kind of), but cmvlc currently works around that by trying again. Ahh, might be my --mux-src-scalers
that run in the background.
--
And when anyhow at it, I'd like to suggest --bridge
instead of --mvlc
and --caen
in rwdump
?