• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 296 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC1311P3: CC1311P3

Alex Katsovich
Prodigy 150 points
Part Number: CC1311P3

Hello,

We are trying to replace the current using chip CC-430 to new one CC-1311.

Does somebody can give some tips/help how to find a correlation between RF registers and configurations of CC-430 and CC-1311.

I attached to this topic a text file with today using registers of CC-430.

I will be appreciate to any tips and help.

Thanks,

Alex Katsovich

RF Config.txt
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
//////////////////////////
// 433 Mhz //
//////////////////////////
#ifdef MOD_2GFSK_38_4KBPS
#error "For 433Mhz band ,2GFSK @ 38.4KBPS is not yet implemented !!!"
#elif defined(MOD_2GFSK_250KBPS) //250K 2GFSK 433Mhz highest sensitivity
static const RF_SETTINGS s_rfSettings_433 = {
//0x08, // 0x0C, // FSCTRL1 Frequency Synthesizer Control
0x0C,//
//0x00,//0x2D, // IOCFG0 GDO0 Output Configuration
0x06,
0x00, // FSCTRL0 Frequency Synthesizer Control
0x10, // FREQ2 Frequency Control Word, High Byte
0xA7, // FREQ1 Frequency Control Word, Middle Byte
0x62, // FREQ0 Frequency Control Word, Low Byte
0x2D, // MDMCFG4 Modem Configuration
0x3B, // MDMCFG3 Modem Configuration
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0
    TI__Genius 14460 points

    Hi Alex,

    Please see the following as it was written for exactly this purpose: https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_7_10_01_24/docs/proprietary-rf/proprietary-rf-users-guide/proprietary-rf/cc1101-migration.html#migrating-from-cc1101 

    We recommend using one of our LaunchPad development boards and using it with SmartRF Studio 7 alongside your CC430 product.

    We do not have a CC1311x LaunchPad that is optimised specifically for 433 MHz, but you could use either a LAUNCHXL-CC1352P-4 or LP-CC1352P7-4 LaunchPad for finding the PHY settings as they will be the same for the CC1311x. The CC13x2 and CC1311x devices use the same RF front-end.

    Otherwise, you could use a LP-CC1311P3 LaunchPad (https://www.ti.com/tool/LP-CC1311P3) and modify the BOM to use the 433 MHz path from one of the boards mentioned above (the 433 MHz paths are the same).

    SmartRF Studio will enable you to:

    1. Check that the CC1311x settings are backwards-compatible (if it needs to be).
    2. Easily modify both the CC430 and CC1311x registers.
    3. Export the CC1311x settings for use with the SDK.

    Regards,

    Zack

  • 0 in reply to ZC
    Prodigy 150 points

    Thank you Zack.

    Additional question:

    Transmit from CC1311 and receive via CC1311 works ok (using evaluation boards for both).

    Transmit from CC1311 and receive  via CC430 (using old product that still has CC430)  not works. This is point that we can't resolve. May be you can give us any tips which registers are should be checked in first  .

    Thanks,

    Alex

  • 0 in reply to Alex Katsovich
    Mastermind 6180 points

    A very common issue in cases like this is frequency offset between the "old" and "new" products. Are you able to check this? I assume that you are using the same sync word, data rate, deviation etc on both sides. 

  • 0 in reply to Alex Katsovich
    TI__Genius 14460 points

    Regarding possible frequency offset issues mentioned by TheGhostOf, please see SWRA122 (CC11xx Sensitivity Versus Frequency Offset and Crystal Accuracy): https://www.ti.com/lit/swra122

    The same principle of accounting for the crystal tolerances applies for the CC1311.

    If this does not resolve the latest issue, details of the PHY settings used by both devices will probably be needed as a next step so we can check them.

    Regards,
    Zack

  • 0 in reply to ZC
    Prodigy 150 points

    Hi Zack,

    I think we found the issue - wrong sync word.

    Thanks,

    Alex