STM32 MCUs Wireless

Hello,I have found some bugs in linker scripts generation when creating a project from CubeMX. Those bugs appears only when code is generated for STM32CubeIDE, related to linker scripts:/* Highest address of the user mode stack */ _estack = 0x20040000; /* end of "RAM" Ram type memory *//* Memories definition */ MEMORY { RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 256K FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 1024K }_estack should be set to 0x2003000, otherwise the system goes into hard fault.RAM_SHARED section does not appear, without it the coprocessor is unreachable I guess.MAPPING_TABLE, MB_MEM1 and MB_MEM2 are not mapped to RAM_SHAREDOn the other hand, if I generate a makefile or TRUEStudio project for stm32wb55cg (1 MB of flash), the linker reports only 512 KBHope to see this fixed, thanks for your help!

In STM32CubeProgrammer I can set RDP on AA level and BB level, but in CLI mode read/write protection is constantly in BB. In CLI protection byte doesnt change, I mean I can't change itand can't write FUS or stack, and even check the fuse version.C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe -c port=usb1 -rdu     -------------------------------------------------------------------                      STM32CubeProgrammer v2.1.0     -------------------------------------------------------------------USB speed  : Full Speed (12MBit/s)Manuf. ID  : STMicroelectronicsProduct ID : DFU in FS ModeSN      

I have successfully uploaded stm32wb5x_FUS_fw.bin to my STM32WB55CC and the next step resulted in the error I don't know how to deal with. Here is the CMD log     ------------------------------------------------------------------                      STM32CubeProgrammer v2.1.0     ------------------------------------------------------------------USB speed  : Full Speed (12MBit/s)Manuf. ID  : STMicroelectronicsProduct ID : DFU in FS ModeSN         : 2065369C3136FW version : 0x011aDevice ID  : 0x0495Device name : STM32WBxxFlash size : 256 KBytesDevice type :

..

I am trying to reconfigure the BLE_HID application to the smallest STM32WBCC processor.The linker script for BLE_Hid example with STM32WBRG which look like this ( stm32wb55xx_flash_cm4.ld) /* Highest address of the user mode stack */_estack = 0x20030000;  /* end of RAM */ /* Generate a link error if heap and stack don't fit into RAM */_Min_Heap_Size = 0x400;   /* required amount of heap */_Min_Stack_Size = 0x1000; /* required amount of stack *//* Specify the memory areas */MEMORY{FLASH (rx)         : ORIGIN = 0x08000000, LENGTH = 512KRAM1 (xrw)         : ORIGIN = 0x20000004, LENGTH = 0x2FFFCRAM_SHARED (xrw)      : ORIGIN = 0x20030000, LENGTH = 10K}_______________________________________________________________I

When programming a binary file stm32wb5x_FUS_fw into the STM32WB55CC, after the line "RSS Status is RSS_IMAGE_IS_NOT_AUTHENTIC" appears a line "Error: fireware not authentic" in red. Why could an error like that happen and why it is impossible to proigram that file on any PC (I tried different!)? Any advice would be highly appreciated.

Try to get demo firmware sources for USB dongle MB1293C. Also a .hex file will be useful.I am trying to use STM32Cube utility to generate code from the .ioc file but the code generated does not support the usb driver properly. Any hints to how to get usb driver code working will be useful to me.

The original version of STM32WB Ble stack is 1.0.0.3/e, Other releases include 1.0.0, 1.1.0, 1.1.1, 1.2.0. What are the differences between these versions? Can you provide detailed documentation?In addition, I'm going to buy some STM32WB . Are these chips manufactured with Ble stacks installed?​

You can find it here : http://risinghf.com/#/product-details?product_id=26&lang=en

I see that cubemx shows x-cube-ble1 as an available sw package for a stm32wb55 project. Is it possible to use the x-cube-ble1 stack on the wb series? I'm having a hard time in getting the flow of how a ble app is configured on the wb, in this forum someone suggested me to read the ble1 and ble2 programming guidelines and they seem clearer and better explained than the wb wireless application notes. Sorry for the basic questio, thanks!

I'm developing a custom board with STM32WB55CGU6 with firmware based on Cable Replacement example. Trying changing the advertised name, I can not put more than 5 chars, the BLE stops working. I know the standard advertising supports until 7 chars. What I have to configure to have a bigger advertised name ?

​FLASH_CR:

So we update the FUS following the steps specificed in the release note, the process went ok and the FSU was upgradedUSB speed : Full Speed (12MBit/s) Manuf. ID : STMicroelectronics Product ID : DFU in FS Mode SN : 206936933136 FW version : 0x011a Device ID : 0x0495 Device name : STM32WBxx Flash size : 256 KBytes Device type : MCU Device CPU : Cortex-M0+/M4     RSS state is RSS_ERROR   RSS status is RSS_UFB_CORRUPT   RSS state is RSS_IDLE   RSS status is RSS_NO_ERROR Deleting firmware ... Firmware delete finished fwdelete command execution finished   hoel@iMac-de-Hoel-7 / $ /Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/MacOs/bin/STM32_Programmer_CLI -c port=usb1 -r32 0x20030030 1 ------------------------------------------------------------------- STM32CubeProgrammer v2.1.0 -------------------------------------------------------------------       USB speed : Full S

In application note AN5289 page 35 it is written that you need to wait for the connection to be established and then call aci_gap_set_pairing_req(). I call this function when connection established event happens, but when I do this return status is 0x46 -> BLE_STATUS_NOT_ALLOWED. My question is if this is the right time to call this function, should I call any other function before or this status flag has to do something with wrong settings before the function call?Do you happen to have an example of how security pairing is established, or maybe an application note that I missed?Thank you in advance,Jaka

I have WB55 Dongle board that someone may have programmed previously. I am trying to start it fresh and make sure it is up to date using all files from  from STM32Cube_FW_WB_V1.2.0I followed the procedure to install new FUS and BLE Stack:STM32_Programmer_CLI.exe" -c port=usb1 -fwdeleteSTM32_Programmer_CLI.exe"  -c port=usb1 -fwupgrade stm32wb5x_FUS_fw.bin 0x080EC000 firstinstall=0STM32_Programmer_CLI.exe"  -c port=usb1 -fwupgrade "stm32wb5x_BLE_Stack_fw.bin" 0x080CC000 firstinstall=1Then I used the Programmer in USB mode to download BLE_TransparentModeVCP_reference.hexAll that seems to work fine. But when I set the switch back to normal boot and plug it in, there are no lights, and no COM port is recognized. Ironically, before I did this, the device did show up on COM3, but it was also unresponsive. What did I do wrong, or how can I figure what is w

The STM32WB55xx devices embed an Arm ®(a) CPU1 Cortex ® -M4 core.I use this chip manual.I operate strictly according to the chip manual, but all of them have errors in reading, writing and erasing a sector.the flash meomory address range:​0x0800 000-0x080f ffff,But when I use burning tool to burn, there is an error in this address 0x080f 6000, reading and writing all report this address error, the following areas can not read and write, using mass erase also report errors; when using j-link burning, erase blank chiperase, erase sector succeeds, erase chip error.

Hi Sir/Madam,Here i need calculate the current required to operate the STM32WB55REvx. I downloaded the datasheet of this MCU. In the datasheet should i need to consider the operating conditions or absolute characteristics to calculate the current required to drive the STM32WB55REvx.Thanks & Regards,

FLASH address: 0x0800 0000~0x080F 5FFF, CPU1 (cortex-M4) can read and write to its normal access, address 0x080F 6000~0x080F FFFF is protected by CPU2 （cortex-M0）and read and write.

Hi,I am a new to STM32WB55 Nucleo and have just started to understand it from the examples provided by the ST. In this process, I have observed unknown data format on hyper terminal. i tried with different baudrates and all the available UART library examples but none of them resolved this issue. May i know the reason why this Board is showing unknown data format for this uart examples. Thanks, Suyodhana

..

Using STM32Cube, I can build the demo project MOTENV1_IKS01A3_WB55RG fresh from the zipfile fine. However, you cannot open the MOTENV1_IKS01A3_WB55RG.ioc file in it's original location. You get and error that it is the wrong name. So I copy MOTENV1_IKS01A3_WB55RG.ioc from the MOTENV1 directory , into the MOTENV1/STM32CubeIDE/MOTENV1_IKS01A3_WB55RG directory. (where it should be)But if I open it there, make no changes and and regenerate the code, I get numerous errors. The first is: motenv_stm.c:149:3: error: unknown type name 'MOTENV_STM_App_Notification_evt_t'; did you mean 'EDS_STM_App_Notification_evt_t'?Diffing against the previous directory shows numerous changes. Looking at just the .ioc file when opened with CUBE, these lines are different:188,189c188,189< ProjectManager.CustomerFirmwarePackage=..\\..\\..\\..< ProjectManager.DefaultFWLocation=false---> ProjectManage

Specifically, I am trying to compile the STM32WB Dongle Thread General CoAP example. Although this isn't a problem specific to STM32 but more with the IDE, I was hoping somebody might have a hint on how to solve the issue. Also, all of the files exist within the scope of the workspace. Error:Info: Internal Builder is used for buildarm-atollic-eabi-gcc -c ..\..\..\..\..\..\..\..\Drivers\STM32WBxx_HAL_Driver\Src\stm32wbxx_hal_cortex.c -mthumb -mcpu=cortex-m4 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -std=gnu11 -DCORE_CM4 -DUSE_HAL_DRIVER -DUSE_STM32WBXX_USB_DONGLE -DTHREAD_WB -DSTM32WB55xx -DST_OT_DEBUG -DOPENTHREAD_CONFIG_FILE=<openthread_api_config_ftd.h> -I../../../../../../../../Drivers/STM32WBxx_HAL_Driver/Inc -I../../../../../../../../Drivers/CMSIS/Include -I../../../../../../../../Drivers/CMSIS/Device/ST/STM32WBxx/Include -I../../../../../../../../Drivers/BSP/P-NUCLEO-WB55.USBDongle/ -I../../../Core/Inc -I../../../STM3

Hello,I'm currently developing an application on the STM32WB55 that utilises IEEE802.15.4 communication. Based on the example application project from the STM32Cube_FW_WB_V1.2.0 package (802.15.4 MAC), I was able to successfully (well, at least to some point) make the communication between an RFD and an FFD work. There is one problem, though. The association process goes well; then I send some data from the RFD using the MAC_MCPS_DATA_REQ command. The FFD gets the data and calls the APP_MAC_mcpsDataIndCb callback. I am, however, unable to read the payload of the MCPS frame. What I get in the application running on the CPU1 core from the CPU2 after the frame reception is a MAC_dataInd_t struct, inside of which there is an msduPtr pointer that should point to some buffer with payload data. As I observed, it points to an address in the SRAM2a protected area (always around 0x20035000; SBRSA option byte is set to 0xA, so the beginning of the protected a

Hi,I'm using STM32WB55 controller in my project for low power BLE. But I have zero knowledge on BLE. Can any one help me in understanding from basics of BLE.

Hlw Sir,I am piyush kumar having a STM32F030 Nucleo Board and one ESP8266 WIFI Module.I am very new to IOT . Can you please guide me on this how can i start IOT with these two.