Thanks for the explanation. That make sense. I suppose that I also could have just pulled and recompiled MPM directly on the N310 (in lieu of re-flashing the SD externally or using mender).
Rob On Mon, Jul 23, 2018 at 12:55 PM Martin Braun <martin.br...@ettus.com> wrote: > On 07/23/2018 06:57 AM, Rob Kossler wrote: > > Martin, > > Re-flashing the SD card with the 3.12 image fixed my issue! > > Rob, > > that's great news, and I'm happy you're unstuck! I'm still not entirely > sure what the exact reason is for this is, but here's a short analysis: > > On the N310, we use an architecture where a piece of software called > 'MPM' runs on the device and handles most of the device-specific > controls. Sometimes we need to fix bugs in MPM, which is a little more > annoying than fixing bugs in UHD because it's a bit harder to update. > However, whenever we change something which *requires* you to update > MPM, we will bump a compat number. > It looks like we made a change that would have required a compat number > update, but we missed that and didn't change the compat number. The end > result is that UHD 3.12 continued to happily work with MPM 3.11, but > really shouldn't have. This explains why your 3.11 UHD was fine (because > the device was running MPM 3.11), but your UHD 3.12 was only fine when > you only updated MPM. > > Like I said, we normally would force users to upgrade by changing the > compat number, which we didn't in this case. However, when issues like > this pop up, a good thing to try is to update your SD card image. You > don't have to remove the SD card in most cases, you can use our > Mender-based workflow (see here: > http://files.ettus.com/manual/page_usrp_n3xx.html#n3xx_rasm_mender). > > Cheers, > Martin >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
