Does SmartRF Studio 7 require both the debug (DD, DC, RESET_N) interface as well as the SPI (SCLK, MISO, MOSI, CSN) interface in order to communicate with the CC2540?
I will be soon sending our product out for FCC Qualification testing and wish to use SmartRF Studio 7 to put our products into the necessary continuous TX and continuous RX modes for testing. When connected to our products (GND, VCC, DD, DC, RESET_N), SmartRF Studio appears to recognize and control the CC2540. It recognizes the chips and no errors are reported. However it does not actually start the TX or RX as one would expect.
However, if I connect a pair of CC2540 MiniDK key fobs instead of our product, SmartRF Studio works just fine. I have also tried mixing one MiniDK and one of our product, in both directions -- swapping which is setup to TX and which is setup to RX -- and still fail to get a carrier.
The size of our product PC board does not permit including the 10 pin 0.05" header. Thus I don't have the SPI port available to connect to SmartRF Studio.
Is the SPI port necessary for SmartRF Studio 7 to control the CC2540?
If so, is my next best option to augment our product code with calls to HCI_LE_TransmitterTestCmd() and HCI_LE_ReceiverTestCmd() to initiate the FCC testing conditions, or is there a better approach?
If the SPI port is not needed, are there any ideas what might be causing our product to communicate properly with SmartRF Studio? (Note that I know that the CC Debugger connection to our product is good because I use it for flash programming and debugging without any issues.)
Thanks, Doug Bartlett
