STM32CubeWiSE open port failed

[AnthonyS]

Hello,

I would like to report an issue encountered with the "STM32CubeWiSE - Bluetooth LE Explorer" tool, version 1.1.0.

I am using a custom board equipped with an STM32WBA65, running firmware in "TransparentMode.
"To connect my board to the PC, I am using an FTDI USB-to-serial adapter.

The problem occurs when the tool opens the COM port: the first command, "HCI_READ_LOCAL_VERSION_INFORMATION," fails because 4 unexpected characters (0xFF, 0x01, 0x00, 0x00) are sent by the PC.
Even the retry attempt, which occurs one second later, fails because the HCI protocol is no longer synchronized.
Consequently, the tool fails to recognise the chip and is not usable.

This issue does not occur with the Nucleo board's USB-to-serial adapter.
STM32CubeMonitor-RF 2.19.0 works fine.

As a workaround, I modified the firmware to ignore the 3 next characters when its get an invalid packet indicator with value 0xFF.

BR
Anthony S

[priviteo]

Hello

On current STM32CubeWISE-Bluetooth LE Explorer v1.1.0 the default automatic device recognition framework is based on the usage of onboard Nucleo ST-Link utilities with the possibility to move to a manual recognition framework as described on UM3534 , Section 3.8:

“Go to settings → select "Board Series" and set Automatic (default) for automatic device recognition based on "on-board" NUCLEO Kit ST-Link FW utilities, or choose the specific device based on the effective connected device (to be used when no ST-Link Fw is available on the device board). “

So when using FTDI USB-to-serial adapter user should simply :

Go to Settings menu, select "Board Series" and select the specific devices series (STM32WBAx as example). Then user should select the COM port and make open.

BR

​​​​​​​OP