Developing a universal module

Did you wire up the 5V pin (pin 1) of the module to the devo8?
I can't actually test the devo module in the multi-module right now because mine is connected to the module itself. So I need to have the devo module in its original socket to use the multi-module, and it does not work to have it installed in both places at the moment

yes, that is how the module was actually designed to work. The only reason i included the CYRF socket was for the X9d, I want it to work with Devo radios too (for the Devo7e and to make it easier to install), but it wasn't tested in that configuration.
I was able to set it up the way you have it installed, and I could bind, but range is really short (like a few inches). I have no idea why, but I can at least debug it now.

Ok, I figured it out. There was a bug in the code when initializing the power-amp on the cyrf module when using it with the multi-mod board.

I've updated the nightly build. Make sure to use nightly ac4f0b2 or newer.

Thank you for being patient. Please let me know if you run into any issues. This is still very new and there are probably other things we'll run into.

With that I'm confident enough to start shipping out my spare modules. For those of you who contacted me regarding that, you should be hearing back from me in the next several days.

The Devo7e has not been tested with the multimod board yet. It is very likely an initialization thing, as I changed the initialization code a lot. I'll try installing the module in my devo7e soon and see if I can veirfy it works.

I've seen the reboot loop with a few of the NRF24L01 protocols. I haven't ever seen it with any other protocols.

even with the MultiMod installed, you should be able to go back to 4.0.1. can you ensure your DEVO binds properly there? As I said there have been big changes to the initialization stuff, so it is quite possible that the CYRF6936 stuff doesn't work on the Devo7e

Your 1st crash indicates that the crash happened during the module initialization and the 2nd during module de-initialization. On the Devo7e, the errors.txt doesn't include the module backtrace which makes these much less useful. I should fix that

I have updated the avr.hex to Rev3 (see the downloads section to obtain the new file)
You must use the latest nightly-build (which was uploaded today: e623f92) with this (though the latest nightly will also work with the old Rev2 avr.hex as well).

There are 2 changes:
1) The multi-module will not respond to a version query until after it has been initialized to control a switch, and the CSN line has toggled at least once. The purpose of this change is to allow the multi-module to co-exist with older firmware, since otherwise the multi-module could communicate on MISO and corrupt built-in module data

2) I added more-robust detection of the nrf24L01

I'm still not happy with reliability. I don't know why I get occasional module initialization issues. It appears to have something to do with the SCK pin. If I attach the logic-analyzer to the SCK pin it is 100% reliable, but without it, I get occasional initialization issues. I've tried adding a small cap to the SCK pin without benefit. The LA has very low input cap, so maybe that isn't it. I'm currently at a loss as to what is going on It is difficult to debug something you can't measure.

blackmoon, I assume you are using the built-in CYRF module, right? Do you have the diod mod?
If not you should set:
has_pa-cyrf6936 = 0
That should let you bind your Devo protocols properly.

Edit: Also, I verified that the nrf24L01 is working properly on my Devo7e with the multimod as well. If you still have issues, upgrade to the latest nightly and Avr.hex V3

the default tx.ini used to have the proper PA settings for the devo7e, but I forgot to update that when I switched the the hardware.ini. That is why you don't recall updating it before. I've fixed it so the devo7e hardware.ini is correct going forward, but for you, it is easier just to change it.

I've updated the ModuleList with the proper connectivity here:
bitbucket.org/PhracturedBlue/deviation/wiki/ModuleList

The Multi-Module pins are reversed compared to all other modules, which is probably very confusing.

And yes Your connectivity is correct. There are multiple names used for these funtions:

Vdd = Vcc (on the programmer, hook this to the 3.3V pin regardless of what voltage your programmer uses), but you should generally program with 3.3V or without any tarnsceiver modules installed
RST = Reset
Vss = GND