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.

LAUNCHXL-CC1310: CC1310 F128RHBR project stuck?

Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310,

Hi team:

1,The official routines are developed for the development board's chip. Now the new board is the CC1310 F128RHBR chip. Now the official routine rfPacketTx is dead. Runs pretty well on the development board LAUNCHXL-CC1310.

2,Routine directory: C:\ti\simplelink_cc13x0_SDK_4_20_02_07\examples\nortos\CC1310_LAUNCHXL\drivers\rfPacketTx

3,what is the project configuration if the chip has been replaced? The main thing is that TI has different packages of chips. The pins can be different?

4,to prevent the pin configuration from being the cause, note the IO operation code. The location of the dead time is

/* Send packet */
RF_EventMask terminationReason = RF_runCmd(rfHandle, (RF_Op*)&RF_cmdPropTx,RF_PriorityNormal, NULL, 0);

stuck in RF_runCmd function does not return!

5,It is OK to send and receive with smart RF. 

Best regards

Alex

  • Hi Alex

    If you have made your own board with a 5x5 package, you need to update the board files in your project to reflect your HW.

    For example, to change to the 5x5 package, remove all defines for all IOs not available (IOID_15 and higher) since the 5x5 package has only 15 DIO pins as listed in the datasheet.

    Remove the modules/pins not used including ADC, Display, SPI1, LED, and PIN due to limited pins.

    Siri

  • For example, to change to the 5x5 package, remove all defines for all IOs not available (IOID_15 and higher) since the 5x5 package has only 15 DIO pins as listed in the datasheet.

    Remove the modules/pins not used including ADC, Display, SPI1, LED, and PIN due to limited pins.

    The customer asked 

    How to remove?

  • They need to take the CC1310_LAUNCHXL.h file and make it correspond to the 5x5 device .

    For example is the analog capable DIOS on 5x5 on DIO_7 to DIO_14 and not DIO_23 to DIO_30 as on the 7x7.

    The customers have made their own board I assume, so they need to make this file correspond to their HW. 

    The also have to change CC1310_LAUNCHXL.c

    There are for example code for setting up the Display, but if their HW does not have a display connected of the same type as the LP, this code should be removed.