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.

MSP430F5438A controling CC1120

Other Parts Discussed in Thread: MSP430F5438A, CC1120, CC1101, CC1020

We received another MSP430F5438A question from our customer:

I have another issue in hand. I am using software written for F5438A to control CC1120. I have ported part of this software into our project which was created for F5522 processor. I am also trying to control CC1120.

According to CC112x user guide – page 7 – when CSn is pulled low, MCU must wait until CC112x SO pin goes low before starting to transfer… After pulling CSn low, I do not see SO pin going low even after a long wait.

Is there anything else needed to be set for this to work? Regards, MM

Your thoughts?

Thank you. -DN

 

  • One thought is to double check the CPOL and CPHA settings of the SPI configuration (in the USCI).  The CC112x might refuse to respond if SCLK is not in the expected idle state (high or low).

    Jeff

  • Jeff, 

    We are working on a various demos and one of them is a little demo for the MSP430F5438A Experimeters board and the CC1120 & CC1101

    Regards,
    /TA

  • Can you please post the preliminary datasheet for the CC1120?  Or if you cannot do that, then can you please contact me off-list so I can obtain that.  It's clear that some TI customers have access to it, as evidenced by this thread.  And although I know the official TI stance is "wait until June," the fact is that my company has started a new design based on the CC1020, and we need to change to the CC1120 in light of the fact the CC1120 will eventually replace the CC1020.

    Thank you.

  • James,

    The CC1120 is in limited sampling, please contact me directly (you should be able to send a private email thru the forum) or contact your local sales office/FAE. What is your key care-about when comparing the CC1020 to a the new CC1120.

    /TA

  • My key care is this.  My company has used the CC1020 in various RF designs since 2004.  We started a new RF design only a couple weeks ago, based on the CC1020.  But due to problems with frequency shifting in our previous designs, we have been more closely examining every datasheet and application note we can find on the CC1020, in hopes of resolving past problems.  More specifically, AN027 is our key concern.  I have posted about that application note here, in fact:

    http://e2e.ti.com/support/rf__digital_radio/etc_rf/f/228/t/100031.aspx

    Having received no replies whatsoever in this forum concerning AN027, I decided to write TI directly.  TI redirected me to the Japanese division, as our corporate headquarters are based in Japan.  The Japanese TI rep told us they do no recommend starting any new RF designs on the old CC1020 chip, suggesting instead that we wait for the CC1120, as it will ship in quantity in Fall 2011.  However, our design has already begun.  I don't see changing to the new CC1120 chip to be a problem.  Our biggest problem is being forced "to wait," hence my desire to get technical information on the CC1120 (even "preliminary" data) as soon as possible.  Once again, if TI had not told us to avoid new development around the CC1020, then we would not be in such a rush to get the CC1120 data.  But when I wrote our Japanese TI rep (our "local sales office") back to request a preliminary datasheet, I was told to wait because they said they had nothing they could send me at this time!  But that makes no sense.  And honestly, English info is all we need -- we don't need another language version of your technical documentation.  That is why I am making an appeal here, in this thread, to get some straight answers and real data without further delay.

    I would like to add that I read a post from TI employee "Erling" in other forums, so I wrote to him with my inquiry, but he never wrote me back:

    http://e2e.ti.com/members/611885/default.aspx

    I will send you a private email as you suggest.

**Attention** This is a public forum