Interface and connectivity ICs

Hi,I have a working 3-phase STPM33/34 energy meter. Voltage is correct. The current is wrong by a fixed factor of approximately 60.Setup:CT: 80A primary / 5A secondaryBurden resistor: 6.8 ΩGain: x2Mode: UART with auto-latchExpected reading: 0.6A → Actual reading: 0.01AWhy I think this is a calibration/formula issue and not a hardware fault:The error is consistent and proportional (not random)Voltage on same chip reads correctlyCRC passes on every frameNo register corruption detectedMy question to the community:Has anyone seen a x60 error factor on STPM33/34 current channels? Which misconfigured parameter — CT ratio in firmware, KI calibration register, Kint constant, or gain setting — would produce exactly this ratio?

Hello, I have designed a custom PCB for sensor acquisition and I am using an STM32U575 as main processor and then a BlueNRG-M2SA module configured as a coprocessor with the DTM_SPI.hex image. They are both connected through SPI but I can't seem to get past the verify_packet() function. I attach a zip file with my STM32 project in which I am using the X-CUBE-BLE2 middleware with the beacon application and HCI_TL set to Basic and HCI_TL_INTERFACE to UserBoard.My SPI is configured with polarity set to low, 1 edge clock phase and with a frequency of 1MBit/s.The problem I am having is that it seems like the packets I am receiving through SPI don't make sense completely and they seems to be a bit off. I have measured the SPI signals and the received header is {0xFF,0x09,0x01,0x06,0x00}. The measured signal is shown below together with the clock and the rising edges marked The data received after the header is {0x04, 0xFE, 0x06, 0x02, 0x00, 0x02}. The following image shows the

H563ZI Nucleo and Nucleo-67W61. Using the CLI Binary version 1.1.0 I get: #### Welcome to ST67W6X CLI Application ###### build: 20:14:53 Sep 25 2025--------------- Host info ---------------Host FW Version: 1.1.0[ERROR] [575] [spi_xfer_engine] (spi_iface.c:297) Invalid magic 0x5501[ERROR] [575] [spi_xfer_engine] (spi_iface.c:512) Invalid spi header from peer, magic 0x5501, len (0, 0x0), version 0, type 0flags 0x0, rsvd 0x1[ERROR] [2575] [spi_xfer_engine] (spi_iface.c:448) waiting for spi txn ready timeouted[ERROR] [4000] [ST67W6XTask] (w61_at_common.c:375) sem_if_ready not received[ERROR] [4000] [ST67W6XTask] (w61_at_sys.c:314) Could not init Modem handler[ERROR] [4000] [ST67W6XTask] (main_app.c:783) [ERROR] in W6X_Init API[ERROR] [4000] [ST67W6XTask] (w6x_sys.c:101) W61 Init failed[ERROR] [4000] [ST67W6XTask] (main_app.c:283) failed to initialize ST67W6X Driver, 2##### Application end Suggestions? Thank you.

I am designing a board with the ST87M01. I am using two separate LDOs (TLV757 series) both connected in parallel to a 5V VBUS source.Rail A: 3.3V for GPIO/UART.Rail B: 2.5V for the Modem PMU.Since both LDOs start simultaneously, there may be a slight millisecond variation in when each rail reaches its target voltage.Questions:Does the ST87M01 have a strict requirement for the 2.5V PMU rail to be stable before 3.3V appears on the GPIO pins?Is there a risk of latch-up or back-powering if the 3.3V rail rises ~100µs faster than the 2.5V rail?Should I implement a hardware delay (e.g., RC delay or Power-Good signal) on the 3.3V LDO Enable pin to ensure it trails the 2.5V rail?PS. add ST87M01 label to choose in forum for topic creation. Greetings,Andreas

We have several custom boards with ST67W61 modules. If we flash the device with t02, per instructions on wiki,  we are able to successfully communicate with these devices and also re-flash them if need be. So far so good.However if the device is flashed with t01 it is no longer flashable or even usable unless you do a full chip erase. I'm mentioning this here in case other people run into this problem.QConn_Flash\QConn_Flash_Cmd.exe --port COMxx --erase --whole_chip Note that this issue only occurs with t01 binaries and not with t02. D:\temp\x-cube-st67w61-main\Projects\ST67W6X_Scripts\Binaries>QConn_Flash\QConn_Flash_Cmd.exe --port COM38 --config NCP_Binaries\mission_t02_flash_prog_cfg.ini --efuse=NCP_Binaries\efusedata.bin [08:14:13.300] - Serial port is COM38 [08:14:13.300] - ================================================== [08:14:13.300] - FW get address from partiton file D:\temp\x-cube-st67w61-main\Projects\ST67W6X_Scripts\Binaries\NCP_Binaries\./partitio

Dear ST Support Team,I’m currently trying to run the ST67W6X_CLI application (from the Wi-Fi ST67W6X CLI Wiki)using the following setup:Wi-Fi Expansion Board: X-NUCLEO-67W61M1Host MCU Board: NUCLEO-F446REIDE: STM32CubeIDE (latest version)Middleware: FreeRTOS (as provided in the ST67W6X_CLI example)The project builds successfully and the firmware is programmed without errors, but at runtime, I encounter a HardFault_Handler.The fault occurs inside the FreeRTOS queue management code, specifically during a call to xQueueReceive() in queue.c. Debug Information:When the fault occurs, the debugger stops inside:prvCopyDataFromQueue(pxQueue, pvBuffer);and the corrupted member is:pxQueue->uxItemSizeObserved value: 536871212 (0x2000412C) — which clearly points to an invalid or corrupted queue structure.Call stack snapshot:HardFault_Handler()prvCopyDataFromQueue() at queue.cxQueueReceive() at queue.cspi_get_txbuf() at spi_iface.cPlease see the attached screenshot (from STM32CubeIDE) showin

Hello, I am reviewing the reference design for the ST87M01 and noticed that a 1nF capacitor is specified for the DC block on the GNSS RF path. In many high-sensitivity GNSS designs, 100pF is the standard choice for the 1.5 GHz L1 band to ensure the Self-Resonant Frequency (SRF) remains well above the operating frequency. Questions: Why was 1nF selected for this specific SiP instead of the typical 100pF? Does the internal matching of the ST87M01 rely on the specific reactance of a 1nF series capacitor at 1575 MHz? For a design strictly optimized for GNSS sensitivity, would a 100pF High-Q (C0G) capacitor offer any measurable improvement in insertion loss or noise figure compared to the 1nF reference value?   Greetings, Andreas

Hello everyone,I am trying to establish IO-Link communication between the P-NUCLEO-IOM01M1 (STEVAL-IOM001V1 + NUCLEO-F446RE) and an external IO-Link sensor, the Wenglor P3PC012 (COM3, 230.4 kbaud), using the STSW-IOM001 firmware.Hardware setup:STEVAL-IOM001V1 powered with 24V on CN1Sensor connected on CN3: L+ on pin 1, GND on pin 3, CQ on pin 4NUCLEO-F446RE connected via USB to PCWhat works so far:I2C communication with L6360 confirmed working (LED1/LED2 registers write correctly, LEDs blink as expected)L+ enable working correctlyConfiguration register writable (CQ Push-Pull mode)What I am trying to do:Read process data (distance measurement) from the sensorAny advice or working example code would be greatly appreciated. Thank you.

Summary: When enabled st67w61 forcefully keeps MISO low and doesn't let other slaves use SPI. In our setup: - STM32L452: Is master SPI with latest mission_profile_t02. - st67w61: Is SPI slave 1 with dedicated CS pin - 3rd party SPI slave 2 with dedicated CS pin SPI bus speed is 2MHz, and CPOL, and CPHA are 0 Reproducing problem: 1.  st67w61 is enabled (CHIP_EN is HIGH), - BLE initialized W6X_Ble_Init() successfully - Advertisement starts - We are able to pair with st67w61 successfully via our phone - We then try to start SPI slave 2 with no success. Data is being sent via MOSI but MISO stays low. We have tried this with other types of slaves with no success. After turning OFF (CHIP_EN to LOW) st67w61 module, we can communicate successfully with Slave 2. However we need to have both slaves enabled for our application to work. Note that CS pins are in the correct state. It seems like the st67w61 forcefully pulls MISO line low when enabled and doe

Hi all,I’m exploring whether the S2LP LDC mode can be adapted for a transceiver configuration.From what I understand, ST’s example code provides separate implementations for RX-only and TX-only devices. Using these individual examples, I’ve verified that reliability is good. Additionally, the datasheet also describes the TX and RX sections separately.However, I’m interested in implementing LDC mode in a transceiver setup (where the same device handles both TX and RX). Has anyone implemented this successfully? If so, did it work reliably, and would you be able to share any reference code or guidance?Thanks in advance for your support. @Gyessine @waclawek.jan 

Dear ST,I am searching for  LTE module , basic data transfer is to send 2Kb of data using mqtt and perform http opeartion. I have got to know about ST87M01 LTE module, for getting started i got the evaluation board EVKITST87M01-2 i have few doubts before getting it 1) Can i use Vi, Jio or Airtel sim card with it.2) In some series it is showing esim, so does it have built-in esim or need to add it in design externally.3) can i interface ST4SI2M0020TPIFW esim with it.4) If i done with prototype with it, can i get the design and component availability for large.5) Documents for gettign started with ST87M01 and ST4SI2M0020TPIFW esim. Regards,Shubham

Hello everyone, I'm using a host (STM32F7) communication with ST67W611 BLE WIFI via SPI.So far, I can configure application P2P Client, T01 architecture, gen code and build pass.The issue what I'm facing is I can't init SPI communicaiton with ST67W611. so Could you help me answer some question to debug what issue is?1. I bought ST64W611, so Could I need to re-flash firmawre for this module?2. the W6X_Init(0 function init failed, I checked the pin SPI_RDY alreay has level low (= 0).so I hope if there is someone has worked with ST67W611 via SPI with a host STM32, please share me the experience? Thank you very much!

Hi,I’m currently working with an ST4SIM-300M eSIM and testing it for an IoT application.I was able to read the following ICCID from the device:89019990001234567893I wanted to ask if anyone knows which operator or profile this ICCID belongs to. Also, I’m not sure how the activation process should work for the ST4SIM-300M.Does it come with any initial bootstrap profile for network access, or do I need to provision a profile first before it can connect?AT%PINGCMD=0,"8.8.8.8"OKAT+CPINERRORAT+CSQ+CSQ: 99,99OKAT%PDNSET?%PDNSET: 1,,IPV4V6,,,,,0,0,0OKat+cops?+COPS: 0OKat+cops=0At the moment I’m not able to get network connectivity, so any guidance on the correct activation/provisioning steps would be really helpful.Thanks in advance!

Hi,I´m trying to get the BLE p2p running on a STM32G0B1. But it´s really hard to figure out what to copy from the U5 demo application! Is there any detailed guide how to do this?When configuring it in STM32CubeMX there´s also the problem, that Application can not be selected - maybe because FreeRTOS is integrated in G0 package and can not be selected as a component. Best regards,Achim

Hello ,i filled ConnectOpts.Reconnection_nb_attempts = 4; ConnectOpts.Reconnection_interval = 2; strncpy((char *)ConnectOpts.MAC,(const char *) Mac, sizeof(Mac)); strncpy((char *)ConnectOpts.SSID, WIFI_SSID, W6X_WIFI_MAX_SSID_SIZE); strncpy((char *)ConnectOpts.Password, WIFI_PASSWORD, W6X_WIFI_MAX_PASSWORD_SIZE);after running W6X_WiFi_Connect() api getting following error even hot spot is n:CW:ERROR,12\r\n\r\n\r\n\r\n"WLAN_FW_SCAN_NO_BSSID_AND_CHANNEL\n" any one have idea? Thanks!Edited to apply source code formatting - please see How to insert source code for future reference.

Hello,I've got a question about pairing and bonding for BLE with iOS devices for ST67W61.I've checked available functions and AT commands, I don't see any mean to encrypt the characteristic. As the iOS BLE stack requires it to pair and bond - am I missing something or it's not yet implemented?Best regards

  I am currently evaluating a power line carrier (PLC) communication solution and plan to use the ST8500. The client’s equipment is quite densely packed, with several hundred units, and requires auxiliary communication via the power line to promptly detect equipment failures and crashes. The estimated node capacity needs to reach 1,000. These 1,000 units are distributed within a high-voltage transformer, which cannot be expanded or relocated.   According to the description in the ST Smart Grid Products brochure, the ST8500 can support a network of up to 1,200 nodes. This raises the first question: are these nodes connected directly to a concentrator, or do they require repeaters to forward signals to the final concentrator? Do the repeaters need to be isolated from one another by transformers?   The client has a large number of devices, some of which have very high time-sensitivity requirements. Can these 1,000 nodes communicate across different frequency bands? Furtherm

We have followed single conversion mode as outlined in: L9966 lambda sensor interface – rev. 1.0.0 1 L9966 lambda sensor interface Application Note. But the result register is all zeros.Is there anything missing?The register nameing is not consistant datasheet has DWT_VOLT_SRC_LSF_CTRL, but app note DWT_VOLT_SRC_CTRL.The sequencer mode works fine. 

Hello everyone, I find your new product, the ST87M01-1301, an interesting alternative to Nordic or Simcom. However, I haven't found any hardware design guides for the module yet. Could you please provide some? A schematic would be really helpful, showing how to wire the pins and connect the SIM card, antennas, etc. What is the maximum current draw of the module? If you have any battery management products, how can they be used together (for example: BMS + STM-Host MCU + ST87M01 – an example schematic would be great) so that people can use your specifications as a guide and build their own prototypes with your modules. I really like how Simcom handles their documentation; you could certainly learn from their example. Currently, your documentation for the module is a bit chaotic and incomplete, as if it were done by an intern. Many greetings,Andreas 

I have eval kit EVALSTPM33 from Digikey. When I plug it into my PC USB port, I see a red LED near the USB port, and in the Windows device manager it shows up as com port #6. If I connect to that com port and try to read a register in software from https://www.st.com/en/embedded-software/stsw-stpm001.html, I get an error. After 10 seconds or so the red LED goes out. I do not have anything connected besides the USB port.     

I use DTM project,download to my board,but it is not running.I use my project it can running normal.How to solve it ,thanks

hiii,Do you plan to support BLE TMAP on this module? 

Hi Does ST have any WIFI chip with FTM? Thanks

Im trying to get the reading from distance sensor SICK DT35 through STEVAL-IOM001V1 which uses the L6360 IC via STSW-IOLINKGUI to get the proper reading we need to upload the IODD file of the sensor which I'm not be able to do with the GUI. There's not sufficient information about the GUI which is the cause of the problem so provide the needed documentation otherwise provide us the way to get the value from the sensor. and specify that what is the STSW-IOLINKGUI for is it just to test the connection via running the LED BLINK code.Give me a detail documentation to understand all the functions of the GUI.

Hello,we have developed our own RF modules based on the S2-LP transceiver and we are currently characterizing their maximum usable sensitivity.Measurement setupTX and RX are connected through a calibrated variable attenuator.The transmitter sends 500 packets with a 200 ms interval between packets.After the test, we create statistics on successfully received messagesOur RF settings: Frequency base = 433 MHz, Data rate = 3.84 ksps, Deviation = 2 kHz, Filter = 12 kHz; Preamble length = 64 bits. Rest parameters are identical to the configuration generated by the S2-LP DK GUI.The only parameter that changes is the RX timer configuration.Observed behaviorWe obtain different maximum usable sensitivity values depending on the RX timer setting:RX timer set to infinite (S2LPTimerSetRxTimerCounter(0)):→ Maximum usable sensitivity ≈ –105 dBmRX timer set to 200 ms timeout (S2LPTimerSetRxTimerUs(200000)):→ Maximum usable sensitivity ≈ –111 dBmThis is a significant difference (~6 dB), and we would li