diff options
author | Trung Tran <trung.tran@ettus.com> | 2017-11-13 08:32:13 -0800 |
---|---|---|
committer | Martin Braun <martin.braun@ettus.com> | 2017-12-22 15:05:06 -0800 |
commit | 9ea0d6da9e3756af91c7d1e99ee35e56bf2270d6 (patch) | |
tree | b24c75a58aaf1217aefa9798ddf241b10031db8e /firmware/usrp3/.gitignore | |
parent | fa765de7db4ab0933578e986c967d6e8eea60170 (diff) | |
download | uhd-9ea0d6da9e3756af91c7d1e99ee35e56bf2270d6.tar.gz uhd-9ea0d6da9e3756af91c7d1e99ee35e56bf2270d6.tar.bz2 uhd-9ea0d6da9e3756af91c7d1e99ee35e56bf2270d6.zip |
mg: enable init and track calibration API
Currently, AD9371 turned on most of the calibration and hard coding the turning
on process during bringup time.
This change enables users to pass in a mask field for init ARM calibration and
tracking arm calibration at the time creating USRP device reference.
This mask field can be passed through device arguments of:
1/ init_cals : for init ARM calibration masks. This is defined in AD9371 UG-992
table 65. Default to 0x4DFF
2/ tracking_cals : for tracking calibration masks. This is defined in AD9371
UG-992 table 66. Default to 0xC3
Example of pasing in init calibration and tracking calibration mask
usrp_application --args "init_cals=0x4f, tracking_cals=0xC3"
NOTE: UHD currently expect user to input the correct init_cals and
tracking_cals. There's no mechanism to check if init mask and tracking mask are
valid. For example if the init mask field not mask 0x4f, the AD9371 will failed
to setup.
Diffstat (limited to 'firmware/usrp3/.gitignore')
0 files changed, 0 insertions, 0 deletions