Hello,
As other people in this list, i face issues with calibration.
I use a limeSDR board, v1.4s, and the LimeSuite, compiled from latest git master, on Ubuntu
So, I see in the source tree: mcu_program, nevertheless no documentation, even a short readme
Looking into this source tree, it seems it tests the calibration, that may be done inside the on board MCU.
I compile with cmake, copy the files it needs ( rxtest.ini, calibrationsLMS7_MCU.hex)
- remane RxTest.ini as rxtest.ini (looking into the source code)
Then I run
$ sudo ./MCU_TestBench
[INFO] LMS7002M cache /home/laurent/.limesuite/LMS7002M_cache_values.db
[INFO] Estimated reference clock 30.7195 MHz
[INFO] Selected reference clock 30.720 MHz
Running tests with LimeSDR-USB FW:3 HW:4
MCU programming : 16384/16384
MCU Programming finished, 926 ms
MCU calibration FAILED : 0x72
F: 1000 MHz, DCI: 0 DCQ: 0 GI:2047 GQ:2047 PH: 0 - FAIL | 100 ms
So, test fails, great but WHAT does IT means ?
Thanks in advance
Laurent
2 Likes
Hi, MCU_TestBench is not meant to be complete end user application to verify calibration correctness.
It’s an internal development utility that was used to prototype and debug calibration algorithms to meet the MCU hardware constraints.
From your given information I can say that failure is caused by failing to lock transmitter’s PLL due to wrong reference clock.
Your board’s reference clock is 30.72MHz, while in the test bench source code MCU is being specified to expect 40MHz
status = MCU_SetParameter(MCU_REF_CLK, 40e6);
You’re right: i changed the source code value, then the test declare itself “OK”
Nevertheless, this is not understandable without any (even short) documentation
$ ./MCU_TestBench
[INFO] LMS7002M cache /home/laurent/.limesuite/LMS7002M_cache_values.db
[INFO] Estimated reference clock 30.7195 MHz
[INFO] Selected reference clock 30.720 MHz
Running tests with LimeSDR-USB FW:3 HW:4
MCU programming : 16384/16384
MCU Programming finished, 915 ms
F: 1000 MHz, DCI:-14 DCQ: 5 GI:2047 GQ:1983 PH: -6 - OK | 241 ms
