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.

CC2650: CC2654 HCI_RTS line does not go low.

Part Number: CC2650


Hi,

We are using our own development platform with MSP432p401r and CC2654C and the A3DP_SRC sample code from :

D:\ti\Connectivity\CC256X BT\CC256x MSP432 Bluetopia SDK\v4.2.1.1\Samples\A3DPDemo_SRC

We are using the HFX 48 Mhz crystal also. 

The problem we are having is that we can not get the HCI_RTS line to go low after SHTDWN pin is asserted.  We have verified SHTDWN pin goes high and ACLK is present (off by 100hz).

This is all I am doing to enable ACLK:

 GPIO_setAsPeripheralModuleFunctionOutputPin(HRDWCFG_ACLK_PORT_NUM, HRDWCFG_ACLK_PIN_NUM, GPIO_PRIMARY_MODULE_FUNCTION);

Do I also need to set the CS_initClockSignal() ?   I have seen this in other posts:

But we are not using LFX xtal.  And as mentioned before we see the 32.768Khz xtal going in to the Slow Clock ping on CC2654.

What can be causing our problem?

I have another question,  why is the CTS interrupt on P3.6 being intialized twice?  Once before asserting SHTDWN pin high and then again right after.

In theory the interrupt to trigger after SHTDWN pin goes high...

Here is the snippet...

   /* Configure the CTS pin as an input.  Default to using a pull-down  */
   /* resistor because the pin is typically low while the controller is */
   /* both active and in sleep mode.  Note that we enable the CTS port  */
   /* interrupt here, but do not enable the CTS pin interrupt.  We will */
   /* leave it up to the caller to enable the CTS pin interrupt after   */
   /* they have configued the interrupt edge select bit.                */
   GPIO_disableInterrupt(HRDWCFG_HCI_CTS_PORT_NUM, HRDWCFG_HCI_CTS_PIN_NUM);
   //ODR:  Dan says this is a no no.. make pull up
   //GPIO_setAsInputPinWithPullDownResistor(HRDWCFG_HCI_CTS_PORT_NUM, HRDWCFG_HCI_CTS_PIN_NUM);
   GPIO_setAsInputPinWithPullUpResistor(HRDWCFG_HCI_CTS_PORT_NUM, HRDWCFG_HCI_CTS_PIN_NUM);
   GPIO_clearInterruptFlag(HRDWCFG_HCI_CTS_PORT_NUM, HRDWCFG_HCI_CTS_PIN_NUM);
   Interrupt_enableInterrupt(HRDWCFG_HCI_CTS_INT_NUM);

   /* Pull the controller out reset by setting the nSHUTD line high.    */
   GPIO_setOutputHighOnPin(HRDWCFG_NSHUTD_PORT_NUM, HRDWCFG_NSHUTD_PIN_NUM);

then when we return from this function call....

      /* The controller should be disabled before this function was     */
      /* called and it needs to be enabled, enable it now.              */
      HAL_EnableController();

CTS is initialize again!


      /* CTS is high while the controller is in reset and for several   */
      /* milliseconds after its pulled out of reset.  We cannot send    */
      /* data at this time.  We will configure the CTS interrupt to be  */
      /* high to low active to detect when the pin goes low.            */
      GPIO_interruptEdgeSelect(HRDWCFG_HCI_CTS_PORT_NUM, HRDWCFG_HCI_CTS_PIN_NUM, GPIO_HIGH_TO_LOW_TRANSITION);

      /* Clear the interrupt flag in case that it was set when we       */
      /* enabled the high-to-low transition interrupt.                  */
      GPIO_clearInterruptFlag(HRDWCFG_HCI_CTS_PORT_NUM, HRDWCFG_HCI_CTS_PIN_NUM);

      /* We have finished configuring the CTS interrupt, enable the     */
      /* interrupt.                                                     */
      GPIO_enableInterrupt(HRDWCFG_HCI_CTS_PORT_NUM, HRDWCFG_HCI_CTS_PIN_NUM);

Thanks in advance,

Ozzy

  • I just want to reiterate that :

    "But we are not using LFX xtal.  And as mentioned before we see the 32.768Khz xtal going in to the Slow Clock ping on CC2654."

    states the that the 32.768Khz clock signal is coming from ACLK. not a xtal.  Sorry for the confusion.

    Also our Development Board was designed for LFX xtal and DCO, but since project code only supports HFX xtal we switched if for now just to get BT Chip up and running.

    Later, we will have to get the LFX/DCO code working.

    Thanks,

    Ozzy

  • Hi Ozzy,

    I think its best we start with a schematic/ layout review to better understand the clock connections. You can submit a request here: https://www.ti.com/tool/DUALMODE-BT-DESIGN-REVIEWS.

     

    We can then take a look and see if there is a HW connection issue.

     

    Thanks,

    Riz