• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 207 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.

CC2564MODA: device is discoverable but remote connection fails

Alain Werck
Prodigy 220 points
Part Number: CC2564MODA

Hello everyone,

 

We have been working with CC2564MODA for some years now, using an HFP + WBS Bluetooth profile. The product we developed is functional and meet the client expectations. Thus, we decided to re-use this module on a new product which also requires a Bluetooth HFP profile.

The 2 products mentioned above use a STM32L4 microcontroller: the old product uses the STM32L433 and the new one uses the STM32L496. The stack previously developed is expected to be compatible with the new product (excluding minor stuff like pin assignment).

Our issue is :

the STM32L496 correctly communicates with CC2564MODA. Startup, connectable, pairable, discoverable, HF server opening, … processes are working fine. We can see the Bluetooth device with a phone, a laptop, …

But it is impossible to connect the device. On the microcontroller side, there is no event to indicate a connection attempt (even probing the UART bus line, it stays idle). We logged two connection process: the succesful one on the old device and the failed one on the new device.         

Could you please help me on this subject?

 

Thanks in advance,

Alain.

connection_log.zip

  • 0
    TI__Mastermind 40965 points

    Hi Alain,

    Looking at your logs, it seems like in your new device a connection timeout occurs. This timeout is due to the host (your new device) not responding to the connection request in time. Is your host application for both the new device and the old device similar? I would take a look at your connection response code, and ensure that there isn't anything blocking the new device from accepting incoming connection requests in your application code.

    Regards,
    Michael

  • 0 in reply to Michael Reymond
    Prodigy 220 points

    Hi Michael,

    Thank you for your reply.

    The problem was indeed due to the code being freeze and thus stop calling the BTPS_ProcessScheduler function....
    Now it is solved !

    Regards,

    Alain.