STM32 MCUs Products

how to simply test the 2.4 tft mucfriend's display is working with stm32h743   144-nucleo board  using 8bit parallel,  where to get exact code and library? my driver shown in ardrino's ID check coding using serial monitor, it works with ili9325.

Hi,I'm trying to implement an STM32H735 device with LwIP and FreeRTOS. I've been following this documentation: https://community.st.com/t5/stm32-mcus/how-to-create-project-for-stm32h7-with-ethernet-and-lwip-stack/ta-p/49308Although I've managed to resolve debugging errors, I'm still unable to successfully ping the device. Any assistance from fellow developers would be greatly appreciated.

Hi.Im trying to read potentiometers on the pins pa6 and pa7,according to the values blink the leds with if else conditions.Im simulating the project in proteus but i cannot get any output from the leds...I have  used internal oscilator with hclk 84mhz pll method.My proteus simulation settings and simulation is here.My code is here as programmed in HAL LIBRARY #include "main.h"uint32_t adc_buffer[2];uint32_t adc_value[2];ADC_HandleTypeDef hadc1;DMA_HandleTypeDef hdma_adc1;  void SystemClock_Config(void);

Hello, I don't know whether this is appropriate place to ask, But will STM32H7A3RIT6 or H7B3RIT6 a good choice for projects considering availability? Are these in production to use on new products and trust the availability exists? Thank you! 

Hello everyone, I am working on a custom device that is using an stm32 L433. One of its peripherals is set to generate interrupts to wakeup the device from the stop mode, but there are certain instances where I need it to stop for 30 seconds or so and ignore this specific interrupt.I enter the stop 2 mode with HAL_PWREx_EnterSTOP2Mode(PWR_STOPENTRY_WFI), and it works exactly like I want it to under normal conditions.But when I need to do the special case of ignoring the Interrupt I first tried disabling the IRQ for the pin using HAL_NVIC_DisableIrq(); and it still woke up. Completely de-initializing the pin with HAL_GPIO_DeInit(); does do the job.But what's throwing me off is in the reference manual RM0394 Table 27 describing stop 2 mode states the following for Mode exit"If WFI or Return from ISR was used for entry: Any EXTI line configured in Interrupt mode (the corresponding EXTI interrupt vector must be enabled in the NVIC). The interrupt

Using STM's MDMA example, I setup a simple loop to transfer an array of 1000 bytes 100 times.The code worked but the MDMA transfer were causing glitches on the VDD rail.I then compared it to memcpy, and to my surprise found that it was around 18% faster than MDMA, and did not generate the nasty glitches on the VDD rail.Instruction caching is enabled, data caching disabled.Is this behaviour as expected?

Posted on December 05, 2014 at 10:05i'v tested the nucleo on arm mbed, very nice. but, when i use the onboard stlink v2.1 to debug my application board, the mbed mass-storeage disk is always pop-up a window. so, can i disable this disk (not by disbable the system autorun function), only keep the stlink swd & cdc functions? #nucleo-f401re-st-link/v2-1

Hi,I have a power management setup with a smart battery, charger Ic and the host msu - all connected on the SMBUS. I am  facing some issues and I doubt that the data on the SMBUS is getting corrupted. The issue is only happening when the MCU tries to access the bus. There are bus traffic on the smbus due to the communication between the charger IC and the smart battery. So, should the MCU check if the bus is idle before initiating a communication on the smbus ? I have also noticed that the clock frequency is different between the communication between the chargerIC and the smart battery (64 KHz), and between the MCU and the charger IC/smartbattery (93 KHz). Can the difference in the clock frequency lead to data corruption ?Is there an HAL SMBUS api to check if the bus is busy/idle which can be used before accessing the bus ?I hope the HAL SMBUS library support bus arbitration and should the clock frequency be same for this ? 

Hello,I've got some questions about STM32H753 PLL setting. 1) There are many configurations of M, N and P parameters that give the same output clock. Are there some configurations that are more precise than others (regarding the output clock) ? 2) The datasheet gives some insight about clock precision, for example: What means "long term jitter" exactly ? I understood this is the difference between the PLL output clock and the "target" clock" in average, is it correct ? Indeed, I did some test (comparing the accuracy of a timer to an external very precise signal) and I've got the same order of precision (less

Hopefully this is more of a sensible non-noob question, it relates to interrupt handling, in my case a simple USART receive interrupt. I can see how the CubeMX tool is managing the .c file, its created an interrupt handler, for me to insert my code, thats easy. I can detect the interrupt and spit out a short string in response, so its working - all good. The question I have is, what can I do inside that ISR safely.  Do I need to preserve any registers. My aim is to throw anything I receive into a ring buffer of some form, with a view to building a received packet of data.  At some point I will need to pick up each completed packet from a list. In order to do that I will possibly need to allocate some memory, and it would be useful if I do not have to put the whole implementation of that ISR in the file that is being auto-generated, so would be handy to also be able to call a function where I can contain the implementation of the ISR in its

Hi,Currently, I am facing an issue with STM32 MCU I2C communication.I have facing an I2C timed-out error on the host side while communicating with the MCU I2C continuously.The I2C clock line was held low when the issue occurred, I wasn't able to communicate further with the I2C line.I've attached an image for you to look over. The I2C line will recover after resetting the MCU.  This issue only occurs in long-run continuous communication in the I2C line.  Configuration:MCU: STM32L476JGY6TRSLAVE I2C: I2C-2SPEED: 400KHZ(Fast Mode)INPUT FREQ: 48Mhz - MSI ClockI2C lines are pulled up with a 4.7K ohm resistor to a 1.8V source Kindly help to solve this.Thank you!

Dear ST Community, I am currently working with the STM32L433RC board, specifically utilizing its 12-bit ADC. Despite my efforts in writing a simple program, I have encountered accuracy issues with errors exceeding 4.5%, and in some instances, even surpassing 30%.Code :- HAL_ADC_Start(&hadc1);HAL_ADC_PollForConversion(&hadc1, HAL_MAX_DELAY);adc_value = HAL_ADC_GetValue(&hadc1);float vin = adc_value * (3.3/4095);sprintf(msg2,"vol = %.3f \r\n",vin);HAL_UART_Transmit(&huart2, (uint8_t *)msg2, strlen(msg2), HAL_MAX_DELAY);HAL_Delay(1000); I am also attaching excel sheet to see the difference between Vin and Vout.

Hi,I use stm32h743zi nucleo board and I try to GPIOx_BSRR register .This register has two 16 bit registers "BSRRL" and "BSRRH".As I understand BSRRL is used to set bit and then BSRRH is used to reset bit.GPIOB->BSRRL =(1<<0); to set the zero pin ,but there is an error: #136: struct "<unnamed>" has no field "BSRRL"

Hello, I'm using a STM32 F446RETx trying to trigger an ADC conversion on PA0. I use TIM2 Channel 1 using a pwm with no output to trigger the ADC 1 conversion on channel 0. I have exactly one line that trigger an error at compilation (When I comment it, it compile without any error):../Core/Src/tim.c:48:13: error: 'TIM_Base_InitTypeDef' has no member named 'AutoReloadPreload'48 | htim2.Init.AutoReloadPreload = TIM_AUTORELOAD_PRELOAD_DISABLE;../Core/Src/tim.c:48:34: error: 'TIM_AUTORELOAD_PRELOAD_DISABLE' undeclared (first use in this function)48 | htim2.Init.AutoReloadPreload = TIM_AUTORELOAD_PRELOAD_DISABLE;I would like to know if I'm using the wrong firmware and if yes, how can I get the IDE to use the correct one.Or instead how can I configure the AutoReloadPreload register in bare-metal C.The firmware package I'm using is STM32Cube FW_F4 V1.23.0

While i try to build SBSFU package for stm32f769i discovery board package, User App build failed.I am using SBSFU latest package v2.6.2.IDE version : STM32CUBEIDE_1.7.0I got this below errormake allarm-none-eabi-gcc -z max-page-size=1 -o "UserApp.elf" @"objects.list" -mcpu=cortex-m7 -T"../STM32F769NIHx.ld" --specs=nosys.specs -Wl,-Map="UserApp.map" -Wl,--gc-sections -static -L../../../2_Images_SBSFU/STM32CubeIDE/Debug -Xlinker -L ../../../Linker_Common/STM32CubeIDE --specs=nano.specs -mfpu=fpv5-d16 -mfloat-abi=hard -mthumb -Wl,--start-group -lc -lm -Wl,--end-groupFinished building target: UserApp.elfarm-none-eabi-size UserApp.elftext data bss dec hex filename21536 208 6040 27784 6c88 UserApp.elfFinished building: default.size.stdoutarm-none-eabi-objdump -h -S UserApp.elf > "UserApp.list"Finished building: UserApp.listarm-none-eabi-objcopy -O binary UserApp.elf "UserApp.bin"Fi

Hello Everyone I am try to upload my code through stm32f103 necleo debuger or programmer but  have facing one issue for no st link found error I have attached the pic please give the solution .

Hello all,does anybody know the  workload of the STSW-PFCBIDIR's controller when converting AC -> DC ?Is the controller able to do some more expensive calculations (current controlling) and communication tasks (CAN) ?Kind regards !

Hello, everyone.    I use STM32L496 on my board, and use PA9 as a GPIO for input, without any external resister.    Software program is based on HAL. I have a sample demo like this:    int main(void)    {        HAL_Init();        BSP_Init();        while(1)        {            delay_ms(1000);        }    }    While, in the BSP_Init(), like this:    void BSP_Init(void)    {        GPIO_InitTypeDef GPIO_InitStruct = {0};        __HAL_RCC_GPIOA_CLK_ENABLE();        GPIO_InitStruct.Pin       = GPIO_PIN_9 | GPIO_PIN_10 | GPIO_PIN_11        GPIO_Init

Hi all,I'm using an STM32F746 Disco board. I'm not sure if the code (below) for this codec came from one of the examples for this board or other disco or nucleo board but it is from an STM32 example or board or github.There are three lines for "WM8994 Errata Work-Arounds". I tried to look for the errata sheet for the WM8994 but I can't find it. The datasheet says not to write to register not shown in the map. The registers being addressed in the "Work-Arounds" are not shown in the map. What do the "Work-Arounds" lines fix or do?Here is the beginning lines of wm8994_Init: uint32_t wm8994_Init(uint16_t DeviceAddr, uint16_t OutputInputDevice, uint8_t Volume, uint32_t AudioFreq) { uint32_t counter = 0; uint16_t output_device = OutputInputDevice & 0xFF; uint16_t input_device = OutputInputDevice & 0xFF00; uint16_t power_mgnt_reg_1 = 0; /* Initialize the Control interfac

I completed an alpha prototype design with the NUCLEO-G071RB, the STM32 Nucleo-64 development board with a STM32G071RB MCU plus a custom daughter board. Hardware and software using the HAL library work well, so I moved on to the next step, a beta design: a custom board with the STM32G0B1RET MCU for extra memory.The alpha source code was ported to the new MCU using the HAL library, and MX was used to adjust the pinout.Result: the beta device establishes UART communication with the external device, but reports unexpected HAL_TIMEOUT errors:err = HAL_UART_Receive(huart1, (uint8_t*) uart_RxBuffer, packLen, timeout);The variable 'timeout' is 20 ms, and the oscilloscope shows that a response received within 4 ms. It should work, so why teh timeout error. (I assume the measurement unit is milliseconds.)What can cause these timeout errors? Thank you!

Hello,I have a question regarding the bootloader of the STM32C0 (especially the TSSOP 20 version STM32C031F6Px).According to the datasheet and the reference manual, the bootloader can communicate via UART1 and I2C1.The pins it is using are PA9&PA10. These pins are mapped to PA11&PA12. But if I configure UART1 in CubeMX, UART1 is not and can't be assigned to these pins.Could somebody please explain:How to do the configuration of using UART1 as the communication interface for the bootloader in CubeMX?What happens and how to deal with the situation that I have assigned some other STM32 peripheral to PA11&PA12 and the triggering the bootloader? Is UART1 then remapped to these pins even it was on other pins before the bootloader?How is this remapping of the pins PA9/PA10 to PA11/PA12 done?BR,      Andreas

After the cube ide and programmer updated, the debugger broke and this is the message I would get:make: *** No rule to make target 'ENGC 371\project1\file\STM32F429ZITX_FLASH.ld', needed by 'project1.elf'. Stop. what would be the best take? i am using stm32f429 mcu board

Hello,we have an electronic with two possible µC as footprint on the PCB.STM32L071CZSTM32L071KZInside the layout it was necessary to route two signals to different GPIOs, thereforewe have a difference in the configuration.We want to avoid a #define to distinguish between both firmware with different GPIO settingsfor these two signals.Is there any chance to distinguish between these both µC by any register that we can read?GreetingsStefanPS1:CPUID -> does not work, it doesn't contain information about the packagePS2:We tried to use #define IOUTENA_PIN_49Pin GPIO_PIN_2 // BGA#define IOUTENA_GPIO_PORT_49Pin GPIOC#define IOUTENA_PIN_32Pin GPIO_PIN_1 // QFP#define IOUTENA_GPIO_PORT_32Pin GPIOAif (IS_GPIO_PIN_AVAILABLE(IOUTENA_GPIO_PORT_49Pin,IOUTENA_PIN_49Pin))But this doesn't work also. We guess that both packages contain the same Die, therefore 

I am using STM32CubeIDE version 1.14.1 on a WIN10 machine.The following C code asm("VMUL.F32 s0, s0, s0"); volatile float xyz = 3.1415; xyz = xyz * 2.3; disassembles to the following:  79 asm("VMUL.F32 s0, s0, s0"); 08000df0: vmul.f32 s0, s0, s0 80 volatile float xyz = 3.1415; 08000df4: ldr r3, [pc, #344] ; (0x8000f50 <main+360>) 08000df6: str r3, [sp, #0] 81 xyz = xyz * 2.3; 08000df8: ldr r0, [sp, #0] 08000dfa: bl 0x8000598 <__extendsfdf2> 08000dfe: add r3, pc, #328 ; (adr r3, 0x8000f48 <main+352>) 08000e00: ldrd r2, r3, [r3] 08000e04: bl 0x8000648 <__muldf3> 08000e08: bl 0x8000bf8 <__truncdfsf2> The compiler flags are set:

Hello,I am using NUCLEO-F756ZG. My application is ADC related. I am measuring an analog signal at high sampling rate. Recently, I had a discussion with my team and had an interesting proposal. Our target signal is pretty much guranteed to be within 0.5V to 1V range. So, I thought of supplying external reference voltage for a custom range. On nucleo boards, the VDDA and VREF+ are tied to VDD by default and makes the ADC range 0V~3.3V. But from the MB1137 schematic I found here, it seems that I can decouple VREF+ from VDD by removing SB12. Problem is that VREF+ is tied to VDDA on the board and can't be decoupled. So, if I put 1V or less in AVDD pin, it's probably not going to be enough to power the ADC. Or is it? Additionally, VREF- seems to be connected to ground through SB162 and by removing it, seems like I can supply an external VREF-. Would it work if