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.

  • Resolved

LAUNCHXL-CC1350: High-Speed Mode with Advanced Packet Mode (CMD_PROP_RX_ADV/CMD_PROP_TX_ADV)

Prodigy 30 points

Replies: 3

Views: 56

Part Number: LAUNCHXL-CC1350

Is there any documentation available for setting up and using High Speed mode for the CC13x0/CC26x0 line of radios? It's advertised with the radio, but I've found one bit of example code for setting up HSM which more-or-less works and absolutely no documents explaining it. In addition to the lack of docs, the command structures for CMD_HS_TX/CMD_HS_RX in rf_hs_cmd.h are in a completely different order from the command structures for CMD_PROP_RX/CMD_PROP_TX found in rf_prop_cmd.h and in the CC13x0 documentation. I can't tell if that's because the processor reads the commands differently (why would it be implemented like that?) or if the provided driver is wrong but close enough to work in some cases.

The end goal of this exercise is to use high-speed mode with the advanced packet structure so that we can send more than 255 bytes at a time. We're using the simplelink_cc13x0_sdk_3_20_00_23 libraries.

  • Hi Mark,

    I think you may find this related thread useful: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/548001 

    Thanks,

    Alexis

  • If you are refeering to the 4 mbps mode, this is not supported throught the CMD_PROP_RX_ADV/CMD_PROP_TX_ADV or CMD_PROP_RX/CMD_PROP_TX, only through the CMD_HS_TX/CMD_HS_RX commands. These are only documented in the rf_hs_cmd.h, but every field in the command are well described. As you can see, the maxPktLen filed is uint16_t, meaning that it is not a problem to transmit packets longer than 255 bytes.

    BR

    Siri

     

  • In reply to Siri:

    Thanks Siri. It looks like the Queue driver I was using was incorrect, as it only provided a uint8_t for the length field, but I see that the underlying command is indeed uint16_t.

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.