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.

SimpliciTI 1.2.1 Beta Version

Other Parts Discussed in Thread: SIMPLICITI, CC1120, CC110L, CC113L, CC115L, MSP430G2302, MSP430G2955, MSP430G2553, CC1101, CC1310

1781.SimpliciTI-IAR-1.2.1-Beta.zip

By decrypting the accompanying SimpliciTI-IAR-1.2.1-Beta.zip file using the enclosed password you agree with the stated SimpliciTI License Agreement found in the same directory as this file.

In addition, you accept the "Beta" release provides no guarantee of merchantability or compatibility with any future official releases of SimpliciTI by Texas Instruments.

Decryption Code: TISimpliciTI

NOTE: for CC1120 RF setting, please refer to the following important note:

http://processors.wiki.ti.com/index.php/SimpliciTI_FAQ#Compatibility_Between_Different_Transceivers

  • By looking at the SimpliciTIchangelog.pdf file, this appears to be an older version. 1.1.0.  Is that intended?

  • Hi,

    this is a beta release, the documentation is not yet updated. sorry for that

  • Hello.

    I agree with blb (Barry). I downloaded this code and compared it with the current Installer 1.2.0 code I have. There are some critical fixes I asked Jim Noxon to include in the 1.2.0 release which he did. These fixes are not in the code I downloaded from this link. This look like 1.1.1 code to me. It is messed up.

    BTW The version bytes in the nwk_globals.c of the 1.2.0 release are incorrect.

    lfriedman

  • Hi guys,

    thanks for the input. Basically i was only told to upload this beta version to E2E, and i will check this issue with the original file owner. 

    One thing for sure is that this beta version contains project files for the new TrxEB board which is (AFAIK) not available in the previous v1.2.0. This also includes then the support of CC1120.

    I will get back to you as soon as i got some update from the file owner.

  • Heheh, still waiting for the CCS version of SimpliciTI 1.2.0 :(

  • Hi, Leo

    I am wondering when the SimpliciTI official version supporting CC1120 will be released. Do you have a schedule?

    Thank you!

  • Dear Leo,

    I have been testing the Simpliciti 1.2.1 that you have shared in a TRXEB evaluation board (rev 1.5) with the CC110L evalution boards of the CC110LDK_EM_868_915 rev1.0.0 or even with the CC1101EM 3.0 and it doesn't work.

    I have tested the simple peer to peer example, the AP as datahub and also the Polling with Ap. I have changed the smartf settings to a new ones and I can get it to pass though the SMPL_init function. What is problem?

    It should a basic test. 

    Maybe I'm missing something, but I've searched everything inside TI (E2E also) website and also global network (search engines) and nothing.

    What I must do?

    I have a solution based on the CC113L and CC115L with my own protocol working perfectly well, but Simpliciti I can't get it to work.

    I need a clean working example of the Simpliciti working if I can't put it working in the next days I will have to go to the Miwi protocol from Microchip.

    Can you help me?

    Regards

  • Hi all,

    Did anyone have the same problem as I?

    Or is really a problem of my IAR compiler eventually?

    Regards

  • Ralph,

    i uploaded a newer version of v1.2.1 Beta which i got from the product group team in my first thread above, it looks cleaner, and i tested some basic porting and it works without problem.

    Could you see whether it works for you?

    Thanks.

  • Hi Leo,

    Thanks for your response. The newer version is uploaded in the same location as the previous?

    I have again downloaded it (1781.SimpliciTI-IAR-1.2.1-Beta.zip) but it seems that is the same code.

    I will double check and try it again.

    As soon as I have further information I will send my feedbacks.

    Regards

  • Hi Leo,

    I've downloaded the 1781.SimpliciTI-IAR-1.2.1-Beta file.

    I've compiled, downloaded and tested the Simple pear to pear example. One of the TrxEB+ CC1101EM is the LinkTo and the other TrxEB+CC1101EM is the LinkListen device.

    Debugging the LinkListen program it passes the BSP_Init function but when he enters in the SMPL_Init(sRxCallback) function it doesn't go out. The program is always in the nwk_pllBackgrounder function blinking the leds.

    I don't understand the reason for this behaviour.

    I will check with the other examples if there is something different.

    Do you have any suggestion?

    Regards,

    Ralph

  • Hi Ralph,

    i see the problem now. This is because per default, the FREQUENCY_HOPPING feature is enabled in the project setting. Therefore the stack will try to first synchronize the time in SMPL_Init(). If you don't need the frequency hopping feature in your application, just changed the definition in smpl_nwk_config.dat from:

    /* Remove 'x' corruption to enable frequency hopping. */
    -DFREQUENCY_HOPPING

    to:

    /* Remove 'x' corruption to enable frequency hopping. */
    -DxFREQUENCY_HOPPING

  • Dear Leo,

    Your answer is working now.

    I have another doubt, if I want to use the frequency hopping with the SimpliciTI in both devices  how I must do? Or I can't use?

    Regards,

    Ralph

  • Ralph,

    The frequency hopping does actually work (I have tested it myself before). Basically in frequency hopping system, you need to synchronize the time between the nodes, so that they can jump from one frequency to the other at the same time. 

    in SimpliciTI this is also implemented that one node acts as the clock reference for another node. In order to make this work, you need to define a node (usually the Access Point since it is usually implemented as always on node) with NWK_PLL_REFERENCE_CLOCK during compilation.

  • Dear Leo,

    Now I have more interesting question.

    How can I use the a small value line microcontroller with the Simpliciti? I just need the protocoll of communication with the essentiality of Simpliciti.

    Basically I need to put the Simpliciti in small and cheaps microcontrollers. If not, I must do my own network with my own protocoll. Please keep in mind that normally the value line micros have very short RAM space.

    Can you give me some ideas of do that?

    Regards,

    Ralph

  • Ralph,

    if you want to use the value line as an end device, i believe this should be feasible. But for getting the AP run on MSP430 value line, i don't think this make sense.

    I wrote a porting guide a while back ago, and the process should be pretty straight forward:

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

  • Dear Leo,

    My intention is to use an MSP430G2302 or 2402 as an END Device with the Simpliciti. The Data Hub micro will be MSP430G2955 or an similar micro.

    The End Devices will batery supplied, so I need a small and low power, low cost microcontroller.

    My idea of the system is to use one Data Hub (master) and several slaves, most of them will be waken from the sleep (low power) by the master, but there will some of them that will a sort of keyfob device. These ones would eventually trigger (begining to work) the Master. After that will the Master that will wake the End Devices and control all the information of them.

    Can I do this? With the micros that I choosen?

    Regards,


  • Dear Leo and all readers and supporters of TI forum,

    I know now (after several tests and workarounds) that at least I need a micro with 8K of flash and 1K of RAM,

    So my idea of using a low cost microcontroller (value line) it is not feasible. The only family that could eventually be use is the new family of the MSP430G2955.

    Even though thanks to all for the support.

    Regards

  • Ralph,

    if you want to use the small MSP430G2xx value line devices as End Device, this is possible. I have a preliminary version of SimpliciTI port on MSP430G2553 (16KB Flash, 512 bytes SRAM), and if i compile the Simple-Peer-To-Peer code as is, i get:

    7 506 bytes of CODE memory
    428 bytes of DATA memory (+ 46 absolute )
    136 bytes of CONST memory

    Please notice that the Simple-Peer-To-Peer configuration requires 2 connections, 2 in frames and 2 out frames. Usually for small End Devices, you can just configure the parameters as 1. So basically it should be feasible to run SimpliciTI on G2553. 

  • Leo,

    Is there support for the CC1120 in the v1.2.1 Beta ?

    Regards,

    Lars

  • Hi Lars,

    yes there is a support of CC1120 in V1.2.1 beta. However i just notice there is something very important note for this when trying to work with the SimpliciTI and CC1120 regarding the carrier frequency setting.

    Since the CC1120 doesn't support channel selection as the older transceiver like CC1101, basically i just found out that if you generate the RF setting for CC1120 using the SmartRF Studio, the FREQ2, FREQ1, FREQ0 for the carrier frequency setting are actually "ignored" by the stack. The real setting which is used by the stack is somehow hard-coded in the stack as the value of mrfiLogicalChanTable[][] array in mrfi_radio.c. So if you want to set the carrier frequency, you need to copy the values generated by the SmartRF Studio into this array. 

  • Hi Leo,

    That is good to hear. Thanks for your support :-)

    Regards,

    Lars

  • Dear Leo,

    Sorry for my late response but I've been some days out in holidays to stop the motor.

    Regarding your response I have choosen the 2955 micro instead of the 2553. The reason is that as the basic code is near the top of the capacity of the micro and as intent to have more comunications and/or I/Os interaction I eventually will need more space (in RAM). Also, as the difference in price is not too much, I rather prefer to have more space.

    At this moment I'm trying to comunicate between the 2955 and the CC1101 with Simpliciti rules, I must see all the information I can get, because I need put it working within 2/3 days.

    Regards

  • Ralph,

    unfortunatelly i don't think we have any plan to make a porting on MSP430G2995, since basically we don't have any good platform (i.e. development kit) to show this. I agree that this would be interesting.

    Anyway, i would suggest you to still refer to the porting guide as this should be able to help you:

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

  • Hello, 

    I'm working with TRXEB (rev 1.7) board, with cc1120 transceiver.
    Downloaded the 1781.SimpliciTI-IAR-1.2.1-Beta file.

    Opened the IAR & programmed the project Simple_peer_to_peer. 
    I can see the LinkListen arriving to the linkFrom func' but never did he hears the LinkTo.. (so no link is established).
    The linkTo never succeed in creating link, SMPL_Link func always fails. 

    This isn't a hardware issue, I've tested it with SMARTRF and all works OK (in both 900 & 800 MHz).

    when running the Simple_peer_to_peer I've tried both default version & the smartRF configuration, both failed.

    What am I'm missing?

  • Leo, when I look at smartrf_cc1120.h in the beta version downloadable from the first post in this thread it looks like the deviation is set to 100 kHz? Shouldn't MODCFG_DEV_E=0x0E instead?

  • Is there ever going to be a Simpliciti 1.2.0 version for CCS released?

  • I also wonder if Simpliciti is still active...

  • SimpliciTI is still active. We have now moved the ownership of development and support internally to be better able to do further development. 

  • That's good news, I'm anxious for a 1.2.0 or better for CCS.

  • Hello
    I rarely use IAR so I was wondering if you could quickly help
    When I try and build any of the projects for the EXP461x or EXP543x I get :-

    Error[e183]: Static overlay map generation (-xo) is not supported for the MSP430 processor.

    Any ideas how I get rid of this, I am using EW for MSP430 5.60.1

    Regards

    Bob Bacon

     

  • Bob, you need to disable the "static overlay map" in the linker option as follows:

  • Thanks Leo, that solved  it

  • Hi,

    Maybe I'm blind but I'm not seeing the password to unzip this file. How can I get it?

    Thanks

    Eric

  • Decryption Code: TISimpliciTI

  • Dear Leo,

           Could you tell us how many end devices are supported by SimpliciTi if the network has a AP?

         255 or 31(PORT 0x20-0x3F)?  According to NUM_CONNECTIONS?

      Best regards

    watson

  • Dear TER,

           Could you tell us how many end devices are supported by SimpliciTi if the network has a AP?

         255 or 31(PORT 0x20-0x3F)?  According to NUM_CONNECTIONS?

      Best regards

    watson

  • Dear Leo,

    Frequency Agility and Frequency Hopping all make the devices move to different channel, but what's difference between them?

    If Sleep devices can not use FHSS, How to solve in battery field that need MCU enters sleep?   

      

    Best regards

    watson

  • Dear Leo,

            We don't care about connection nums, but how many end-devices(different radio address ) does AP can keep connecting with at the same time? 

         We use CC1110F32(32K flash,4k Ram) on SimpliciTi, could you let us knonw the exact numbers end devices but

    not connection. 

            Best regards!

      Waston

  • Hi

     http://www.ti.com/lit/sg/slya020a/slya020a.pdf

      In this selection guide i came across the Memory need for the mesh networking is > 64Kb. 

    I am not clear about the Speed of the controller required for this. Could you let me know 

    what speed of controller i have to select  (40Mhz, 100 Mhz, etc)  or how to choose the

    operating frequency of controllers for this stacks.

    Thank you

  • hi TER,

         Our system is based on the AP and a number of EDs, we have use nv_obj_write_nwk_cfg () and save the connection information 'sPersistInfo' to the flash of cc1110. It is workable for "simple peer to peer" in this way . But for 'AP as Data Hub', the system will be unable to work. The BUG described as follows: 
          Even if the AP and EDs are stored 'sPersistInfo', at the next power cycle, ED can not receive any message from the AP without SMPL_Init () successful . 
           We hope that once our ED and AP have once successfully JOIN and Link ,we don’t need SMPL_Init () successful and re-Join and link at the next power cycle. 
            In this case, in addition to storage 'sPersistInfo', what other information do we need to store?

    Regards

  • Will CC1310 support by SimpliciTI ?

    Regards
    Sam
  • Hi Sam,

    We are currently looking over our Internet of Things software strategy, and as it stands now SimpliciTI will not be officially supported at CC1310 RTM.

    That being said, SimpliciTI is far from abandoned. We have a new TI Design coming out any day now called Connected Home which uses SimpliciTI on CC1120 and CC430 to connected several nodes for Smart Home, Smoke Alarm and Security applications.

    Best regards,
    Niklas
  • Hi
    This question was asked a couple of years ago, but I havent seen any news; is there a SimpliciTI 1.2.1 version (that supports CC1120) for CCS?

    Thanks.
    ~Nathaly
  • We have not planned new versions of SimplitiTI. That said, we have not received any bug reports on the beta online and if you need SimpliciTI you should start from this version.