BLE堆栈是否有可以检索的日志或以任何方式进行HI***？

BLE API具有检查HI（硬件接口）状态的功能。没有内置的日志记录功能，但您可以看到处理BLE回调参数/事件时发生的所有事件。然后，您可以将这些事件/结果镜像到UART输出或类似的日志记录。
CyByLoPraceSeVScript（）将处理调用调用CyByLead启动（回调）的回调函数所发生的所有事件；函数。
如果您有从回调处理程序记录的数据/事件，那么您应该看到更多关于该问题的信息。
有一点要注意的是，Android和其他“标准”操作系统的设备往往有怪癖/刚涉及某些硬件的连接行为（如蓝牙，USB，等）导致只属于特定的硬件特定的操作系统甚至是特定版本的问题。
我的猜测是，你缺少处理一些事件发送响应的Android应用程序，它是希望以正确连接。



     以下为原文
  The BLE APIs have functions to check the HI (Hardware Interface) states for behavior. There is not built-in logging functionality, but you can see all of the events that occur when handling the BLE Callback arguments/events. Then, you can just mirror those events/results to a UART output or something similar for logging.
CyBle_ProcessEvents() will handle all events that occured by calling the callback function passed to the CyBle_Start(callback); function.
If you have the data/events logged from the callback handler, then you should see more information on the issue(s).
 
One thing to note is that Android and other "standard" OS on devices tend to have quirks/rigid behavior involving certain hardware connections (such as bluetooth, u***, etc.) leading to issues that pertain only to specific hardware for specific OS and possibly even for specific versions.
 
My guess would be that you are missing handling some of the events to send responses to the android app that it is expecting in order to correctly connect.

非常感谢！这是我在阅读数据表时所期待的。



     以下为原文
  Thank you very much!  This is what I expected from reading the datasheet.

回调中的HCI事件具有最低级别的信息，但我没有深入挖掘它们，以了解它们是多么有用。但是，如果您正在寻找比回调中的标准BLE事件所提供的更详细的信息，那么HCI事件将是查找日志数据的下一个位置。
祝你好运，
亚·普拉特



     以下为原文
  The HCI events in the callback have the lowest-level information, but I have not dug into them deeply enough to know how useful they are. But, if you are looking for more detailed information than what the standard BLE events in the callback provide, then the HCI events would be the next place to look for logging data.
 
Best of luck,
Elijah Pratt