HCI command tx timeout

RE: HCI command tx timeout

Kenneth — Mon, 17 Feb 2025 09:24:43 GMT

Hi,

A colleague suggested you try to merge this pull request: https://github.com/nrfconnect/sdk-nrf/pull/19869

Can you try that? They suspect lost HCI Command Buffers, the PR will detect misconfigurations.

Kenneth

RE: HCI command tx timeout

Dawid_Lech — Fri, 14 Feb 2025 13:29:42 GMT

Migrated to 2.9.0, unfortunately same issue persists.

Here are logs after Nordic Controller becomes unresponsive:

Thread analyze:
 HCI uart TX         : STACK: unused 1048 usage 488 / 1536 (31 %); CPU: 0 %
                     : Total CPU cycles used: 544115
 thread_analyzer     : STACK: unused 528 usage 496 / 1024 (48 %); CPU: 0 %
                     : Total CPU cycles used: 91685
 sysworkq            : STACK: unused 320 usage 192 / 512 (37 %); CPU: 0 %
                     : Total CPU cycles used: 1
 MPSL Work           : STACK: unused 704 usage 320 / 1024 (31 %); CPU: 0 %
                     : Total CPU cycles used: 12555467
 logging             : STACK: unused 480 usage 544 / 1024 (53 %); CPU: 0 %
                     : Total CPU cycles used: 153741
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 99 %
                     : Total CPU cycles used: 2642233638
 main                : STACK: unused 1440 usage 608 / 2048 (29 %); CPU: 0 %
                     : Total CPU cycles used: 2804754
 ISR0                : STACK: unused 1120 usage 928 / 2048 (45 %)

RE: HCI command tx timeout

Kenneth — Thu, 13 Feb 2025 12:05:02 GMT

Hello,

Please try the latest nRF Connect SDK for comparison, it could be items that have been fixed:
https://docs.nordicsemi.com/bundle/ncs-2.9.0/page/zephyr/samples/bluetooth/hci_uart/README.html

Kenneth