Hardware.ini changes?

I have a devo 7E with the multimod and all 4 added modules that I built 2 years ago. I have been using the A7105 and NRF24 modules, but wanted to start using the cc2500 for a FRSky XM+ Rx, which protocol was not in the 5.0.0 build I did back then. SO, I upgraded to the latest nightly build 2 days ago, and stupidly overwrote the hardware.ini file when updating the files. I restored from a USB Backup folder the following (I'm not sure it was the final version, but I think so):
;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
extra-switches=3x2
;
;button_types: trim-all, trim-(left|right)-(up|down|both)
;May occur more than once if necessary.
;extra-buttons=
;
[modules]
; there is no need to enable the cyrf6936 module unless
; it is wired to an alternate port. It is Enabled automatically otherwise
; enable-cyrf6936 = B12
has_pa-cyrf6936 = 1
enable-a7105 = S1
has_pa-a7105 = 1
enable-cc2500 = S3
has_pa-cc2500 = 1
enable-nrf24l01 = s402
has_pa-nrf24l01 = 1
enable-multimod = A13

I am now getting a MultiMod missing message when I boot up the radio, and nothing works. If I bypass that msg. I get a "Protocol Mismatch 0801fcec 0801fd1c" error, and if I open a model (SymaX) that was working, I can't re-init (nothing happens), nothing binds automatically, and even though the FRSkyX protocol is in the list, I can't enter the protocol to get to a sub-menu (like for SymaX). Other than that my upgrade went perfectly.

Have any pin addresses changed for the hardware.ini in the last 2 years, specifically does this look correct for the multimod?
Appreciate any advice! Thanks!

The protocol mismatch error indicates the upgrade was not successful (protocols directory not updated?). Maybe best to back up the models directory, do a full install of the nightly build, then restore models.

OK, I'll try it. Does the hardware.ini look OK? Also do I want the devo7e-256-v5.0 or the devoe7e-v5.0...?

I think the ini is okay but have never had a multimodule. The -256 build is for folks who've replaced the CPU chip.

Thanks! That worked. Syma, Bayang. and Flysky (Nihui) now working again. Now can move on to see if cc2500 will bind to XM+ (FRSkyX).

Oh, I tried the 256 version and radio was dead after flashing! Thought I bricked it!

Appreciate the help!