What firmware to flash so the STM32WB board can be used with CubeMonitor-RF

​Hello

You are right, the transparent mode firmware must be used for the main processor :

- BLE_TransparentMode for Nucleo board,

- BLE_TransparentModeVCP for the USB dongle.

Wireless stack for co processor is stm32wb5x_BLE_Stack_fw.bin (not the HCI one)

Point to check :

The uart should be visibile in the computer, if not the driver may be missing.

On Linux computer the modemmanager may take control of the uart. User need to wait some time before connecting (or disable modemmanager)

If you problem is not solved, ca you give more details ? (What OS is used, is it a dongle or nucleo, do you see the uart ? )

Best regards

Stephane

Thanks for the Help.

For the dongle:

• Flashing the co processor i am getting the following error

Updating firmware ...
Waiting for firmware upgrade end
 
RSS state is WIRELESS_STACK_UPGRADE_ONGOING
 
RSS status is RSS_NO_ERROR
 
RSS state is WIRELESS_STACK_UPGRADE_ONGOING
 
RSS status is RSS_IMAGE_NOT_AUTHENTIC
Error: Firmware not authentic!

• flashing the BLE_TransparentModeVCP with the CubeProgrammer fails, which is also true for the nucleo board, because it cannot write sector 0

Memory Programming ...
10:21:55 : Opening and parsing file: Production.hex
10:21:55 : File : Production.hex
10:21:55 : Size : 53537 Bytes
10:21:55 : Address : 0xFACEB00C
10:21:55 : Download in Progress:
10:22:00 : Error: failed to download Segment[0]
10:22:00 : Error: failed to download the File
10:22:00 : Time elapsed during download operation: 00:00:04.999

For the nucleo:

• i can flash the stm32wb5x_BLE_Stack_fw with no error
• i can also flash the BLE_TransparentMode firmware with the system workbench and start debugging with the onboard st-link. but seems to fail the APPE_Init() and then reboots
• if i am using the st-link serial usb connection the monitor RF application can not connect to the port or does not receive a respond from the port, depends if i restarted the device after programming
• the user usb port does not offer a device at all

I am working on a windows 10 machine, drivers seem to be fine since the preloaded example is working fine, dfu mode and st-link are also working

Sorry, I have no idea for the dongle error. I assume you have followed the procedure is in the release note of the copro firmwares (STM32WB_Copro_Wireless_Binaries\Release_Notes.html). Looks like corrupted file. couldbe good to reinstall the package and check the file.  

For the nucleo : can you try to program the nucleo and then run it without debugger/IDE  ? 

When the port is detected, do you see some information in the tool log windows, and do you have a warning message from the tool ?

Best regards

Stephane

Hi. I have 2 stm32WB dongles but neither are recognised in the device manager. What driver to I need to install for them to be seen?

​Hello

for the STM32WB USB dongle, you need VCP driver to communicate with the application, and DFU to load software. 

For VCP driver : With windows 10, the native inbox driver should be used. For older windows version, you can use driver STSW-STM32102 from st.com.

For DFU mode (bootloader), the driver should be installed with STM32CubeProgrammer. 

Best regards

Sorry, I still don't understand. If I connect an stm32wb dongle (in boot mode) to a windows 10 pc should it appear in the device list? Niether of mine appear in the USB devices.

In the device manager, I see the device "DFU in FS mode" when the dongle is plugged in boot mode  (SW2 moved to "1" side) (in the Universal Serial Bus devices). Do you have some error messages when the device is connected ?

I have the same problem, moreover my device was recognized as 256kB variant, not as 1MB. Something is wrong with these dongles, or with firmware?

I've updated FUS to newest version