Interface and connectivity ICs

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

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/>

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

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.

Recently, I started using the ST67W6 Wi-Fi module on a custom PCB with an STM32H723VET MCU to implement the HTTP Server application provided by ST.The application requires D-Cache to be enabled in order to operate correctly. However, as soon as I enable the D-Cache, my other peripherals that rely on DMA transfers, such as SDMMC and ADC, stop working correctly or fail completely. When I disable the D-Cache, all of these peripherals work normally again, but the HTTP Server application no longer functions, and I am unable to detect or connect to the Wi-Fi network.From what I have studied, I suspect that the issue is related to cache coherency between the CPU and DMA peripherals. My understanding is that I may need to configure the MPU to place DMA buffers in a non-cacheable memory region, or otherwise separate the memory used by the Wi-Fi module from the memory used by other DMA peripherals.However, I am still learning about MPU configuration, cache management, and memory mapping on STM32

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,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! 

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 ?

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?