Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

CC1352R: DMM sub-GHz RF only randomly transmitting

$
0
0

Part Number:CC1352R

This is a follow-on to the related post, I will try to include all pertinent details here...

I am working with a custom board using the CC1352R. We had a sub-GHz protocol implemented and running on the board when I was tasked with adding BLE capability to "provision" the board at power up. I started with the DMM WSN/Simple Peripheral example, removed the WSN sub-GHz implementation and replaced it with ours. The sub-GHz tasks are waiting on the BLE task to complete (either a connection/disconnection or a timeout) before doing anything with the radio.

I did modify the DMM states and policy- added a BLE done state and a policy entry that gives the sub-GHz priority when BLE is in that state (BLE also set to PAUSED in that state). (However, because I have exited the BLE task and am no longer doing anything, I think this change is moot.)

I have gotten to the point that everything is compiled and running, but I am only seeing sub-GHz RF activity on a spectrum analyzer randomly and not every time I am attempting to transmit.

The sub-GHz protocol is pretty straight-forward- starting at a base frequency, transmit a packet, sleep for 1 second, increment the frequency 1 step, repeat. After 50 increments, it returns to the base frequency. I expect to see the transmission every second. Running for over 60 seconds, I am seeing only 6-10 transmissions.

I have confirmed that the attempt to transmit is occurring every second and that no errors are being returned from the library:

//start tx at start slot
RFFE_SetMode(RFFE_MODE_TX);

/* Set frequency */
RF_postCmd(myRfHandle, (RF_Op*)&RF_cmdFs, RF_PriorityNormal, NULL, 0);

/* Send down link control packet */
RF_postCmd(myRfHandle, (RF_Op*)&RF_cmdPropTx, RF_PriorityNormal, NULL, 0);

This code is unchanged from the original project which runs as expected.
The original project is built using CCS7 with compiler 16.9.6.LTS, SDK CC13x2 2.10.0.48, & XDCTools 3.50.4.43
vs. CCS9 and newer tools for the DMM-based project- compiler 18.12.1.LTS, SDK CC13x2 2.30.0.45, & XDCTools 3.50.8.24

As you can determine from the SDK used, the CC1352R part on our custom board is a pre-production Rev. C.

Any thoughts on why I am not getting the actual transmission each time I request it?

Thanks!
.Tim


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>