Getting a warning that - Device under test not responding COM port closed - when trying to connect the STM32CubeMonitor-RF to the WB55 Nucleo or Dongle.
Getting a warning that - Device under test not responding COM port closed - when trying to connect the STM32CubeMonitor-RF to the WB55 Nucleo or Dongle.
Using either the default program or programming the BLE_TransparentMode default hex file results in this error. I have both a windows 10 and macOS 10.14.4 machine that I get this result. The VCOM port doesn't seem to be the issue as I can program and see the units. Any help would be much appreciated!
This error usually means that tool has no answer from device. In this case the log will look like this :
The tool has tried to contact the target, but there was no answer after few seconds.
There could be various causes for this :
Not using the Transparent Mode. The tool rely on transparent mode software to communicate with the STM32WB. On Nucleo and USB Dongle kit, the default program is not transparent mode. Transparent Mode must be used.
opening the wrong com port : It is good to check in the device manager if the virtual com port is visible with the same number. (The tool shows all serial ports of the computer).
the transparent mode is not running properly. If the software is crashed on the target, the tool have no answer
the serial path is not correct : Nucleo should be connected by the ST-Link port and jumpers TX RX should be present.
For USB dongle the Transparent mode has been used instead of BLE_TransparentModeVCP
For user pcb, the uart used is not the same as nucleo, or not properly configured.
For USB dongle, the VCP driver is not installed (it is not the same as the ST-Link driver)
There is an overview of the connection in the user manual (UM2288, chapter 2) You may find some clues in this doc, and it should help to understand the connection path.
Best regards
A
Anonymous
October 25, 2019
Hello @stephane.legargeant ! I think this problem concerns to me too. But to use the transparent mode? I'm using stm32wb55 and I want to connect it with my phone.
@BGoathals @stephane.legargeant @Kolab Have you found any solution to the problem, e.g. how to set a transparent mode?
A
Anonymous
July 9, 2020
@MPiot.1 I really forgot how I overcame this issue(issues were a lot :) ) but I get an idea. On the STM32CubeWB folder look for the folder BLE_TransparentMode and look at the readme, it may help.
@Kolab Thank you for your reply. The point is I cannot find the mentioned folder, as well as I do not see the directory containing the examples, which could be also helpful.
@MPiot.1 I tested on my USB Dongle and it works properly. I did as I explained to you before. Open the device management and check if it's all okay with the ports. Check if the port that you are using is not opened in another program. Try to disconnect the port in device management and reconnect and check if all jumpers are in the correct places (you can see in the documentation how they should be put).
@Kolab Thank you, that worked. However there is no project (.ioc) file for that example and my goal is to enable the COM Port connection for my project.
A
Anonymous
July 16, 2020
.ioc is available only for the Nucleo board as I can see. You can use this board. Although you can try to create a new project in Cube for the Dongle and activate there the transparent mode and com port.
@Kolab Actually, I tried the Nucleo example. The binary is working just fine, I can connect through the COM Port. However, when I generate and compile the project, the compiled binary gives the same error as described.
A
Anonymous
July 16, 2020
As I understood the problem is when you compile your own project. If I am not wrong you are just generating and compiling, please correct me. Did you compare what is in the ST example with what is in your project?May be important configurations you left behind
Anybody got a solution to this problem? I've encountered the same issue and I tried following the steps recommended by @stephane.legargeant both in a PC with windows and another with linux to no avail.
