WATCH ON-DEMAND | STM32 Summit 2026
Ask questions and find answers on connectivity ICs, focusing on protocols and I2C challenges on STM32 Nucleo boards and BlueNRG products.
Most recent activity
I created a KNX communication module using ST KNX, but when the KNX Bus voltage is transmitted, the waveform is ringing, resulting in a communication error. I am using the recommended value of 68 Ω for the external resistor RTX on pin R68. Please give me some advice on how to improve this.
What's the max DC powerline voltage I can use with the X-NUCLEO-PLM01A1 expansion board? Asked another way, what's the max voltage I can connect to the PLM_CONNECTOR C1?
I have a SPIRIT1 DK_2.2.1 dev kit, with two motherboards and two STEVAL-IKR002V3D transciever boards with EEPROM.When I run two of the SPIRIT1 DK - Application v2.2.1 (one per motherboard) and set one for TX and the other for RX with default settings in BASIC packet format the Rx sees the Tx as expected.When I take the STEVAL-IKR002V3D and attach it to a test setup using a Nucleo-F429ZI board, running FreeRTOS, using STM32CubeIDE HAL, and a port of (SPIRIT1 DK_2.2.1/Projects/Drivers/BSP/Components/Spirit1/SPIRIT1_Library and SPIRIT1 DK_2.2.1/Projects/Projects_Cube/Spirit1Library_Examples/Src/BasicGeneric/SDK_BasicGeneric_B.c, the SPIRIT1 sees the EEPROM, completes initialization and sits in the while(1) loop with a state: MC_STATE: 0 0x07, 1 0x02 (READY, XO_ON, RX_FIFO_EMPTY)Only a single interrupt is received, with xIrqStatus 000D0500.If I use the SPIRIT1 DK - Application's TX to send messages, the Nucleo SPIRIT1 does not appear to see the messages, remaining in the above mentioned st
Good morning everyone,I purchased the X-NUCLEO-BNRG2A1 board, and I am interested in using it as a standalone device rather than as a BLE shield for an STM32 microcontroller.According to the board specifications and pinout, this should be possible by directly programming the BLUENRG-M2SP module via the J12 connector and an ST-Link.However, I am a little confused about how to start developing the firmware. If I understand correctly, the reference SDK should be STSW-BLUENRG1-DK, but it does not include any projects that can be directly imported into STM32 Cube IDE.Could someone kindly provide me with some guidance on how to functionally integrate the SDK and the reference IDE, and suggest a practical starting point for developing a simple BLE server with a couple of characteristics?Thank you for any suggestions,Fabio Rossi
..
A cursory search of the internet shows the Zephyr Community decided not to port the BlueNRG-LP for use with the Zephyr Framework/RTOS. The reason they gave (in 2023) was: "not planned". That seemed a bit vague to me. Though this is likely a question for the Zephyr Community, I wonder if anyone here can answer why there seems to be little appetite for porting the BlueNRG-LP to Zephyr? I considered undertaking this effort myself but wasn't sure if there is a reason bigger than: "No one has the time or inclination". I will try to ask the same question of the Zephyr Community if no answer here.Jeff
Hello,Our product is currently in the testing phase, and we are using the USB2534 hub IC for both data transfer and device charging on downstream port.In our setup, we are using USB 2.0 with a Type-C connector. A pen drive or mobile phone is connected to the downstream port of the USB2534, while an iPad, MacBook, or laptop is connected to the upstream port.Data transfer on the downstream port and mobile charging are working well.However, our key requirement is to enable iPad charging on the upstream port while the iPad is connected as a host and transferring data simultaneously.Could you please suggest a suitable USB PD controller IC or any other solution that could meet this requirement?A simple block diagram of our device is attached for batter understanding. Looking forward to your guidance. Best regards,Tushar Raval.
Dear ST Support Team,I attempted to test the interfacing of X-NUCLEO-67W61M1 using 32F746GDISCOVERY, but unfortunately, it did not work as expected. In order to resolve this issue, I have several questions:I am trying to test X-NUCLEO-67W61M1 using STM32F7 instead of the sample products list(H7S3L8, H563ZI,N657X0-Q ...). From what I understand, the listed boards are simply examples for which you provide ready-made code samples, but the X-NUCLEO-67W61M1 should be interfaceable with STM32F7 as well. Is that correct?I implemented an NCP Loader for 32F746GDISCOVERY based on the sample code for NUCLEO-H7S3L8 you provided . I also modified the batch file in an attempt to retrieve the chip info from X-NUCLEO-67W61M1, but the operation failed. Below are the batch file I used and the error message I encountered:---------------------- execute result of batch file -----------------------------------------[18:09:54.152] - Chipname: qcc743[18:09:54.152] - Version: eflash_loader_v2.5.1[18:09:54.152]
如何在 STM32F1/F4 或其他制造商的 MCU 上使用 ST67W61?是否有完整的开发过程?基于 MDK Translated to English by Google: How to use ST67W61 on STM32F1/F4 or other manufacturers' MCUs? Is there a complete development process? Based on MDK.
Dear all, ST67W611M1 is a wonderful module that STM could fulfil the gap for wireless connectivity compared to ESP32, while performing design for the prototype board, I found that the WIKI page did not mention any future update capability and requirements for update. Can any ST member answer this question for me? 1. Do I required perform USART connectivity for runtime firmware update?2. Can I update the module via BLE same as stm32wb/stm32wba series?3. Please advise all methods to update the module. Thank you all in advance. JowyC
I want to get a pair of ST60 module for demo test,requirement:1, ST60 for Near Field Communication2,one RJ45 to another RJ45 transparent transmission;3,module has RJ45 connector\Power connector\buildin antenna;4, support 100Mbps and above;5, Sold in China
Split from this already-solved thread. Hi there,I am also having questions about that module, especially when it comes to the symbol difference between the one found in the X-NUCLEO-67W61M1 product page here:https://www.st.com/resource/en/schematic_pack/mb2230-antenna-a04-schematic.pdf And the one in the datasheet: https://www.st.com/resource/en/datasheet/st67w611m1.pdf Shall we understand the RESERVED pins in the datasheet will eventually be designated as GPIOs (USB, JTAG, UART...)? Or since the dev board schematic files are older than the datasheet, are the peripheral features of the ST67W611M1 being reducted for future releases? Also as the author of the thread mentioned, what should be done with the RESERVED pins ? Should they be left NC or tied to GND?Thanks for your support
Hello,I am working on a project using the Nordic nRF9160 (cellular IoT module with LTE-M/NB-IoT support) and would like to integrate it with your ST4SIM-200M (MFF2 eSIM).I would appreciate guidance on the following:What are the required hardware and software steps to use the ST4SIM-200M with the nRF9160?Does ST provide any AT command interface, SDK, or middleware for modem communication with this eSIM?How do I provision or activate the eSIM if my mobile operator only provides SM-DP+ activation via QR code?Is there any documentation or application note specifically for using ST4SIM with Nordic modems?I’d be grateful if you could point me to the right documentation, software tools, or reference designs.Thank you!
In the datasheet of the BLUNERG-M2 module, it states the following:"The BlueNRG-M2 module allows applications to meet the tight advisable peak current requirements imposed withthe use of standard coin cell batteries. Optimized results are obtained when the embedded high-efficiency DC-DCstep-down converter is used (BLUENRG-M2SA). Instead, for the BLUENRG-M2SP the best performance in termsof power consumption is achieved using a 1.8 V DC power supply. The BlueNRG-M2 can be powered directlywith a standard 3 V coin cell battery as with a pair of AAA batteries or any power source from 1.7 to 3.6 V."Is there a place where I can see more detailed differences between the M2SP and M2SA modules, especially regarding the internal DC-DC converter? I tried looking in the datasheet, but there is no detailed explanation.
Hello ST Community,I'm working on a Web Bluetooth project using the STM32WB55 and the ST Web Bluetooth App.So far, I’ve successfully connected to a single BLE device (e.g., MYDEVICE00) using a custom BLE service and characteristic. However, I would like to connect to multiple STM32WB devices at the same time, and retrieve characteristics from each device concurrently, because I would to send various sensors data at the same time.=>What I've Done:I’m using the default Header.js logic, which currently uses a single myDevice object.I tried modifying it to use a list of devices (connectedDevices), but I quickly realized navigator.bluetooth.requestDevice() allows selecting only one device per user gesture.I also tried filtering automatically for 'MYDEVICE00' in code to avoid repeated user interaction, but Web Bluetooth requires explicit user gestures for each connection request.=>What I Need:A proper approach to connect multiple STM32WB devices one by one and store each device's GATT
BLE Mesh option is not shown in STM32WBA55CG
Hi, I´m a bit confused, how to get thsi bluetooth modul running:- I designed my own board with a STM32H747 and the bluenrg-m2sp modul- I want to run the modul in hosted mode (application is running on the STM32H747-> M4 Core)- I configured everything in CubeMX with the X-CUBE-BLE2 middleware, activated Wireless BlueNRG-2 and Device BLE2 Application (I don´t understand e.g. why I need to configure a UART interface and SPI interface?) It took my some days to figure out, that the bluenrg-m2sp is deliverd without firmware and where to get it. After reading some articles I found and flashed the DTM_SPI_NOUPDATER_M2SP.bin and finally I got a communication over SPI and the code of the STM32H7 run to the main loop without errors, but from that mainloop on, no further communication happend on the SPI. I also tried to find the modul via blutooth with my phone, but was unable.I´m still not sure, if this is the rigth firmware for the module?So I flashed the B
Dear [Support Team / Sir/Madam],I am encountering an issue with connecting to the network using an ST4SIM200M eSIM along with the nRF9151 DK board.I have followed all necessary setup steps, but the device is still unable to successfully register on the network.Here are the AT commands I executed along with their responses:> ATOK> AT+CEREG=5OK> AT+CSCON=1OK> AT%XSYSTEMMODE=0,1,1,0OK> AT+CFUN=1OK> AT+CEREG?+CEREG: 5,4OK+CEREG: 2,"C154","00366391",9+CSCON: 1+CEREG: 2,"C154","00366391",9,0,11+CSCON: 0+CEREG: 2> AT#XPING="www.google.com",45,5000,5,1000"EAI_SYSTEM"ERRORThe AT+CEREG? command consistently returns 0,4, which indicates that the device is not registered and is searching for a network.Additionally, AT+COPS? shows 0, implying automatic network selection, but registration is not succeeding.For your information:I am located in Surat, Gujarat, India.The eSIM is the ST4SIM200M model provided for IoT deployments.The board in use is the nRF9151 DK.And at the truphone
Hello,We are using 128MHz clock in our board. Can any of the buffer in this 54AC164245 devices be used as a clock buffer for this clock? We will directly feed 128MHz crystal clock oscillator output to one of the input pin and the output clock coming out of it will be used as an input clock for the processor.Does 54AC164245 support 128MHz?
In the AN6316, the table 2 has a column with pin name for ST67W611M1 but they don't correspond to any pin found in ST67W611M1.Would be great to have the correct pin name for ST67W611M1.
Hello all, The journey of trying to run 6LoWPAN on the S2LP continues. After resolving compilation issues (see: https://community.st.com/t5/stm32cubeide-mcus/not-compiling-subg2-generated-project-and-not-sure-if-working/td-p/803758), I can confirm that generating the project from the board caused problems, while generating from the MCU resolved most of them—except for a timer issue. Switching to the system timer (SysTick) resolved that as well, even though I initially wanted to keep it free and use a different timer. However, after compiling and loading both the server and client projects onto their boards, the behavior remains the same: they seem to have no connectivity with each other. I also tried using the border router and a serial sniffer—none of them appear to be working. It's as if the devices stop responding within seconds. The serial sniffer doesn’t even register a button press event. Does anyone have suggestions on where I should start looking or what I might be missing to g
I want to communicate with ECU using L9663 PSI5 transceiverUse only transmission mode, No receiving mode is required.In the circuit diagram in the datasheet, it looks like PSI1 and 2 pins are connected to the ECU. Is that right?What is the DOUT pin? Is it correct to use it only for sending data received from the sensor to the MCU by connecting it to the MCU in direct/interrupt mode?And I need L9663 sample source code, so please share it with me.
Hi everyone Does anyone know if I can use X-NUCLEO-S2868A2 for 915Mhz ? . It's a quite confuse , the schematic says the RF balun can operate 868 - 930 MHz . If not could you recommend similar board for 915Mhz .I'm trying to avoid the board that has external PA range extender .Due to I wanna to test only the S2-LP consumption and no other .Thanks in advance
Hi: The sensor is set to 20 bits of payload, 3 bits of frame control, 1 bit of status, and 16 bits of data. Currently, the InitiatDATA-RDY bit of L9663 has been set. I use the format of initializing data to set initobuf_id to 0 and register to 1. The data sent to 9663 through SPI always returns 0x44000001. No matter what the initobuf_id and register are set to, they are all 0x44000001. I would like to ask where the error occurred。
Hi, I have to interface microcontroller with ST4SIM-200s through modem for cellular connectivity. But I can't find out any details about modem from data brief of ST4SIM-200s. can you give me suggestion about modem?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.