• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 79 subscribers
  • Views 608 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.

smartrf studio 7 - iar workbench - EM430F6137RF900

James Moore64724
Prodigy 120 points
Other Parts Discussed in Thread: SIMPLICITI

As a newby to TI I am in need of some direction.  There is so much information on the TI website and forums a person can get lost.  I have the FET430F6137RF900 wireless kit that comes with two EM430F6137RF900  boards.  With little trouble we have successfully used the peer to peer sample code in IAR workbench to load on the developement boards, they work great.  We recently found Smart Studio 7 from TI and like it alot.  It has some really useful features.  I would like to use Smart Studio 7 to help debug and develope my project.  Is it possible to use IAR  and Smart Studio 7 simutaniously?  The CC debugger actually sounds like what I am looking for but the .pdf states that the CC degugger doesn't support the CC430.  Can someone help?

  • 0
    TI__Genius 14940 points

    James,

    The FET430F6137RF900 wireless developmen t kit should have come with an MSP-FET430UIF programming pod (available here if not http://focus.ti.com/docs/toolsw/folders/print/msp-fet430uif.html) which is used to program the CC430 device.  The CCdebugger only works on the 8051 based CCxxxx parts and will not work on the CC430 (see the introduction section on page three of the CCDebuggers Users's Guide located here http://focus.ti.com/lit/ug/swru197c/swru197c.pdf).

    SmartRF Studio is for developing the signaling protocol of the radio (modulation, bandwidth, data rate, etc.)  It allows you to generate packet error rate tests in order to test the signalling you have defined.  While it is connected to the CC430 (via the MSP-FET430UIF), the USB end point is allocated to the SmartRF Studio application and therefore the IAR debugger is not able to access it.  Similarly when you are debugging code on the CC430, you cannot use the SmartRF Studio to manipulate the radio.

    If you want to get creative, you can use the SmartRF Studio on one radio and then write your own code to receive or transmit packets on the other radio and in effect utilize both programs together but you will need two MSP-FET430UIF modules to do this.  Also, it seems a bit redundant since the things you can do with the SmartRF Studio are limited and the code for both sides of the operation is already operating in SmartRF Studio.  Other than possibly some peculiar need to debug packet handling architectures unique to your implementation, this approach has limited usefulness.

    If you are really in need of watching what is happening with the radio links dynamically, I would suggest getting a third radio and use the SmartRF Protocol Packet Sniffer (available here http://focus.ti.com/docs/toolsw/folders/print/packet-sniffer.html).  This way, you can watch the data transfers in real time and also filter out unnecessary data transfers which are not applicable to what you are looking for.  This software matches several protocols available from TI including the SimpliciTI protocol used in the peer to peer example code.

    Regards,

    Jim Noxon

     

**Attention** This is a public forum