Missing Modules CYRF6936

I soldered a bridge to the gap in the SCK trace and now I am not getting the missing CY6936 module error.

Next step is getting the mm I bought from Deal57 installed

Finally..................

I installed the mm today, edited the hardware.ini and was able to bind and fly my Syma X11.

Thanks everyone for all the help and suggestions.

Hi,

I'll try building off this thread before creating a new one.

I have:
* Devo 7e
* installed NRF24L01 (for bayangtoys) and A7105 ( for estes proto-x )
* installed the 10/25/15 nighly deviation-devo7e-v4.0.1-583c468

Everything worked great for 4-5 days.

This morning I powered on my Devo 7e and I get "Missing Modules: CYRF6936" and the bayang protocol has a '*' in front of it. Why does my devo think that the bayang protocol need the CYRF6936?

I'm currently working around this by putting "force=1" in my hardware.ini

Jon

The asterisk in front of Bayang indicates your tx is not detecting the nrf module either. Only the first missing module appears on the 7e/10 due to the small screen.

If you can actually control aircraft with force=1 then the module detection test is failing. I'd suspect the SPI MISO line as then protocols that don't read from the module would still work. Since the built-in module is also affected maybe MISO is shorting to another trace?

In the past, there were bugs that caused the CYRF to be reported as missing even though it was ok and some other module was missing. There were some patches to address this added, but I'm pretty sure I saw this issue afterwards as well. There may have been yet more since then, though.

Hexfet, do you believe those are now history, and we're no longer getting spurious missing module reports?

I suspect I solved my problem. I think it was z-height. I had routed my wires for the 2 new modules over the shield of the stock CYRF6936. Unfortunately, the battery housing was squeezing the wires and the shield. I think that was causing an intermittent missing CYRF6936 problem. As soon as I undid the screws a few rotations the problem went away. I opened it up the rest of the way and routed the wires around the CYRF6936 to avoid future problems.

Follow up: Quick update. 5 days and hours of flight time later. My problem has not returned. I up to about 90% confidence that I have solved the problem.

mwm wrote: Hexfet, do you believe those are now history, and we're no longer getting spurious missing module reports?

My recollection is that it was only an issue with the multi-module and was fixed, but could be wrong.

Hello everyone
I am French, sorry for the translation. I have a problem with my devo12s my cyrf Module 6936 does not work since I installed the A7105 and nRF24L01 modules for my V913 and Syma X8C .The two modules work very well but devo protocols and DSM2 not. ?? ??? . I'm on devo12-v4.0.1-97b55c0 and I did not notice this is my error and hardware settings:; Only Useful for transmitters with an after-market vibration motor
; 1 = enable-haptic
;
; switch_types: 3x2, 3x1, 2x2
; extra-switches =
;
; 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 unit UNLESS cyrf6936
; it is wired to an alternate port. Otherwise it is automatically Enabled
; enable-cyrf6936 B12 =
; has_pa-cyrf6936 = 1
 enable-a7105 = A13
 has_pa-a7105 = 1
; enable-CC2500 = A14
; has_pa-CC2500 = 1
 enable-nRF24L01 = A14
 has_pa-nRF24L01 = 1
; enable-Multimod = A13
Can you help me, thank you

Did you snap any photos of your installation connections? The fact that the other modules work would imply that the CYRF might have a bad connection somewhere. Post a sharp detailed photo if you can. Perhaps one of us can see something out of the ordinary.

thank you for helping me
here are some pictures I took during editing and schema that guided me:

I can open the radio if you want more photos.
I said that the two additional modules work well ...
Thanks Deal57

I just reconnect my radio on my pc and I looked in the '' error '' ... oops !!!!!! ???:

[Hard fault]
devo12-v4.0.1-97b55c0
R0 = 00000000
R1 = 40000000
R2 = 00000000
R3 = 08027831
R12 = 2000bf40
LR [R14] (subroutine call return address) = 080291b3
PC [R15] (program counter) = 080291b2
PSR = 01000000
BFAR = e000ed38
CFSR = 00000400
HFSR = 40000000
DFSR = 00000000
AFSR = 00000000
SCB_SHCSR = 00000000
Top of Stack:2000c000
Stack Detect:2000bf88
Backtrace:
2000bf94 : 08027831
2000bf9c : 080291b3
2000bfac : 080292cb
2000bfb0 : 08027831
2000bfbc : 08027863
2000bfc0 : 08027831
2000bfc4 : 0802592b
2000bfcc : 08025d1f
2000bfdc : 0800ae8f
2000bfec : 0800af7d
2000bffc : 0802f111
Done

I disconnected the A7105 module and cyrf6933 work .. ?? !! I reconnect the A7105 Module works well but the cyrf6933 not ... I do not understand. If my welds were bad, it would not work (A7105) NO ????
other photos:

I cannot really see anything wrong with the wiring, but it seems to me if modules stop working like that, you have a hardware issue. I can't find any other references to this sort of issue except when power issues seem to be implicated. As I understand, the 12S works on 3.3v; is it possible you're drawing too much power? Next time you power up, go into your active model and turn the TX power level down to 10mw, and disable any telemetry.

I also suggest that you see if you can get ONE of the modules working correctly before adding the second one.

Any other 12S users with ideas?

Hello
I tried another A7105 module (one of the original radio V913) and it is the same problem .
I only left the nRF24L01 and then everything goes well, the cyrf and nrf ... works very well.
I have not tried to reduce the transmission power, or remove the telemetry but before removing the original radio module of the V913, I did a test with it and the module working good . Can be a problem on the Tms circuit? .Dommage But for now I leave like that. I will watch on the forum if someone has the same problem ....
Thank you Deal57