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.

CC1125 SPI interface

Other Parts Discussed in Thread: CC1125, CC1121

Hi

  I am trying to connect CC1125 with SPI to PIC micro controller. As per the datasheet, when we pull CSn pin low

the SO pin have to come low right. But for me when i pull CSn low the SO still  at HIGH.

i raised the CSn to HIGH , then i get the SO pin to LOW .!!

you know i am not yet written anything in to SPI registers , since i am stuck in starting of that itself.

--

e2e.ti.com/support/wireless_connectivity/f/155/p/308126/1079071.aspx#1079071

from this post i get something to debug,

If the SO line never goes low, check:

- Does the xosc running?   pin 32 -- > Yes

- Do you have 1.25 V on Rbias  - Yes i measured   pin 14----> 1.22V

- Do you have 1.8 V on the DCoupl pins. - yes  pin 6  ---- > 1.82V

Where it went wrong? any tips for me to debug and move to next step

  • Could you send a plot of CSn/ SO/ xosc to show what you are doing?

  • My scope don't have capture ,

     even now i am doing is just pull low the CSn and  Test the SO pin by using I/O Pins.

    my code snippet

       CC1125_CSN=0;
      DelayMs(10);


        while(1)
        {

        if (CC1125_SO==1)
        {
            send_string("High\r");
        }
        else
            send_string("Low\r");
        }

  • Use the code we have in our code examples for CC112x for SPI communication and take a picture of the screen.

  • I am using the same code only. earlier the whole code is working with CC1121 chips.

    Now i am doing a narrow band radio using CC1125 but before that i am trying to test the CC1125 is responding or not.

    i will try to get capture that to send you , before that let me know  after Pull CSn to low , how much time duration the SO will be in low. 

  • The SPI interface on CC1121 and CC1125 is exactly the same, if you have a code that communicate with CC1121 this should work on CC1125. Do you use a TCXO or a xtal on CC1125?

  • We are using TCXO 32Mhz. Connected to 32 pin EXTOSC.

    The code is same but i different controller ,

    RF_STATUS resetcc1121x(void)    // the same old code 
    {
      
      chip_Enable();  //pulls low here
      if(Poll_SO_pin(LOW)==FALSE)
         return FALSE;
      Spi_write(CC112X_SRES);    //  spiwrite(CC112X_SRES);
      Poll_SO_pin(LOW);
    
      chip_Disable(); // set to high again
      DelayMs(10);
      return TRUE;
    }

    This returns FALSE for me , this is the reason i am debugging step by step.

  • I borrowed a scope and taken the trace, Have a look on this.

    , top trace is CSN and bottom is SO.

  • what are  you doing in the Poll_SO_pin(LOW function)?

    This should be a check to see if MISO is low and I do not know why it is returning FALSE, because your plot shows that it is LOW and everything is fine.

    When sending the SRES strobe, CHIP_RDYn will go high for a while before going lowagain. 

    You can either pull CSn high just after the reset and then remember to check MISO next time you are talking to the radio (pulling CSn low) or you can wait for CHIP_RDYn to low again before pulling CSn high. 

    Siri

  • One HW check. When using TCXO remember to ground XOSC_Q1. Otherwise there is a finite possibility that that chip will use the XOSC, which is not present, instead of the TCXO as clock source

  • Yes Sverre, We connected the XOSC_Q1 to GND. And the XOSC is also shows stable in my scope 32.0000 Mhz.

  • Sharing the answer with you,

    If the SO line never goes low in CC1125, check:

    1. - Does the xosc running?   pin 32 -- > Yes

    2. - Do you have 1.25 V on Rbias  - Yes i measured   pin 14----> 1.22V

    3. - Do you have 1.8 V on the DCoupl pins. - yes  pin 6  ---- > 1.82V

    4. Keep the CSn at HIGH

    5.  Also ensure the RESET pin of CC115 must be in HIGH  (Here is the issue came for me)

    6. Verify the SO is HIGH now.

    After all these above steps,

    Pull the CSn LOW  , in 18-25us you will get SO pin LOW

    TI Support could help me in the first reply itself; I don’t know why they are not giving real support to me.

    Thank you for the mind storming, which leads me to get the answer.

    A small suggestion: TI CC chips are highly useable TRx in the market, why don’t you write a Getting started quick easy steps or FAQ on Interface..etc which will help the start-ups easy to come out to maintain and increase your market share.

     

     

     

  • Sorry to hear that you don't find the support adequate. But if you don't keep the reset line high, you would not get the correct voltage/ function on 1 to 3 above.

  • I will do verify that and let you know shortly.

    I have TRxEB boards with me, i would like to setup the tools & software to program my app to test that in TRxEB

    i downloaded CCS 5 , i dont know which license to choose to use MSP430 & my EVKits. (I have Launchpad , TRxEB,ez430)

    Help me  which free license to choose

    Free Licenses

    We have a number of different free tools options available in CCS. 

    Evaluation License: When you download CCS from the web you can choose to generate a time limited evaluation license the first time you run the product.  This will allow you to use all of the features of CCS for 90 days so that you can evaluate TI devices and tools but at the end of that time period it prompt you to provide another license.

      This i don't want

     

    Code Size Limited (MSP430): There is a 16KB free code size limited license available for MSP430 users. With the code size limited license you can use all of the features of CCS, you can create production code but the object code size will be limited to 16KB.

    Bundle License (Free Limited License): CCS can be used for free with many of our community boards, LaunchPads, DSKs and EVMs (Evaluation Module) kits.  You can download CCS and then select to use the free license for use with development boards. This CCS will only work with the onboard emulation on the board, XDS100 debug probes and simulators as well as the XDS560v2 mezzanine card available in C6000 multi-core EVM bundles. You may use this version to create production code. This license will work with eZdsp kits. DO NOT USE THIS WITH MSP430 EZ430 KITS, instead use the code size limited license.

    can i run the TRxEB (MSP430 - 16KB code limit) and Launchpad with this ,except the ez430.

    Thank you

  • You should use the Code Size Limited license for MSP430.

  • Hi TER

       Just i checked the 1 to 3 points, when the RESET is LOW,

      Again i got the result , DCPL - 1.81

                                              BIAS - 1.34V

                                               Oscillator clocks   ,

    Please check and let me know.

  • Sorry, I didn't think through what happens under a reset. The digital regulator will be on (DCPL = 1.8 V) but the digital part will be in a reset state and the crystal oscillator buffer is not on hence the system does not have a clock.

    When doing support through a forum like this we have to do some assumptions when asking questions and one of them is that the reset line is high.