1 of 1 people found this helpful
The MBT tool uses HCI commands directly, whereas WMBT uses WICED HCI commands.
MBT tool should work. Not sure why its failing at your side. Can you please hard reset the board once and try once again ?
Thank you for your prompt reply. Unfortunately, it didn't resolve even if HW reset.
Here is additional info. In the case of bluetool, the reset command works well.
47:36.831 com6 c> Reset
[03 0C 00]
opcode = 0xC03 (3075, "Reset")
47:36.843 com6 <c Reset
HCI Command Complete Event
[0E 04]: 01 03 0C 00
event = 0xE (14, "Command Complete")
Num_HCI_Command_Packets = 0x1 (1)
Command_Opcode = 0xC03 (3075, "Reset")
Status = 0x0 (0, "Success")
Thus, only mbt tool does not work fine under my environment. (wmbt and bluetool work fine.)
Just to be sure, I will check UART CTS level during the mbt tool.
I found out the root cause.
In the case of mbt tool, UART_CTS was H level during sending command from host under my environment.
Thus the chip did not send any data to the host. This means NO response from the chip.
I tried to set UART_CTS L level forcibly by pull-down. Then the mbt tool became to work well.
DOWNLOAD_BAUDRATE: 115200 (default)
APPLICATION_BAUDRATE: 115200 (default)
Sending HCI Command:
0000 < 03 0C 00 >
Received HCI Event:
0000 < 0E 04 01 03 0C 00 >
Do you know the way to change UART_CTS polarity configuration of mbt tool?
We use wmbt tool intead of mbt tool. So I close thei thread.
Hi Yoshinori San,
I was able to reproduce the issue with mbt tool.
Yes , please proceed with wmbt tool for now.