Interface and connectivity ICs

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.

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 oscilloscope, a

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

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

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.

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? 

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.

The "S2-LP bring-up good practices v1.0.pdf" [1] document states the following information regarding AFC:"AFC_CORR is 2-complement byte (signed). Granularity is 508Hz for 50MHz Xtal"The mentioned step size of 508 Hz for a 50 MHz oscillator also corresponds to my practical observations.The following information can be found in the datasheet:[..]Fdig/(3*(2^13)) where Fdig is the frequency of the digital block (24, 25 o 26 MHz).1 LSB is:At 24 MHz: 976.5625 HzAt 25 MHz: 1017.25260416 HzAt 26 MHz: 1057.9427083 Hz[..]Since Fdig corresponds to 25MHz for a 50MHz oscillator, the AFC_CORR step size would therefore be 1017Hz.This doesn't match the actual results or the information in the mentioned PDF.What is the correct formula to calculate the step size for all oscillator frequencies?Thanks~Matthias[1] https://community.st.com/t5/interface-and-connectivity-ics/frequently-asked-questions-on-st-s2-lp-sub-1ghz-transceiver/m-p/736882/thread-id/11431?attachment-id=28318 

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'm trying to use a Soracom SIM to experiment with the ST87M01 on the plan01s. Its not clear how to set the APN using the ST87M01. I tried AT+CGDCONT=1,"IPV4V6","soracom.io", but kept getting an +CME ERROR: 4.Any advice?  

Hi,1. can we interface directly ST4SIM-200S with LTE modem? 2. how we will integrate service provider like airtel/jio please share me any readable document that how it works with cellular network. 

I connected the evkitst87m01-2 to the Nucleo64u5. registered and installed the provided sim, and loaded the wifi location demo app. I connected up 2 usb serial ports so i can see the conversation between the U5 and the ST87, and that is below. note that the xxxxx.net is just a placeholder for the real apn, as im not sure if that is specific to me or not. So the code just runs and never registers on the network. Im in the US if that matters. #REBOOT_RESET #SIMST: 1 AT#NVMRD=5,12,1 #NVMRD: 08 OKATE0 +CEREG: 2,"","",,,,"","" OK OK AT+CMEE=1 AT+CEREG=5 OK AT+CSCON=1 OK AT#SLEEPIND=0x1F OK AT#WDGMODE=0 OK AT#TEMPLIMIT=-40,85,-45,110,0,1 OK AT#VBATLIMIT=2200,3000,2000,3200,1,0,0 OK AT+CFUN=0 +CEREG: 0,"","",,,,"","" OK AT+CGDCONT=1,"IPV4V6","xxxxx.net" OK AT#BANDSEL=20,8 OK AT#BANDCFG=0,0,20,01,7910 OK AT#BANDCFG=0,1,0,2,1,100,0 OK AT#BANDCFG=0,2,0,2,1,100,100 OK AT#BANDCFG=0,3,0,2,1,100,200 OK AT#SCAN=1,-104,1,360,1,360 OK AT+CEDRXS=1,5,1011 OK AT#PTW=0011 OK AT+CPSMS=1,,,"00

Hi,I am currently working on a feasibility project using the X-NUCLEO-67W61M1 and NUCLEO-U575ZI-Q.The sample code I am using is ST67W6X_FOTA.The FOTA functionality is working properly. However, during the initial connection phase, there is about a 50% chance of encountering Wi-Fi connection-related errors. The errors I have observed include:"Wi-Fi connect timeouted""Wi-Fi connect in error""Failed to initialize the DTIM"Whenever these issues occur, the only way to recover is by resetting the MCU and restarting the process.Are there any recommended methods or best practices to resolve these issues? 

The API documentation for the "AT+CIPSTART" command on the ST67W611M1 chip seems to be incomplete. It is missing the parameter lists for UDP and SSL types. https://wiki.st.com/stm32mcu/wiki/Connectivity:ST67W611M_AT_Command#AT-2BCIPSTART The rest of the API is documented on the ESP-AT page: https://docs.espressif.com/projects/esp-at/en/latest/esp32/AT_Command_Set/TCP-IP_AT_Commands.html#at-cipstart-establish-tcp-connection-udp-transmission-or-ssl-connection

Split from Question about ST eSIM solutions - which is solved.This is a new question.Hi!Can you please tell me how the activation process on the ST4SIM-300M chip works now?

Hi! We have two custom boards that we have soldered the ST4SIM-300M eSim to. We have earlier been using the ST4SIM-200M and followed this activiation procedure:https://www.st.com/resource/en/application_note/an5740-st4sim-with-truphone-connectivity--activation-procedure-stmicroelectronics.pdfto get them working with truphone.Now when i try to do the same thing with our new eSim i get the same ICCID from both, this is what i get:at AT%XICCID %XICCID: 89019990001234567893 When i try to enter it on truphones activation page it says that the device is not found.Am i doing something wrong or missing anything? 

Hi everyone,I’m hoping to get some clarity on an issue I’ve been running into while using this forum.When I try to create or interact with posts here, the page sometimes behaves unpredictably—like certain elements not loading properly or the submission process taking longer than expected. There have been a few times where I wasn’t even sure if my post went through or not, which makes it a bit frustrating to stay engaged.While trying to figure this out, I ended up checking something through a discord server, just to compare how things were functioning elsewhere, and it made me wonder if what I’m experiencing here could be related to browser compatibility, scripts not loading fully, or even temporary platform-side issues.I’ve already tried basic fixes like refreshing, switching browsers, and clearing cache, but the issue still pops up occasionally. Has anyone else noticed similar behavior when posting or browsing? Or is there something specific I might be overlooking in terms of setup or

Hi,1. [Part Number] STM32H7R7I8T6 2. [Environment] x-cube-st67 1.2 version and latest cube IDE.3. [Schematics] If it is a custom board --> Share the schematics using “Attach file” option or inserting some image.4. [Details] I am using STM32H7R7I8T6 MCU and integrate the x-cube-st67 related codes.But i am facing this error: sem_if_ready not received.xReturned = xSemaphoreTake( mdm->sem_if_ready, pdMS_TO_TICKS(time_ms) ); if (xReturned != pdPASS) { SYS_LOG_ERROR("sem_if_ready not received\n"); return W61_STATUS_ERROR; } i compared the h7r3 example included ioc file, no idea what's difference.Meanwhile, I also update the ST67 firmware by this command:.\QConn_Flash\QConn_Flash_Cmd.exe --port COM11 --config .\NCP_Binaries\mission_t01_flash_prog_cfg_v2.0.89.ini --efuse .\NCP_Binaries\efusedata.binBut still got the issue. The CS pin, RDY PIN, EN pin are all Hi. boot pin is low.SPI CLK no output. Any ideas? codes  is in attached.5.&n

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

The function of the PERS_RX flag in PROTOCOL 0 is described as: '1: enable the persistent RX mode.' What does that actually mean/do? I couldn't see any explanations in the rev. 13 data sheet for the S2-LP. 

Hi, Here i post a driver for SSD1306 128X64 Oled Display. You must enable I2C configuration void I2C_ConfigurationMaster(void) { GPIO_InitType GPIO_InitStructure; I2C_InitType I2C_InitStruct; /* Enable I2C and GPIO clocks */ if ((I2C_Type*) SDK_EVAL_I2C== I2C2) { SysCtrl_PeripheralClockCmd(CLOCK_PERIPH_I2C2 | CLOCK_PERIPH_GPIO, ENABLE); } else { SysCtrl_PeripheralClockCmd(CLOCK_PERIPH_I2C1 | CLOCK_PERIPH_GPIO, ENABLE); } /* Configure I2C pins */ GPIO_InitStructure.GPIO_Pin = SDK_EVAL_I2C_CLK_PIN; GPIO_InitStructure.GPIO_Mode = SDK_EVAL_I2C_DATA_MODE; GPIO_InitStructure.GPIO_Pull = DISABLE; GPIO_InitStructure.GPIO_HighPwr = DISABLE; GPIO_Init(&GPIO_InitStructure); GPIO_InitStructure.GPIO_Pin = SDK_EVAL_I2C_DATA_PIN; GPIO_InitStructure.GPIO_Mode = SDK_EVAL_I2C_DATA_MODE; GPIO_Init(&GPIO_InitStructure); /* Configure I2C in master mode */ I2C_StructInit(&I2C_InitStruct); I2C_InitStruct.I2C_OperatingMode = I2C_OperatingMode_Master; I2C_

How is the best configuration for setting MTF as free-running timer ?void MFT_Configuration() { MFT_InitType timer_init; NVIC_InitType NVIC_InitStructure; SysCtrl_PeripheralClockCmd(CLOCK_PERIPH_MTFX1, ENABLE); /* Init MFT1 in mode 2 */ timer_init.MFT_Clock1 = MFT_PRESCALED_CLK; timer_init.MFT_Clock2 = MFT_NO_CLK; timer_init.MFT_Mode = MFT_MODE_2; timer_init.MFT_CRA = 0xFFFF; timer_init.MFT_CRB = 0xFFFF; /* If a square waveform is @ input with a frequency of 10kHz => T = 100 us * * with Prescaler = 16 - 1; => 1us sampling period * the counter number within a period is 100. * * with Prescaler = 1 - 1; => 62.5ns sampling period * the counter number within a period is 16000. More resolution. */ timer_init.MFT_Prescaler = 1-1; MFT_Init(MFT1, &timer_init); /* Set the TnCNT1 at the max value. No matter about the TnCNT2 since it is not used. */ MFT_SetCounter(MFT1, 0xFFFF, 0xFFFF); /* Enable MFT irq */ NVIC_InitStructure.NVIC_IRQChannel = MFT1A

Hello,I recently purchased the STEVAL-IDP004V2 board, and I'm encountering an issue when connecting it with the GUI V2 ST and the TE Concept IO-Link application. The same error repeatedly appears: "master application 6148 Appears and Disappears."Could anyone provide guidance on how to resolve this issue?Thank you in advance for your help.