CC2652P: Device no respond after scan enable

West Chu

Part Number: CC2652P

Hi all,

I have chip CC2652P on my custom board. I found the chip will stuck after I send "GapScan_setPhyParams" and "GapScan_enable", like below image show:

Sometimes I send "HCIExt_ResetSystemCmd" twice will make chip back to controllable, but the chip need to be powering off/on to back to controllable state in most case.

Are there any ways to avoid chip getting stuck after these settings?

over 1 year ago

0 Clément over 1 year ago

TI__Guru** 100470 points

Hi,

Thank you for reaching out.
This behavior makes me think about a limitation of the host_test example (probably at the UART level).
May I kindly ask you to review the following piece of documentation and tell me if it helps?
https://software-dl.ti.com/simplelink/esd/simplelink_cc13xx_cc26xx_sdk/7.10.00.98/exports/docs/ble5stack/ble_user_guide/html/ble-stack-common/npi-index.html?highlight=util_systemerrorevent#npi-limitations

Best regards,

0 West Chu over 1 year ago in reply to Clément

Prodigy 60 points

Hi Clément,

Thanks for your reply. I tried reducing maxNumRecords number from 40 to 0. Stucking issue still happend ,but happen less frequently.

According to the page you shared, reduce ratio of scan window/interval can work, but both scan window and interval value are customer required.

Are there have other settings can reduce the chance to serial port be stuck? Or how to modify the host_test example code to do that?

0 Clément over 1 year ago in reply to West Chu

TI__Guru** 100470 points

Hi West,

I would recommend to enable scan filtering. As it would reduce the number of "useless" reports transmitted to the host.

In addition, I would recommend to increase the UART baudrate. This change can be made in the file NPI/Transport/UART/npi_tl_uart.h by changing the value of NPI_UART_BR.

I hope this will help,

Best regards,

Bluetooth®︎

Bluetooth forum

CC2652P: Device no respond after scan enable