CC2564: HCI down and TI logger shows ERROR: Data Abort !!!, Link Register: 0x9257925a

Pierre Simon

Part Number: CC2564

Hi,

We are facing what it seems to be a firmware bug on the CC2564.

While the chip is performing a LE scan, the TI logger shows errors:

72033 1 03/26/18 10:50:06.420 +0:25:40.889 <No Port> ERROR: Data Abort !!!, Link Register: 0x9257925a
72034 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72035 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72036 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72037 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72038 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72039 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72040 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72041 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72042 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72043 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72044 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72045 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72046 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72047 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72048 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72049 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72050 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72051 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72052 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72053 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72054 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72055 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72056 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72057 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72058 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72059 1 03/26/18 10:50:06.421 +0:25:40.890 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72060 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72061 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72062 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72063 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72064 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72065 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72066 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72067 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72068 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72069 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72070 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72071 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72072 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72073 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72074 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72075 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72076 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72077 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72078 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72079 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72080 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72081 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0x47e10
72082 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72083 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72084 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72085 1 03/26/18 10:50:06.422 +0:25:40.891 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004
72086 1 03/26/18 10:50:06.426 +0:25:40.895 <No Port> ERROR: Data Abort !!!, Link Register: 0xe10f0004

Beyound this point, the chip does not answer to HCI commands. This is reproductible on many of our boards embedding the CC2564 and may occur after few days of continous normal operation.

Our boards use:

Linux 4.8.6

Bluez 5.45 - default configuration

BTS file: 480-0035-R1.0_3000000_baud.bts

Please find the attached log file.1107-debug171-v10-nowa-modulenot responding.zip

Any help on this matter would be highly appreciated,

Best regards,

over 6 years ago

0 Chen Loewy over 6 years ago

TI__Expert 5285 points

Hello Pierre,

Can you please add some more details to this issue.

Which CC2564x are you using?
Which firmware version (can you attach the .bts you are using - the one you have attached here doesn't seem to be an official version).

What is the exact scenario?

BR,
Chen Loewy

0 Pierre Simon over 6 years ago in reply to Chen Loewy

Intellectual 305 points

Hello Chen,

The chip is a CC2564. (not B, not C)

Here is the BTS file:480-0035-R1.0_3000000_baud.zip

The BTS file is renamed and placed here: /lib/firmware/ti-connectivity/TIInit_6.6.15.bts

The firmware is loaded thanks to this linux command: hciattach -s 115200 /dev/ttyAPP0 texas 3000000

The scenario is the following:

1- boot linux 4.8.6 kernel

2- load BTS file and attach hci interface

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 CC2564 stops returning HCI event status

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

- the event status is not returned from the CC2564,

- the HCI logs from TI logger displays errors at this exact same moment (see my first post) instead of displaying the LE scan disable command from host,

- the CC2564 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 Chen Loewy over 6 years ago in reply to Pierre Simon

TI__Expert 5285 points

Hi Pierre,

This is a very old chip.
And you are using an old version.

However to give you more information i will need you to attach FW logs so i can see where exactly did the FW crash
and what can be done about this.

BR,
Chen Loewy

0 Pierre Simon over 6 years ago in reply to Chen Loewy

Intellectual 305 points

Hi Chen,

Please find in attached file, a FW log from init to the crash: 1107-module not responding.zip

Thank you,

0 Chen Loewy over 6 years ago in reply to Pierre Simon

TI__Expert 5285 points

Hello Pierre,

From an initial look it seems that the issue might be connected to the HCILL.

can you please remove the HCILL - and test again?

In the .bts file please remove the following lines:

## Enable eHCILL
Send_HCI_VS_hcill_parameters 0xFD2B, 0x0010, 0x0050, 0x96
Wait_HCI_Command_Complete_VS_hcill_parameters_Event 5000, 0x00, 0xfd2b, 0x00

Send_HCI_VS_Sleep_Mode_Configurations 0xFD0C, 0x01, 0x01, 0x00, 0xff, 0xff, 0xff, 0xff, 0x0064
Wait_HCI_Command_Complete_VS_Sleep_Mode_Configurations_Event 5000, 0x00, 0xfd0c, 0x00

Please update on the test results.

BR,
Chen Loewy

0 Pierre Simon over 6 years ago in reply to Chen Loewy

Intellectual 305 points

Hi Chen,

I just started the test with HCILL removed. I'll keep you posted.

Thank you,

0 Pierre Simon over 6 years ago in reply to Pierre Simon

Intellectual 305 points

Hi Chen,

Unfortunatly disabling HCILL did not solve the issue.

Please find the full log from init to crash with HCILL disabled:1107-debug117-v10-nowa-nohcill Session 01.zip

Thank you for your help.

0 Chen Loewy over 6 years ago in reply to Pierre Simon

TI__Expert 5285 points

initscripts-TIInit_6.6.15.bts initscripts-TIInit_6.6.15_ble_add-on.btsHello Pierre,

I'm attaching here a version for you to try.

Please check with the attahced .bts file and specific BLE add on file.

BR,

Chen Loewy

0 Pierre Simon over 6 years ago in reply to Chen Loewy

Intellectual 305 points

Hi Chen,

The CC2564 chip loaded with your last BTS file 6.6.15 updated on 13-Mar-2018 17:58:16.08 and BLE add-on, stops responding to HCI commands after 8 hours of operation.

Logs from chip shows a warning when the communication is lost:

1191781 04/09/18 18:32:47.199 +2:04:45.188 *** WARNING *** No OSA buffer available, pool id: 10

Please find the full log file:

1107-debug117-v10-nowa-bts-chen-not-responding-2018-04-09_18-32.zip

Thank you for your help.

0 Pierre Simon over 6 years ago in reply to Pierre Simon

Intellectual 305 points

Hello Chen,

Do you need additional data to understand this issue ?

Best regards,
Pierre

0 Chen Loewy over 5 years ago in reply to Pierre Simon

TI__Expert 5285 points

Hello Pierre,

I will go over the zip file and get back to you with an analysis.
Due to holidays we are only back in office today.

BR,
Chen

0 Chen Loewy over 5 years ago in reply to Chen Loewy

TI__Expert 5285 points

Hello Pierre,

I went over the logs and unfortunately still can't find the core reason.

will you able to send me your Hardware and instructions and i will recreate the problem here and debug it.

Please let me know if that's a viable option.

BR,

Chen Loewy

0 Chen Loewy over 5 years ago in reply to Chen Loewy

TI__Expert 5285 points

Hello Pierre,

please let me know if sending your HW is an option.

BR,
Chen Loewy

0 Pierre Simon over 5 years ago in reply to Chen Loewy

Intellectual 305 points

Hello Chen,

Thanks for the follow-up, I will send the hardware with instructions. Could you provide the shipment specifics ?

Best regards,

0 Chen Loewy over 5 years ago in reply to Pierre Simon

TI__Expert 5285 points

Hello Pierre,

Instructions were sent over email.

BR,
Chen Loewy

Bluetooth®︎

Bluetooth forum

CC2564: HCI down and TI logger shows ERROR: Data Abort !!!, Link Register: 0x9257925a