STM32 MCUs Wireless

The schematics on page 5 says regarding HSE external""C31 must be placed in orderto avoid stubs on XTA pathwhen C31 not fitted."Probably R41 is meant to be placed.

Hello, I'm using STM32WB55 for my application and I'm following the AN5289 Rev 3 to write data into flash. When the BLE is looking for a device to connect, the procedure stuks checking PESD bit for more then 30 seconds. It is normal?I suppose the amount of time the program is stuck is directly connected to the timeout of the "searching" phase. Is it true?If I jump that control, the procedure fails, so, do you have any suggestion to follow?

I have STM32WB55REV6 based custom target board which contains 512KB flash. I tried to download FUS and BLE stack, but it seems like did not programmed correctly and Host controller (CM4) is in wait for event from network processor (CM0). Following batch file command sequence and address used for target STM32WB55REV6 as per release note. SET BIN=STM32WB5x/stm32wb5x_FUS_fw_1_0_2.bin SET STACK=STM32WB5x/stm32wb5x_BLE_Stack_full_fw.bin   STM32_Programmer_CLI.exe -c port=SWD -fwdelete timeout 2 >NUL STM32_Programmer_CLI.exe -c port=SWD -r32 0x20030030 1 timeout 2 >NUL STM32_Programmer_CLI.exe -c port=SWD -fwupgrade "%BIN%" 0x0807A000 firstinstall=0 -v timeout 2 >NUL STM32_Programmer_CLI.exe -c port=SWD -fwupgrade "%STACK%" 0x08057000 firstinstall=0 -v   pauseI have tried with firstinstall = 1 flag too.I have also attached the log.txt file of executed commands from batRequest to guide for the same.

Hi all,My problem is as follows: using ChirpStack to collect data from custom built nodes where the LoRaWAN part is derived from ST LRWAN 1.3.1 codebase, the following happens. Compiling the firmware with Region set to EU868 everything is hunky dory and traffic flows smoothly all the way up to App Server. Joins and uploads are 100% succesfull so apparently everything is in order.When switching the project (and GW conf) to US915 and recompiling, again a functional application is created. However, this time every join attempt is consistently discarded at the Gateway (IMST packet forwarder) due to CRC error.What is very curious is, that i can take the original ST demo app, compile it on a nucleo-l476RG with a SX1272MB2xAS shield, and the demo works nicely in both Regions, no CRC errors or at least rarely.Both nodes have the exact same ST MCU and same Semtech SX1272 radio, with essentially identical HW and SW implementation. Specifically, the Region settings are unmodified between implemen

Hello,I' trying to update the FUS on my STM32WB55CG (1M), I have the latest STM32Cube_FW_WB_V1.3.0, I followed the Release_Notes in the STM32WB_Copro_Wireless_Binaries :for information I use this chip on my own board (not a nucleo)I switched the MCU in bootloaderthenSTEP 3 : Delete current wireless stack :STM32_Programmer_CLI.exe -c port=usb1 -fwdeletethen STEP 4 : Read and upgrade FUS VersionSTM32_Programmer_CLI.exe -c port=usb1 -r32 0x20030030 10x20030030 : 00050300 : FUSv0.5.3 => Must be updated using STEP 5.0x20030030 : 01000100 or 01000200 : FUSv1.0.x => Up to date, you can download the new wireless stack using STEP6.so I need to update it STEP 5 : Download new FUS :STM32_Programmer_CLI.exe -c port=usb1 -fwupgrade [FUS_Binary] [Install@] firstinstall=0in my caseSTM32_Programmer_CLI.exe -c port=usb1 -vb 2 -fwupgrade stm32wb5x_FUS_fw.bin 0x080EC000 firstinstall=0I increse the verbose mode to 2 (I join the log file flash_FUS_VB2)most of the time the upgrade

..

Hello,I have a STM32WB35Cx MCU that has 256 K of flash according to the datasheet, in my STM32CubeIDE in STM32WB35CCUXA_FLASH.ld FLASH is given 128K of LENGTH. I changed this to 256K on my board without any noticable issues.

Hello everybody,I've a project with a stm32wb55 and I need following functions :BLERTC (Tamper, Calendar and alarms,backup registers)I get started from Nucleo example IBeacon.I got some difficulties to start CM0+ but thanks to an other topic I succeeded to emit BLE advertising : https://community.st.com/s/question/0D50X0000Az4HdhSQE/cant-get-the-advertising-stateThe next step was to implement RTC, I succeeded in getting and setting date, setting alarmA and got it fired on EXTI line 17 !BUT : when I use cubeMx to generate "RTC A and B alarm interrupt through EXTI line 17"(RTC_Alarm_IRQn), my BLE is not working anymore...In fact, IPCC_C1_RX_IRQHandler never fires !Please look at the diff attached to this message when I generate or not RTC_Alarm_IRQHandler which make my BLE working or not. What is the link between them ? Both are working but not together :sad_but_relieved_face: Thanks for your help,Clément Duval

I am looking for a possibility to connect multiple UART to the device and thus looking at a possibility of connecting via a multiplexer like SN74LV4052A. I wanted to use 2-ports for -wire and 2 for UART standard communication. How do I accomplish that. I guess I have to dedicate LPUART1 for Thread_CLI and thus want to use USART1 only with a mux.

Hello, I am from Turkey and I want to use my university project STM32WB55 SOC. However, I do not have the chance to obtain Murata production from band pass and low pass filters used in reference designs. MLPF-WB55-01E3 IPD will not be in stock until the project deadline.

..

Posted on April 05, 2017 at 22:40     LoRa Discovery Kit   STM32L072 and LoRa Discovery Kit featuring Open LoRa module by Murata using STM32L072CZY6TR MCU   http://www.st.com/en/evaluation-tools/b-l072z-lrwan1.html   Features   Ultra-low-power STM32L0 Series MCUhttp://www.mouser.com/stm32l0, Cortex® -M0+ based with 192Kbytes of Flash memory, 20Kbytes of RAM, 6Kbytes of EEPROM, LCD, crystal-less USB, T-RNG, PCROP 157dB maximum link budget +20dBm, 100mW constant RF output versus Vsupply +14dBm high efficiency PA Programmable bit rate up to 300kbps High sensitivity: down to -137dBm Bullet-proof front end: IIP3 = -12.5dBm 89dB blocking immunity Low RX current of 10mA, 200nA register retention Fully integrated synthesizer with a resolution of 61Hz FSK, GFSK, MSK, GMSK, LoRa™ and OOK modulations Built-in bit synchronizer for clock recovery Sync word recognition Preamble detection 127dB+ dynamic range RSSI Built-in temperature sensor and low battery indicator 1

Hi,I'm using the ST Disco board for a wireless sensor application. Most of the time the hardware is in sleep, but when it needs to get back operating it seems it can't recover from sleep. Any suggestion?Dario

Hello everyone, in the last few days, I have been looking at a storage method. The goal of the application is to save the individual environment calibration of BSEC algorithm from BME680 in a non-volatile memory of the uC.My uint8 to uint64_t shifter works very well and reliably. Also, the method to read the flash registers works without limitations.When writing the data, the same error occurs over and over again. The write operation is only successful if this register has never been written before. Flashing the Chip changed nothing. If the register has already been written once, the write commandHAL_FLASH_Program(FLASH_TYPEPROGRAM_DOUBLEWORD, StartPageAddress, data64[byte] );     /* *Function from stm32wbxx_hal_flash.c */ HAL_StatusTypeDef HAL_FLASH_Program(uint32_t TypeProgram, uint32_t Address, uint64_t Data) { HAL_StatusTypeDef status;   /* Check the parameters */ assert_param(IS_FLASH_TYPEPROGRAM(TypeProgram)); assert_param(IS_ADDR_ALIGNED_64BITS(Address));

How to add LORAWAN package into my project and I try to include the package into include path but not any success.

void Set_Option_Byte( void ){ FLASH_OBProgramInitTypeDef OBInit; /* Unlock the Flash to enable the flash control register access *************/ HAL_FLASH_Unlock(); /* Clear OPTVERR bit set on virgin samples */ __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_OPTVERR); /* Unlock the Options Bytes *************************************************/ HAL_FLASH_OB_Unlock(); OBInit.OptionType = OPTIONBYTE_USER; OBInit.UserType = OB_USER_IWDG_STOP; OBInit.UserConfig = OB_IWDG_STOP_FREEZE; HAL_FLASHEx_OBProgram(&OBInit);  /* Start the Option Bytes programming process */   if (HAL_FLASH_OB_Launch() != HAL_OK) { /* User can add here some code to deal with this error */ while (1) { } } /* Prevent Access to option bytes sector */  HAL_FLASH_OB_Lock(); /* Disable the Flash option control register access (recommended to protect the option Bytes against possible unwanted operations) */ HAL_FLASH_Lock();}Note: I had forgot to call HAL_FLASHEx_OBGetConfig(&OBInit); thus OBInit might ha

Hi everyone I have been working with the BL072Z-LRWAN using the AT Slave software provided by stm.In our custom devices , we are using the same module and to save power we have a relay to turn on and off the module , as and when required. But the problem is that whenever i switch off the module , the key and OTAA join parameters are lost , and to send data over LoRa , we have to initiate Join Command again , which is not a good way to go.Can you please guide me on how can i save the join parameters in the memory so that i don't have to do it again?Is there any AT command to save the information?Thanks and RegardsRajat Kalyan

Is there a firmware package I can use with the P-NUCLEO-WB55 USB Dongle so that I can use that dongle as a USB BLE Radio? I want to be able to develop a BLE device (Nucleo board) as a bluetooth device but my Windows PC doesn't have a Bluetooth radio compatible with BLE (I have a USB Bluetooth 2.0+EDR dongle but this isn't compatible with BLE).Looking at the example selector in STM32CubeIDE, `BLE_TransparentModeVCP` looks like the closest candidate. Would this be what I'm looking for?

I used STM32-B-L072Z-LRWAN1 board and want to used COMP 1 and COMP2 in my project.to used COMP1 as per data sheet PA1 can be used as inputbut on STM32 LORA board its not incorporated.I want to know where PA1 is used ,any doc is useful.Can I used this pin/COMP1 separately in my custom board or not.pls help me out

Tried p2pserver, HealthThermometer and Custom. It goes well up to advertising but I'm not able to connect to the ST Sensor BLE app on the smartphone. Using STM32CubeIDE all along. It used to work with STM32CUBEWB 1.9 and earlier. Is it just me?

I'm not able to connect the NUCLEO-STM32WL55JC1 board (Updated FW today to V3.J7) to the STM32CubeMonitor V.1.1.0 ​Fun facts: Blink connection test works and the firmware is reported correctly in the connection config box.​Error message reads: "not connected | JTAG/SWD error/f5) In addition: Please fix the copy & paste bug of the Mac version (1.1.0). Known for at least 8 months.

I would like to be able to set the time from the LoRa network. So when I receive the time I make a HAL_RTC_SetTime with the information collected, but then my program freezes. Do I have to stop the Lora layer, timers beforehand?Thank you in advance for your help

HiI`m having some issues with programming p-nucleo usb dongle board with USB DFu mode.The way I understand is ,there is an internal system bootloader inside STM32WB which supports USB Firmware DownloadIf I can jump to bootloader from my application , my custom board/usb donle will present itself in Windows Device Manager as `USB DFu Device`When above occurs , Dfuse application can detect the chip and download previously generated *.dfu filethis is the piece of code that i use to jump to system bootloader on button click. I modified the DFU Standalone Project provided by STM. #define USBD_DFU_APP_DEFAULT_ADD 0x0800C000U typedef void (*pFunction)(void);   void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin) {   pFunction JumpToApplication; uint32_t JumpAddress;   switch(GPIO_Pin) { case BUTTON_SW1_PIN: /* Change the period from 500ms to 250ms or 250ms to 500ms */ delay = (delay == 250) ? 700 : 250; JumpAddress = *(__IO uint32_t*) (USBD_DFU_APP_DEFAULT_ADD); JumpToAppl

All Examples for the STM32WB have the following code in their app_ble.c:const uint8_t* BleGetBdAddress( void ) { ... udn = LL_FLASH_GetUDN(); if(udn != 0xFFFFFFFF) { company_id = LL_FLASH_GetSTCompanyID(); device_id = LL_FLASH_GetDeviceID();   bd_addr_udn[0] = (uint8_t)(udn & 0x000000FF); bd_addr_udn[1] = (uint8_t)( (udn & 0x0000FF00) >> 8 ); bd_addr_udn[2] = (uint8_t)( (udn & 0x00FF0000) >> 16 ); bd_addr_udn[3] = (uint8_t)device_id; bd_addr_udn[4] = (uint8_t)(company_id & 0x000000FF);; bd_addr_udn[5] = (uint8_t)( (company_id & 0x0000FF00) >> 8 );   ... }Also Application Note AN5289 has the same listing.Comments and descriptions lets me believe this yields a valid public bluetooth address.The address created is "80:E1:26:XX:XX:XX". The first part is the OUI which should belong to ST Microelectronics. But in fact 80:E1:26 is not assigned. STMs OUI is 00:80:E1.So I have to assume that ST does not supply a valid MAC address for t