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.

CC1310: Problems when using the 4x4 package of the CC1310

Part Number: CC1310
Other Parts Discussed in Thread: CC1101, SEGGER

Tool/software:

Hello I have question regarding the package sizes of the CC1310 and what if any differences there are regarding programming them.

I work with two boards, one beeing the cc1310 Launchpad and the other one is a custom board. My application sends a telegramm depending on an intervall variable and toggles a display depending on an other. My code runs on both the Launchpad and the custom board, but only the Lauchpad transmitts the telegram. I checked with the debugger and EasyLink_transmit(&lbtPacket_1) returns EasyLink_Status_Success in both cases. I only use pins that are accessible on both boards and both can toggle the Display. I used smartRF Studio to generate the rf settings. Now my question is: Are there any Speciffic setup procedures that I have overloocked that make the smaller package work? 

I also have set the cap-array delta so it is the same in my application as it is in the example application for the custom board.

  • Hi GBU,

    Can you communicate from your custom board, to/from the Launchpad using SMARTRFSTUDIO?

    Please run the test, as that will allow us to know if the radio path on your custom board is correct.

    Regards,

    Arthur

  • Hello Arthur,
    I cant connect my custom board to smartrf Studio, but I have confirmed, that the RF-Communication works, with the examples provided by the designer of the Custom board. This example has TX and RX so both ways work. I also compared the smartrf setting files and could not find any major differences, except the ones I made. I have to use Manchester Encoding and be compatible with a cc1101 chip because thats what the gateway uses that Iam working with.

    ps: I have just seen that it should be possible to use the launchpad as a bridge for smartrf Studio, but my custum board uses a Segger J-link for Programming and debugging and the PDF i have found doesnt mention the cc13xx which Iam using.(CC Debugger User's Guide (Rev. H) (ti.com)

    Greetings
    GBU

  • Hi GBU,

    This PDF you are mentioning is indeed not for the XDS110, but for our older CC Debugger probe.

    As long as you have access to the cJTAG signals TMS and TCK, you should be able to connect thoses to a Launchpad, and use SmartRF studio.

    Regards,

    Arthur

  • Hi,
    got it connected, but cant see anything on my sdr (I currently only have one launchpad so I cant use that to check for messages) and I only have a very limited ammount of settings accessible compared to when i connect the Launchpad.
    There are no CC1101 settings for example. But the sent packet counter increases.

  • Hi GBU,

    Then it is a bit worrying. Are you seeing anything on the SDR if you put the antenna very close to the device?

    Regards,

    Arthur

  • No it does not show anything.
    The SDR Antenna and the Custom board are right next to each other on my workbench.
    I can check some other example Applications this afternoon (at least it will be afternoon where I am).
    But they worked befor, so i think it might be something different.

    In the drop down menu " RF Design based on:" I can choose between a few different Designes, but i guess that doesnt realy make a diffenrence since my options and settings dont change when I do that. But I still belive it has to do something with the cc1101 option I have to use. 

    Regards,
    GBU

  • Hi GBU,

    Just to clarify:

    • The CC1310 requires an XDS110 debugger and this can be using the on-board XDS110 debugger from another LaunchPad.
    • The CC1101 requires a CC Debugger, following the instructions in Section 6.3 of SWRA197 (which you linked to previously).

    To set up the CC1310 4x4 (RSM) package in SmartRF Studio, you can do this by selecting Settings -> Custom Target Configuration and selecting New - from there you can select the device, package size, and front-end configuration as well as the I/O configuration.

    Regards,

    Zack

  • Hey Zack,
    I set up the RSM Package as you showed, but it didnt work. The launchpad still works even with the 4x4 settings and shows on the sdr, but the custom board does not.
    I have checked again with the "lbt example" and that works on the custom board, so its not the board. I then configured the working settings files to use Manchester with the following overwrites:

    HW_REG_OVERRIDE(0x52B4,0x270C)
    MCE_RFE_OVERRIDE(0,5,0,1,0,0)
    Format conf: 0x0AA0
    That worked, but I cant use these setting to connect to the gateway that uses the cc1101 as Receiver. That only works when i choose the legacy settings in smartrf Studio and the above overwrites and only with the launchpad.


    Greetings 
    GBU

  • Hi GBU,

    Compatibility between the CC1101 and CC1310 has some limitations regarding Manchester encoding: https://dev.ti.com/tirex/explore/node?node=A__ANOIr3l08chTYsei9X2-SQ__com.ti.SIMPLELINK_CC13XX_CC26XX_SDK__BSEc4rl__LATEST

    SmartRF Studio 7 can also be a little tricky to configure overrides as it can reset the overrides when selecting between TX and RX.

    Please can you check you are implementing the steps described in the User's Guide? Please also share the packet format you are trying to receive.

    Regards,

    Zack

  • Hello Zack,
    after a week of mailing screenshots I could get an answer of the Manufacturer of the Board Iam using. They mistakenly send me a Board which uses a Revision A Chip. I was told that these chips have problems working with smartRF Studio. I have received boards using the Revision B Chips but have not had time to check if they work yet. But I belve they should, since the Launchpads I have are also Revision B. 
    I will keep you informed about my findings after I checked if the new Boards Work.

    Greetings,
    GBU