e310/e320: Move E310 to MPM architecture and refactor

- Turns the E310 into an MPM device (like N3xx, E320)
- Factor out common code between E320 and E310, maximize sharing between
  the two devices
- Remove all pre-MPM E310 code that is no longer needed
- Modify MPM to remove all existing overlays before applying new ones
  (this is necessary to enable idle image mode for E310)

Co-authored-by: Virendra Kakade <virendra.kakade@ni.com>
Signed-off-by: Virendra Kakade <virendra.kakade@ni.com>

1 files changed, 6 insertions, 0 deletions

diff --git a/mpm/python/usrp_mpm/periph_manager/base.py b/mpm/python/usrp_mpm/periph_manager/base.py
index 2dc69e908..e297effbd 100644
--- a/mpm/python/usrp_mpm/periph_manager/base.py
+++ b/mpm/python/usrp_mpm/periph_manager/base.py
@@ -131,6 +131,12 @@ class PeriphManagerBase(object):
     # specific implementation. Each PeriphManagerBase-derived class should list
     # information required to update the component, like a callback function
     updateable_components = {}
+    # The RPC server checks this value to determine if it needs to clear
+    # the RPC method registry. This is typically to remove stale references
+    # to RPC methods caused by removal of overlay on unclaim() by peripheral
+    # manager. Additionally the RPC server will re-register all methods on
+    # a claim(). Override and set to True in the derived class if desired.
+    clear_rpc_method_registry_on_unclaim = False
 
     @staticmethod
     def generate_device_info(eeprom_md, mboard_info, dboard_infos):