Interface and connectivity ICs

Is there a demonstration project (outside of the CLI) for the target-wake-time feature?

Hi,I'm integrating a newly ordered X-NUCLEO-67W61M1 shield with a NUCLEO-H753ZI board, using the X-CUBE-ST67W61 package. I'm hitting an init failure and want to confirm the root cause before I flash anything, since I have some open questions about the flashing process itself.1. Original symptom — SPI header validation failure at bootRunning the ST67W6X CLI/Echo application, I consistently get:EXTI callbackInvalid magic 0x5501Invalid spi header from peer, magic 0x5501, len (0, 0x0), version 0, type 0 flags 0x0, rsvd 0x1sem_if_ready not receivedsem_if_ready not receivedCould not init Modem handler[ERROR] in W6X_Init APIW61 Init failedFailed to initialize ST67W6X Driver, 2This happens on every boot, identically, every time — not intermittent. Expected magic is 0x55AA; I consistently receive 0x5501 (high byte correct, low byte wrong).2. What I've verified so farTo isolate whether this is a wiring issue or a missing-firmware issue, I connected a USB-to-UART (Silicon Labs CP210x) adapter dir

Dear all, I have designed a custom board using the STM32H563ZIT6 as the host MCU and the ST67W611M1 as the NCP. As part of the initial bring-up, I am attempting to flash the ST67W611M1 using the QConn_Flash_Cmd-ubuntu tool in standalone mode. For this, I have connected a USB-to-TTL converter directly to the NCP UART interface. The BOOT and CHIP_EN pins of the ST67 are controlled by the host MCU, which toggles them in the required sequence to place the NCP into UART (flash) mode (see below code). I use the same sequence given in the NCP_Loader Example. if (flash) { LL_GPIO_SetOutputPin(BOOT_GPIO_Port, BOOT_Pin); } else { LL_GPIO_ResetOutputPin(BOOT_GPIO_Port, BOOT_Pin); } /* RESET NCP CHIP */ LL_GPIO_ResetOutputPin(CHIP_EN_GPIO_Port, CHIP_EN_Pin); HAL_Delay(100); LL_GPIO_SetOutputPin(CHIP_EN_GPIO_Port, CHIP_EN_Pin); if (flash) { /* CLEAR BOOT */ HAL_Delay(100); LL_GPIO_ResetOutputPin(BOOT_GPIO_Port, BOOT_Pin); } I verified the BOOT and CHIP_EN signals on an oscillosco

Hi I want to update firmware on my X-NUCLEO-67W61M1 board. I'm talking directly to the board using QconnFlash tool.I have pulled BOOT and ENABLE pins high as described in manual. Looks like communication is established, but later it fails on receiving the ack. Any idea while it fails?Log is here: F:\Projects\ST67W6X_Utilities\Binaries>QConn_Flash\QConn_Flash_Cmd.exe --port COM18 --config NCP_Binaries\mission_t01_flash_prog_cfg.ini --efuse=NCP_Binaries\efusedata.bin[23:06:09.042] - Serial port is COM18[23:06:09.042] - ==================================================[23:06:09.058] - FW get address from partiton file F:\Projects\ST67W6X_Utilities\Binaries\NCP_Binaries\./partition.bin[23:06:09.060] - Address=0x10000[23:06:09.060] - FW get size from partiton file F:\Projects\ST67W6X_Utilities\Binaries\NCP_Binaries\./partition.bin[23:06:09.062] - Size=1785856[23:06:09.069] - Program Start[23:06:09.069] - ========= eflash loader cmd arguments =========[23:06:09.097] - seri

Continued from: STM32 Host with ST67W611 Wifi BLEHi everyone, Currently, I'm trying to re-flash firmware for ST67W61 module via UART without host ( use USB TTL), and I got the issue in below:[22:36:53.388] - Serial port is COM5 [22:36:53.394] - ================================================== [22:36:53.394] - FW get address from partiton file C:\Users\Admin\STM32Cube\Repository\Packs\STMicroelectronics\X-CUBE-ST67W61\1.2.0\Projects\ST67W6X_Scripts\Binaries\NCP_Binaries\./partition.bin [22:36:53.394] - Address=0x10000 [22:36:53.394] - FW get size from partiton file C:\Users\Admin\STM32Cube\Repository\Packs\STMicroelectronics\X-CUBE-ST67W61\1.2.0\Projects\ST67W6X_Scripts\Binaries\NCP_Binaries\./partition.bin [22:36:53.394] - Size=1785856 [22:36:53.397] - Program Start [22:36:53.397] - ========= eflash loader cmd arguments ========= [22:36:53.397] - serial port is COM5 [22:36:53.397] - cpu_reset=False [22:36:53.677] - com speed: 2000000 [22:36:53.677] - ========= Interface is

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)

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

This account only shares restored community content posted by members between May 22 and June 9, 2026, who did not register for the new community.We are designing a 6-layer PCB with limited board area. The layer stackup is as follows: TOP / GND2 / SIGNAL / POWER / GND5 / BOTTOM.Due to space constraints, we are planning to place one STPM33 on the TOP side of the board, and another STPM33 rotated 90 degrees directly on the opposite BOTTOM side. Similarly, one STPM34 will be placed on the TOP side, with another STPM34 rotated 90 degrees directly beneath it on the BOTTOM side.In summary, the board will carry a total of four ICs: one STPM33 and one STPM34 on the TOP side, and one STPM33 and one STPM34 on the BOTTOM side, with each TOP-side IC having its counterpart placed directly behind it on the BOTTOM side.Please find attached a diagram illustrating the top/bottom placement of the STPM34. Key points of this layout are as follows:The power supply pin traces on the TOP and BOTTOM sides are

Hello,Im using the RHFLVDS31A  and I have some unused I/O pins. Should I terminate them or should I leave them floating? I saw that there is an internal pull up for Cold Sparing so I didn’t want to impact that.

I am trying to test the target-wake-time (TWT) feature of the ST67 using the CLI firmware. I have attempted to setup a TWT connection on two different routers but both times the ST67 reports “Could not setup TWT” in response to my wifi_twt_setup command. The routers I have tried are the TP-Link AX5400 (Archer AX73) and the EERO Max 7. Here is an example command sequence:w61/>Connected to following Access Point :[8c:dd:0b:e5:ff:c8] Channel: 6 | RSSI: -42 | SSID: EEROStation got a new IP address : 192.168.4.36w61/>powersave 1w61/>wifi_twt_setup 1 1 13 128 1000Could not setup TWTw61/>wifi_twt_statusTWT not supportedw61/>

I’m using BALF-SPI2-02D3 with the S2-LP at 433 MHz and have a question about Figure 13 in the datasheet.The recommended PCB stackup shows:Top plane: 35 µm + 31 µmMid layer: 31 µmBottom plane: 35 µm + 31 µmWhat exactly does “35 µm + 31 µm” mean for the outer layers?Is this:base copper + plated copper,finished copper thickness in ST’s stackup notation,or something else?I’m trying to choose a 1.0 mm, 4-layer PCB stackup from a commercial manufacturer and would like to match the recommendation as closely as possible.Thanks for any clarification.

Hi , I recently acquired an ST4SIM-300M eSIM and I am unsure how the ST4SIM-300M should be activated initially.I also watched your video about Remote SIM Provisioning using the Motive eSIM Secure Connect portal, and I would like to ask whether the activation and profile download for this SIM should be done through that portal.Additionally, I would like to understand whether the SIM already contains a bootstrap profile by default. If so, how can I verify this from the device?Finally, I would appreciate it if you could share a list of your eIM partners that support the ST4SIM-300M for testing purposes

ECMF02-2AMX6 has only one pin for the GND connection, which is unusual.Where should this pin3 (GND) be connected to? the connector GND or the system GND? I have common mode choke between the connector GND and the System GND.  Based on the dot notation on the common mode choke, I assumed pin 5 and pin6 should be connected to the connector side so pin3 should be connected to the system GND?

Do we have an evaluation board and documentation package on place to get samples and test ?Does it developed with 3D  AOA and Phase difference of arrival. How does it UWB road map leverage narrow band assistance or BLE co-processing? 

Hey, I'm using the ST67W611M (NCP + STM32f7 host, X-CUBE-ST67W61, T01 firmware v2.0.97) in WiFi station mode, with TLS running on the NCP via W6X_Net_Socket(..., IPPROTO_TLS_1_2). I'm trying to download a 750 KB file over HTTPS from a server that sits behind Cloudflare, and it reliably dies after about 200 KB - W6X_Net_Recv returns -1 ("ssl_read FAILED: -0x0001") and the socket goes DISCONNECTED. Same spot every time. So I took a packet capture to see what's actually happening (TLS 1.2, AES-128-GCM). Cloudflare uses dynamic record sizing, so its TLS record size grows over the connection: 1369 -> 4229 -> 16384 bytes. Everything up to the 4229-byte records comes through fine (~200 KB). But the moment the first full 16384-byte record arrives, the device immediately sends a fatal TLS alert and RSTs the connection - the abort clearly comes from the device, not from Cloudflare.That made me suspect the NCP's TLS record buffer is simply too small to hold a full 16 KB record. Looking at t

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,

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! 

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

Hello everyone,I'm trying to establish communication between an IO-Link master and an IO-Link device, but I'm very new to this field and I'm having a lot of difficulty getting the communication done.I'm using a STEVAL-IOM001V1 with the L6360 transceiver. I generate an 80 µs wake-up pulse on the bus using a timer in alternate function with the USART. Then, through my state machine, I'm able to send a Type_0 message with MC = 0xA2 and the corresponding checksum at different transmission rates, while keeping the Tdmt timing between consecutive messages within the required range of 27–37 Tbit.Using an oscilloscope, I can see that the wake-up sequence (Twup + Tren) and the messages are correctly generated and transmitted to the device. However, in most cases, the device does not respond.As the IO-Link device, I'm using an X-NUCLEO-IOD02A1 with the L6364Q transceiver and the ST example software with the MiniStack.Has anyone experienced a similar issue or have any suggestions on what I might

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 ?