STM32 MCUs Products

Hi,I'm using STM32H755 Nucleo board and I'm trying to use TIM2 to trigger Dual ADC conversion. M7 core is running FREERTOS and M4 is bare metal. ADC is controlled by M4 core. DMA is used to transfer data to M7 and then M7 is using ethernet to transfer data further. Sampling rate of my ADC is 1.92MSPS (12bit). I try to use TIM2 to trigger ADC. This should happen with rate of 60Hz. Every 16.67ms (60Hz), I would like to collect 2x2048 samples.For some reason my TIM2 interrupt occurs every 52ms. It sounds like my clock rate is not 200MHz as shown in .ioc, but it is 64MHz. What might explain the problem?

Hello, According to reference manual/datasheet/ANs, it exists some documents that are pointing out that FDCAN2 is the capable bootloader port for upgrade.In ANs and reference manual, it is specified that FDCAN bootloader mode is available on PD0 & PD1 related to FDCAN1 instance. Can you confirm please? Thank you

Hi everyone,I’m currently facing an issue related to bootloaders and FreeRTOS on STM32 microcontrollers, specifically the STM32H735 and STM32H730.Here’s the background:STM32H735 Development Board: I have successfully implemented a bootloader that jumps to an application stored in external flash memory. This setup works perfectly with FreeRTOS. In order to ensure that the jump worked correctly, I had to explicitly disable FreeRTOS-related interrupts before performing the jump:// Disable FreeRTOS interrupts         taskENTER_CRITICAL();         portDISABLE_INTERRUPTS();After adding these lines, the jump to the external application works without any issues on the STM32H735.STM32H730 Custom Board: Here's where the problem arises. I'm

We are trying to bootload an STM32L443CCT device using CAN bootloader.The documentation for the STLINK V3 details that by using jumper JP7 and CN5 to connect, we should be able to communicate with a device which has been triggered into bootloader mode (by using option bytes only - avoiding having to set or clear any hardware pins to select bootloader). The advantage of this is that we should be able to reprogram devices using the standard CAN interface which each device currently uses, without having to take the device apart to program using JTAG or SWD access.What we are observing is that the T_CAN_TX and T_CAN_RX lines coming out of CN5 are identical, which means that the difference between the signals is essentially nothing. Observing other CAN messages on our bus from other source, it's clear that the CAN_TX and CAN_RX lines should be approximately inverted, yet we are seeing them the same.We've resorted to using the CN7 connector where we need to use a CAN

I'm building a loop pedal for guitar, and I need to store audio buffers to be looped over. The 1MB provided by the STM32H743VIT6 won't do for recordings longer than 5s on 24bits + 44.1kHz audio quality. I bought some ESP-PSRAM64H chips, which can operate on SPI and QSPI.I'm a beginner, and I want to know if it's feasible to use them as external RAM, and what would be the approach, pseudo-code-wise. I have found on this board and online that memory mapping wouldn't be possible, but to use it only as an external buffer storage would be feasible.

I'm using an STM32H753ZI, specifically the Nucleo H753ZI board, to read data from an ADS8556 adc. Upon signaling to the ADS8556 to start a conversion, a BUSY signal on the adc goes high and falls when the data is ready to be read.I currently have BUSY connected to PG13, set up as HRTIM1 AF2, with falling edge sensitivity and configured as External Event 10. I have nRD set up on PG6, HRTIM1 CHE1, with its SetSource configured to HRTIM_OUTPUTSET_EEV_10, and its ResetSource as HRTIM_OUTPUTRESET_TIMCMP1, in line with the desired pulse width. For CHE, I also have `ResetTrigger = HRTIM_TIMRESETTRIGGER_UPDATE | HRTIM_TIMRESETTRIGGER_EEV_10`, continuous mode (I've also tried SINGLESHOT_RETRIGGERABLE), and repetition counter = 4.With this setup, I'm seeing nRD (PG6) pulse once on the falling edge of BUSY, and not the desired 5 (I'm only reading from 5 channels out of 6 on the AD

I used MultiQ example 'LPBAM_DMA_MultiQExec' I change code for U545REQ board but it doesn't work.i found some issueThis is 'LPBAM_DMA_MultiQExec' codetatic void MX_LPDMA1_Init(void) { /* USER CODE BEGIN LPDMA1_Init 0 */ /* USER CODE END LPDMA1_Init 0 */ /* Peripheral clock enable */ __HAL_RCC_LPDMA1_CLK_ENABLE(); /* LPDMA1 interrupt Init */ HAL_NVIC_SetPriority(LPDMA1_Channel0_IRQn, 0, 0); HAL_NVIC_EnableIRQ(LPDMA1_Channel0_IRQn); /* USER CODE BEGIN LPDMA1_Init 1 */ /* USER CODE END LPDMA1_Init 1 */ handle_LPDMA1_Channel0.Instance = LPDMA1_Channel0; handle_LPDMA1_Channel0.InitLinkedList.Priority = DMA_LOW_PRIORITY_LOW_WEIGHT; handle_LPDMA1_Channel0.InitLinkedList.LinkStepMode = DMA_LSM_FULL_EXECUTION; handle_LPDMA1_Channel0.InitLinkedList.LinkAllocatedPort = DMA_LINK_ALLOCATED_PORT1; handle_LPDMA1_Channel0.InitLinkedList.TransferEventMode = DMA_TCEM_LAST_LL_ITEM_TRANSFER; handle_LPD

Hi, I am using the STM32U575.In my application, I have to transfer ADC readings to a destination buffer. I have set the DMA source address to the ADC data register (16-bit), and the destination address to a memory buffer start address. The data width is 16-bits or half word, as per the STM32 size definitions.My requirement is that I need to fill the ADC 1024 samples into the memory and after receiving these, transfer them to another buffer, that is connected to a UART, to be transmitted out.However, I need to increment the DMA destination buffer address by 32 bits, after each sample from the ADC, meaning, leave alternate half words empty. The data would look like this in the memory buffer:ADDR 0: fill with sample 1 (16 bits)   - increment DMA destination address by one word (32-bits)ADDR 2: empty - 16- bitsADDR4: fill with sample 2 (16 bits) - increment DMA destination address by one word (32-bits)

Hi,I am using STM32H753 in my designCan I short JTAG reset, NRST of MCU and supervisory IC reset ? Will it create any issue while debugging via JTAG interface?

Body:Hello STM32 Community,I’m facing an issue with EXTI interrupts on my Nucleo-G0B1RE board (STM32G0B1RE). The EXTI interrupt doesn’t trigger, even though the configuration appears correct, and I’ve tested both hardware and software triggers. I’ve tried multiple pins (PA0, PA1, PA8, PC13) and created a fresh STM32CubeMX project, but the issue persists. The SysTick interrupt works fine, indicating that the interrupt system is partially functional. I’d appreciate any insights or suggestions to resolve this issue.Problem DescriptionI’m trying to set up an EXTI interrupt on PA0 to trigger on a rising edge. PA0 is configured with a pull-down resistor, and I toggle it by connecting it to VDD (3.3V) to generate a rising edge. The GPIO input works (PA0 detects voltage changes), but the EXTI interrupt never triggers. I’ve also tried forcing a software EXTI interrupt using

How does the bootloader in the STM32C071 system memory generate its 12-character USB serial number string descriptor (e.g. "205537C24236")?  I notice some similarities between this serial number and the 96-bit unique device ID at address 0x1FFF7550, but overall they look very different.  I'm asking because I would like my firmware to use the same serial number as the bootloader, and being able to use a compact serial number would be beneficial as well.Here are some examples of the 96-bit unique ID (hex formatted, with dashes after every 2 bytes) and the corresponding 12-character USB serial number:1: 7A00-2500-0150-3642-4837-3020, 205537C242362: 7B00-5700-0150-3642-4837-3020, 208737C342363: 7B00-2700-0150-3642-4837-3020, 205737C342364: 7B00-8100-0150-3642-4837-3020, 20B137C34236I looked at the documentation of the unique ID in RM0490, section 30.1, but that documentation was partially incorrect and did not help. 

I'm developing a tool to gang program STM32 products. I'm currently working on the STM32F411 (reference manual RM0383) and the FLASH_CR register SNB field mentions two sectors: user specific sector and user configuration sector. The user configuration sector is documented later in the manual but the user specific sector is only mentioned twice and not elaborated on. At a guess, I'd say its for the OTP region, but OTP can't be erased so its unclear. I've checked other RMs and some mention the user specific sector but don't elaborate on it either. Can anyone tell me what the "user specific sector" is and what I'm erasing if I set SNB to 0b1100 for an erase operation?Thanks,Keith

Hello, ST experts PB3&PB4&PB5 pins are configured to SPI_SCLK,SPI_MISO,SPI_MOSI in STM32U595VIT6. The code framework is generated according to CubeMX. It works well when communicating with its partner(TI's 32bit ADC), and HAL_SPI_Receive() is called when ADC's interrupt happened, there are no transmit opeartions all the time. The ADC need a clean SPI_MOSI signal when the chip select pin is enabled, but it seems that this pin is not driven to a certain state as the picture below.  And when the PB5 is set to GPIO, the signal is much more different from this. It is very clean. So I want to know how to set SPI_MOSI to a certain state when operating SPI. 

I'm using an STM32H733 running from HSE clock with CSS disabled.In a normal situation, the used GPIO inputs correctly read as HIGH as they are pulled HIGH by an external pull-up / LVTTL (push-pull) drive, verified with the oscilloscope.After exposure to a brief (max. 1 second) EMI event, the HSE clock fails and those GPIO inputs are pushed LOW (as if they became GPIO outputs), verified with the oscilloscope. Furthermore, the UART communication is frozen (verified with oscilloscope, TX voltage is LOW), although a high-priority task is still able to toggle the SWO pin (verified with oscilloscope) albeit at a much lower frequency. Moreover, the MCU seems to have switched to run from the HSI clock, which would explain the lower frequency.After that, when merely plugging in an STLink-v3 debugger (without even connecting to it), the MCU resumes normal operation: those GPIO pins resume working as intended and no longer push the voltage LOW, and UART communication resume

Hi.. i'm stuck with this problem for days... i'm not able to store basic data in the G030 flash memory...When i tried to erase a flash page using HAL_FLASHEx_Erase(), the FLASH_WaitForLastOperation() returns a HAL_ERROR... I did not found the issue...page to user data = 0x08007800 to 0x08007FFF (it's the last page for my STM32G030K6) Here are the main.c code (i have created a blank project to test it): int main(void) { /* USER CODE BEGIN 1 */ uint32_t FirstPage = 0, NbOfPages = 0; uint32_t Address = 0, PageError = 0; __IO uint32_t MemoryProgramStatus = 0; __IO uint32_t data32 = 0; static FLASH_EraseInitTypeDef EraseInitStruct; /* USER CODE END 1 */ /* MCU Configuration--------------------------------------------------------*/ /* Reset of all peripherals, Initializes the Flash interface and the Syst

Hello guys, I am building a product, actually am migrating my product from ATmega to STM MCUs, my requirements exactly are as follows,Cortex M0 or better core, >48 MHz2 Channel 5V DACs1 Channel CAN for OBD2 Interface2 Channel ADCs, at least 10 bit resolution8 GPIOs at leastNative USB to UART- Should be able to connect to serial terminal without external debugger.105/ 125 degrees Celsius Temperature tolerance, AEC qualification is better.I had a look into STM32G0x1 and the STM32F0 series MCUs, but am still not very sure if this is the right one. Am looking for suggestions and recommendations from the community or any employees.  

Designing custom board based on STM32F746G-DISCO.  I am using the TQFP chip, so a few less IO.   The DISCO board uses a 4 wide data, but I do not have enough pins so I will only have 1 bit wide data.  I only want to use SD card to be able to upload new firmware via bootloader. Can the bootloader work with 1 bit data?

@Tesla DeLorean  Hi! I wonder if someone can help me! I am trying to initialize a LCD screen and I have some questions. I am using a STM32F469IIT6, and it does not have enough memory in itself to hold a buffer for my screen 800x480. I did not set up a DMA to use an external memory o handle the buffer, however I have the following questions: I - What would happen if I assign a smaller buffer for the LTDC? will it still paint partial part of the screen, or it will not work at all? II - Once I set the background colors in the .ioc, give the buffer address in the configuration and do not use the function: HAL_LTDC_SetAddress(&hltdc, buffer, 0), will the buffer be filled with the colors set in the background?   I've set up a logic analyzer to try to answer these questions, however, unless I am understanding it wrongly, my buffer is so small

Hello, As a newbie to STM32 , Could some experts please answer these questions for meIs there any basic documentation that provides an overview of what software i will be needing installed on the PC? This is what is my understanding so far, there is STM32CubeIDE and STM32CubeMX, STM32CubeIDE is an eclipse based IDE and the STM32CubeMX is a standalone graphical user interface to configure the different MCU peripherals. But I read somewhere that the CubeMX is now integrated into STM32CubeIDE (so why do we need the standalone STM32CubeMX anymore)? Regarding the ST-Link debugger , do we need to get a separate standalone debugger/Flasher ? I think the discovery boards come with the debugger circuitry ..so all i need is a USB cable? Please confirm.Is it absolutely necessary to use CMSIS? , I notice that when we generate code always there is a CMSIS folder being created. Cant a project be made without the bloated HAL libraries, Is t

Hello, according to the datasheet of stm32g051f8, the absolute max power supply voltage is 4V but the fully charged 1-cell LiPo battery Voltage is 4.2V. Can I power this MCU directly from the battery?

Hi everyone,I'm currently working on a BLDC motor control project using the STM32F103RB (Nucleo-F103RB) board. I have two questions regarding handling 5V logic signals with this MCU:I need to read 5V logic-level signals from a BLDC motor's Hall sensors. As far as I understand, most GPIOs on the STM32F103RB are designed for 3.3V logic. However, I read that some GPIOs are 5V-tolerant.→ How can I configure GPIO pins in STM32CubeIDE to safely accept 5V logic inputs from the Hall sensors? Is there any specific setting in the GPIO configuration in CubeMX/IDE, or are the 5V-tolerant pins automatically handled by the hardware?I'm also using SPI to communicate with a motor driver IC. In this setup:STM32 sends 3.3V logic signals via MOSI.The motor driver IC responds with 5V logic levels on MISO.→ Is it safe to connect the 5V MISO signal directly to the STM32F103RB? Can STM32 SPI peripherals accept 5V logic levels on the MISO line without damage?

Hello,When I plug this board to my computer, appears a removable disk of 1,6 MB capacity.Is this disk accessible from the MCU? For store small data, or make a dataloggerWhere the filesystem is stored? Neither the STM32F446RE nor STM32F103CB of the STlink have enough capacity 

Hello.I am testing QSPI indirect mode using STM32G474 and STM32H753.However, I found a weird operation of QUADSPI_BK1_IO3 pin.Other pins are OK, but QUADSPI_BK1_IO3 is high states as in the redboxes.It should be low states (0).I have tested in STM32G474 and STM32H753.Both are the same.Plz let me know how to solve this issue. JG  

Hello everyoneIt's my first time messing around with STM32 microcontrollersA few days back I got a black pill (STM32F401CCU6 - https://robu.in/product/stm32f401ccu6-minimum-system-board-microcomputer-stm32-arm-core-board/) and an ST-Link V2. The black pill came with 3 buttons, namely (KEY, NRST, BOOT0) and a USB-C Port. Since the ST-Link was arriving later, I connected the black pill to my PC through USB-C. The PWR LED on the black pill turned on. I pressed down the boot0 button, clicked the nrst button and then released the boot0 button to enter the dfu mode (according to the guides I saw online) I fired up the Arduino IDE, wrote a tiny blink program, and it worked.A few days later, I got the ST-Link V2. I connected the SWCLK, SWDIO, GND and 3.3V terminals to the black pill as I found online, and connected

Hello STM32 world!Here are a few words to share our issues—now resolved—with the LAN8742A Ethernet PHY.We designed a board based on the STM32H573, featuring an Ethernet interface.We strictly followed the design used in STM32 boards, particularly the STM32H573-DK evaluation board.Unfortunately, the 100MHz auto-negotiation was unstable, making communication nearly impossible.However, our board complied with all the constraints specified by Microchip in terms of BOM, placement, and routing, including properly matched 100Ω differential lines on the Ethernet side.After losing a lot of time, we reached out to Microchip support.They responded quickly and informed us that the issue was caused by our oscillator.We were generating the 25MHz clock for both the STM and the PHY using a standard MEMS oscillator. These oscillators have a jitter of ±28ps max, which is too high for the PHY’s PLL. However, this crucial detail is not mentioned in Microc