STM32 MCUs Wireless

I’ve modified the firmware code generated out of STM32CUBEMX the endpoint size change from 64B to 128B. Since this change is in the firmware, the Host driver will read this value from the Device descriptor (during enumeration) and ensures that the driver receives and transmits max of 128B. Though it is against the USB2.0 FS standards which recommend max of 64B, what could be the impact and issues. So far I've tested with short packets and upto 128B, it works seamlessly correct without packet or data loss.

..

..

does ST maintain an archive of CubeExpansions, e.g. I-CUBE-LRWAN? On the product pages, it is always only the latest version that can be downloaded.

Hi. I'm currently implementing an application for test purposes on the STM32WB Nucleo Demoboard. So far I'm very pleased with the experience of adding new services and transvering data. However, to save some energy I want to change the connection interval on my device to 1s or higher. I've enabled L2CAP_REQUEST_NEW_CONN_PARAM and called BLE_SVC_L2CAP_Conn_Update as in the p2p server demo application. That should start the connection interval change. However, in my case the application gets stuck in UTIL_SEQ_WaitEvt() in while((EvtSet & EvtWaited) == 0) with EvtSet = 0. The p2p server demo application doesn't. I can't find any differences regarding this function so far. If I understand correctly EvtSet is set by the M0 core handling the BLE stack. Is there anything else i need to set or change to enable the interval change of an established connection? thank you

..

Hello,I made several modifications to the STM32WB HandsOn_3 example (based on p2p-server project located at c:\STM32WB_workshop\HandsOns\HansdsOn_3) and succeeded to communicate with my mobile application - all OK =) However the above working solution is based on Sequencer (UTIL_SEQ_Run(~0) ) scheduling mechanism. As my entire project is based on freeRTOS, I'd like to find the best approach on how to convert the working Sequencer mechanism into freeRTOS Mechanism? (for P2P server project)P.S I tried to modified the above working HandsOn_3 project, in CubeMX 5.4 by unchecked the Sequencer utility, and checked the freeRTOS however:CubeMX auto code generator implements the HRS one way comm vs. P2P Server two way comm. while debug this code in CubeIDE (1.1.0) the FW got stuck in endless loop2. I checked the examp

I am using the ST32CubeIDE and the imported HeartRate project from the STM32CubeWB package. For both boards the project compiles and is loaded into the board, and then the boards just stop working during debugging. I am not probing the boards or touching them in any way. This is the oddest thing I've ever seen. Has anyone else experienced this?

I couldn't get the CLI application running on the P-NUCLEO-WB55.USBDongle. I updated the FUS firmware according to ../STM32WB_Copro_Wireless_Binaries/Release_Notes.html and installed the stm32wb5x_Thread_FTD_fw.bin on CPU2. The FUS update exited with:FUS status is FUS_IMAGE_NOT_AUTHENTICError: Firmware not authentic!but STM32_Programmer_CLI.exe -c port=usb1 -r32 0x20030030 1 does return the right code (01000200). Flashing the stm32wb5x_Thread_FTD_fw.bin was successful. However, when I flash the ..\STM32Cube_FW_WB_V1.3.0\Projects\P-NUCLEO-WB55.USBDongle\Applications\Thread\Thread_Cli_Cmd\Binary\Thread_Cli_Cmd_reference.hex binary, the system doesn't seem to work. Windows is not able to detect the USB device. Error 43 (Device descriptor request error). The same procedure on the Nucleo64 (with the correspondig binary) worked fine and the CLI is available trough the ST-Link VCP.

I 've built a Lora sender with Arduino.I want to rebuilt it with STM32 (STM32F030F4P6).So I 'm thinking of starting with the Lora library https://github.com/sandeepmistry/arduino-LoRa .I mean to convert it to Atollic studio code (a class I suppose).(I 've also found an STM32 STM32duino library https://github.com/armtronix/arduino-LoRa-STM32/blob/master/src/LoRa_STM32.cpp that might help.Am I on the right track in accomplishing my goal?How do I create a class in TrueStudio?I just create a new file in src folder of my project?

I started messing around with the End_Node example with my B-L072Z-LRWAN1 board, and enabled the sensors despite not having the nucleo board to test with. Curiously I noticed instead of delivering an error, it just locked up.After some investigation I realised that it was hanging in an infinite loop, waiting for an I2C timeout that never comes. The timeout counter seems to be determined by the HAL_GetTick() function, which in turn has its variable incremented by the SysTick_Handler.Having placed a breakpoint on this function I can see that it never fires, leaving anything that relies on it for a timeout stuck indefinitely.I set up a quick empty project in CubeMX and it seems to be called absolutely fine. Changing the TICK_INT_PRIORITY in the example doesn't seem to do anything to fix it either.So why is the SysTick_Handler not being called? How do I fix this?I'm running the End_Node example from STM32CubeEx

In addition to turning the Blue Led on with the p2p server app, I want to turn a Led on connected to a GPIO, using the same signal.

Available as a standalone software running on Windows®, Linux®, and macOS™ operating systems, or through Eclipse plug-inMore precisely what http to enter as "check this site" for "new (STM32CubeMX) software" ?what text filter? ( STM32CubeMX ?) Eclipse 2019-09 takes its sweet time when "checking ALL sites " for new software.

I want use computer Bluetooth to communicate with STM32 board .First, I use ST BLE sensor, succeed.second，use conputer

HiI don't not know if this is the right section to ask my question, but I did not found any specific topic for device S2-LP.I'm performing some tests with the above component interfaced with a MCU STM32L0. The communication is realized through a SPI interface. I succeed in sending a command but unfortunately I cannot understand properly the answer.In the S2-LP user manual, there is a list of registers that can be sued but not a description of transport ptotocol format.For example: The first character of the TX frame is WRITE_HEADER = 0x0. Is correct? The RX frame has another header character. These defines are into the S2LP library that I use. My question is: Is there a documentation that explaining which is the protocol used to communicate to S2-LP component? I read the official s2-lp.pdf user manual but I don't find this specific topic.Thanks in advance for the cooperation

..

I started messing around with the End_Node example with my B-L072Z-LRWAN1 board, and enabled the sensors despite not having the nucleo board to test with. Curiously I noticed instead of delivering an error, it just locked up.After some investigation I realised that it was hanging in an infinite loop, waiting for an I2C timeout that never comes. The timeout counter seems to be determined by the HAL_GetTick() function, which in turn has its variable incremented by the SysTick_Handler.Having placed a breakpoint on this function I can see that it never fires, leaving anything that relies on it for a timeout stuck indefinitely.I set up a quick empty project in CubeMX and it seems to be called absolutely fine. Changing the TICK_INT_PRIORITY in the example doesn't seem to do anything to fix it either.So why is the SysTick_Handler not being called? How do I fix this?I'm running the End_Node example from STM32CubeEx

I have the development board, B-L072-LRWAN1 with the CMWX1ZZABZ-078 module by Murtata on it. This module has an 32.768KHZ crystal on it which will be used for keep the RTC. I would like to implement a wakeup timer using this crystal to wakeup every 250MS to perform a check action, then put it back into stop mode, repeat. I would like advice on how this can be performed and what is required since I cannot find any code examples implementing this wakeup timer with the RTC crystal. I am using the Keil IDE to work with module, but have gotten the debugger to work with STM32CubeIDE. Any help would be appreciated. Thanks!

I'm working to complete the port of BlueNRG code to the STM32WB. I've gotten everything working up to the point where I make the device discoverable. The WB stack is returning an error, but there's no documentation to explain what this error could mean.Here's the binary exchange: # GAP discov   00000000: 00 00 00 00 00 00 00 00 01 83 fc 0d 00 00 00 00 ........ ........ 00000010: 00 00 00 00 00 ff ff ff ff ........ . #? complete 1 fc83 -> 42 ERR 00000000: 04 0e 04 01 83 fc 42 00 ......B. The first 25 bytes are the command sent to the stack. There are eight bytes of pointers that aren't used, one byte for the message type which is BLE CMD, the two byte command code, one byte payload length, and then the parameters. I'm using all default parameters at this point in order to eliminate possible issues. The response I get is code 42, which means parameter error. So, if the parameters are

Hi there,I am working on Murata cmwx1zzabz (i.e. STM32L072CZ) and my code is based on the ST en.i-cube_lrwan. For all the basic stuff (joining, sending messages) it runs fine. The Mac commands, that actually manage the network, are OK except the "sticky" ones.As stated in the Semtech library, "The sticky answers were introduced to the specification in order to ensure that critical MAC commands have been understood by the end-device. You can see the sticky answers like an acknowledgement." So these sticky Mac commands require some acknowledge from the device because it is related to critical parameter (sticky Mac commands are SRV_MAC_RX_PARAM_SETUP_REQ, SRV_MAC_RX_TIMING_SETUP_REQ, SRV_MAC_DL_CHANNEL_REQ). So when the device is receiving one of these, the Mac layer notifies the application layer that an uplink is required as soon as possible. The MlmeIndication callback is then executed.But looking at the ST library lora.c (more specially LOR

..

..

How change mbed linker for STM32WB55 to used STM_OTA bootloader (need to add TAG_OTA_START, TAG_OTA_END ...). This is my code but don't work, mbed given my error:; #if !defined(MBED_APP_START) ; #define MBED_APP_START 0x08000000 #define MBED_APP_START 0x08007000 ; #endif   ; #if !defined(MBED_APP_SIZE) ; 768KB FLASH ; #define MBED_APP_SIZE 0xC0000 ; 768KB FLASH - 0x7000 = 0xB9000 #define MBED_APP_SIZE 0xB9000 ; #endif   #if !defined(MBED_BOOT_STACK_SIZE) #define MBED_BOOT_STACK_SIZE 0x400 #endif   #define Stack_Size MBED_BOOT_STACK_SIZE   ; 768KB FLASH (0xC0000) + 192KB SRAM (0x30000) + Shared mem LR_IROM1 MBED_APP_START 0x184 { ; load region size_region   ER_IROM1_LOW MBED_APP_START 0x184 { ; load address = execution address *.o (RESET, +First) *.o(TAG_OTA_START) }   ; Total: 79 vectors = 316 bytes (0x13C) to be reserved in RAM ; RW_IRAM1 (0x20000000+0x13C) (0x30000-0x13C-Stack_Size) { ; RW data RW_IRAM1 (0x20000004+0x13C) (0x30

I'm using ST-LINK of p-nucleo-wb55 board. I tried to connect P-Nucleo-wb55 to the ST-LINK Utility, but I can't. Below the comment of ST-LINK Utility.11:09:19 : ST-LINK SN : 0671FF39373842504306602511:09:19 : ST-LINK Firmware version : V2J35M2611:09:19 : Connected via SWD.11:09:19 : SWD Frequency = 4,0 MHz.11:09:19 : Connection mode : Normal.11:09:19 : Debug in Low Power mode enabled.11:09:20 : Can not connect to the target!         Please select "Connect Under Reset" mode from Target->Settings menu and try again.11:09:22 : Unexpected errorWhen I using the STM32CubeIDE Debug, it works. But I want to erase the program of wb55. Can I erase the program on the STM32CubeIDE?or How can i connect the ST-LINK Utility to P-Nucleo-WB55?

I am new to STM32WB, i have written BLE middle-ware application it is working on Scheduler, in main while Loop SCH_Run(~0) is handlling the entire middleware, now i want to wirte the actual application for Cortex-M4 but when i add anything in the While loop my BLE Stack stop working. So kindly guide me how to code in Multi-core controller