Solved

Evaluating the STM32G081B-EVAL board, and I’m struggling to find the sizes of the two DC barrel jacks on the board and UCPD daughter board (5V CN16 and 19V CN3). As I understand it, it would be sufficient to power CN3 and let that power the mainboard, but I can’t find either of these sizes.Checking the BOM shows CN3 as Qiaod DC-094, but I can’t find any information about this either.Does anyone know what size of power supply barrel jack we will need for either (preferably CN3)?

I’m running into a ‘Heisenbug’ crash (just adding or moving a bit of general code between builds makes it either crash or work), and when it crashes, the STLINK-V3MINI can’t attach, or if already attached, it fails to halt the processor.Any tips or advice about catching it in the act or theories as to the cause?  

Hi Team,I am using the STM32C542RC on the STM32C5 Nucleo-64 board (MB2213),What is the max. supported baud rate for the USART baud rate?We have checked that, with STM32CubeMX, the DIV1 prescaler, and oversampling by 16, the maximum supported USART baud rate is 9 Mbit/s, assuming the peripheral clock is configured appropriately.However, in our setup, we are receiving garbage/corrupted data at 1.5 Mbit/s. Communication works correctly at 1 Mbit/s (TX and RX both working at this baud rate), but increasing the baud rate to 1.5 Mbit/s or higher in that case results in receiving garbage/invalid data. The STM32 receiver and the sender are configured with the same UART settings:Baud rate: 1.5 Mbit/sStop bits: 1 (also tested with 2)Parity: NoneWord length: 8 bitsHardware flow control: None Please check the above configuration and let us know how to achieve reliable data on the receiving end at a 1.5 Mbps or higher baud rate. If any additional configuration is required, then please let us know. 

Greetings,We have a new HW design based on the STM32H573ZI. We are using the USB port and have itgoing to a 4-pin micro-USB connector with VBUS, D-, D+, and GND. I would like to run an H5 Example application to verify that the HW is functional, something like the Ux_Device_HID example.However the Ux_Device_HID examples I see seem to only support USB-C with USBPD (Power Delivery). Are there any simple Device Only examples which natively support micro-USB, or USB-A? ThanksKen CarlsonDraeger Medical Systems 

Hello ST team.I am working on the boot chain from qspi NAND flash memory. The board is based on the STM32MP135F SOC and the w25n01gvzeig winbond 128MB IC. The IC is sitting on qspi bank 1 on the default BOOTROM pins (AN5474 p49).I have already succeeded the bootchain for EMMC and USB uboot successfully locates and flashes the nand with the partitions I have specified. But as set the boot pins to 111 I get 0 logs from the serial.By reading in the forum I suspect that the OTP should be programmed with the NAND layout configuration but I would like to be sure. Note the I have build tf-a with the STM32_SPI_NAND=1 on the extra flags and I get a boot log from NAND boot if i perform software reset from uboot usb.With softreset and tfa hardcoded the otp value for nand block nb[7:0]:STM32MP> resetresetting ...▒NOTICE: CPU: STM32MP135F Rev.YNOTICE: Model: STMicroelectronics custom STM32CubeMX board - openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11INFO: Reset reason (0x74):INFO: System

CubeMX allows the user to change the Preemtion Priority of the “System service call via SWI instruction” / SVCall_IRQn.When its not at the default value of 0, CubeMX generates this HAL_NVIC_SetPriority(SVCall_IRQn, X, X); inside HAL_MspInit(). When USE_FULL_ASSERT is enabled this function call triggers an assert. Namely assert_param(IS_NVIC_PRIO_INTERRUPT(IRQn)) where IRQn is SVCall_IRQn and IS_NVIC_PRIO_INTERRUPT(X) checks if IRQn is != to SVCall_IRQn.I noticed this on a STMU385, using CubeMX version 6.18.1Best Regards, Cecil

Hi. I built the PCB myself at home. While working, I noticed strange anomalies in the image. The anomalies are in different places and on different photos. I asked AI but didn't get a satisfactory answer. I tried reducing the frequency without any positive effect. I suspect ESD or power supply issues. The traces are very thin, 0.4 mm for power and 0.35 mm for data. Has anyone experienced this? 

The GT911 configuration (as far as I know registers 0x8047 - 0x8100, but maybe there is more?) on my module got overwritten by my experiments, and touch now has large dead zones, where no touch is registered at all. The driver/sensor channel map is specific to this panel and isn’t in any BSP, so I have no factory copy to restore from, and I also don’t have a 2nd board.Could anyone with a working DK dump their GT911 config and paste the values? (Or does ST have the default config for this module, I sadly couldn’t find it anywhere?) From my understanding it should be as simple as: uint8_t reg[2] = {0x80, 0x47};uint8_t cfg[186];i2c_write(0x5D, reg, 2);i2c_read (0x5D, cfg, 186);  

I’m trying to build the LED example for the P-NUCLEO-WB55.USBDongle.I have included all the necessary include & source paths yet when I try to build it exits with the following, This file does actual exist though,  and its location is in the paths list, What am I missing here?

I hope you are doing well.We are currently working on a Driver Monitoring System (DMS) project at Rapidise Technologies Pvt. Ltd.Could you please let us know if STMicroelectronics has any DMS reference design, application board, or evaluation board based on an STM32 microcontroller?If available, could you kindly share the following:Schematic files PCB/Board design files Bill of Materials (BOM) Hardware design documentation Design guidelines Reference software or demo projects (if available)These reference materials will help us evaluate the platform and accelerate our hardware development.

i started working on the B-G431B-ESC1 board with a 2836 motor but it would not start. so i started looking at the setup and tried different configurations but no luck. the profiler would not run the motor either. after i disconnect the motor and removed the bus voltage, the Iq in the motor pilot still shows significant numbers.. i wonder if this is a sign of damaged board?   

Hi ,We observed the timing details for each state during card detection. These measurements were captured while running the demo cycle continuously in a while loop for card detection on bare metal. We are using the NFC Reader stack on an AUTOSAR platform and executing the NFC task every 1 ms. During testing with NFC-A and Proprietary technologies, we observed that the card detection and validation process takes approximately 300 ms.Could you help us understand how these timing values are expected to be observed and interpreted?We observed that the PollTechDetectCnt reached 1162 during testing. Could you please confirm the expected number of iterations for each state in the polling and card detection sequence? Initialization for discovery parameters -   discParam.compMode = RFAL_COMPLIANCE_MODE_NFC;  discParam.devLimit = 1U;  discParam.nfcfBR = RFAL_BR_212;  discParam.maxBR = RFAL_BR_KEEP;  discParam.p2pNfcaPrio = false;  discParam.wakeupEnabled = false;  discParam.wakeupConfigDefault =

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

Hello everyone,I am experiencing an issue with MotorPilot on a new laptop.Problem descriptionWhen I start MotorPilot, the application window opens but:I can only see a black screen whit a white arrow the content is flickering no GUI elements are visible or usableThe issue only affects the application window, not the whole system.System informationOS: Windows 11 Laptop: New system (Intel Core Ultra 7 255HX + RTX PRO 2000)Additional observationsThe program seems to be running, but the UI is not rendered correctly This looks like a graphics / rendering compatibility issue Problem occurs only on the new laptop (older systems worked fine)What I already triedRunning as Administrator Disabling fullscreen optimizations(no improvement so far)Has anyone experienced the same issue with MotorPilot?Is there a known workaround? Can hardware acceleration be disabled? Are there recommended settings for modern GPUs?Any help would be appreciated.Thanks!  

Hello Team, I am using STM32N6, Now i have initialised STM32N6’s XSPI1,XSPI2 at 1.8v (set VDDIO-2,VDDIO-3 = 1.8V), VDD=3.3V, If I use GPIOs from the XSPI1 and XSPI2 pins, will those GPIOs have a high value (1) in the range of 1.8v or 3.3v? Thank you

In RM0366 Reference Manual GPIO section it says that there is a BRR register at offset 0x28 but in the GPIO register map its not shown. I assume this is a mistake but I want to know if STM32F301C8 has a BRR register. 

Hello!I a new in this.I have two sets of DA files: for password access and for access via certificate.I've tried to flash a NS-firmware, provision a password.obk, then change Product state to Provisioned/closed. Thas was successful. I can perform a regression from this state.But i also tried to open a debug session. Without success. CubeProgrammer says, that I am able to make full regression only, while Cube IDE asks for certificate DA.I know, that certificate auth method is valid with TZEN=1 only, but I tried to provision that obk with TZEN=0.As a result, I Have this:The default ST password from CubeProgrammer's folder is not working,I tried to provide all-zeros and all-FF password without success.But maybe I need to change something in the header. Or change a password length.So, 3 questions:1. Is this device totally bricked, or I can some-how calculate a password.bin2. How to perform debug in closed product state on STM32H563 if TZEN=0 ?3. How to perform debug of the the secured

I am having trouble generating an HSO based project.  I have already confirmed the board works with “Observer+PLL”.  When switching to HSO I am able to select it in the drop down, at which point it:1. Resets my current sense gain (should be 50), I have no issues replacing this value.2.  Under Speed Sensing I am provided with an empty Current Scale box, which is a “required field” however upon entering a value it remains red and tells me I cannot enter a value, as “no value is allowed”. Is this a bug or have I configured something incorrectly?  It also seems odd that the current gain setting is cleared, although I can edit that without issue.  

Hello ST Community,I am working with STM32WB05 in a custom PCB (new design) and it does not run when power on the PCB. To run it, I have to reset by reset line. If I am debugging, I neither have problem.I had used others microcontroller before (STM32L1, STM32WL55...) and it had never happend. I have check the pollowing points:1-  Power supply. I am using a externa battery with 3-3,5Volts.2- BOOT pin: I think that the problem is the STM32WB05 enter in boot mode but in the datasheet, I can not see any pin to enter it.I have tried to join PA10 to GND by 10K resistor (I see in nucleo manual UM3343 that BOOT0 pin is PA10) but that no work.3-  Clock source: I am using interna clock HSE4- reset line is always high level Any confirmation or guidance would be greatly appreciated.Thank you for your support.

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

Hi,by chance I found the “RoT Provisioning Software Pack” (https://github.com/STMicroelectronics/stm32-util-rot-provisioning).Looks promising; are there already any examples using it? I’m currently in the process of adapting the H563ZI OEMiROT examples in some custom project. Kolja 

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 everyone,I am facing a bizarre issue with an STM32F407 running a custom PCB. I am trying to put the MCU into STOP mode (Low Power Regulator ON), but it seems to enter deep sleep for a fraction of a second (current drops to almost 0mA) and then immediately wakes up/resets, stabilizing at a constant 9.8mA.I am programming via DFU and using a custom bootloader that jumps to the main application at 0x08010000.Here is what I have already done in my "Deep Sleep Test" routine to isolate the issue: Hardware Isolation: All external peripherals (W25Q Flash, FRAM, LDOs) are completely disconnected or powered down. The 3.3V line is isolated. GPIOs: All GPIOs are set to GPIO_MODE_ANALOG, except for specific pull-up/pull-down pins strictly required by the hardware. USB PHY: I am explicitly disabling the internal USB transceiver using USB_OTG_FS->GCCFG |= USB_OTG_GCCFG_PWRDWN; and then disabling the clock. Interrupts & SysTick: I disable SysTick->CTRL = 0, clear SCB->ICSR, mask

Dear Team, We are currently working on a project based on the STM32N657X0H3Q MCU. As part of our design, we are planning to use a QSPI Flash and SDRAM instead of the OctoSPI Flash and HexaSPI PSRAM used in the reference designs. Could you please share any reference schematics, application notes, or design examples that demonstrate the integration of QSPI Flash and SDRAM with the STM32N657X0H3Q? Additionally, our design is highly space-constrained. If anyone has a reference for a minimal power supply/regulator design for the STM32N657X0H3Q, we would greatly appreciate it if you could share that as well. We look forward to your response and guidance. Thank you for your support. Best Regards, Ajnas C

  Hi Team   Am working on a custom hardware design using the STM32H745IIT6 microcontroller and interfacing it with an external SDRAM   IS42S83200J-7TLI.  Any available reference designs, including: Schematic diagrams PCB layout design files  Application notes or design guidelines specific to STM32H7 FMC/SDRAM interface If anyone has experience with a similar configuration or can share reference projects, evaluation boards, or design tipsespecially related to signal integrity, routing, or SDRAM timing configurationit would be very helpful. Regards, Sathiya