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

RTOS/LAUNCHXL-CC2640R2: BLE SPP Crash After Unsuccessful Notification

user5186587
Prodigy 20 points
Part Number: LAUNCHXL-CC2640R2
Other Parts Discussed in Thread: BLE-STACK

Tool/software: TI-RTOS

Hi there!

I'm trying to implement UART over BLE and started with github examples provided by TI and SimpleLink CC2640R2 SDK 1.40.0.45.

As my application requires, I changed the BAUD rate to 921600. After configuring the connection parameters (min, max conn = 15ms) i try to send a 177 byte msg every 20 msg.

It all runs smotly and the stack/hw is able to provide this throughput, but when a notification fails the HW simply becomes inreponsive, going to the AssertHandler function and to a spinlock.

As the application clearly is able to withstand the bandwidht required, shouldnt the un-notified messages be dequeued?

Already checked heap manager and it's set for auto.

How could i prevent this behavior when notifications fail? (I would like to simply move on to the next message)

.

  • 0
    TI__Genius 12815 points
    Hi user5186587,

    I'm going to need a little more information to help here:
    1. Other than the baud rate and connection parameters, did you make any modifications to the project?
    2. What do you mean by the notification fails? Does it fail to be sent or does it fail to be received? A sniffer capture or a logic trace of the RF data outputs (configuration discussed here: processors.wiki.ti.com/.../CC26xx_Range_Extender_Control) can help determine which side is failing if you are unsure.
    2. Are you seeing this error with the server application or the client application?
    3. Are you running on a LaunchPad or a custom board?
    4. Have you checked for any memory failures by enabling HEAPMGR_METRICS (See Debugging Common Heap Issues chapter of the TI BLE-Stack User Guide)?
  • 0 in reply to RachelP
    Prodigy 20 points
    Running on a LaunchPad!
    Thanks, after checking correctly the code and re-writing from the example the setup is running smothely!