Solved

Hi, I was wanting to know that if I only use one channel of the TDA7297, say input 1, but not input 2, how should I handle the unused channel? Should I just leave the unused input floating, or should I tie it to ground, or tie it to ground via a resistor? Thanks,Erik

there is a delay between caling dcmi_start_dma function and data being actually received in dcmi_dr in stm32l4r9discovery the pixel clock is 24 mhz 

This is my first time making and external loader for an SPI flash device. I followed the examples and documentation I was able to find. I was to get the project setup on Keil and ".stldr" file loaded onto ST-Link Utility & CubeProgrammer.Initially, I set up the "Read" function to send dummy data and that worked fine, so I thought everything would be straight forward from there.When I added the quadspi code (which has been tested to work on application), the "Init" function would fail by HardFaulting presumably (I was unsuccessful at setting up a debugging project). Through trial and error, I have isolated the fault to be in the HAL_QSPI_Init() function where the "hqspi" function parameter is first referenced to access the hqspi->Instance. From my pseudo-debugging, I have concluded that that function parameter is incorrect and yields all 0xFF for all struct members, causing the HardFault; it almost seems as if that function parameter was corrupted and points somewhere else. 

I am working on implementing a firmware update on my electron app using CubeProgrammer_API. I keep encountering issues on connecting to the DFU bootloader in which is giving me CUBEPROGRAMMER_ERROR_NOT_SUPPORTED (-5). I compiled my code into a .exe and run a JavaScript code to execute the .exe. However, when I run the .exe manually, it works fine, but not on my Electron app. I have the latest version of STMCubeProgrammer (2.16.0). 

BOOT0 Input equivalent circuit data cannot be found. Please let me know if you have any materials.

I want to use AES peripheral for encryption in ECB mode (256). I am able to encrypt and decrypt on the same MCU, but if I compare the encryption results, the HW peripheral has a different result than the SW library AES.c or encryption in Python - the last two have the same result.hcryp.Instance = AES;hcryp.Init.DataType = CRYP_DATATYPE_32B;hcryp.Init.KeySize = CRYP_KEYSIZE_256B;hcryp.Init.pKey = (uint32_t *)aAES256key;hcryp.Init.Algorithm = CRYP_AES_ECB;hcryp.Init.DataWidthUnit = CRYP_DATAWIDTHUNIT_BYTE;hcryp.Init.HeaderWidthUnit = CRYP_HEADERWIDTHUNIT_BYTE;hcryp.Init.KeyIVConfigSkip = CRYP_KEYIVCONFIG_ALWAYS;if (HAL_CRYP_Init(&hcryp) != HAL_OK)I use it like that: HAL_CRYP_Encrypt(&hcryp,(uint32_t*) plain_text, 16,(uint32_t*) tmp_encrypt,0xffff);  uint8_t aAES256key[32] = { 0x4d, 0xf0, 0x2c, 0x47, 0x64, 0xa4, 0x28, 0xd9, 0xe5, 0x36, 0x83, 0x38, 0x4c, 0x3e, 0x69, 0xfa, 0x14, 0x4d, 0xb9, 0xb4, 0xdf, 0x4d, 0x77, 0x43, 0x4c, 0xf3, 0xf6, 0xff, 0x5d, 0x5c, 0xde, 0x

Hi,I have created a project using CubeIDE 1.14.0 for the STM32L452CE. Inside the IOC editor, I changed the following things:SYS => Debug set to Serial WireProject Manager => Advanced Settings => Set both RCC and GPIO to use LL instead of HALI then generated the code and fixed the broken linker script as outlined here: https://community.st.com/t5/stm32cubeide-mcus/stm32l452ce-cubeide-linker-script-causes-hardfault-inside-reset/m-p/651426#M25207When I build and flash the code, I get a hardfault when executing the line: LL_FLASH_SetLatency(LL_FLASH_LATENCY_0); The full code is below, but it is just the default code that is generated...   /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2024 STMicroelectronics. * All rights rese

Hello, I use NUCLEO-H753ZI with processor STM32H753ZI. In deafault settings there is not mounted external oscillator, but I need application where it's mounted. So I added oscillator 25Mhz (same type as is described in schematic for board) and capacitors. Then I try to run FatFs_USBDISK_Standlone (intended for STM32H743 - STM32H743I-EVAL). If I switch on internal oscillator (HSI) example is running. But if I use external oscillator (default settings of project) the frequency is not correct. I verified it by test led blink with timer (the measured frequency is about 3 times smaller then calculated). Also if I try to measure oscillator frequncy (on C70 - see schematic for board) i can see signal with 8Mhz frequency on oscilloscope (the waveform is similar to a charging and discharging of capacitor ~ triangle waveform).   Does anyone know what may be incorrect in my settings?   Thank you for response!

Dear STM team,I am debugging the chip since hours and I think there is something wrong with the PB5 and PB15 pins:1. SPI1 with MOSI on PB5:I have configured SPI1 and want to get the SPI1_MOSI on PB5 (as mentioned as ALT5 in datasheet).I use a STM32U5A5 with LQFP64 package.Nothing comes out as MOSI (constant high, no bit pattern driven by SPI1).But:if I configure PB5 as GPIO - I can toggle - OK, no shorts on PCBI can also use the SWAP function for SPI - now MOSI comes out on PB4 (which was MISO) - all OK (SPI1 works - MOSI is now out on PB4)I can also use MOSI on PA7 - also fine!Just:PB5 is NOT a SPI1_MOSI as mentioned in datasheet!And: if I connect with SWAP configured (PB4 is MOSI) with PB5 (now as MISO): the waveform is damaged!There are not anymore nice bits out of MOSI: so, the PB5 seems to be driven all the time, with something else (see below on Remarks).2. PB15: if high - USB failsI want to use PB15 as GPIO.When I configure as GPIO and set as low (RESET pin value) - fine (USB co

Hello,I'm starting a project with an STM32F429IIT6 MCU, but I have a doubt. The project will have a display (I haven't decided yet if it will be 4.3" or 7"), and I'll be controlling the display with the MCU's internal TFT controller using TouchGFX. So far, so good. The issue is that the device needs to be able to capture a screenshot of the screen and save it to an internal microSD. Is this possible, or should I use an external driver to achieve this?Best Regards,                                                                                                                                                       

  Hi everyone.There is a my page. I defined a virtual function there. And I changed the image's location. But I can not call this function from C. I research many example but can not arrive the success. otherPageView.hpp #ifndef OTHERPAGEVIEW_HPP #define OTHERPAGEVIEW_HPP #include <gui_generated/otherpage_screen/otherPageViewBase.hpp> #include <gui/otherpage_screen/otherPagePresenter.hpp> class otherPageView : public otherPageViewBase { public: otherPageView(); virtual ~otherPageView() {} virtual void setupScreen(); virtual void tearDownScreen(); virtual void handleTickEvent(); virtual void function1(); protected: }; #endif // OTHERPAGEVIEW_HPP   otherPageView.cpp #include <gui/otherpage_screen/otherPageView.hpp> #include <touchgfx/Color.hpp> #include <texts/TextKeysAndLanguages.hpp> #include <math.h> #include <touchgfx/hal/OSWrappers.hpp> extern "C" void call_C_f(otherPageView* u) // wrapper

Reproduction steps:Open STM32CubeIDE. “File” menu → “New” → “STM32 Project”.Switch to the “Board Selector”, and pick the NUCLEO-H503RB. Click “Next”.I've successfully reproduced this issue with the NUCLEO-H503RB and NUCLEO-H563ZI. I suspect it applies equally to every board or MCU part with I3C support.Give the project a unique name – I'm using “broken-mx”. Target the C language, an executable binary, and an STM32Cube project.Pick firmware package V1.1.1. Ensure the code generator is configured to “Copy only the necessary library files”. Click “Finish”.This issue can also be reproduced with firmware package V1.1.0. It's an STM32CubeMX problem, not a problem with the firmware package.When asked whether I wanted to “Initialize all peripherals with their default Mode ?”, I picked “Yes”.This issue can also be reproduced without default peripheral initialization. It just requires a couple more clicks as you'll have to acknowledge that the icache is disabled every time you generate code.The

The Ethernet peripheral is missing from the STM32H5 in STM32CubeMX 6.10!It appears if the Nucleo or Discovery kit boards are selected as the starting point for a project, but if the project is started from a device selection the Ethernet peripheral is completely missing.First noticed on STM32H573VI, then checked it is also missing on STM32H563ZI even though this is exactly the same device as used on the Nucleo board!If I create a project using the Nucleo board then edit the .ioc file to changeboard=NUCLEO-H563ZIboardIOC=truetoboard=customthen when I open the project the Ethernet peripheral is there, but the project is based on the device not the Nucleo board!Without this being fixed, STM32CubeMX is useless for our application :(

Hi.Problem:stm32h5_xx_hal_conf.h is generated with #define HAL_USART_MODULE_ENABLED but the file stm32h5xx_hal_usart.h is not included in the project code generation.I'm using one usart peripheral in asynchronous mode, it is OK to just comment out the row in stm32h5_xx_hal_conf.h to make the project compile and work, I must do that each time the .ioc changes.Versions:STM32CubeIDE version 1.14.0STM32CubeMX version: 6.10.0-RC9STM32Cube FW_H5 V1.1.1Settings:Peripherals initialized as a pair of '.c/.h' files per peripheral 

Hello, I am looking to get hold of the SET cross-section data for 54VCXH163245 if it exists? 

I am using stm32f103rct6 controller board. I am not getting fixed ADC values for POT. I was used poll for conversion in ADC. Please attach code to get a fixed ADC value or else please address me for how to solve the problem.

Working with a STM32F426G-DISCO evaluation board and trying to get the Audio Playback application example to run properly.  Using the V1.17.1 firmware repository downloaded from ST with the Keil toolchain to build the project which builds with no warning or errors.  When I load the image onto the board it starts up as expected, but seems to hang after putting up the message “LUN #0:” on the display.  I have tried a variety of USB memory devices of various sizes and manufacturers with the same results so I believe I have eliminated that as a possible cause.  Using the debugger the application appears to be stuck in the USBH_MSC_Process function (line #363 in usbh_msc.c file) in the MSC_READ_INQUIRY state where the USBH_MSC_SCSI_Inquiry function always returns a BUSY status which prevents the state machine from advancing.  Hoping someone else has observed this same behavior and can guide me to a solution.  I did some stepping thru the code to try to fig

hello,trying to write to a ST25DV tag mailbox, via I2C with DMA.The chip has a mailbox of 256 bytes.I use  the function:HAL_I2C_Mem_Write_DMA  When I try to write data of size 256 bytes, only 255 is written and the last one is written to 0.Writing 255 bytes works fine.  Writing without DMA fixes the issue:  HAL_I2C_Mem_Write    

Dear Team,I am interfacing Nucleo-h743zi2 board  with LCM display(GUI) through UART using Interrupt method.I can transmit the data to LCM and it is displaying properly on the LCM display.Now I am trying to send the commands from LCM display to STM controller.  I tried to press the button for many times on LCM display and observed sometimes it is triggering and sometimes not triggered). I think there is a  problem with synchronisation for receiving from LCM display to STM controller. I can see the events are triggered sometimes in debugging steps.I tried to change the system clock to different values but it did not worked. Also I tried to increase the delays, decreasing delays at different places did not worked.I tried to copy the receiving buffer into the other buffer and cleared the buffer. But this also does not worked.Please find the below Receive function for your reference: extern uint8_t data_u[100];uint8 j, max; uint8 ReadSerialByte( uint8 *data){&n

I have installed the example USB-C projects using the General/Import Projects from Folder or Archive option targeting the NUCELO-G474RE:DRP1M1_DRPSNK1M1_SinkSNK1M1_SourceWhat do I need to do to make these regular STM32 projects such that the Build All, Build Project and Clean options are available (currently they are greyed out)?       

i am using ubuntu 22.04 ltsThe above mentioned photo  is what was the output when i follow Readfile. How to do.txt;i cannot able to figure out what was the issue.And because of this issue i am getting this issue isn't it?  (below attached)Now this error evolved like this.

Hello everyone,I have Custom board that has STM32H7 controller.I wanted to interface display module G070ACE-LH3 and i have RGB to LVDS  DS90C385AMT/NOPB.As I am a beginner wanted using Stm32 LTDC interface to bring up the display.Can anyone help me with that?#LTDC to LVDS

Hello,i am trying to interface 1.8 inch SPI TFT Display 128 x 160 to the STM32F103C8 using SPI2.https://www.az-delivery.de/products/1-8-zoll-spi-tft-displaySPI1 is used for LoRa, i thought to connect TFT too to SPI1 using addresses but i am affraid to influence theLoRa.The library which i am using is from this website:https://controllerstech.com/st7735-1-8-tft-display-with-stm32/A year earlier i tried to interface LoRa to STM32F103C8 using SPI2 but without success.Is it a general problem in STM32F103C8 using SPI2?Any help is appreciated.

Hello:I have external sdram on FMC bus. I initialized with bootloader, mapped sdram to Bank2(0xD000 0000), and jumped to APP to run. The configuration of my APP is shown in the figure.I find that the more ram is used in the APP, the longer it takes for bootloader to jump to the app.The speed is about 1.1MB/s.However, when I ran the read and write tests in bootloader（sdram）, it took about a few hundred milliseconds to write all of them,Why is this?

  Hello, I am trying to control two Motor Drivers (TMC5041) through SPI communication using STM32F103. The compiler uses IAR. I am trying to communicate with two SPI Masters, but perhaps due to an initial configuration issue, only one SPI is controlled, so I am posting this to ask for help. ​ The current progress was controllable when each SPI2 and SPI3 were controlled one by one. For example, control is possible when TMC5041 Motor Driver 1 is controlled without defining SPI2. Controllable when controlling TMC5041 Motor Driver 2 without defining SPI3 Therefore, it is judged that there is no problem with the communication protocol with each TMC5041. ​ Here, when I try to use two SPIs 2 and 3 together, I am experiencing the problem that only one of the two SPIs can communicate and one is not communicating. In the process of specifying the initial configuration of two SPIs and sending and reading the data specified for each SPI, one SPI was able to write and read witho