2020-10-15 01:48 AM
I got some STM32WB55CG samples from st office and the date code is 034. The read out FUS version is 1.1.0. Has the default firmware been upgraded? So the customer doesn't have to upgrade FUS anymore?
D:\Program Files\STMicroelectronics\stm32cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe -c port=SWD mode=HOTPLUG -r32 0x20030030 4 -r32 0x20030024 50
-------------------------------------------------------------------
STM32CubeProgrammer v2.5.0
-------------------------------------------------------------------
ST-LINK SN : 32FF6C063047463341421351
ST-LINK FW : V2J37S7
Board : --
Voltage : 3.23V
SWD freq : 4000 KHz
Connect mode: Hot Plug
Reset mode : Software reset
Device ID : 0x495
Revision ID : Rev Y
Device name : STM32WBxx
Flash size : 1 MBytes
Device type : MCU
Device CPU : Cortex-M0+/M4
Reading 32-bit memory content
Size : 4 Bytes
Address: : 0x20030030
0x20030030 : 01010100
Reading 32-bit memory content
Size : 52 Bytes
Address: : 0x20030024
0x20030024 : A94656B9 00000001 01010000 01010100
0x20030034 : 00000006 00000000 00000000 00000000
0x20030044 : 00000000 00000000 00658473 0080E126
0x20030054 : 00000496
Solved! Go to Solution.
2020-10-26 08:33 AM
Yes sir. I did. The yellow LED on the ST-Link side blinks but not the other three LEDs that are supposed to be used by the application. Also curious to know, though the board shows ST-Link why is it that programmers sees only USB1? Is there anything I am missing? Thank you for your time.
Best regards
2020-10-26 08:49 AM
Hi Remi QUINTIN,
I tried to read the binary file memory location 0x080CB000. The connection gets lost and I need to restart afresh. However I am able to read code from 0x8000000.
2020-10-26 09:04 AM
Could you please download the option bytes.
You won't be able to read above address 0x080CB000. This area is protected from all read/write accesses once the SFSA is set to 0xCB. Hence the importance to know what are the option bytes.
CubeProgrammer tool can use either SWD or USB ports (or UART). It depends pn how you set the Nucleo board.
2020-10-26 09:20 AM
Hi Remi QUINTIN,
Here are the option bytes.
RDP - AA
BOR_LEV - 0
User configuration screenshot is here -
SFSA - 0xf4
Should I post other options too? Thank you.
2020-10-26 09:42 AM
So obviously there is no RF stack programmed on the dongle.
So first perform a mass erase (it should generate an error that you won’t consider) or erase all sectors up to the 0xF4 one.
Then program the RF stack. If it is successful, check the SFSA option byte. It should be set to 0xCB if the RF stack is correctly installed
If it is, just finalize your configuration, programming the application at the address 0x08000000.
It should work.
So perform a mass erase (this will generate an error that you should not consiere) or you erase all ectors up to the 0xF4 one and above.
2020-10-26 09:51 AM
Hi Remi QUINTIN,
Thank you for the reply. Will mass erase delete FUS firmware also? Do I need to program it again?
Best regards
2020-10-26 10:13 AM
No The FUS is located in the secure area. This area is defined as all sectors above the SFSA pointer.
This area is protected against any read/write/erase access.
This is why this SFSA pointer is updated with a much lower value (for example 0xCB) when the RF stack (BLE stack for example) is correctly installed.
2020-10-26 10:21 AM
Hello Remi QUINTIN,
I programmed the controller as advised. Now SFSA shows 0xcb. I programmed the application hex file, still problem remains same. Only once after programming the device the GREEN LED was ON, but the application in the mobile could not detect any BL devices. I removed power and applied again. Now the GREEN LED is OFF and app is unable to detect any BL device.
2020-10-26 11:05 AM
Are you selecting the right BLE_p2pserver application for the dongle (not the one for the nucleo)?
The green LED should blink (not light on only).
Green led off means the RF stack is not advertising => Strange.
Could you recheck the option byte?
2020-10-26 08:53 PM
Hello Remi QUINTIN,
Sorry for the delayed reply. I am using the Nucleo board and am using the programmes for this board. To connect to the board I am using my mobile (Android based). I will redo everything again and post the results. I would also like to get ZigBee working. I guess once BL is working I may be able to get ZigBee working without bothering you. Kindly help me solve these issues. Thank you.