Solved

Hello,I am Bansi Attara. I initially used the STM32F7508-DK for my application, but due to its obsolescence, I transitioned to the STM32F746G-DISCO. During this shift, I encountered two variants of the STM32F746-DISCO:1. DK32F746G$CU42. DK32F746G$CU2While the second model (DK32F746G$CU2) works perfectly, the first model (DK32F746G$CU4) has issues with proper display functionality.I have attached an image for your reference to help illustrate the issue.Thank you for your attention to this matter.Best regards,Bansi Attara

Dear all!this is the first time i handle with STM32H7 series. in my project control ILI9488 by TouchGFX platform, 4 mosfets, 1 Led. in the first step, i try to blink a led at pin PB5 but seem unsuccess. i don't know how to fix, so can you share me my mistake and how to fix it. in attach file have schematic. can you take a look and share me your input.

Does the STM32H753ZI microcontroller provide a built-in unique key or mechanism to ensure that the chip cannot be unlocked, and firmware cannot be flashed, read, or erased without the correct key, effectively preventing unauthorized access or modification?

STM32H573 with Secure Manager provisioned, the non-secure app cannot access the RNG anymore.  Will it be ok to use Secure Manager API psa_generate_random() to replace HAL_RNG_GenerateRandomNumber()? 

I want to make some modifications to the STM32H747I_DISCO_USB_Webcam example embedded in the FP-AI-VISION1 package, however I cannot find a way to open it in STM32CubeMX. I also checked the repository on GitHub for this example and no success. Any idea about how to open the settings of this example in STM32CubeMX? Thanks!

I am trying to compile a STM32 project with my own code structure. I have not changed the structure created by the IDE when creating the project and have added my .c and .h files in the Src and Inc folders in Core directory. But I am getting an error where the compiler is not able to find the include paths. I am attaching the error and screenshots for your reference. I have added the include paths in project settings. Is there something that I am missing?  

Hello, I build a business card with the M24LR64E-RMN tag.When using NFC Tap application on Android everything works perfectly. I'm able to write and read the NFC tag.However, when using with iPhone 12 (IOS 17.7.1) - while reading a tag I'm getting the following fault. I'm not able to write NDEF commands and neither can I read the tag (When with Android everything works fine).Have any of you face similar issues?  

Hello, I am currently trying to being up the STM32MP257F-EV1 development board and running into a problem. I am using CubeIDE following the following guide: https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP2_boards/STM32MP257x-EV1/Develop_on_Arm%C2%AE_Cortex%C2%AE-M33/Modify,_rebuild_and_reload_the_firmware.Specifically I am on step 8 when you have to create the run and debug configurations. I followed the guide and created the configurations correctly but now when I run the example application (OpenAMP_ttyecho_CM33_NonSecure) I get the following error:Error in final launch sequence:Failed pre launchFailed pre launchFirmware remoteproc load failed, please:1. make sure that /lib/firmware on your target has space2. make sure that /lib/firmware has write access> you can open a Console View for this.. Any help would be greatly appreciated. Thanks! Carson

Hello again!I've been trying to measure water level using the VL53L1 sensor and reading forum posts on it, and I've gathered that RefSPAD calibration isn't really recommended anymore.From my research on the topic, I know that water reflects only 2% of perpendicular incident light, with the rest getting transmitted and also that the transmitted rays will be fully absorbed at a minimum water level of 10cm.I was wondering if doing the RefSPAD calibration utilizing the VL53L1 (with a cover glass) leveled parallel to a water suface from a body deep enough to absorb all transmitted laser could end up improving the sensor's results by giving more weight to SPADs more likely to detect those perfectly reflected photons.Thanks in advance!

how to set up the meta-qt5 toolchain, cross compilation and Qt creator in order to deploy Qt applications to a target STM32MP157d-DK1 from a linux host machine.please give me step wise instruction on how to do 

Hi there TouchGFX team!I've a STM32MP135F-DK and I would like to run it using QT, where do I start?QT seems to have several examples but there's a lot of apps that I don't even know where to start.  Thanks a lot in advance!

I am working on a project where the end goal is that TIM8 is used to capture an incoming PWM signal on PC6.  I want TIM2 to trigger from TIM8 and generate a single pulse on PB11. I have TIM8 working, capturing both rising and falling edges properly.  However, after many attempts, I am not getting anything on TIM2. I decided to check the output itself, and PB11 can be set high or low just fine, set as open drain.  This rules out any hardware/PCB issues with the pin.  Next I tried running a continuous PWM on TIM2 and the pin stays high.So I stepped through the debugger, and I noticed that TIM2 registers aren't getting set.  I tried manually setting them in the debugger and they immediately revert back to 0.//This code worksTIM_HandleTypeDef HeaterTimer;HeaterTimer.Instance = TIM4;HeaterTimer.Init.Period = 0xFFFF;HeaterTimer.Init.CounterMode = TIM_COUNTERMODE_UP;HeaterTimer.Init.ClockDivision = TIM_CLOCKDIVISION_DIV1;HeaterTimer.Init.RepetitionCounter = 0;Hea

The STLink Mini data sheet has a pin labeled "T_NRST" I am wondering if this needs to be connected to the "DEBUG_JTRST" or the "NRST" pin of the microcontroller.

I doing bare metal coding for STM32L496ZGT6. Now in SPI, extra bytes are sent. There are only 4 Registers in SPI but unable to resolve the issue. Below is my codeNOTE:I am using Aardwark Total Phase Control Center software for debugging. I am attaching the related images. The Chip select to be handled by the SPI Hardware. Data sheet is DS11585.#include "lib_headers.h"#define SPI1EN (1U << 12)#define GPIOAEN (1U << 0)#define SR_TXE (1U << 1)#define SR_RXNE (1U << 0)#define SR_BSY (1U << 7)const char write_data[] = "ABCD"; // Data to write (4 bytes)char read_data[5] = {0}; // Buffer to store received data (4 bytes + null terminator)uint8_t reg_address = 0x01; // Example register addressvoid delay(volatile uint32_t count) {while (count--);}void spi1_transmit(uint8_t *data, uint32_t size) {uint32_t i = 0;while (i < size) {while (!(SPI1->SR & SR_TXE)) {}SPI1->DR = data[i++];}while (!(SPI1->SR & SR_TXE)) {}while (SPI1->SR & SR_BSY

I've noticed that when I create a notify characteristic, two functions are created each time: one is called Custom_<name of char>_Send_Notication(), the other is Custom_<name of char>_Update_Char(). What is the difference? They both end up calling the same function, Custom_STM_App_Update_Char(CUSTOM_STM_PINGRESPONSE, (uint8_t *)NotifyCharData), but point to different arrays - why different arrays / what is their purpose?

I would like to change the state of the INT_DRDY of LPS22DF. I have tried to change the value of INT_H_L bit in register CTRL_REG3 (12h), but it has no (immediate) effect. Is it necessary to activate the pin? I have also tried different values in CTRL_REG4 (13h), without effect.Thank you.

I am using the X-CUBE-CRYPTOLIB (V4.2.0) in a project for STM32F207.I am successfully able to generate ECC key pair using cmox_ecdsa_keyGen() and generate ECDSA signature using cmox_ecdsa_sign() but I am now needing to generate a shared secret using cmox_ecdh() function. The problem I have is that the cmox_ecdh() function expects the public key in raw data format (64 bytes) but I only have the public key available in compressed format (33 bytes) where 32 bytes is the x component and the other byte indicates if the y component is odd or even. The y component can be derived from this information but I could not find a function within the  X-CUBE-CRYPTOLIB that does this which means I am unable to generate the shared secret.Is there a way of achieving this with the  X-CUBE-CRYPTOLIB?

i am new to makefile Enviromint please refer the screenshot  regards,raj

Using STM32CubeIDE v1.6.1 on MacOS 11.3.1Steps to reproduce:Create a new STM32 project.Board Selector -> Select STM32F411E-DiscoName project, leave everything else as default, hit finish.Initialize all peripherals with their default Mode? YesDebug as STM32-M C/C++ Application.Hit play then pause and you'll end up in the Error_Handler.Stepping through the program it errors out waiting for the HSE to be ready.Troubleshooting:I made sure I wasn't insane and choosing the wrong board. I am staring at the board name on the back of the PCB as I write this. I am able to use the board and interact with the LEDs and button when using the internal clock.Tried to increase HSE Startup Timeout to 10 seconds, still times out.I checked the solder bridges, SB14, SB16, R66 are off and I made sure with a multimeter.I want to use the USB OTG but can't do so without the external clock but I haven't tried to use an entirely separate clock circuit yet. What bothers me the most is that I'm using entirely d

Hello,For the vd55g0, you provide a kernel driver and device tree as source here: https://www.st.com/en/embedded-software/stsw-img505.htmlYou also provide a libcamera integration stack (STSW-IMG505_LCAM), but this is closed source, and only the libcamera-base.so and libcamera.so files are provided via the .deb package. This makes it such that we cannot work with the libcamera source or custom applications, unless we use your pre-compiled libcamera libraries.Could we please get source code for the changes, per LGPL 2.1, which libcamera uses? Or, for now, if this takes some time for you to do, please just the camera helper file would be massively helpful. This is likely called "camera_helper_vd55g0.cpp" inside of "src/ipa/rpi/cam_helper/". Of course we can write our own but we chose this path for ease of integration and speed.This would greatly assist us in integrating your sensor to our product.Thank you! We would greatly appreciate it.

Hello,Since the latest release of CubeMX (6.12.1) installed, I have been encountering syntax errors related to the "FLASH.ld" file.This issue only arises when I generate code while setting the Toolchain/IDE to CMake. I am using STM32F103C8T6.It seems that CubeMX does not specify which RAM to use when setting the Toolchain/IDE to CMake.I have also included the FLASH.ld file that was generated for your reference. The terminal output the wrong as below , after  run  the default cmake-build task with the project templete generated by CubeMX (6.12.1)  :STM32F103C8Tx_FLASH.ld:56: syntax errorcollect2.exe: error: ld returned 1 exit statusninja: build stopped: subcommand failed.build finished with error(s).Then, after replacing 6.12.1 flash.ld  with 6.12.0 flash.ld  , the errors are eliminated.Here are two versions of the flash.ld  attached. ---Thanks for your help.

Hello everybody,I am developing a custom board strongly inspired by the STM32MP157D-DK1, except that I use a parallel DPI RGB on 24bit display.I use openstlinux-6.1-yocto-mickledore-mpu-v24.06.26.The frequency of "LTDC_CLK" changes by itself after waking up from "deep suspend".Before putting it into "deep suspend", I measure 31.65Mhz which corresponds well to what is expected for "innolux,at070tn92"But after waking up, i measure 86.21Mhz and this is completely outside the display specifications.All other frequencies changed in the same proportion "HSYNC", "VSYNC", ...Here is the configuration in the kernel and u-boot DTS file : panel_at070tn92: panel_at070tn92@0 { compatible = "innolux,at070tn92"; enable-gpios = <&gpioi 10 GPIO_ACTIVE_HIGH>; power-supply = <&vdd>; status = "okay"; port@0 { reg = <0>; panel_in: endpoint { remote-endpoint = <&ltdc_ep0_out>; }; }; }; &ltdc{ pinctrl-names = "default

GoodmorningI have a new STM32L496ZGT6PU board and I'm currently trying to print a message on the debugger serial terminal, I've followed many official guides step by step failing every time.In particular, I perform the following:Connect the board through a USB type micro-B cable to my laptop (USB PWR connector).Create a new STM32 project, selecting the NUCLEO-L496ZG-P board from the board selector -> target language C++ -> initialize the peripherals with their default mode (YES).In Pinout & Configuration I go to Connectivity -> USART2 -> Mode Asynchronous and leave the default values.Device Configuration Tool Code GenerationIn Src/main.c simply write the following two lines of code in the main() function: /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) { /* USER CODE END WHILE */ /* USER CODE BEGIN 3 */ HAL_UART_Transmit(&huart2, (uint8_t*)"Ciao ", 6, 100); HAL_Delay(1000); } /* USER CODE END 3 */ Then I build the project and sta

Hello,my injected Adc sequence was not being triggered, and I found that the cause is that, with LL driver, the trigger source is not being set by the CubeMX code generation.I had to add this line in the main code:LL_ADC_INJ_SetTriggerSource(ADC1,LL_ADC_INJ_TRIG_EXT_TIM1_CH4); I am testing on a Nucleo L432KC P.S. I have fitted SB17 to have the 8MHz clock in from the STLInk. Otherwise, to use a default solder bridge configuration, the clock source in the IOC file needs to change.

hello, I am developing an application which makes use of LIN break interrupts. At the moment I am using two STM32 dev boards:STM32C0116-DK ( which uses STM32C011F6U6)STM32 NUCLEO G531 (which has STM32G431KBT)We are using the LL drivers interface.Although one processor is Cortex-M0+ and the other is M4, the description of the USART operation seems the same for each processor, as does the low level interface.However, we are seeing very odd behaviour on the C11 (Cortex M0+) platform - we get the LBD interrupt, but it happens a considerable time after the break.. On the M4 platform we see the interrupt a few us after the break is done.UART config and ISR implementation is the same on each platform. (Most of it is generated by Cube.) Here is the code for UART initialisation:  static void MX_USART1_UART_Init(void) { /* USER CODE BEGIN USART1_Init 0 */ /* USER CODE END USART1_Init 0 */ LL_USART_InitTypeDef USART_InitStruct = {0}; LL_GPIO_InitTypeDef GPIO_InitStruct = {0};