Product forums

I have an stm32h7s78-dk and I created a GUI with TouchGFX.  I am trying to transmit some data via UART when a button is pressed.  I have the virtual function triggering in my MainDisplay and I was trying to use FreeRTOS and Queues to communicate from the virtual function from the button press to the uart task that I created via STMCubeMX.  For some reason though, the screen stays black when I try to use an if(xQueueReceive(queueHandle, &message, 0) == pdPASS) { printf("Message received"); }in my uart task. If I comment out this code then everything works fine and the GUI is visible.  I'm not sure what I'm doing wrong.  Here is my main.c/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2023 STMicroelectronics. * All rights rese

Hi,for a project involving a custom educational flight controller, I need to use the following hardware:- steval-FCU001V2 board- steval-drone02 drone kitFor clarity, here are st product page links that i used.Manual:https://www.st.com/resource/en/user_manual/um3117-how-to-build-your-own-minidrone-with-the-stevaldrone02-and-stevalfcu001v2-stmicroelectronics.pdfSteval-drone02 Drone kit companion:https://www.st.com/en/evaluation-tools/steval-drone02.htmlSteval-FCU001V2 FCU board:https://www.st.com/en/evaluation-tools/steval-fcu001v2.htmlMy main issues are as follows: I can’t get it to fly with the factory-loaded firmware, and I can’t even reload the firmware.I followed the UM3117 manual to assemble the kit and perform the initial tests. Compared to the materials and manuals available for version V1 of the drone kit and the Steval FCU001V1, this one seems less comprehensive, and in some images the connections aren’t very clear.When I connected the motors according to the manual, I found th

Could you provide a routine for reading and writing external flash using spi+dma+ interrupt in the STM32F407 standard library?

(HAL_SPI_Transmit_DMA works partially, HAL_DMA_Start_IT not working)I’m working with an STM32U5 MCU using SPI3 with GPDMA to drive an ILI9341 display. I’m trying to transmit a larger buffer (~23040 bytes), but display only receives about 1024 bytes, and goes into HAL_SPI_STATE_BUSY_TX forever.Function used: HAL_SPI_Transmit_DMA()Configs:  Thanks in advance !

My FMC clock, set to continuously generated, only cycles during a bus transaction.On my STM32N657I0H3Q, I have the following setup:FMC enabled in applicationChip Select NE1Muxed PSRAMData/Address: 16 bitsClock: Burst Read WriteAddressValid: YesWait: SynchronousThen, in the configuration, I have "CLK generated continuously" set. I have confirmed all of these settings in the resulting fmc.c code. I've also verified at runtime that hsram1.Instance->BTCR[FMC_NORSRAM_BANK1] = 0x183997(Where 1<<20 -- 0x1000000 is continuous clock generation).Meanwhile, my oscilloscope shows the FMC_CLK waveform:Clearly not continuous! 

 Dear all,I am struggling with getting a good SFLP result, that does not drift too much and does not appear jittery. I went trough most of the posts here but I am still not able to get good results (approx. factor 10 higher drift then according to the data sheet). in one of the posts I found the explanation about the chain of the SPFL:  that was the one im ent: For now, you have the answers: SFLP (as MLC/FSM and other embedded functions) take its input from LPF1 in the accelerometer chain, and from LPF2 in the gyroscope chain; their setting will therefore impact SFLP. Higher ODR leads to a more accurate gyroscope integration, but sensor RMS noise will also be higher. Gyroscope saturation should be avoided, accelerometer saturation matters less. Lower full scale will increase the resolution and therefore the accuracy, but the risk of saturation will be higher. It is a delicate balance that is specific to every application. Post in forum According to th

seriously i just want to design my product around an mp2. literally any. i cant pick one because none of them are in stock.im clicking every single mp2 variant that exists. then im picking the sub variant, and then the package. like 3 trees deep. not a single one ive found so far is in stock. these have been out for like years now. how am i supposed to use this chip in my product if it's availability is near non existent?really bad look for st here. 

When a USART is configured without a clock, the code generator treats it as a UART and assigns HAL_UART_IRQHandler as the interrupt handler. However, within this handler, there is a blocking operation during the idle process:(void)HAL_DMA_Abort(huart->hdmarx);When certain error conditions occur, the code can become stuck in HAL_GetTick(). This happens because the SysTick priority is lower than that of the UART interrupt. I have observed this behavior multiple times, particularly when noise is present on the UART signal line.Has Anyone seen this situation before?

Hello,I have two Winbond W956D8MBYA (64Mb, x8) HyperRAM chips connectedto XSPI1 on STM32H7S3 in dual memory mode (DMM=1):- Chip #0 → IO[7:0] + DQS0- Chip #1 → IO[15:8] + DQS1- Shared: CLK, NCLK, NCSI need to run at 200 MHz, so I need to configure CR0 on both chips:- Initial latency = 7 cycles (default is 6, valid only up to 166 MHz)- Fixed latency (required for dual mode per RM0477)Problem:According to RM0477, in HyperBus 16-bit dual mode:1. Variable latency is not supported (LM bit in XSPI_HLCR must be set)2. Register space access uses only IO[7:0]. Quote from RM0477:"IO8 to IO15 being not used but driven by the controller"So I can only access registers of chip #0.I also tried MSEL bit in XSPI_CR to switch to IO[15:8] in single memHyperBus mode - no effect.Questions:1. How to write CR0 to chip #1 connected to IO[15:8]?2. Is there any way to initialize each chip separately beforeswitching to dual mode?3. Does the controller duplicate data on IO[15:8] during registerwrite in dual mode?M

When I click this button, my mouse keeps spinning but the program does not open, and there is no error message. I tried using Refresh Data, but it had no effect.

Hello ST Community!I've been trying to recreate the DCMIPP_ContinuousMode example with STM32CubeIDE, but have been running into some issues with the IMX335_Probe function, the ID read by the I2C bus never matches the expected define IMX335_CHIP_ID. The original example runs completely fine in the STM32N6570-DK.- AXISRAM3 (0x34200000) is being used as the address for the DCMIPP CSI Pipe.- ISP Middleware does not return any errors in initialization.- All files regarding IMX335 registers and functions match with the original examples. Same for all the BSP drivers.- RIF has been configured for all peripherals involved.- AXISRAM3 has been enabled in the CubeMX configurations, and it's clock has also been enabled.static void IMX335_Probe(uint32_t Resolution, uint32_t PixelFormat) { IMX335_IO_t IOCtx; uint32_t id; /* Configure the camera driver */ IOCtx.Address = CAMERA_IMX335_ADDRESS; IOCtx.Init = BSP_I2C1_Init; IOCtx.DeInit = BSP_I2C1_DeInit; IOCtx.ReadReg = BSP_I2C1_ReadReg16; IOC

Recently, I encountered a tricky problem, I used STM32F405VGT6 this IC, but I found that it could not enter DFU mode normally, after repeated troubleshooting, I found that when the chip was USB probed, HSE was detected and did not vibrate, I also saw a similar article on the forum, I noticed that in the article, changing F405 to F429 can enter DFU mode normally.Further investigation, comparing the difference between the two ICs, it was found that the HSE start-up timeout time of the F405 IC was too short, and the HSE timeout time of the F405 was found from AN2606, and the version of the v3 version was 0.79ms, and the version of the v9 was relatively normal with 96msI want a timeout of 0.79ms, how do I do that? Is there any way to start HSE within 0.79ms of bootloder version v3? I hope the official can give an answer, thank you very much    

Hi, I can't read 40bit with my BlueNRG-1 and help wit timer in free-running. My us is ok but when i tried to read, it stop before read all 40 bits. Here i post my driver dht11. In main for test uint8_t h, t; if (DHT11_Read(&h, &t)) { printf("Humidité = %d %% Temp = %d C\n", h, t); } else { printf("Erreur DHT11\n"); } Thank

HelloAs I am trying to connect the STM32N6570-DK board on the STM32CubeProgrammer, initially the STM32CubeProgrammer recognises my device as in the following picture: When I press Connect on the STM32CubeProgrammer I get awarning: Connection to device 0x486 is lostas in the following picture: and then an error that says Data read failas in the following picture: I am using a MacBook Air M3, 2024, but even on windows (running on a virtual machine) I get the same error on the STM32CubeProgrammer windows version.Is there a way to overcome this issue? What could be the cause? Thank you 

Good day,We are using a composite USBX device class combining CDC and MSC over USB Full Speed, built on X_CUBE_AZRTOS-H7 version 3.3.0 (USBX 6.4). During testing we discovered that a certain Windows PC sends a MODE SELECT(10) command (opcode 0x55) and causes an endpoint stall.After a rather long debugging session, it was found that the USBX source _ux_device_class_storage_mode_select() is explicitly not implemented — it stalls the OUT endpoint, UX_FUNCTION_NOT_SUPPORTED (which is not checked in the thread) and never recovers:The MODE SELECT(6) SCSI command is not even implemented and the storage thread falls through to the default case, also triggering a endpoint stall. So:- Are there any plans to implement these MODE SELECT(6/10) commands properly in a future USBX release?- Does anyone already have a workaround for this?- Wouldn't it be cleaner to reply with an ILLEGAL REQUEST instead of stalling the endpoint?System details:- MCU: STM32H7- USBX version: 6.4 (X_CUBE_AZRTOS-H7 3.3.

How can I get the large signal model for SD2942 TRANSISTOR 

Hi ST Family,We are using STM32H745BIT6 MCU in our design and interfaced the same to multiple I2C slaves. For I2C lines, we have connected pull up of 2.2K to 5V power rail. In STM32CubeMX, we are enabling "No pullup or No pull down" for I2C lines.Since this MCU family is "not true open drain" ( Page 202 of datasheet), we need to know if we can continue with this configuration.Over the long run, do we see any issues of I2C engine going bad because of this configuration.?Regards..

Hey there community, I am having trouble fixing an interesting scenario on Usart communication,With the same software doing a reception on a given usart interface, It has been noticed the reception segregates one connection but not the other, Both connections having the same configurationIt has been tested that the board on which it fails has connection on that line and that the connection actually reaches the intended pin for sure by testing the Usart Rx pin when set up as a both a GPIO input and latter as an output.by playing with this GPIO input and output mechanisms on that pin. and observing respectively from both the led toggles on the board intended to signify sign of life on the pin and, logic analyzer to see the GPIO state when toggled from with in the system.Note, we are able to see the usart signals on both and are able to decode the messages on a logic analyzer for both, but the stm does not receive the message on one connection.We appreciate any insight into the Issue

I am trying to find some information on an ancient (2002?) STMicroelectronics surface-mounted device.  It has14 pins and is labeled "ZVF411."  It is used in a PC board that controls three automotive gauges in a Chevrolet SSR.  I have tried searching the internet, to no avail.  Can someone help me, please?

My design uses a STM32H750VBT6 MCU with the USB3300-EZK PHY for high-speed USB. The hardware and software implementations are complete and in general everything works extremely will. The only issue I am seeing is that there are occasional startup problems with the host computer (both Mac and Linux) reading the device descriptor. This occurs about 10% of the time. The Linux error log is: <6>[19177.992026] usb 1-1.1.4: new full-speed USB device number 75 using xhci-hcd<3>[19178.072046] usb 1-1.1.4: device descriptor read/64, error -32<3>[19178.260043] usb 1-1.1.4: device descriptor read/64, error -32<6>[19178.448021] usb 1-1.1.4: new full-speed USB device number 76 using xhci-hcd<3>[19178.528074] usb 1-1.1.4: device descriptor read/64, error -32<3>[19178.716051] usb 1-1.1.4: device descriptor read/64, error -32 A normal connection log as follows: <6>[19166.984026] usb 1-1.1.4: new high-speed USB device number 74 using xhci-hcd<6>[

Hello I have a STM32f469-discovery. I have trouble loading code/programming. I have successfully programmed the board via the Flowcode software. Also I can use the Hex or Bin generated file from Flowcode, import it in the STlink utility and load it on the board. That works. What I can't do is to open a demo or example for the touchGfx designer and program the board. I click on the "program and run target" but ends up in error"ST-LINK error (DEV_CONNECT_ERR)c:/TouchGFXProjects/MyApplication_7/gcc/include/flash_sections_int_ext.mk:2: recipe for target '_extflash_' failedmake[1]: *** [_extflash_] Error 1../gcc/Makefile:53: recipe for target 'flash' failedmake: *** [flash] Error 2FailedIn the touchGfx there is no indication that the board is connected. I get indication only on the STlinkIf I select the "Generate code" it successfully does it but later on I dont know where to load that code in order to use it to program my board via another software. Is there a specific sequence f

I have an issue with PMIC. It seems that Op-tee won't start och activate the PMIC. Do you know why? Any suggestion? The error is 0xffff0008 = TEE_ERROR_ITEM_NOT_FOUND.Notice that I have copied the DT from DK board. F/TC:0 0 probe_driver_node:543 Probing stm32-gpu on node gpu@48280000 D/TC:0 0 probe_driver_node:556 element: stm32-gpu on node gpu@48280000 deferred 3 time(s) F/TC:0 0 probe_driver_node:543 Probing stm32_pmic2 on node stpmic2@33 F/TC:0 0 stm32_pmic2_probe:923 Probe stpmic2 F/TC:0 0 initialize_pmic2:893 Initialize stpmic2 F/TC:0 0 lock_i2c_bus_access:796 thread access F/TC:0 0 unlock_i2c_bus_access:837 thread access completed F/TC:0 0 lock_i2c_bus_access:796 thread access F/TC:0 0 unlock_i2c_bus_access:837 thread access completed F/TC:0 0 stpmic2_register_read:259 REG[0 v=0x21 F/TC:0 0 lock_i2c_bus_access:796 thread access F/TC:0 0 unlock_i2c_bus_access:837 thread access completed F/TC:0 0 stpmic2_register_read:259 REG[0x1 v=0x11 I/TC: PMIC STPMIC REFID:2.A V1.1 F/TC:0

Hi,I'm using STM32H755 Nucleo board and I'm evaluating ADC. I'm using 1.92MSPS per ADC sample rate for ADC1 and ADC2. I'm using A0 and A5 pins from CN9. I'm using ethernet to transfer data. My input to A0 (I channel) is 100kHz sine and A5 (Q channel) input is constant 1.6V. The problem is periodic noise around 320kHz.What might cause that and is it possible to get rid of that? I have read that it might be caused by ethernet connection. I would need ethernet in final application, so would need to solve the issue somehow. 

There are still some typos to fix in the migration docum. for instance:"Atomic" API names - change to "unitary" as was agreedPACKET - > PACKED 

Hi! Starting a design with an STM32WL31K8V6. This is the 32 pin VFQFPN32 variant.As far as I can see, there is no HW Reference PCB that covers the 32 pin package. Looking at the datasheethttps://www.st.com/resource/en/datasheet/stm32wl31kb.pdfon p.32, there is Figure 10. "STM32WL31xx application circuit with SMPS, VFQFPN32 package" which shows the typical circuitry around the chip (i.e. the matching network).However, looking into the details of AN5457, latter shows a different matching topology than the datasheet. It´s similar, but still...https://www.st.com/resource/en/application_note/an5457-rf-matching-network-design-guide-for-stm32wl-series-stmicroelectronics.pdfSince the AN5457 shows details on how to so the matching I tend to use the topology shown there but what is the reason that there are different references?Thanks