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.

CC2564MODN: 30 to 45 Seconds for RTS to go low

Other Parts Discussed in Thread: CC2564MODN, CC2564

It is taking around 30 to 45 seconds for our CC2564MODN to drive RTS low.  Maybe this means something specific to a CC2564 expert.  Any thoughts?

I would like to mention that our HCI_CTS is tied directly to ground.  We don't plan to use hardware flow control.

Our power cycle is the following.  I believe it meets the power up sequence explained in TI's wiki, however, I can't be sure because the Wiki doesn't list min and max setup/hold times for all relevant signals.

1) Board powers up, which supplies power to the 3.3V rail.  At this point the Tiva C and CC2564MODN have 3.3V. All three are held at 0V:  HCI_CTS, HCI_RX, nSHUTDOWN, CLK, 1.8V rail.  

2) 500 ms later, the 1.8V rail is enabled and CLK starts clocking at 32.768KHz.

3) 5 ms later, nSHUTDOWN is driven to 1.8V.  At this point, HCI_CTS is low (i.e. tied directly to ground) and HCI_RX is undefined.

Roughly 30 to 45 seconds after the above power up sequence the CC2564B drives the HCI_RTS pin low.  (However, the wiki lists this much shorter at 100 milliseconds).

Any thoughts we be greatly appreciated.  BTW, at this point there is no Bluetooth stack running.

  • Hi JR,

    First of all, hardware flow control is mandatory for H4 UART protocol unless you are planning on using Three-Wire UART sofware flow control.

    Regarding the issue you are facing, the sequence looks ok. I would recommend checking at the slow clock frequency. It might me off from the expected value.

    Miguel

  • Miguel:

    Thank you for the fast response.  Yes the 32K clock was the problem.  We were off around 300 ppm.  Once we got the error down to around 160 ppm, the CC2564 started working.  Good job.