element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
RoadTests & Reviews
  • Products
  • More
RoadTests & Reviews
Blog SimpleLink™︎ Sub-1 GHz Wireless Microcontroller - Debug a Sender to Receiver Conversation
  • Blog
  • RoadTest Forum
  • Documents
  • RoadTests
  • Reviews
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join RoadTests & Reviews to participate - click to join for free!
  • Share
  • More
  • Cancel
  • Author Author: Jan Cumps
  • Date Created: 19 Jul 2016 5:57 PM Date Created
  • Views 1408 views
  • Likes 5 likes
  • Comments 3 comments
Related
Recommended
  • ccs
  • debug
  • sub-1ghz
  • cc1310
  • texas_instruments
  • simplelink
  • feature_tutorial

SimpleLink™︎ Sub-1 GHz Wireless Microcontroller - Debug a Sender to Receiver Conversation

Jan Cumps
Jan Cumps
19 Jul 2016

Debug Time !

 

You don't have permission to edit metadata of this video.
Edit media
x
image
Upload Preview
image

 

Let's check how you can debug a conversation between two Sub-1 GHz Radios.

We'll use the TI-RTOS simplest example, and place some strategic breakpoints.

One on the sender side, just before transmission, when the data packet is prepared.

One at receiver side, at the moment that the data is retrieved.

 

image

 

 

Set up the Sender and Receiver

 

In the links below you find instructions to get two separate CCS debug sessions running.

If you've never before used two LaunchPads on a single computer, check them out first.

The remainder of the article assumes that you've configured CCS to run multiple instances, with debug connector talking to the correct LaunchPad.

 

Load the TI-RTOS RF Packet TX exampe in the CCS Sender session, the RX example in the Receiver session.

image

 

Breakpoints

 

For the Sender, set the breakpoint at the lines where the transmit packet is constructed.

Source rfPacketTx.c, function txTaskFunction().

For the Reciver, it's source rfPacketRx.c, function callback().

 

Start the receiver debug session, and kick it off. The program will keep spinning until date is received.

Then start the sender debug session. It will stop at the position where the data is prepared.

 

When the sender session stops, set a watch expression for the packet variable.

Then step over the code to see the random content of the 30 data points getting prepared.

Keep stepping over the code until you reach the RF_EventMask result = RF_runCmd() line.

The receiver debug session is still running interrupted.

Then step over the sending functions. Keep an eye on the receiver CCS session, because it will stop executing.

Our code fell into the receiver callback breakpoint.

 

You can now step until the memcpy() line. Also create a watch expression for the packet variable in the receiver session.

Step over the memcpy() line. You 'll see that the receiver packet has the identical content as what was randomly generated at sender side.

 

image

 

Thats your proof that the conversation worked.

In the real world, the random package could be sensor values, or messages.

You could use the hardware support for encryption and decryption to scramble the packet before it's beamed.

 

I'm curious to see what you will be transmitting with these devices...

 

SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Check  Received Signal Strength
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Use SmartRF to Try Radio Configs
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Debug 2 LaunchPads at the Same Time
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Side Note: Recognise your PuTTY Sessions
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Side Note: Recognise your Code Composer Studio Sessions
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Debug a Sender to Receiver Conversation
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Side Note: Start a Fresh Project
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Create a Transmitter with SmartRF Studio Part 1
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Create a Transmitter with SmartRF Studio Part 2
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Sensor Controller Engine Part 1: Dry Run
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Sensor Controller Engine Part 2: RTOS Integration
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Sensor Controller Engine Part 3: Wake Up Options
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Side Note : Measure Power Use of Sensor Controller Engine
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - ToolKit for Range Testing

on TI E2E community: How to connect a CC1310 LaunchPad to the SIGFOX network

  • Sign in to reply

Top Comments

  • DAB
    DAB over 9 years ago +1
    Nice update. I am curious as to the additional time and bandwidth it will take to do the encryption and decription. Usually there is some additional bytes added to include the encryption and redundancy…
  • Jan Cumps
    Jan Cumps over 8 years ago in reply to DAB

    I'm giving the encryption test a try now, Don.

     

    image

     

    I needed a good reason to start from an empty RTOS skellet, so here we go..

     

    For the BLE simplelink controllers, I've read in the manuals that it's not good t use the hardware encryption module, because the BLE stack uses it.

    I haven't seen encryption options in the .radio stack of my Sub-1 GHz controllers here - so I see no reason why I shouldn't try them... (I haven't read the full manual yet though - User Manual + TRM are a few 1000 pages - gulp)

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Jan Cumps
    Jan Cumps over 9 years ago in reply to DAB

    I could do an example of that, DAB.

    There are some examples (posting links here for my own reference later on image )

     

    https://e2e.ti.com/support/wireless_connectivity/proprietary_sub_1_ghz_simpliciti/f/156/t/479357

    https://e2e.ti.com/support/wireless_connectivity/proprietary_sub_1_ghz_simpliciti/f/156/t/527223

    http://processors.wiki.ti.com/index.php/CC2640_AES_Encryption

     

    I don't need a transmission to test this. It should be possible to time the time needed to en/decrypt, and to measure the size of the message.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • DAB
    DAB over 9 years ago

    Nice update.

     

    I am curious as to the additional time and bandwidth it will take to do the encryption and decription.

     

    Usually there is some additional bytes added to include the encryption and redundancy code.

     

    Are you going to do an example to look at these issues?

     

    DAB

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube