• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 258 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2652R: Not able to establish connection after SDK ported to v5.20

Ddnr
Expert 1760 points
Part Number: CC2652R

Hi geeks,

I'm working on CC2652R1 evaluation board.

I was using SDK v4.40 for developement and all the basic functionalities works fine.

Recently I have ported my project to SDK v5.20.

After that when I tested, the advertisement is working fine.

But when the Central(Smartphone - nrf app) tries establishing connection with the Evalboard (peripheral), it rejects the connection. In the logs I can see "GATT Error"

And I tried to debug, and observed when I break the running, it points to HAL_ASSERT_SPINLOCK (due to HCI_BLE_HARDWARE_ERROR_EVENT_CODE).

May I know what is the reason behind this issue?

Thanks in advance.

  • 0
    TI__Mastermind 37770 points

    Hello,

    It appears you are failing an assertion somewhere in your code. Can you provide more details about what your code does? And perhaps try to use GPIO's/print statements to find the location of the failed assertion? Or even better, put the device in debug mode to find it if possible.

    Best,
    Nate

  • 0 in reply to Nathan Block
    Expert 1760 points

    Hi Nathan,

    It is not about my application code inside.

    I have tested with the SDK version5.20 Simple_peripheral example code and the issue persisits there also. (Not able to connect).

    Thanks.

  • 0 in reply to Ddnr
    TI__Intellectual 1900 points

    Hi

    Sorry for a late reponse.

    what is the error code of HCI_BLE_HARDWARE_ERROR_EVENT_CODE? And you can repeat that error with only our Simple_peripheral example code right?

    if so, it seems you are transmitting is too fast, you may start with that.