• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 54 subscribers
  • Views 829 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/LAUNCHXL-CC1310: Simple 6lowpan CC1310 Launchpad

Janusz Wituski
Prodigy 80 points
Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: TIDA-010003, TIDA-010032

Tool/software: Code Composer Studio

Hello,
i got the software for the creation of a 6lowpan network from the TI site. Once for the Collector TIDA-01547 and once for the End-NODE TIDA-010003. Links are at the bottom of the description. I want to change the software so that if a message is sent across multiple end-nodes, that  each End-Node  will  write their own address into the payload so that you can track the message's path through the network. Currently, only the number of hops is displayed via the UART interface. The software is so extensive that I do not know exactly where to start. I hope someone can help me here in the forum.
BR
Janusz
  • 0
    TI__Intellectual 2095 points
    Hi Janusz,

    The TI 6LoPWAN mesh networking uses RPL storing mode operation by default. Thus, each packet doesn't deliver the entire path information. There is a way to build the topology information via DAO information instead.

    If you take a look at our 6LoWPAN IOT gateway design (search "TIDA-010032" on TI.com), you can find the web server app to show the network topology. In the software example, please search "NM_report_dao". Since the DAO includes its parents, the gateway (or root) can build up the entire topology graphs. You can implement this in a similar way for the TIDA-01547.

    Regards,
    Wonsoo
  • 0 in reply to Wonsoo Kim
    Prodigy 80 points
    Hello Mr. Wonsoo,

    many thanks for your help! I have resolved the problem with the network topology. I still have a question about debugging if I want to use the PRINTF output on the console. As I understand from the code I only have to change the macro from DEBUG_NONE to DEBUG_FULL above. However, if I only change that, nothing will be displayed on the console. I have to add a system_flush () after each PRINTF command, only then does the console the PRINTF commands (see pictures in the appendix). Do I do something wrong or where is the mistake?
    Regards,
    Janusz
  • 0 in reply to Janusz Wituski
    TI__Intellectual 2095 points

    Hi Janusz, 

    The DEBUG_FULL macro was implemented/verified with TIDA-010032 (based on Linux) only. To debug the TIDA-10003 or TIDA-01547, I would recommend to run CCS debug mode by adding some variables to watch. You can check Section 3.1.2.2.3.1 in the TIDA-010003 design guide describing the specific debug variables and how to set-up the debugger. 

    Regards,

    Wonsoo