CC1310EMK: SimpleLink Sub 1-GHz CC13x0 Software Development Kit release on CC1310 Development Board

The easy link examples in SDK can run on CC1310DK directly and TI 15.4 Stack examples might need some modifications to make them works on CC1310DK.

"I am more interested in using it because of the frequency hoping feature." Do you mean CC1310EVM vs CC1310 Launchpad in this case? The EVM and Launchpad are two different development platforms but can support the same things.

The examples for the drivers etc included in the SDK are made to support both the EVM and LPs.

Thank you Chen and TER.

TER what I meant was that the examples for TI 15.4 stack are they designed to work only for CC1310 Launhpad or can then work as it is for Development board as well since the collector, sensor and coprocessor examples are the ones that demonstrate the Frequency Hoping concept ( at least that is what I understand)?

I am aware that the Easy link, proprietary rf examples and driver examples work both for EVM and LP as I have used those for my application but not sure about the TI 15.4 stack examples.

Thank you

Vikram

You can refer to sunmaysky.blogspot.tw/.../how-to-porting-collector-example-in-ti.html

Thank you Chen,
I had done this modification but I was assuming was there any other changes to be done as in the online document it mentioned that the 15.4 stack example works on CC1310 Launchpad.
As when I tried with this changes I was getting memory error stating "program will not fit into available memory.run placement with alignment fails for section ".stack" size 0x500. Available memory ranges:
How to get rid of this error.

Hi Chen & TER,

While going through the frequency hoping document provided in "ti154stack-software-developers-guide" document I came across below paragraph.

"Wi-SUN FAN v1.0 does not specify sleep mode operation, but the TI 15.4-Stack implements a proprietary extension over the behavior defined in the Wi-SUN FAN and IEEE 802.15.4 MAC protocols (see Sleep Mode Operation) to enable sleepy devices in the frequency-hopping networks based on the TI 15.4-Stack. The channel-hopping function for a sleepy device must be set to Fixed, and the fixed channel can be set to any desired channel. The security keys can be set at start-up (if the security keys are already preconfigured for the network), or the security keys can be set after obtaining the same through a key exchange. The key exchange protocol must be handled above the MAC layer."

Does the above detail indicate that if the device is sleepy device it has to be operated using Fixed channel function and if we need the DH1CF based hoping we need to have the non sleepy device which will consume more power?

Thank you

Vikram

Hey Vikram,

What this means is that when the sleepy end device wakes up, the collector must hop to the sensor's "fixed channel" to talk to it. The sensor will hop to the collectors channel when talking to the collector. The rule of thumb is that a device will go to the channel of the the device it wants to send a message to. An example of a poll event:

sleepy end-device wakes up and switches to the collector's channel and sends a poll request. if the Ack has it's pending bit set, then the sensor device will go to it's "fixed channel" and open its receiver as it waits for a message. The collector will hop to the sensors channel and send the message it had queued then hop back to its channel. Since frequency hopping is like non-beacon mode the sensor devices must initiate communication, meaning they hop to the collectors channel.

I hope this helps!

Hi Team,

Thank you for your reply.

I read the "ti154stack-software-developers-guide" document and it has the section "Creating Custom Applications".

The stuff it mentions is there is that if we want our application to start the network and be central node than use the Collector example and if we want the application to join the network and be the node in the network we use the Sensor example.

However, I have a different scenario we don;t want the network concept in our application.

The application is designed in a way that two radios can communication with each other as a transceiver so that both radios are able to send and receive data as and when requested.

That concept is designed using the proprietary RF examples that were provided with the TI - RTOS set of examples.

But we want the Simple Link SDK library to be merged since we need the frequency hoping concept implemented along with the proprietary rf examples.

I am not able to find a way how we can do this. I tried merging the proprietary rf examples with the simple link example but getting all sorts of error with memory.

I have also read through the document for "migration guide" but even that creates errors related to rf initialization.

Is there any document that can give idea about the RF commands are utilized in this SimpleLink examples as they are in the Proprietary RF examples?

Thank you

Vikram

Hi Team,

I am attaching the image of the building error that I get while I try to migrate the proprietary rf example from TI RTOS to Simple SDK.

Also have attached the screen shot of the migration steps as mentioned in documents that I have implemented.

Kindly provide your feedback.

Thank you

Vikram Trivedi

Hey Vikram,

For FH to work, there needs to be a "central" leader node to take care of things like synchronization and configuration of new nodes joining the network. You can port your application to work with TI 15.4-Stack if you want to use FH. The other option is to use the propriety-rf examples and either not exceed the FCC channel occupation time or set transmit power to 0dBm. If your not under regulation of FCC, then check your local regulation authority for rules in your frequency band.