This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1314R10: Canntot transmit properly at 1 Mbps

Part Number: CC1314R10
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

 I am testing transmission of 1 Mbps proprietory mode with cc1314R10. In CCS there is no option for 1 Mbps, so I have modified the 500 kbit phy with the parameters from the 1 mbps phy that is present for the CC1312.

This does not work, I have some test data here, setup is a LP-EM-CC1314 that transmits Ethernet packets over radio, and received on a PC with SmartRF Studio and a LaunchPad CC1312 as receiver.

This setup works perfectly if the transmitter is a self designed board with a CC1312. To eliminate board issues I am using a Launchpad  and SmartRF studio as receiver. Here is a dump of packets received:

19:36:24.088 | ff | 2303 | ff ff ff ff e4 fa c4 77 69 a9 08 06 00 01 08 00 06 04 00 01 e4 fa c4 77 69 a9 00 00 00 00 00 00 00 00 00 00 c0 a8 01 29 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3e 4c 00 00 a5 df ff fd b5 ff fa cf fe f7 7e ff bf ff ff ff dd ff b7 f1 bb 37 ff f1 8f ed ff dd cb ff 55 55 55 56 4c 2d 47 78 2c 3c 00 00 00 ef ff 93 eb 11 dd a6 a4 20 18 00 04 20 00 18 11 de dc 00 01 bf f1 cf c6 bf b9 ff bf 8d f6 fd ff df fd fe fb ab db 6f a7 ef e7 ef 0f 7f 37 bb ef b8 ff c7 ef d5 3c f7 af fb af ef b3 d7 ff 1b 0f fb bf ef ff fd bf ef cf 7f ff ff e3 ff fa ff 6f f1 df 7f f5 7b ee 7f bf dd ee ff dd ff ff bf e3 fb ff ff fe 7d ff e7 fd fa 7d ff fb fa ff bb b9 ff bf ff ed ee ff 7c ff eb ad 8f d9 ff f7 d7 73 fd ef ed 6f e7 ce ff af 3d f6 27 fb 6f f6 bf 7f 7f ff 7b 9f  |  -45 CRC error

19:36:24.619 | 01 | 2192 |  |  -44 CRC error
19:36:24.619 | 0b | 3840 | 00 00 3c 00 64 d1 54 cb 48  |  -45 CRC error
19:36:24.744 | ff | 2303 | ff ff ff ff 5c 93 a2 9d 75 a7 08 06 00 01 08 00 06 04 00 01 5c 93 a2 9d 75 a7 c0 a8 01 38 00 00 00 00 00 00 c0 a8 01 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bf d7 4d ce 70 98 00 08 07 ff ff f7 ff ed fb fe ff 7f fb f3 ee ff bf df 33 ff df bf ff ff fe fb ff ff 9f ef 7f 3d 55 55 55 64 c2 d4 77 82 c3 c0 00 00 0f 7f d7 24 e8 a7 5d 69 c2 01 80 00 42 00 01 81 09 a9 80 00 01 ed ff ff df bf ff ff bf ff ff ff 7f 7b ff bd ff ff ff ff ff 3f ff e6 bb ff bf df fd 7f ff fb ff ff ff ff ff e3 df ff ff be 7b ef 7e fb fd f1 ff ed fe fd ff fe 7f ab ff fd ff ff ff ff fe ff fd ff ff 9f 7f ff 5d fe ff f3 fb fe fb 7f ea ff ff fd ff fd ef de ff ff ff bc ff ff ff ff ff fb ff eb ff e7 ff bf fd 7f ff ff ff ff ff ff fb ff ff ff bf be df fb ff ff ff 6f f7 97 e7 fb df bf 9f  |  -44 CRC error

19:36:25.603 | ff | 2303 | ff ff ff ff 5c 93 a2 9d 75 a7 08 06 00 01 08 00 06 04 00 01 5c 93 a2 9d 75 a7 c0 a8 01 38 00 00 00 00 00 00 c0 a8 01 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bf d7 4d ce 70 98 00 00 0f ff df ff ff fe ff b7 ef f3 be ff df 3f 5f df bf c7 31 ff ff 9f bd b7 fb cf fd fb 3d ea aa aa aa c9 85 a8 ef 05 87 80 00 00 1f 7f ae 49 d1 4e ba d3 84 03 00 00 84 00 03 02 16 56 00 03 ef f7 fe ee 5f ff fb b7 ff df fd ff 3f 7f 6f ff ff af fd bf d7 ff ff cf ff f3 f6 fe ff fd ff ff ff ff ff e7 bf ff ff 9b fb 8d ff 7b 7d ff df ef fd ff fe ff 7f fb ff be bf f9 f7 3f ff ff 9f 6f ff fb 7e ff bf ff ff ff 7f ff 3e df fd ff f8 ff ff ff ff df ff ff ff bf 9f 7f 6f ff dd 3f ff ff fc ff ff fc ff ff fd bd bf 27 ff bf 77 ff ff f5 dd cd 3f fe df 6f 30 ff f7 bf ff fc 7f f7 9f fe ff  |  -45 CRC error

What can be seen is that all packets start with byte 3 of the ACTUAL packet, it contains a one byte ptype indicator, followed by the data. These three captured packets start with 4 bytes 0xff, these are actually 6, so two are lost,  as well as the preceeding ptype byte. Also this proves that we are on frequency, with correct bitrate since part of the data seems reasonable. All packets have a CRC error, where there can be many explanations.

Thús, the identical code that communicates perfectly cc1312 - cc1312 does not receive cc1314 transmissions to a CC1312.

All I want for Christmas is an 1 Mbps entry in CCS that creates a good working configuration for CC1314 that is compatible with the CC1312 implementation.

Regards and I wish you a happy holiday,

Gullik

  • Since I understand you want the sysconfig, here is a cut'n'paste of the sysconfig:

    Copy paste from sysconfig (of my modified 500 kbit example)

    500 kbps, 190 kHz Deviation, 2-GFSK, 622 kHz RX Bandwidth

    Description

    RF Settings module for proprietary protocols

    Frequency Band
    779 - 930 MHz
    PHY Type
    500 kbps, 190 kHz Deviation, 2-GFSK, 622 kHz RX Bandwidth

    PHY Properties
    Frequency (MHz)
    916.0000
    Symbol Rate (kBaud)
    1000.000
    Deviation (kHz)ize
    350.0
    RX Filter BW (kHz)
    2185.1
    TX Power (dBm)
    14
    Whitening
    No whitening
    Preamble Count
    4 Bytes
    Preamble Mode
    Send 0 as the first preamble bit
    Sync Word Length
    32 Bits
    Sync Word
    0x930B51DE

    also, link packet size max is set to 255 bytes

  • Hi Gullik,

    I think that I have found the issue. If you start from the 500 kbps CC1314R10 SmartRF Studio 7 settings, you will use the IEEE 802.15.4 packet format.

    However, if you modify instead the "50 kbps, 25 KHz Deviation, 2-GFSK PHY", it will work.
    Here are two back to back Packet TX, Packet RX tests.

    Let me know,

    Mvh,

    Arthur

  • Thank you very much Arthur,

    This was indeed the case, and I am now running my link CC1312 - CC1314.

    I thought it was strange that all the various parameters that you CAN set looking

    in the technical manual were not in the phy config, but did not realize I was creating the

    wrong "type" of phy.

    I spent so much time handchecking with the debugger that the messages that

    were sent were the ones required. But this resolved the case easily.....

    So, I can continue the migration, and hopefully the code can be shared for these two types.

    A Merry Christmas to you,

    Gullik