, Valkire had the same problem, but I don’t find a solution for it.
As this issue appears only for Raptor, I added the recommended resistors, I “pull-uped” MISO trying to make Raptor similar to cerbuino. Nothing works.
Now the cc3000 module works better on cerbuino but still failing on Raptor.
If someone solved this problem, please let me know how.
@ crespi - Yeah, as I said in that post you linked, you really need an oscilloscope to know what’s going on. Obviously, there is some difference in the signal being generated by the raptor and we can only guess what it is. The cc3000 is very picky. I only added the resistors on the SPI out of desperation.
Is there any difference in how you are powering the cc3000 with the Raptor? Is the ground on the cc3000 connected to the ground of the Raptor processor?
@ Valkyrie-MT - I bought an oscilloscope in order to solve this issue (and others too).
About the power supply, I tried dual and simple power source, always the same results. My module has a gadgeteer socket (RIP simple power module), connected to Socket 1 on the Raptor.
There is some info that maybe someone could be interested in:
Raptor is very sensitive to noise. I can’t debug any program from Visual Studio while the mainboard is supplied by external power.
Although CC3000 module works on Cerbuino, it may fail if gadgeteer cable is too long. Short cables are preferred.
If you pretend to use Raptor with a Xbee module, you should think about plug an antenna to the Xbee.
Thanks Valkyre. If you have any other info that you think it will help me, please tell me about it.
English is not my native language, so please excuse my mistakes.