• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 52 subscribers
  • Views 1613 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.

CC2564MODN: HCI communication lost

Pierre Simon
Intellectual 305 points
Part Number: CC2564MODN

Hello,

We use a CC2564MODN on our new product. This product has to constantly scan in BT classic and BLE to detect when paired devices are powered on, in order to establish connections as soon as possible.

To acheive that we perform in loop an inquiry mode for 5 seconds followed by a LE scan for 5 seconds. Interval and window are set to 11.25ms.

In the long run, the CC2564MODN  does not seem to support this high rate scan. All our boards end up to lost permanently their HCI communication randomly in a time window of 8 to 36 hours.

When this happens, the host cannot communicate with the module as the module does not reply to HCI commands anymore. At the same moment, the module TX-debug printouts many errors:

5921416 2 03/28/18 02:32:49.202 +33:36:20.297 BT Logger 1 HCILL send command: HCILL_GOTO_SLEEP_IND_MSG
5921417 2 03/28/18 02:32:49.202 +33:36:20.297 BT Logger 1 HCILL state machine is: WAITING FOR SLEEP ACK
5921418 2 03/28/18 02:32:49.202 +33:36:20.297 BT Logger 1 HCILL received command: HCILL_GOTO_SLEEP_ACK_MSG
5921419 2 03/28/18 02:32:49.202 +33:36:20.297 BT Logger 1 HCILL state machine is: SLEEP
5921420 7 03/28/18 02:32:49.330 +33:36:20.425 BT Logger 1 SCAN got invalid packet, type 15, length 44, AC 4, bits 28
5921421 7 03/28/18 02:32:49.378 +33:36:20.473 BT Logger 1 SCAN got invalid packet, type 9, length 25, AC 4, bits 27
5921422 3 03/28/18 02:32:49.474 +33:36:20.569 BT Logger 1 lm_lc_start_inquiry_scan
5921423 2 03/28/18 02:32:49.474 +33:36:20.569 BT Logger 1 LC_PICONIZER - allocated network clock 1
5921424 5 03/28/18 02:32:49.474 +33:36:20.569 BT Logger 1 synch event REG received, module INQUIRY SCAN, msi 1
5921425 5 03/28/18 02:32:49.474 +33:36:20.569 BT Logger 1 synch cmd abort instance, module WB_SCAN_MODULE_ID, msi: 1
5921426 5 03/28/18 02:32:49.474 +33:36:20.569 BT Logger 1 synch cmd return event ABORT_FINISH_SUSPENDED,module WB_SCAN_MODULE_ID
5921427 5 03/28/18 02:32:49.474 +33:36:20.569 BT Logger 1 synch cmd start instance, module INQUIRY SCAN, msi: 1
5921428 2 03/28/18 02:32:49.474 +33:36:20.569 BT Logger 1 LC Inquiry Scan - Start, LAP=0x9e8b33, Window=9 frames
5921429 5 03/28/18 02:32:49.474 +33:36:20.569 BT Logger 1 synch cmd return event STARTED,module INQUIRY SCAN
5921430 5 03/28/18 02:32:49.490 +33:36:20.585 BT Logger 1 synch event FINISH received, module INQUIRY SCAN, msi 1
5921431 5 03/28/18 02:32:49.490 +33:36:20.585 BT Logger 1 synch cmd start instance, module WB_SCAN_MODULE_ID, msi: 1
5921432 5 03/28/18 02:32:49.490 +33:36:20.585 BT Logger 1 synch cmd return event STARTED,module WB_SCAN_MODULE_ID
5921433 7 03/28/18 02:32:49.586 +33:36:20.681 BT Logger 1 SCAN got invalid packet, type 9, length 50, AC 1, bits 28
5921434 3 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 lm_lc_start_page_scan
5921435 2 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 LC_PICONIZER - allocated network clock 1
5921436 5 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 synch event REG received, module PAGE SCAN, msi 1
5921437 5 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 synch cmd abort instance, module WB_SCAN_MODULE_ID, msi: 1
5921438 5 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 synch cmd return event ABORT_FINISH_SUSPENDED,module WB_SCAN_MODULE_ID
5921439 5 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 synch cmd start instance, module PAGE SCAN, msi: 1
5921440 2 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 Page Scan start, Window = 9 frames
5921441 5 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 synch cmd return event STARTED,module PAGE SCAN
5921442 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 BLE Test: Transmitted/Bad CRC 0x%x-%x packets
5921443 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 Trace #3784
5921444 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 Trace #6276 : 452 989 0 52939 64815556 3469410304 3095903451 2147487232 5207748 7 7 0 825375029 3552308 3097214167 2147487488 5207748 7 7 0 825375029 3683380 3097476307 2281705472 ( 0x1C4 0x3DD 0x00 0xCECB 0x3DD01C4 0xCECB0000 0xB887BCDB 0x80000E00 0x4F76C4 0x07 0x07 0x00 0x31323935 0x363434 0xB89BBCD7 0x80000F00 0x4F76C4 0x07 0x07 0x00 0x31323935 0x383434 0xB89FBCD3 0x88001000 )
5921445 1 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 ERROR: Data Abort !!!, Link Register: 0x48350
5921446 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 Wibree Test Message
5921447 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 Wibree Test Message
5921448 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 ASSERT: IPC_SEND_FAIL (%1)(%d)
5921449 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 scan_activity_scan_setup_initializations
5921450 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 SCAN got invalid packet, type 9, length 50, AC 1, bits 28
5921451 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 mini_synchronizer_register: ABORT!! current_time: btclk 52928, pt 511. End Time: btclk 52919, pt 1159
5921452 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 mini_synchronizer_register: ABORT!! current_time: btclk 52928, pt 528. End Time: btclk 52919, pt 1159
5921453 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 mini_synchronizer_register: ABORT!! current_time: btclk 52928, pt 545. End Time: btclk 52919, pt 1159
5921454 7 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 mini_synchronizer_register: ABORT!! current_time: btclk 52928, pt 561. End Time: btclk 52919, pt 1159
5921455 1 03/28/18 02:32:49.660 +33:36:20.755 BT Logger 1 ERROR: Data Abort !!!, Link Register: 0xe10f0004

Here is one of our lgr files: 2541.6833-debug-171-v10-nowa-TI-failure.zip

Here are the setup details:

- module CC2564MODN,

- host iMX 283, Linux kernel 4.8.6

- UART set to br 3000000

- BTS file is TIInit_6.7.16.zip  (manual merge from initscripts-TIInit_6.7.16_bt_spec_4.1.bts and initscripts-TIInit_6.7.16_ble_add-on.bts)

- Bluez 5.45

Here is the scenario:

1- boot linux 4.8.6 kernel

2- load BTS file and attach hci interface thanks to this linux command: hciattach -s 115200 /dev/ttyAPP0 texas 3000000

3- start bluetoothd (bluez 5.45) in dual mode (LE + BT)

4- bluetoothd is set in discovery mode (continiously alterning inquiry mode and LE scan every 5 seconds)

5- after few hours in discovery mode (randomly between 8h and 36h), the CC2564MODN stops returning HCI event status

- a LE scan disable command is sent to the CC2564MODN to stop the current LE scan,

- the event status is not returned from the CC2564MODN,

- the HCI logs from TI logger displays errors at this exact same moment instead of displaying the LE scan disable command from host,

- the CC2564MODN does not answer to any HCI commands anymore

6- a hardware chip reset is neccessary to retablish HCI communication

Thank you for your support,

  • 0
    TI__Mastermind 29311 points
    Pierre,
    Please share the CC256x firmware logs of this scenario.
    processors.wiki.ti.com/.../CC256x_Logger_User_Guide

    Best regards,
    Vihang
  • 0 in reply to Vihang Parmar
    Intellectual 305 points

    Hi Vihang,

    The log file is actually attached in my initial post, but here it is again: 3808.6833-debug-171-v10-nowa-TI-failure.zip

    Do you need a full log file including the initialization part ? It may be huge since it could take 36h to get into this error state.

    Thank you for the follow-up,

  • 0 in reply to Pierre Simon
    TI__Mastermind 29311 points

    Hi Pierre,

    Sorry I missed the logs earlier. I do see a firmware crash towards the end of the logs. We need some information from the device initialization to understand this crash. Could you please provide a capture from the initialization? If it takes a long time to reproduce the issue, you can use the Edit->Auto Save and Clear option in the logger to save the logs.
    processors.wiki.ti.com/.../CC256x_Logger_User_Guide

    Additionally, could you also share the TIInit_6.7.16.bts that you had merged mannually?

    Best regards,
    Vihang

  • 0 in reply to Vihang Parmar
    Intellectual 305 points

    Hi Vihang,

    Here is the BTS file manually merged used to initialize the CC2564MODN:

    1641.TIInit_6.7.16.zip

    I will post the full logs from init to crash, in a minute.

    Pierre

  • 0 in reply to Pierre Simon
    Intellectual 305 points

    This module CC2564MODN is not responding since 31 Mar 2018 at 2:38:40.824 AM.

    Please find the full log (board 6826) attached here:

    Full log part 1: 6826-CC2564MODN not responding 18-03-31_02-38-40_824-part1.zip

    Full log part 2: 6826-CC2564MODN not responding 18-03-31_02-38-40_824-part2.zip

    This log file ends-up like this:

    2945212 02:38:40.824   +1:22:33.364 22 BLE message(s) was(were) dropped (BLE buffer was full)

    2945213 02:38:40.824   +1:22:33.364 Trace #2512

    2945214 02:38:40.824   +1:22:33.364 Trace #3782

    2945215 02:38:40.824   +1:22:33.364 Assert - ACL manager illegal scenario

    2945216 02:38:40.824   +1:22:33.364 ERROR: Data Abort !!!, Link Register: 0x48350

    2945217 02:38:40.824   +1:22:33.364 13 BLE message(s) was(were) dropped (BLE buffer was full)

    2945218 02:38:40.824   +1:22:33.364 Trace #3749

    2945219 02:38:40.824   +1:22:33.364 Wibree Test Message

    2945220 02:38:40.824   +1:22:33.364 Wibree Test Message

    2945221 02:38:40.824   +1:22:33.364 Wibree Test Message

    2945222 02:38:40.824   +1:22:33.364 test_queue_lower_to_upper

    2945223 02:38:40.824   +1:22:33.364 SCAN got invalid packet, type 14, length 25, AC 4, bits 30

    2945224 02:38:40.824   +1:22:33.364 SCAN got invalid length 59, type 1, AC 1, bits 29

    2945225 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48987, pt 471. End Time: btclk 48978, pt 1120

    2945226 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48987, pt 488. End Time: btclk 48978, pt 1120

    2945227 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48987, pt 505. End Time: btclk 48978, pt 1120

    2945228 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48987, pt 521. End Time: btclk 48978, pt 1120

    2945229 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48987, pt 538. End Time: btclk 48978, pt 1120

    2945230 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48987, pt 555. End Time: btclk 48978, pt 1120

    2945231 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48987, pt 571. End Time: btclk 48978, pt 1120

    2945232 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48987, pt 588. End Time: btclk 48978, pt 1120

    2945233 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48987, pt 1073. End Time: btclk 48978, pt 1120

    2945234 02:38:40.824   +1:22:33.364 21 BLE message(s) was(were) dropped (BLE buffer was full)

    2945235 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48987, pt 1195. End Time: btclk 48978, pt 1120

    2945236 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 37. End Time: btclk 48978, pt 1120

    2945237 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 54. End Time: btclk 48978, pt 1120

    2945238 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 86. End Time: btclk 48978, pt 1120

    2945239 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 118. End Time: btclk 48978, pt 1120

    2945240 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 149. End Time: btclk 48978, pt 1120

    2945241 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 181. End Time: btclk 48978, pt 1120

    2945242 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 213. End Time: btclk 48978, pt 1120

    2945243 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 245. End Time: btclk 48978, pt 1120

    2945244 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 261. End Time: btclk 48978, pt 1120

    2945245 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 293. End Time: btclk 48978, pt 1120

    2945246 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 325. End Time: btclk 48978, pt 1120

    2945247 02:38:40.824   +1:22:33.364 13 BLE message(s) was(were) dropped (BLE buffer was full)

    2945248 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 432. End Time: btclk 48978, pt 1120

    2945249 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 464. End Time: btclk 48978, pt 1120

    2945250 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 496. End Time: btclk 48978, pt 1120

    2945251 02:38:40.824   +1:22:33.364 mini_synchronizer_register: ABORT!! current_time: btclk 48988, pt 528. End Time: btclk 48978, pt 1120

    --------

    2947133 02:38:40.939   +1:22:33.479 1 activity register while 189 running

    2947134 02:38:40.939   +1:22:33.479 1 activity register while 189 running

    2947135 02:38:40.939   +1:22:33.479 1 activity register while 189 running

    2947136 02:38:40.939   +1:22:33.479 1 activity register while 189 running

    2947137 02:38:40.939   +1:22:33.479 1 activity register while 189 running

    2947138 02:38:40.939   +1:22:33.479 1 activity register while 189 running

    2947139 02:38:40.939   +1:22:33.479 1 activity register while 189 running

    2947140 02:38:40.939   +1:22:33.479 11 message(s) was(were) dropped (UART Debug was full)

    2947141 02:38:40.939   +1:22:33.479 mini_synchronizer_register: ABORT!! current_time: btclk 49097, pt 268. End Time: btclk 48978, pt 1120

    2947142 02:38:40.939   +1:22:33.479 mini_synchronizer_register: ABORT!! current_time: btclk 49097, pt 284. End Time: btclk 48978, pt 1120

    2947143 02:38:40.939   +1:22:33.479 mini_synchronizer_register: ABORT!! current_time: btclk 49097, pt 301. End Time: btclk 48978, pt 1120

    2947144 02:38:40.939   +1:22:33.479 1 message(s) was(were) dropped (UART Debug was full)

    2947145 02:38:40.939   +1:22:33.479 mini_synchronizer_register: ABORT!! current_time: btclk 49097, pt 334. End Time: btclk 48978, pt 1120

    2947146 02:38:40.939   +1:22:33.479 12 message(s) was(were) dropped (UART Debug was full)

    2947147 02:38:40.939   +1:22:33.479 mini_synchronizer_register: ABORT!! current_time: btclk 49097, pt 551. End Time: btclk 48978, pt 1120

    2947148 02:38:40.939   +1:22:33.479 mini_synchronizer_register: ABORT!! current_time: btclk 49097, pt 568. End Time: btclk 48978, pt 1120

    2947149 02:38:40.939   +1:22:33.479 7 message(s) was(were) dropped (UART Debug was full)

    2947150 02:38:40.939   +1:22:33.479 1 BLE message(s) was(were) dropped (BLE buffer was full)

    2947151 02:38:40.939   +1:22:33.479 mini_synchronizer_register: ABORT!! current_time: btclk 49097, pt 701. End Time: btclk 48978, pt 1120

    2947152 02:38:40.939   +1:22:33.479 14 message(s) was(were) dropped (UART Debug was full)

    2947153 02:38:40.939   +1:22:33.479 ERROR: Data Abort !!!, Link Register: 0xe10f0004

    -------------------

    Thank you,

  • 0 in reply to Pierre Simon
    TI__Mastermind 29311 points
    Pierre,

    I wanted to update you on the current status of this issue: we have received the complete logs and we are currently reviewing them. I will be able to follow-up next week regarding further updates. I appreciate your patience.

    Best regards,
    Vihang
  • 0 in reply to Vihang Parmar
    Intellectual 305 points
    Hello,

    Is there anything we can do to help you understand this issue ?

    Best regards,
    Pierre