STM32 MCUs Wireless

can i get the firmaware for st-nucleo-lora-gw-at-fw-v2.1.7-asia923-925-TTN.bin

When I checked the LE Audio unicast operation of the provided project on the STM32WBA55G-DK1, I noticed a strange behavior.For the peripheral, the PAC settings are Sink 2, Src 1, but when I perform QoS Configuration using the following procedure, the notification for the QoS Config of Sink2 is not notified to the central.1. QoS Config Src 1 -> QoS Configuration Notification 2. QoS Config Sink 1 -> QoS Configuration Notification 3. Qos Config Sink 2 -> No Notification Also, for the central, the PAC settings are Src2, Sink1, but for some reason, QoS Config is not executed for Sink even though the peripheral actually supports Sink.From the above behavior of the peripheral and central, I suspect that the implementation is such that QoS settings cannot be set to more than three EPs, or that it cannot be used properly if there is only one EP fo

I am wanting to add the STM32WBMMG to my board but it will need to be compatible with an external NFC antenna so I can have cellular communication. Is this possible and how would I go about implementing this?If it is not possible are there other STM modules that are NFC compliant?   

I am desiring to place the STM32WB5MMG on a board design that already has a large LoRa Antenna. I am reviewing the datasheet and reading over the design suggestions for placing the module. In particular, I am trying to implement the design with this guidance: Where d is 22 mm and c is 27 mm. I am trying to decide between two different design choices. Option A:

I am planning to use the STM32WB05KN as a network coprocessor for a STM32U0. The Nucleo board has both LSE and HSE populated, but since my PCB is space constrained, I would like to use the internal oscillators instead of external and also turn off SMPS. My understanding is that the provided prebuilt DTM firmware would not work without these components and I would need to change these settings:The document this points to (AN5503) describes steps to rebuild the firmware using the BlueNRG GUI but says to use CubeMX for STM32WB0 devices:

example code : MRSUBG_WakeupRadio_Tx of STM32Cube_FW_WL3_V1.1.0board : NUCLEO-WL33CC1compiler : Keilrunning the code, at first message below will shown on Virtual Com,"STM32WL3 LPAWUR - Transmitter example.Use PUSH Button 2 to send a frame."but after pushing Button 2 on board, no message is shown on Virtual Com?!

Hi all, So to my surprise, I have issues getting a button press to work in a Lora PingPong sequencer example, and I can't find any relevant posts, so ...The part I'm using WLE5.The ping-pong code is working fine, but I wanted to add a button to start sending from one end, and PA0 was my choice. I have setup the gpio, and falling edge interrupt, and everything works as far as to setting the Pending bit in EXTI/PR1/PIF bit 0 when I press the button. But no interrupt happens. I suppose I must have missed something. But what? The code sits in HAL_PWR_EnterSLEEPMode() -> __WFI() So I think my question is what parts could I have missed?My main suspicion is related to HAL_NVIC_SetPriority() and HAL_NVIC_EnableIRQ(), which I don't seem to get a hang on. I have tried different arguments (EXTI0_IRQn, EXTI15_10_IRQn) to them, but it makes no difference. How do know which one to use for a particular gpi

Hello everyone !I'm currently working on the STM NUCLEO-wl55jc card and I'm having a few problems with it.I'm using the Ping Pong example code, which allows LoRa point-to-point communication between 2 cards. This works perfectly.My problem now is that I'd like to put one of my 2 cards in StandBy mode. So I use the function ‘HAL_PWR_EnableWakeUpPin(PWR_WAKEUP_PIN1_HIGH);’ -> line 113, to initialise the wakeup pin, and the function ‘HAL_PWR_EnterSTANDBYMode();’ -> line 117, to enter StandBy mode. Then, in my while(1) loop, under ‘ifdef GO_TO_LOW_POWER’, I simply want to turn on an LED when I exit StandBy mode and start LoRa communication using this ‘MX_SubGHz_Phy_Process();’ -> line 146, function. However, when a pulse arrives on the wakeup pin, PA0, the LED lights up but unfortunately communication doesn't take place. So I wanted to know if this was the right way to proceed and if my card really went into StandBy mode at the start or not. Because when it's

Hello everyone,I have encountered an issue with the STM32WB05KZ on a custom board which only allows me to flash the board under very specific conditions. The first time out of the box, everything works fine, I can flash using a ST-LINK V3-PWR straight from CUBEIDE V1.18.0. After this first time programming, the board becomes fully unresponsive to the debugger. My code does seem to run (verified by two LEDs connected to PB4 and PB5). When using STM32CubeProgrammer, the system reports that it's unable to read the Chip ID. After much trial and error, I've found that by disconnecting the reset pin from the debugger and pressing the Close Debug button in the Debug Authentication (which I haven't enabled anywhere) menu, I can connect to the board through the STMCubeProgrammer software. I was wondering if this behaviour is to be expected, because I can't find it in the Reference manual or Datasheet. And if this behaviour can be disabled. For context:- The board ha

Dear STMicroelectronics Support Team,I hope this message finds you well.We are currently using the STM32WB55RGV7 MCU as per your datasheet recommendation, we have designed RF1 Section with a Low-Pass Filter circuit, Like below attached image.This circuit covered range was very low with Low pass Filter. 

Hi everyone,I'm working on STM32WB10CC and I use it as a BLE peripheral only. I would like to have 2 simultaneous BLE connections on it. I used STM32CubeMX with STM32_WPAN to setup my BLE. I'm able to connect one device but when I'm trying to connect a second one, it connect and disconnect instantly with the following errors :- 0x3E (HCI_CONNECTION_FAILED_TO_BE_ESTABLISHED_ERR_CODE)- 0x08 (HCI_CONNECTION_TIMEOUT_ERR_CODE)To handle multiple connections, I used STM32WB-BLE-sensors-multiple-links example.I calculated my GATT table with the excel given by ST (GATT_DB_Size_SRAM_NVM).Here is my config :CFG_BLE_NUM_LINK = 2CFG_BLE_NUM_GATT_SERVICES = 6CFG_BLE_NUM_GATT_ATTRIBUTES = 28CFG_BLE_ATT_VALUE_ARRAY_SIZE = 187CFG_FAST_CONN_ADV_INTERVAL_MIN = 0x80 //80msCFG_FAST_CONN_ADV_INTERVAL_MAX = 0xA0 //100ms

Hello,I have an STM32WB5MMG chip, and I work with power consumption. I have the problem that after I stop advertising (aci_gap_set_non_discoverable()), I see that a flag LL_PWR_IsActiveFlag_C2DS() is still False, and I can not switch to Switch_On_HSI(). Why does the CPU2, after stopping advertising, not go to deep sleep mode?

As described in the subject above, I burned the OTA firmware on the board with the STM32WB55 Microcontroller and I can no longer use CubeIDE or CubeProgrammer because it does not recognize the Debugger (ST-Link). It gives the message below in the image. What really happened? But I can use the ST BLE Sensor App on the smartphone and see the STM_OTA advertising and I can also do the Firmware Upgrade (P2P Application and Heart Rate both adapted to run on FUOTA). Therefore the microcontroller is working well as the BLE Stack too. But unfortunately I can not use the board in CubeProgrammer or CubeIDE and for now I am not finding the solution to solve this. I have already tried changing the mode and reset mode in CubeProgrammer, the voltage is correct, etc.  

I would like to know if the binary recording file (BLE_Ota_reference.bin) that is in the folder pathC:\Users...\STM32Cube_FW_WB_V1.22.0\Projects\P-NUCLEO-WB55.Nucleo\Applications\BLE\BLE_Ota that is seenis in the path P-Nucleo-WB55.Nucleo can be used in other microcontrollers (even STM32WB55), but with differentcharacteristics such as Flash Size, smaller pinouts (Example of the Nucleo kit uses 68 pins STM32WB55GVx) andwhat I want to use is the STM32WB55CE microcontroller that has 48 pins and smaller Flash space.

We are using stm32 mcu STM32WLE5JC custom boardbelow connection we are following for SWD Debugger ISP1 Pin Connected To Function 1 3.3V VDD (VAPP) 2 PA13 SWDIO (Data I/O) 3 PA14 SWCLK (Clock) 4 NRST Reset (optional but recommended) 5 GND Ground but while debugging we are getting below error please suggest solution.   IDE Configuration:

hi ST team supportI’m using the STM32WB09 to develop my locator tag device application, and I have a few questions:Does the STM32WB SDK support the Google Fast Pair service?Do you have any documentation or example code on how to use Google Fast Pair to create a locator tag device that is compatible with Android’s Find My Device app? 

Does the BLE stack full also support encrypted advertising? The only example available is for the extended stack (link)

Hello everyoneI watched the video on ST's MOOC about how to integrate FUOTA via BLE for the STM32WB55 microcontroller and applied this Bootloader feature via the "ST BLE Sensor" smartphone app to the project of a product I'm developing and it's working very well. Now I need to work with a partner to develop our proprietary application on our smartphone app for both Android and iOS. I tried to find something on GitHub, but I couldn't find it. If you have a link or any recommendations, I'd appreciate it.Edited to fix FOUTA typo.

Hi I'm trying to connect NUCLEO-H755ZI-Q with X-NUCLEO-WB05KN via usart. I'm using usart2 (pd3, pd4, pd5, pd6) on the host board and CN7 on the shield. BLE initialisation fails if I set `hw-flow-control` in Zephyr in devicetree. Without flow control and with the same connection, it works fine. I'm using BLE_TransparentMode_UART_with_Updater from X-CUBE-wb05n. I tried soldering SB10 and SB11, but to no avail. It would be great to have a full datasheet with a detailed description of all interfaces and how they work, the only document I could find is UM3355, which is not very helpful. 

Hello i Have a question about the STM32WL5MOC.I need to be able to use the bootlader of the WL and in the same UART line use the AT Command.But it seems that LPUART1 that is the only way to use AT Command Application is not used in the bootloader.

Hi, I want to send data and receive commands through BLE. For that, I followed some tutorials where I learned how to generate code using STM32CubeIDE. I can now see my device name in the BLE scanner, but I also want to send data and receive commands.  I need to write some code for this. Can someone help me with where to write the code? For now, I just want to send some random data like 0x9944. I am using stm32wb55cgu6 board

Dear ST Support Team,I hope this message finds you well.I am currently working on a custom RF design using the STM32WLE5CCU6 in UFQFPN48 package, and I intend to operate in the 433 MHz ISM band with +22 dBm output power.While referring to Application Note AN5457, I found valuable information and examples for PA output matching networks and impedance values extracted via load-pull analysis. However, it appears that the document does not provide any reference impedance data or matching guidelines for 433 MHz at high power levels (+22 dBm) for this specific MCU and package.Therefore, I would like to ask:What is the optimal output impedance (complex conjugate of the load) for the PA in this configuration (433 MHz, +22 dBm, UFQFPN48)?How can I accurately calculate or measure the required PA matching network (L1, C1 values) to transform this impedance to 50 Ω, considering high efficiency and minimal power loss?

Hello ST Community,I am developing a custom board based on the MB1389 development board and have encountered some obsolete components used in the reference design. Specifically:NX3L1T3157GM,115 is now obsolete. I plan to use NX3L1T3157GMZ as a direct substitute.BGS13S4N9E6327XTSA1 is also obsolete, and I am considering BGS13SN8E6327XTSA1 as a replacement.I’ve reviewed the datasheets for both substitutes and noted minor differences in parameters such as on-state resistance and channel matching in the NX3L1T3157 variant, and potential RF characteristics in the BGS13S4 replacement.Could anyone from ST or the community advise if these substitutions are fully compatible with the MB1389 design, or if there are specific implications (e.g., signal integrity, RF performance, PCB footprint) that I should be awar

I can not get any output on PB9 after setting TIM16_Init:void MX_TIM16_Init(void) { /* USER CODE BEGIN TIM16_Init 0 */ /* USER CODE END TIM16_Init 0 */ TIM_OC_InitTypeDef sConfigOC = {0}; TIM_BreakDeadTimeConfigTypeDef sBreakDeadTimeConfig = {0}; /* USER CODE BEGIN TIM16_Init 1 */ /* USER CODE END TIM16_Init 1 */ htim16.Instance = TIM16; htim16.Init.Prescaler = 32000; htim16.Init.CounterMode = TIM_COUNTERMODE_UP; htim16.Init.Period = 65535; htim16.Init.ClockDivision = TIM_CLOCKDIVISION_DIV1; htim16.Init.RepetitionCounter = 0; htim16.Init.AutoReloadPreload = TIM_AUTORELOAD_PRELOAD_ENABLE; // TIM_AUTORELOAD_PRELOAD_DISABLE; if (HAL_TIM_Base_Init(&htim16) != HAL_OK) { Error_Handler(); } if (HAL_TIM_OC_Init(&htim16) != HAL_OK) { Error_Handler(); } sConfigOC.OCMode = TIM_OCMODE_TIMING; sConfigOC.Pulse = 0; sConfigOC.OCPolarity = TIM_OCPOLARITY_HIGH; sConfigOC.OCNPolarity = TIM_OCNPOLARITY_HIGH; sConf

I was able to flash the BLE full extended and run the Ble Transparent Mode in the dongle correctly. But when I want to use the Thread Cli Cmd application it simply won't work. I flash the correct stack (thread ftd bin v1.22.0 (at 0x0808B000 as the Release notes says) and the FUS version is 1.2.0 (from release 1.22.0). The APP_THREAD_CheckWirelessFirmwareInfo() returns p_wireless_info->StackType = 0, so the Leds starts blinking in error. This happens when after uploading the stack I press Start FUS and then proceed to debug. But if I press Start Wireless stack (as I had to do with the nucleo and the ble_thread_dyn stack), when I debug and boot CPU2 it won't send the Ready Notification (which it correctly does when it start with the fus). So the problem is that from the FUS I cannot start the Thread Stack but when I read the Stack version from the CubeProgrammer it says the correct one. Also if I follow this: from CubeProg Start