Interface and connectivity ICs

Hi all,I'm experiencing very poor WiFi scan sensitivity with the ST87M01 (FW 2.9.0) compared to an ESP32 using the exact same antenna (connected via U.FL). While the ESP32 easily finds multiple networks, the ST87M01 only sees very few, or none at all.Device Info & Scan Config (ST87M01)```textatiSTMICROELECTRONICSST87M01-1301A:2.9.0-M:2.9.0-S:2.9.0-G:2.9.0-B:1.1AT#WSCAN=4,1      <-- [Config] RF Path (NB-IoT antenna path)OKAT#WSCAN=3,500   OKAT#WSCAN=5,3     OKAT#WSCAN=2,0     OKAT#WSCAN=1,1,6,11 <-- [Action] Trigger scan on channels 1, 6, 11OK...#WSSTOP           <-- [Result] (Hardly any networks returned)```Reference: ESP32 Scan (Same Antenna, same spot)```text1: Yippie (BSSID: 3C:A6:2F:B5:E4:37, Kanal: 11, RSSI: -48 dBm)2: RAK7268V2_BAD1 (BSSID: AC:1F:09:19:BA:D2, Kanal: 11, RSSI: -50 dBm)3: Yippie (BSSID: D4:24:DD:4D:F2:2F, Kanal: 11, RSSI: -54 dBm)4: Yippie (BSSID: DC:39:6F:1F:5C:03, Kanal: 11, RSSI: -76 dBm)5: linksys (BSSID: 98:FC:11:CE:00:16, Kanal: 9, RSSI: -86 dBm)

Hi all, Regarding EVKIOTST87M01-2. In the design guide is mentioned the High Speed Interface (HST), in the same guide specifies that this interface requires an external Hardware TPA device, named Dongle HST Logger to recover the data flow for ST Analysis. The questions are:Do you sale this Dongle HST Logger? Is the ST-Link compatible?or is the the data available through the STSW-ST87M GUI?Thanks in advance. Susana 

EVAL-SCS006V1 (TSUSB4532) is plugged into a 65W power supply with an in-line USB-C meter. With no load attached, the meter reads 20.06V, 0.016A, and 0.321W. What on the board that consumes this much power?In contrast, an EVAL-SCS006V1 (STUSB4500) is plugged into the same configuration, the meeter reads 20.07V, 0.000A, 0.000W.Please help me figure this out! 

Hello ,I am planning a new NB-IoT design using the ST87M01 module. I am currently using a Nucleo-U545RE-Q host board paired with the EVKITST87M01-2 evaluation kit.The application involves downloading weather observation files (TXT and XML formats, each under 100 KB) from a public server over HTTPS. Since the target server requires TLS 1.3, a large HARICA RSA ROOT CA 2021 (RSA-4096) certificate, and specific Cipher Suites not supported natively by the module, I have decided to run the TLS 1.3 stack directly on the STM32U545 host MCU. The ST87M01 will be used purely as a transparent TCP/IP pipe.Specifically, the server enforces strict cryptographic handshakes with the following parameters, which I will process on the host MCU:TLS 1.2: ECDHE_RSA with curve P-256 and AES_128_GCM TLS 1.3: X25519 key exchange and AES_256_GCM During early tests, I have noticed that the module frequently transitions from RRC Connected to RRC Idle mode, indicated by the unsolicited notification changing from +C

Hi,hope you doing good.We are currently using NUCLEO-L412RB-P along with X-NUCLEO-60K1A1 for testing. We are attempting to perform USB tunneling with the following sequence: 1.NUCLEO-L412RB-P is connected to X-NUCLEO-60K1A12. X-NUCLEO-60L1A1 part and peripheral lines are connected to NUCLEO-L412RB-P.3.X-NUCLEO-60R1A1 part of board is powered up.4.A pen drive is connected to the X-NUCLEO-60R1A1 part of board. Then started getting logs via UART in the following sequence: 1.RF detected( Once remote part is detected it under goes next state low power until it remains in RF detect state) 2.Low power state 3.Tunneling state 4.RSSI from Local and Host -16db on both side 5.L0 state though we got successful enumeration as per software, host end we got device not recognized pop up once it reaches L0 state. could you please give us resolving for this issue? Thank you

I simply can't figure out how to generate this pulse with my STEVAL-IOM001V1 board. Even the supplied code (en.stsw-iom001) doesn't make me any wiser.

Hello Team,I have used STM6824SWY6F Part in one of my Design and I’m performing a de-rating analysis, so could you please share the below details,1. Junction Temperature2. Junction-to Ambient Thermal resistance3. Junction-to-case Thermal resistance4. Maximum power dissipationThanks,Deva

Just got a new chip — does it come with factory firmware preloaded? If yes, what version is it? And will I need to re-flash the firmware before it can work properly?

I am using the ST67W611M1A6UTR Wi-Fi NCP with an STM32H563ZIT6 MCU on a custom board.The ST67W611 is flashed with st67w611m_mission_t02_v2.0.89.bin, and I am running LwIP on the STM32H563ZIT6 host MCU. I am using the ST67W6X_CLI_LWIP example as a reference to implement a custom TCP stack for my board.Below is my current initialization and Wi-Fi/TCP connection sequence:void network_task(void *argument) { W6X_Status_t ret = 0; W6X_WiFi_Connect_t connectData = {0}; W6X_WiFi_StaStateType_e state = W6X_WIFI_STATE_STA_OFF; wifi_init(); network_log_init(); W6X_App_Cb_t App_cb = {0}; App_cb.APP_wifi_cb = APP_wifi_cb; App_cb.APP_net_cb = NULL; App_cb.APP_ble_cb = NULL; App_cb.APP_mqtt_cb = NULL; App_cb.APP_error_cb = NULL; W6X_RegisterAppCb(&App_cb); app_evt_current = xEventGroupCreate(); /* Initialize the ST67W6X Driver */ ret = W6X_Init(); if (ret != W6X_STATUS_OK) { // TODO: Handle this error appropriately, maybe log it or retry // initialization } vTaskDelay(pdM

I am doing g3-PLC test by connecting two board of EVLKST8500GH-2  according to ST G3-Hybrid PLC&RF GUI Quick start guide, but i am not clear test envirionment 1) COM port of PC is connected with ST8500GH-MB or  NUCLEO-G070RB, when i connect with  NUCLEO-G070RB port is recognized but when i connect with ST8500GH-MB, port is not recognized in the PC.   2) I am using 30V(AC) power for Power line because " ST8500 Hybrid PLC&RF Connectivity Development Kit UserManual"  Safety precautions guide of " The kit is intended for use on extra low voltage (ELV): <50 V AC, <75 V DC." but i am not clear this 30V(AC) is enough for PLC. i want to know the level of Power   3) I want to know power line connection between two board EVLKST8500GH-2. serial or pallel ?

Hello! I try calibrate STPM34 device, but have some troubles.I created some xmls file with Reference Manual and AN4470 and compare results by STPM3x_Evaluation_Software and it different. 1) RM use default Vref value as 1.18, but App use 1.22) Calculation of PHC with PHV=2 different (it true if use formula for PHV=1)Also I find errors in metrology coefficients calculation. metrology.c contains formulas with examples, but it results incorrect.All troubles I placed to xmls file with all needed information.Help me please, get correct formulas for calculation.Thank!

In my application I want to implement an custom inband communication between RX <--> TX。I've gone through the official datasheet but couldn't find clear information about the in-band communication data registers or buffers. Could you point me to any additional reference materials, application notes, or documentation on in-band communication?

Dear ST team,I have configured the ST87M01 for sending +CEREG URCs when registration state changes with AT+CEREG=5.But the modem attaches, but does not sent +CEREG notification (see traces below): Is this a nominal behavior ?AT+CEREG=5OKAT+CEREG=?+CEREG: (0,1,2,3,4,5)OKAT+CEREG?+CEREG: 5,2,"","",,,,"",""OK+CEREG: 0,"","",,,,"",""+CEREG: 2,"","",,,,"",""+CSCON: 1+CEREG: 0,"","",,,,"",""+CSCON: 0+CEREG: 2,"","",,,,"",""+CSCON: 1+CEREG: 0,"","",,,,"",""+CSCON: 0+CEREG: 2,"","",,,,"",""+CSCON: 1+CEREG: 0,"","",,,,"",""+CSCON: 0+CEREG: 2,"","",,,,"",""+CSCON: 1+CEREG: 0,"","",,,,"",""+CSCON: 0+CEREG: 2,"","",,,,"",""+CSCON: 1+CSCON: 0+CEREG: 0,"","",,,,"",""#STENG: ECID=08507721,SRV1=FFB11868,PLMN=0002F802,EDRX=00000001,PSM=00000000,ENRG=000045D7#SLEEP DRX 2.4s#WAKEUP DRX#STENG: ECID=08507721,SRV1=FFB21868,PLMN=0002F802,EDRX=00000001,PSM=00000000,ENRG=00000016#SLEEP DRX 1.7s#WAKEUP DRX Best regards,Thierry

Hi everyone,I am encountering an issue where my MCU freezes during continuous data transmission, and I am looking for some advice or debugging directions.Hardware & Setup: MCU: STM32U575 Network Module: ST67W611M1 Protocol: TCP Driver/Firmware Version: V1.3.0 Issue Description: My application is designed to send a 1KB data packet to a remote server every 3 seconds. The transmission works perfectly fine at the beginning. However, after successfully transmitting several hundred KBs in total, the MCU gets stuck.Through debugging, I found that the firmware completely hangs inside the W61_Net_SendData() API.Observations: The remote server is confirmed to be alive and functioning normally when the hang occurs. The MCU does not hard fault; it simply blocks indefinitely inside W61_Net_SendData(). My Questions: Are there any known issues regarding buffer overflows or memory leaks in this specific API when sending large amounts of data over time? Is there a way to configure a non-b

Hello ST-Team.How can I configure the receiver’s LDC mode so that the LDC timer runs for 4 seconds and then reliably receives a data packet? I want to configure GPIO3 as the RX_DATA_READY interrupt so that the microcontroller wakes up, processes the data, sends an acknowledgment, and then returns to LDC mode.How must the timing be configured on the transmitter side? It would have to send many data packets so that the receiver catches one of them inside the RX window. And when is the acknowledgment allowed to be sent?The goal is to achieve ultra‑low power consumption on the receiver side. Do you have a solution for this?

Hello Team, We are currently investigating an issue related to the SPI communication between the STPM34 sensor and the STM32F4 microcontroller.At system startup, all values measured by the STPM34 remain stuck at zero. Even when voltage and current are injected using an OMICRON test bench, no measurement values are received or displayed.Several tests were performed:If we power up the system and confirm that the issue is present, then electrically restart only the board containing the STPM34, the communication recovers correctly and the measured values are no longer stuck at zero.We also soldered wires on one of the SPI buses (SPI1). Since there are two STPM34 devices on the board, two SPI instances are used to communicate with each sensor. The purpose was to verify whether the communication between the sensor and the STM32 was correctly established.Interestingly, simply soldering wires on this SPI bus makes the issue disappear for this instance. However, on the second SPI instance,

从数据手册只能了解STWLC68的TX流程，而它的RX流程不清楚。STWBC86的TX与RX都不清楚。我想实现的目标是MCU采用i2c通过STWBC86读取STWLC68的i2c寄存器或者MCU采用i2c读取STWBC86收到来自STWLC68的TX数据。我应该如何去发送和接收数据以及在哪儿去拿数据。是否能提供两个芯片固件库的白皮书或使用手册？Google translation: “The datasheet only provides information on the STWLC68's TX flow, but its RX flow is unclear. The STWBC86's TX and RX flows are also unknown. My goal is for the MCU to use I2C to read the STWLC68's I2C registers via the STWBC86, or for the MCU to use I2C to read TX data received from the STWLC68 via the STWBC86. How should I send and receive data, and where should I retrieve the data? Could you provide the white paper or user manual for both chip firmware libraries?”

Dear original factory support team,Hello. Recently, we have purchased your eSIM chip ST4SI2M0020TPIFW(ST4SIM‑200M series) twice through the distributor Mouser Electronics, and found that there are doubts about the working mode and activation ability of the eSIM in the two batches. We hereby ask your company for confirmation:1. Purchase batch information:First order: 550 piecesSecond order: 1010 pieces2. Mode confirmation request:According to your product specifications, ST4SI2M0020TPIFW supports two eSIM configuration modes: GSMA SGP.02(M2M mode) and SGP.22(Consumer mode).All the chips of the same model we used many times in the past are SGP.22 mode and run normally. However, this time, two batches of chips were suspected to be preset in SGP.02(M2M) mode after customer test feedback, which caused the customer to be unable to confirm the "preset" carrier profile (ICC ID/ISDP) when the chips were shipped from the factory, so the activation and subscription service could not be completed.

Hi, i experimented the following configuration STEVAL-MKBOXPRO with BLEMLC code available within FP-SNS-STBOX1 package. For my specific application, i want to increase the BLE transmit power of the BlueNRG-LP chip of the MKBOXPRO. So i modified the code with the aci_hal_set_tx_power_level(1,31) +8dBm (since default value was  aci_hal_set_tx_power_level(1,4) -16dBm). Everything is fine with compilation with Cube IDE. But in practice with the app ST BLE Sensor v5.2.6, the real connection distance still remains about 25m, with a disconnect when RSSI is about -92dBm. These values are correct but what is not correct is that any tries to change aci_hal_set_tx_power_level with different "theoretical" power levels (from -54dBm to +8dBm) do not change anything in practice. It looks like aci_hal_set_tx_power_level has no effect on "real" transmitted poser. Any help will be welcomed to this topic. Thanks reading et thanks in advance or your help. Christian

Hello I am trying to use STM32N6 with ST67W611.What works so far:STM32N6570-DK with X-NUCLEO-67W61M1, I am able to run my firmware that creates an AP and runs a web server with files from the SD card. Based on the discovery board and the ST67 nucleo, I have designed my own PCB. I have three times the exact same board. 001, 002 and 003.Board 001 works fine, AP and web server start. This is the console output:--------------- ST67W6X info ------------ST67W6X MW Version: 1.2.0AT Version: 1.0.0SDK Version: 2.0.97Wi-Fi MAC Version: 1.6.44BT Controller Version: 1.6.121BT Stack Version: 1.10.70Build Date: Nov 19 2025 11:35:01Module ID: C6AFDBD111400004 (-B)BOM ID: 2Manufacturing Year: 2025Manufacturing Week: 13Battery Voltage: 3.348 VTrim Wi-Fi hp: 5,5,5,5,5,5,4,4,4,4,5,5,5,5Trim Wi-Fi lp: 5,5,6,6,6,7,7,7,7,7,8,8,8,8Trim BLE: 4,3,3,4,5Trim

Specific part: ST4SI3M004600HFWAccessed via Quectel modem AT commandshttps://estore.st.com/en/st4si3m004600hfw-cpn.htmlAccording to the product page, it features "Bootstrap connectivity profile provided by a trusted partner".Application note AN5740 says that it applies to ST4SIM-300M (https://www.st.com/resource/en/application_note/an5740-st4sim-with-truphone-connectivity--activation-procedure-stmicroelectronics.pdf).At time of writing ST4SI3M004600HFW, appears to be the only instance of ST4SIM-300M available.So it sounds like the activation instructions in AN5740 should apply to ST4SI3M004600HFW.Those instructions rely on reading the ICCID and feeding it to Truphone.However, the eSIMs that we (and other users) encounter have ICCIDs which are neither unique nor recognised by Truphone (https://community.st.com/interface-and-connectivity-ics-52/st4sim-300m-getting-the-same-iccid-162326).Questions:- Does AN5740 apply to ST4SI3M004600HFW?- Is there a version of the chip that does come with

Hello! I currently have several questions regarding STM8500 + STLD1 DC carrier communication. Please reply!   1: I send differential signals via STLD1, which are capacitively coupled at high voltage between DC48V and DC48V_GND, then received at the receiving end. Shouldn't be any issues, right? The theoretical transmission distance can reach 3km, right? Is there a more complete reference schematic design available? The schematic provided in the official manual is incomplete.   2: The STM32F401 communicates with the ST8500 via UART. Can I use the ST8500 simply by calling AT commands or API interfaces? Or do I need to program the ST8500 itself or download firmware to use it?   *This post has been translated from Chinese to comply with the ST Community guidelines.

Hello,I am testing FP-SNS-BLEMESH1 on two STEVAL-MKBOXPROA boards.Setup:Board: STEVAL-MKBOXPRO AFirmware: BlueNRG-Mesh Sensor Demo v2.1.3Library: BlueNRG-Mesh Library v01.14.000Bearer: PB-ADVOne board configured as Embedded ProvisionerOne board configured as Sensor Node (unprovisioned device)Issue #1 – Embedded Provisioner cannot discover unprovisioned nodeThe provisioner starts scanning correctly, but no unprovisioned device is found.At scan step, the console reports that no unprovisioned device is nearby, even when the second board is physically next to the provisioner.The sensor node logs show:DIAG: PB_ADV_SUPPORTED=1 PB_GATT_SUPPORTED=1 BEARER_INFO=3 Unprovisioned device BlueNRG-Mesh Sensor Demo v2.1.3 BlueNRG-Mesh Library v01.14.000 BLE Stack Initialized & Device ConfiguredSo the node appears to advertise correctly as unprovisioned.Issue #2 – ST BLE Mesh mobile app crashes/stops after provisioningSince Embedded Provisioner could not discover the node, I switched to the ST B

Does the ST67W611M1  (-B version) with PCB antenna have a built in rf switch? We want to programmatically or via pins switch between the PCB antenna and an external antenna.

Module / setup- Module: ST87M01-1301- Host: STM32-class MCU over UART, 115200 8N1, no flow control- Carrier: 1NCE NB-IoT (auto-PDP on CID 5)- AT manual reference: v3.1, 2025-10-06Current sleep-related configuration16:34:39.720 -> === AT readbacks ===16:34:39.720 -> >>> AT+CGMR16:34:39.720 -> <<< A:2.7.0-M:2.7.0-S:2.7.016:34:39.720 -> <<< OK16:34:39.720 -> >>> AT#SLEEPMODE?16:34:39.720 -> <<< #SLEEPMODE: 1,5,016:34:39.720 -> <<< OK16:34:39.720 -> >>> AT#WAKEUPEVENT?16:34:39.720 -> <<< #WAKEUPEVENT: 15,316:34:39.720 -> <<< OK16:34:39.720 -> >>> AT#SLEEPIND?16:34:39.720 -> <<< #SLEEPIND: 0C16:34:39.720 -> <<< OK16:34:39.720 -> >>> AT#RINGPIN?16:34:39.720 -> <<< #RINGPIN:0,20,1,10016:34:39.720 -> <<< OK16:34:39.720 -> >>> AT+CPSMS?16:34:39.847 -> <<< +CPSMS: 1,,,"10010100","0000111