• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 165 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC110L: FSCAL = 0X00

KOLDO CEBALLOS
Prodigy 60 points
Part Number: CC110L

Hello 

I am trying to configure a CC110L transceiver. I configure all the registers and after I read them in order to check the values are correct, and they are.

Then I send the command strobe STX with FS_AUTOCAL=0X01 configured. 

The value of MARCSTATE goes to 0x13 which is ok for STX state but the FSCAL1 value is 0x00. It has changed from 0x3F to 0x00 but I suspect this is not a good value, and the transceiver does not send anything.

Any idea which could be the problem? I check also the MARCSTATE value since I send the STX command and see that the values are 0x08 (CALIBRATE) , 0X09 (BW_BOOST) and 0x13 (TX ON). I don' see 0X0A sate whcih is supposed to be FS_LOCK, but not sure if I should see it.

Thanks for your help in advance

  • 0
    TI__Guru**** 317180 points

    - Do you do this on custom hardware? If so, have you tested on a CC1101EM that you know work? 

    - Have you tried to connect your board to SmartRF Studio via a CCDebugger? When debugging it's an advantage to do tests with either known hardware or known software so you are able to known if it's a software of hardware issue

    - Have you verified that you are not transmitting anything, even on an unwanted frequency? 

  • 0 in reply to TER
    Prodigy 60 points

    Hello,

    Yes I am using a custom board. I have been working with the CC110l since 2014. We have used it for desiging different remotes but never had this issue.

    I am wondering if this FSCAL1=0x00 value is normal or not. I know that when different from 0x3F it is supposed that PLL is locked, but can 0x00 ve a good value? 

    Yes. I checked in the analyzer and there is not any transmission at any frequency.

    Thank you

  • 0 in reply to KOLDO CEBALLOS
    TI__Guru**** 317180 points

    As I read the description of the FSCAL1 register 0x00 could be a valid value but I don't see it as very likely. 

    - Have you tried to connect your board to SmartRF Studio via a CCDebugger? When debugging it's an advantage to do tests with either known hardware or known software so you are able to known if it's a software of hardware issue

    - Is it a delta between the board you are using now and the boards you have worked with in the past? Or more general, what is different from last time you got an output signal to now? 

  • 0 in reply to TER
    Prodigy 60 points

    Hello,

    I don't have the CCDebuger and I am debugging the firmware in the MCU with Keil and checking also the SPI signals with the logic analyzer. SPI signals are ok and register values are the ones they supposed to be despite the FSCAL1 which I think is not ok.

    Hardware is the same as used before with all the radio part remaoining the same, but I am afraid that in component mounting process somethins was wrong because I don't really feel it is a software issue. It has all the same firmware instructions like in other devices where it works fine.

    That is why my first question was if FSCAL1 was a possible goog value or not, and when this 0x00 FSCAL value could be got because normally I have a 0x1A or similar value when PLL is locked. 

    Regards

  • 0 in reply to KOLDO CEBALLOS
    TI__Guru**** 317180 points

    It sounds like you are able to operate most of the chip as normal. Could you route CLK_XOSC/1 to a pin (Table 5.18) and check if the xtal frequency looks correct? 

  • 0 in reply to TER
    Prodigy 60 points

    Hello,

    I have checked the XOSC_CLK/1 in GD0 pin by configuring the IOCFG0 to 0x30. I checked I received a signal of 26MHz.

     

  • 0 in reply to KOLDO CEBALLOS
    TI__Guru**** 317180 points

    Ok, that's good.

    You wrote that you don't have a CCDebugger. Do you have a TXEB? As I wrote it would be interesting to run this with known good software to see if it's something related to this version of the hardware or this version of software.

    - Do you see this issue on multiple boards or just one? 

    - Have you tested your current hardware with software you know works or the other way around?