Hi Joe, Marcus is right wrt. MPM being on the device. In short you can say that everything that is Python runs on the device while the CPP code is on the host. The bootup procedure basically is as follows:
* The device starts up. * MPM is started as service on the device. * When MPM starts on X4x0, it’ll bring up the RFDC already as far as it can. * When a UHD session is initiated, it’ll connect to the device and do what we call the self-calibration (which you may consider as the last step in the RFDC initialization) In UHD 4.4 the self-calibration was done during the device startup, too. However, with the clocking flexibility of X440 which shares a big amount of the driver with X410 we had to move the self-calibration into the UHD session startup in UHD 4.5 as only there we really know which exact configuration the user has requested. While it takes a little bit longer to bring up the first session after a device startup, the RF performance is slightly improved, too. Any subsequent session which uses the same clock configuration (for X410 that’s basically only clock source and time source not changing) won’t re-run the self-cal but will be based on the cal coefficients from the last self-cal. BR, Martin From: jmalo...@umass.edu <jmalo...@umass.edu> Sent: Wednesday, October 4, 2023 4:32 PM To: usrp-users@lists.ettus.com Subject: [USRP-users] Re: RFDC initialization in UHD 4.5.0.0 for x410 Thanks for the insight. I was under the impression that the MPM was completely host-side. So if I am understanding correctly, When the radio block is instantiated, the x410 calls the host side for the RFDC initialization? And additionally, and I am not sure if this is the “right” way to think about it, does the x4xx.py “run” on the x410 itself? National Instruments Dresden GmbH; Geschäftsführer (Managing Director): Jerome Meyer; Sitz (Registered Office): Dresden; HRB (Commercial Register No.): 22081; Registergericht (Registration Court): Dresden This email and any attachments are intended only for the person to whom this email is addressed and may contain confidential and/or privileged information. If you received this email in error, please do not disclose the contents to anyone, but notify the sender by return email and delete this email (and any attachments) from your system.
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com