Interface and connectivity ICs

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

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,here is a post for wireless community (Sub-1Ghz solutions) to answer many frequently asked questions and good practices using ST S2-LP transceiver.please find attached document to get additional information on this perfect Radio chipset.ThanksPhilippe

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 an engineering student working on my senior graduation project using the STEVAL-WBC2TX50 evaluation board. I need the STSW-WBC2STUDIO (or the updated WPSTUDIO) GUI to configure the board, but all official links on the ST website return a 404 error.Could you please provide a working download link or the installer files? My project exhibition is approaching soon, and this is a critical blocker.Thank you for your support.

(official project, W61 firmware updated, full setup completed) **[BUG/HELP] X-CUBE-ST67W61 V1.2.0 — sem_if_ready not received on NUCLEO-N657X0-Q after complete setup**---**Hardware:**- NUCLEO-N657X0-Q (MB1940)- X-NUCLEO-67W61M1 (MB2230)- JP1 and JP2 closed, Arduino connectors fully seated**Software:**- STM32CubeIDE 1.16.x- X-CUBE-ST67W61 V1.2.0- X-CUBE-FREERTOS V1.4.0- STM32CubeProgrammer v2.22.0- Project: ST67W6X_Echo for NUCLEO-N657X0-Q (official, unmodified)---**Setup completed (all steps verified):**1. W61 firmware updated to st67w611m_mission_t01_v2.0.97 using QConn_Flash_Cmd via COM port — [All Success] with SHA256 match2. FSBL compiled from official project (0 errors, 0 warnings), signed with STM32_SigningTool_CLI --align (v2.22.0), flashed to 0x70000000 and verified successfully3. OTP word 124 programmed to 0x00018000 (HSLV_VDDIO2 + HSLV_VDDIO3)4. Boot switches in flash boot mode (BOOT0: 1-2, BOOT1: 1-2)5. eraTerm on STLink VCP, 921600 baud---**Terminal output (always the

Dear all,is it possible to measure the frequency of the 32,768kHz oscillator (external crystal used) at a buffered pin similar to the MOC pin of the STM32 to tune the frequency by the external capacitors? It would be difficult to do this at pin XTAL32k_IN/OUT without influencing the oscillator frequency.Best regards,Peter

Good afternoon,First post here, so aologies for any ignorance.I am trying to combine the subghz radio feature of WL55JC1 and the ST60 high frequency communication Full Duplex UART bridge.Ideally, I would be switching between these two functions.I have ported the ST60 example to the WL55JC1 dev board, and can get both running independently.But my problems arise because the subghz radio example uses the STM32 Sequencer utility, while the ST60 doesn't.When I try to integrate the sequencer into the ST60 code, it seems like the I2C comm/config channel for ST60 stops working.Does anyone have any guidance/direction in this area?Appreciate your time.

Hi, hope you doing good,In our design, we are using the ST60A3H1C1CCEPY3 controller. please clarify if there are any layout restriction or keep-out zones around the controller where other peripherals should not be placed.Thanks,

Hello Team, Hope you are well! Could you confirm if the following top marking on ST4SI1M0008SCIFW is correct? 8942310525 000000923 FN527 Many thanks! Robert

Split from  ST87M01 : MAX length of the data returned by AT#IPREAD - which is solved.This is, indeed, a new question.Hello Didier,I have an additional question on this topic (I don't know if I should create a new post, but this question is very much linked to the previous one...) :- From the ST87MXX AT Command User Manual §9.8 AT#IPSENDUDP, the max IP frame size is 1400 bytes- But from ST87MXX TCP/UDP-IP Application Note §3.2 IP default parameters command, the max IP frame size is 1600 bytes,Is there a mistake in one of these documents, or is there something that I didn't understand ?Best regardsThierry

Dear ST team,In the ST87MXX AT Command User Manual, I can find that I can retrieve the data received on a socket withAT#IPREAD:AT#IPREAD=<context_id>,<socket_id>#IPREAD: <context_id>,<socket_id>,<data_length><data>OKBut I cannot find the max length of the <data> field that can be returned by the modem. Where could I find this information ?Best RegardsThierry

I am using STM32H723ZGT6 as the host MCU with the ST67W611M1 Wi-Fi + BLE module. Software details: Firmware flashed on ST67: T01 binary STM32 firmware package: X-CUBE-ST67W61(1.1.0) Application selected: BLE P2P Enabled parameters: Wi-Fi SAP: Yes Wi-Fi STA: Yes BLE: Yes NET: Yes DHCP: STA+SAP Issues observed: Intermittent failure after reset in debug mode When I reset the board while running in debug mode, the system sometimes does not work correctly(w6x init failed or other intiliazation failed in mainapp.c). The behavior is inconsistent—occasionally it works, but often it fails after reset.   Wi-Fi SoftAP start failure The following API fails: ret = W6X_WiFi_StartAp(&ap_config); While debugging, the failure occurs due to a timeout in the following function: /* Initialize the dual interface mode */ ret = TranslateErrorStatus(W61_WiFi_SetDualMode(p_DrvObj)); SPI clock configuration doubt Could you please confirm the recommended SPI clock frequency for STM32H723ZGT6 when interf

Hi ST community,I am using STM32H723ZGT6 as the host MCU with the ST67W611M1 Wi-Fi + BLE module.Software details:Firmware flashed on ST67: T01 binarySTM32 firmware package: X-CUBE-ST67W61(1.1.0)Application selected: BLE P2PEnabled parameters:Wi-Fi SAP: YesWi-Fi STA: YesBLE: YesNET: YesDHCP: STA+SAPIssues observed:Intermittent failure after reset in debug modeWhen I reset the board while running in debug mode, the system sometimes does not work correctly(w6x init failed or other intiliazation failed in mainapp.c). The behavior is inconsistent—occasionally it works, but often it fails after reset.Wi-Fi SoftAP start failureThe following API fails:ret = W6X_WiFi_StartAp(&ap_config);While debugging, the failure occurs due to a timeout in the following function:/* Initialize the dual interface mode */ret = TranslateErrorStatus(W61_WiFi_SetDualMode(p_DrvObj));SPI clock configuration doubtCould you please confirm the recommended SPI clock frequency for STM32H723ZGT6 when interfacing with S

Hello, I am working with the ST67W61 WiFi module and NCP firmware provided in X-CUBE-ST67W61. The firmware flashing process works correctly when using the reference setup: NUCLEO-U575ZI-Q X-NUCLEO-67W61M1 expansion board However, the same flashing procedure fails on our custom board, which is designed based on the X-NUCLEO-67W61M1 schematics. Issue observed:During NCP flashing over UART, the process fails at handshake stage with the following error: "ack is b''" "CHIP IMG LOAD SHAKEHAND FAIL" Observations: UART communication appears inactive (no response from module) Same firmware and flashing tool used Same COM port configuration verified Power supply is stable (3.3V confirmed) Issue is reproducible consistently on custom board Connections replicated from reference design: CN6: 3V3, 5V, GND CN5: SPI (CLK, MOSI, MISO, CS) CN9: BOOT, CHIP_EN, SPI_RDY, UART TX/RX Suspected area:We suspect the issue may be related to: BOOT pin configuration during reset CHIP_EN / RESET sequencing

Hello, as in the title I'm facing issues with high intensity BLE transfers (~4 writes and 4 reads and indicates per second) on X-NUCLEO-ST67W71 paired with STM32N6570-DK.Randomly during the transfer I'm encountering this error which simply breakes the communication with ST67:ST67 Log: [ERROR] [1055938] [spi_xfer_engine] (spi_iface.c:448) waiting for spi txn ready timeouted ST67 Log: [ERROR] [1057938] [spi_xfer_engine] (spi_iface.c:448) waiting for spi txn ready timeouted ST67 Log: Timeout waiting for tx ST67 Log: [WARN] [1058941] [ST67Task] (st67_app.c:1138) Set read data error! ST67 Log: [ERROR] [1059938] [spi_xfer_engine] (spi_iface.c:448) waiting for spi txn ready timeouted ST67 Log: [ERROR] [1061938] [spi_xfer_engine] (spi_iface.c:448) waiting for spi txn ready timeouted ST67 Log: [ERROR] [1063938] [spi_xfer_engine] (spi_iface.c:448) waiting for spi txn ready timeouted ST67 Log: Timeout waiting for tx ST67 Log: [WARN] [1063951] [ST67Task] (st67_app.c:1143) Data indication error! ST

Hi, For STM32H753IITx + ST67W611M1 on a custom board with FreeRTOS: What is the recommended integration approach for X-CUBE-ST67W61 on STM32H753? Specifically: Is STM32H753 officially supported/recommended as a host MCU for ST67W611M1? For H753, is it recommended to use the middleware directly from CubeMX? Are there known FreeRTOS version compatibility issues between CubeMX-generated FreeRTOS and X-CUBE-ST67W61 on H753? Thank you.

I am porting the ST67W611M1 WiFi/BLE driver (X-CUBE-ST67W61 v1.2.0) from a NUCLEO-U575ZI-Q to a custom PCB with STM32F767VIT6. The Nucleo version works perfectly. On the F767 custom board, W6X_Init() hangs indefinitely.HARDWARE- Host MCU: STM32F767VIT6 (216MHz, Cortex-M7)- WiFi module: ST67W611M1 (NCP firmware: mission_t01_v2.0.97.bin — confirmed flashed and verified)- SPI2: PB12=NSS(SW), PB13=SCK, PB14=MISO, PB15=MOSI- CHIP_EN: PD4, SPI_RDY: PD7 (EXTI rising+falling, NVIC enabled)- DMA1 Stream3 (RX, CH0), Stream4 (TX, CH0)- FreeRTOS heap: 102400, configMAX_PRIORITIES: 56- LOW_POWER_MODE: disabled, W6X_CLOCK_MODE: 1 (internal RC)SYMPTOMSPuTTY output stops at:W6X_Init...[hangs forever]W6X_Init() never returns. The FreeRTOS task blocks on sem_if_ready permanently.DEBUG FINDINGSI added debug prints to spi_port_transfer_dma() to log RX buffer contents. Here is what the module sends during init:RX[0]=0D [1]=0A [2]=72 len=12 → "\r\nr..." (boot message start)RX[0]=AA [1]=55 [2]=00 len=12 → SP

I am working on a project that uses the ST67W611 for cloud connectivity, but I am experiencing some issues when trying to connect to AWS IoT Core.Note: The NCP is already flashed with the T01 binary. The AWS endpoint is correct — for the sake of this question, let’s assume it is:xxxxxx-something.amazonaws.com. What Works Broker: test.mosquitto.org I am able to publish data to the broker and receive data from it when using test.mosquitto.org. However, I am now trying to get it working so that our custom device can connect to AWS IoT Core. MQTT Configuration (This is my current MQTT configuration.)   #define MQTT_BROKER "xxxxxxxxxxxxxxxxxxus-west-1.amazonaws.com" #define MQTT_PORT 8883 #define MQTT_CLIENT_ID "Thing01" #define MQTT_USE_TLS 4 #define MQTT_KEEPALIVE_S 60 static const char s_aws_ca_cert[] = "-----BEGIN CERTIFICATE-----\r\n" "Conten........\r\n" "Conten........\r\n" ..... "-----END CERTIFICATE-----\r\n" static const char s_aws_client_cert[] = "-----BEGIN CERTI

Hi,while integrating the module, we noticed that UDP client connections appear to be explicitly blocked in the driver (w61_at_net.c) for mission_t01 firmware (LwIP offload). The following code only allows TCP and SSL connections:if ((conn->Protocol != W61_NET_TCP_CONNECTION) && (conn->Protocol != W61_NET_TCP_SSL_CONNECTION) #if (W61_NET_IPV6_ENABLE == 1) && (conn->Protocol != W61_NET_TCPV6_CONNECTION) && (conn->Protocol != W61_NET_TCPV6_SSL_CONNECTION) #endif /* W61_NET_IPV6_ENABLE */ ) { NET_LOG_ERROR("Only TCP and SSL protocols are supported for client connections\n"); return W61_STATUS_ERROR; }However, according to the official AT command documentation, UDP client connections are supported:https://applist67.github.io/Web_AT_Documentation_ST67/v2.0.106/index.html#establish-udp-connectionAfter commenting out this restriction, I was able to establish a UDP client connection successfully, and communication seems to work.Is there a specific reason why

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 all,In order to have two possible functionalities on the same M12 plug I need to multiplex the C/Q line of IO Link with an analog input signal. The device is configured before the connection is established and it should stay in that mode during the whole operation. Here is the basic idea:My first Idea is to use a latching relays. Do you think it could cause problems to take the IO Link signal over the relays? I have never before used a relays in a signal path (digital or analog) and I am not sure if it could cause trouble. My second idea was to just connect both signals together without an additional switch or something like that:But I couldn't find out, if the OUT and I/Q Pins can handle a voltage when there is no 24V supply at VCC. (24V is only present when there is an IO Link Master connected to the plug). The analog signal can be 4-20mA, 0-10V or PWM (24V). Could the L6362A handle this? Also would this maybe impair the accuracy of the analog signal measurement? I also have

We have successfully tested the  ST67W6X Network Driver CLI example on a NUCLEO-U575ZI-Q with X-NUCLEO-67W61M1 development boards.We would like to port the example to an STM32F746.However, this is not simple due to the tight timing constraints required by the ST67W6x - e.g. the examples utilise the advanced SPI DMA available in the STM32U5xx family.Searching the internet shows other developers noticing dropped data on other processors. There are also reports that the following requirements must be met:Respond within ~30us of SPI_RDY going highNo breaks of more than ~2-3us in the DMA while streaming the SPI data.Do you have an example port for the STM32F746? Or at least on a processor with similar limited DMA capabilities?