Hi,
I am following the "CYW920706WCDEVAL Kit Guide" to view the traces on the windows with Bluetooth application Hello Sensor
I had followed "4.4.2 View Traces Using a Terminal Emulation Program" with no problem.
However, When I tried to view the traces using the BTSpy (4.4.3 View Traces Using the BTSpy Windows Application), I could not see trace messages. The Client Control and BTSpy displayed these and no more:
16:45:43.762 Opened \\.\COM46 at speed: 3000000 flow on
16:45:45.753 Startup
16:45:45.753 Set discoverable:1, connectable:1
16:45:45.753 Set Pairable:1
The Bluetooth application is built and downloaded and works well.
Thanks
Solved! Go to Solution.
Hi JiYa_3557771
Please note, for CYBT 343026 , you have to select 115200 baud rate for HCI UART in Client control.
Then only you will get BTSpy traces correctly.
Regards,
Anjana
I did this on Hello Sensor app.
Do not comment the below in the makefile:
C_FLAGS += -DWICED_BT_TRACE_ENABLE
C_FLAGS += -DENABLE_HCI_TRACE
Comment out the following line
wiced_set_debug_uart(WICED_ROUTE_DEBUG_NONE);
Have the ClientControl app open your peripheral port.
Hi JiYa_3557771
Please note, for CYBT 343026 , you have to select 115200 baud rate for HCI UART in Client control.
Then only you will get BTSpy traces correctly.
Regards,
Anjana
Hi Stan / Jieqiu Yang ,
The reason is , HCI_UART_DEFAULT_BAUD is set to 115200 for most of Ez-BT modules and HCI_UART_MAX_BAUD to 1000000
You can always check this in platform.h file before opening HCI port in Clientcontrol.
Regards,
Anjana
It works now with HCI UART. Does the BTSpy work with the peripheral UART? I have tried and have no success.
Thank you all!
No, BtSpy will work only with HCI UART
Regards,
Anjana
I had similar problem, but with CYBT-413034. See my solution here, maybe will solve your problem too?
Regards