cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CUBEMONITOR-RF am i missing something?

Javier1
Principal

Hi dark wizards of embedded electronics, its me again, javi.

This time im trying to use the STM32CUBEMONITOR-RF with my STM32WB55 Nucleo pack.

I cannot make it work with my NUCLEO BOARD

Once i flash the USB DONGLE (STM32WB55CGU6) with the

\STM32Cube\Repository\STM32Cube_FW_WB_V1.12.1\Projects\P-NUCLEO-WB55.USBDongle\Applications\BLE\BLE_TransparentModeVCP

 I am succesfully able to use STM32CUBEMONITOR-RF

0693W00000DmVxWQAV.png 

But when im trying to use the NUCLEO BOARD (STM32WB55RGV6)....

I flash the

\STM32Cube\Repository\STM32Cube_FW_WB_V1.12.1\Projects\P-NUCLEO-WB55.Nucleo\Applications\BLE\BLE_TransparentMode\Binary\BLE_TransparentMode_reference.hex

 And no response whatsoever, it doesnt work....

0693W00000DmVuOQAV.png 

I am clueless why, maybe im flashing the wrong firmware in the nucleo board?

Maybe the coprocessor .bin is corrupted?

we dont need to firmware by ourselves, lets talk
1 ACCEPTED SOLUTION

Accepted Solutions
Javier1
Principal

i believe this is caused because i corrupted the coprocessor firmware in both my nucleo boards, and i am unnable to programm it back to normal now

https://community.st.com/s/question/0D53W000013qLmwSAE/cubeprogrammer-firmware-upgrade-error-firmware-not-authentic-pnucleowb55

edit:

okay i put the coprocessor firmware back in place, now it works.

(trough stlink's usb not user usb)

0693W00000DmdfzQAB.png

we dont need to firmware by ourselves, lets talk

View solution in original post

1 REPLY 1
Javier1
Principal

i believe this is caused because i corrupted the coprocessor firmware in both my nucleo boards, and i am unnable to programm it back to normal now

https://community.st.com/s/question/0D53W000013qLmwSAE/cubeprogrammer-firmware-upgrade-error-firmware-not-authentic-pnucleowb55

edit:

okay i put the coprocessor firmware back in place, now it works.

(trough stlink's usb not user usb)

0693W00000DmdfzQAB.png

we dont need to firmware by ourselves, lets talk