Solved

Enabling any interrupt at the initialization triggers the WWDG_IRQHandler when watchdog timer doesn't even configured in the code whereas excluding bootloader fw doesn't seem to cause any issues, code runs fine. In the bootloader fw, I haven't configured any interrupts except the cubemx generated system interrupts such as NMI, Hardfault, svc, Pendsv, systick and RCC_CRS. I've ensured to define handler for all interrupt request in the app fw. code is developed for stm32g0b1ret6 mcuHere is my jump to app code look alike:SYS_ERR_t SYS_JumpToApplication() { // This is the offset to the application execution region // Ideally this puts the flow of control of the application to right // After the Vector table const uint32_t NUMBER_OF_INTERRUPTS = 30; uint32_t *executeAddress ; executeAddress = (uint32_t*) 0x08020000; // Creates a pointer pointing to start of Application address space void (*ApplicationFunction)(void); /// Points function pointer to its reset handler ApplicationFu

Hello,I worked until now with FreeRTOS. And in FreeRTOS there are Trace Hook Macros.Is there an equivalent on Azure RTOS ThreadX?Trace hook macros on FreeRTOS are a very powerful feature that permit you to collect data on how your embedded application is behaving.Key points of interest within the FreeRTOS source code contain empty macros that an application can re-define for the purpose of providing application specific trace facilities. The application need only implement those macros of particular interest - with unused macros remaining empty and therefore not impacting the application timingSpecifically I am looking for:traceTASK_SWITCHED_IN()Called after a task has been selected to run. At this point pxCurrentTCB contains the handle of the task about to enter the Running state.traceTASK_SWITCHED_OUT()Called before a new task is selected to run. At this point pxCurrentTCB contains the handle of the task about to leave the Running state.I looked at the Azure RTOS documentation but co

The code below links Timer1 in master mode to Timer3 in slave mode producing a 4 second toggle on PB8 and it works correctly.My question is I'm not able to follow the flow of the signal in the Timer chart below the code.If someone would show me the signal flow I would appreciate it. I have shown how I think the signal flows. Is this correct?void LinkTimer1And3(){   // GPIOB clock enable   RCC->IOPENR = 2;   // Set PB8 alternate function   GPIOB->MODER &= ~(3 << 16);   GPIOB->MODER |= (2 << 16);   // Alternate function to TIM3 CH1   GPIOB->AFR[1] &= ~0x0f;   GPIOB->AFR[1] |= 3;   // Enable TIM1 and TIM3 clocks   RCC->APBENR2 |= (1 << 11);   RCC->APBENR1 |= (1 << 1);   // Master Mode Selection - Select Update Event as Trigger output (TRG0)   TI

Hello,I followed this guide:https://community.st.com/s/article/how-does-the-threadx-semaphore-workAnd everything works.But when I try to add a modification, a HAL_UART_Transmit - HAL_UART_Transmit(&huart2, (uint8_t *)&message, 1, 10); - in one thread I always get the error 'huart2' undeclared. Well huart2 is declared in my main.c but of course not in the app_thread.c. And there are my threads. So my question is how can I solve this error? With FreeRTOS I just created threads and all the code in my main.c so there was no issue to use HAL_UART. But I am not sure how to solve it on ThreadX?

Hello,in the Semaphore example(https://community.st.com/s/article/how-does-the-threadx-semaphore-work) there is this step:Open Core\Src \main.c – you can copy and paste the code below, but please notice the" USER CODE BEGIN", to properly place the code snippet:/* Private user code ---------------------------------------------------------*/   /* USER CODE BEGIN 0 */   #define USE_UART_PRINT   void __io_putchar(char ch) {   #ifdef USE_UART_PRINT   // Code to write character 'ch' on the UART   HAL_UART_Transmit(&huart3, (uint8_t *)&ch, 1, 10);   #else   ITM_SendChar(ch);   #endif   }   /* USER CODE END 0 */The question I have is why is this step and piece of code needed? I understand the previous steps and the code that I need to add in the \app_threadx.c file. But this part I am not sure and it is not explained in the guide.Can anyone please tell why this part is needed? Thank you

I'm trying to follow the reference manual to use USART over USB via VCP (bare metal), but Realterm isn't able to read *any* data. According to the user manual, USART/VCP over USB should be supported, mentioning it's on the PC4,PC5 pins. Here's the code I'm using:#include <stdio.h> #include "stm32f303xc.h"   /* USART1 is an alternative function of GPIOC */ #define GPIOCEN (1U << 19) #define USART1EN (1U << 14)   /* USART1 -> CR1 Control Register */ #define CR1_TE (1U << 3) #define CR1_UE (1U << 0)   #define SYS_FREQ 8000000 #define APB2_CLK SYS_FREQ   #define USART_BAUDRATE 9600   static void usart_set_baudrate(USART_TypeDef *USARTx, uint32_t PeriphClk, uint32_t BaudRate); static uint16_t compute_usart_bd(uint32_t PeriphClk, uint32_t BaudRate);   void usart1_tx_init(void); void usart1_write(int ch);   int main(void) { usart1_tx_init();   while(1) { usart1_write('H'); usart1_write('i'); } }   void usart1_

Hello everybody,My name is Rego, as a hobby I work on displays, image processing, etc...I'm not very familiar with ST, but I'm really enjoying these MCU. I've already implemented RTC using VBAT and it works very well. Now I want SRAM backup,On battery it loses data I can't understand the reason for the problem, can anyone help me?thanks

helloi am working on a custom bootloader or STM32F405.the Flash process is done correctly by the Bootloader, i checked the content of the flash.the problem happens when the bootloader jumps to the application firmware which is located at adress 0x0800C000, the program goes to the Hard_fault handler function: this is what i am using to jump from the bootloader : thanks.

So firstly, I'll explain what I'm trying to achieve. My company is planning to utilize an STM32H7B0 because it's the chip that we were able to find stock of. For testing, I'm using a STM32H7A3 because it was available as a Nucleo board. The primary requirement we have is that updates to the device must have as little downtime as possible. Functionally this means that an update should be downloaded into a second image slot during normal operation, and then switched with as little downtime as possible. This would be simple using the H7B3 or H7A3, but we cannot find available parts.My current approach is to use MCUBoot to load the image into RAM from a slot contained in a QSPI NOR flash. This also enables us to encrypt the image in the QSPI for IP protection. This is also the primary reason I'm not pursuing XIP. In theory this approach should work just fine, and I've already confirmed that the software runs just fine out of RAM instead of flash.The problem I'm facing is in setting up a sa

Hi all,is it possible to connect a SDCard to the stm32f723e-disco [1] board? The webpage [1] is talking about some microSD connector, but I do not really find one. So is this a mistake on the webpage?Additionally, I would like to ask, if it is possible to expose the SDIO pins (CLK, CMD, DATA[0:3]) through the GPIO pins such as the Arduino header for example. This would allow us to connect an SDCard through a external break out board [2]. If so, would it be possible receive an example code how to do so?Ideally would be some device tree configuration how to configure the PINCTRL, because I develope the application with Zephyr RTOS [3].Thanks in advise.RegardsAndi[1] https://www.st.com/en/evaluation-tools/32f723ediscovery.html[2] https://learn.adafruit.com/adafruit-microsd-spi-sdio[3] https://zephyrproject.org/intro-to-zephyr-rtos/

A year ago I heard from a friend that there was a problem with the STM32F103's hardware I2C. All the ones I found on the internet said there was no problem with the hardware I2C of the ST, but not the F103 series. So, I have two questions. First, I want to know if the hardware I2C of the F103 series still has problems now. Second, what is the problem with the hardware I2C of the F103 that was once circulated and how to deal with it.Translated with DeepL

breakpoint reached normal;from here this jumps to "show.."and then this breakpoint seems never reached, but when going step by stepline 1354 is reached and also the following "sprintf.." , but it gets curious:when "Radio.." text is selected , is drawn on TFT and program runs on,but when"PLAY..." is selected, it never prints and "hang up" in some loop around DMA-INT-busy-ready-DMA...endless. but no hard-fault coming, just busy looping.+ i did something...probably...because some days before all this working without any problem (since many weeks) and i changed nothing here. just i made some "improvement" in grouping the "chars" and "uint8" together, just for better clarity.and then tried to improve the ESP web radio program, (-> Radio-ESP active);just today i found the other "play" hanging up...i would be happy with any idea, whats wrong here now.just...this is the asm here:

On a stm32 mcu, using HAL_I2S_Receive_DMA the clock generation is started. At first, the application went into a hard fault and nothing is subsequently written in the data receive buffer.HardFault_Handler:08000942:  push  {r7}08000944:  add   r7, sp, #0 89     while (1)08000946:  b.n   0x8000946 <HardFault_Handler+4>I corrected some settings and now it is in BUSY mode which is fine. However, now the receive data buffer does not get filled. What is the reason that the receive data buffer doesn't get filled:uint16_t i2s_receive_buffer[100];HAL_I2S_Receive_DMA(&hi2s2, i2s_receive_buffer, sizeof(i2s_receive_buffer));

Hello. I use a SwipeContainer with 2 pages. I have a button with which I want to switch to another page. But the simulator and also the STM32F7508 crashes. Does anyone have an idea to solve this problem?

Hello,i am porting a project made initially on STM32H750, but because of the semiconductor shortage on the market, the only available part was a stm32H725IGK6, which i started working on.Regarding the usb connection, i have the following pins used:PA9 - connected via 10k resistor to 5VusbPA10 - connected to ID usb pinPA11 - connected to DN usbPA12 - connected to DP usbDoes this devices supports VCP over usb? Because i am trying to work with some usb cdc examples, but so far i am not able to make it visible on the computer.

Hello,i intend to use a STM32H725IGK6 device in my design.The system will be suplied from a single 3.3 voltage source.Apart from VDD,VBAT pins, i see this device has some VDDLDO pins, and 3 VCAP pins.How shall i power the vddldo pins? Can i tie them together with VDD supply ( 3.3V) ?As i understood the vddLDO pins is supling the internal core regulator.And what about the VCAP pins? All 3 vcap pins must be connecter together with capacitor to ground? Or every vcap pin separate tied to GND via capacitor?

Could someone assist and clarify how to configure GPDMA for DAC for use the callback function HAL_DAC_ConvCpltCallbackCh1(DAC_HandleTypeDef* hdac) with STM32U575CGU6. I caught:/* Data Transfer Error Interrupt management */ if ((__HAL_DMA_GET_FLAG(hdma, DMA_FLAG_DTE) != 0U)) /* Update the DMA channel error code */   hdma->ErrorCode |= HAL_DMA_ERROR_DTE;My goal is to catch the callback functions:HAL_DAC_ConvCpltCallbackCh1(DAC_HandleTypeDef* hdac) and HAL_DAC_ConvHalfCpltCallbackCh1(DAC_HandleTypeDef* hdac)and integrate mp3 player with STM32U575CGU6. Before STM32U575CGU6 I worked with STM32F413 and my the code worked.Please assist. Thanks! Please see some parts of the code for explaining.//////////////////////////////////////////////////////////this is a configuration of DMA ///////////////* Includes ------------------------------------------------------------------*/#include "gpdma.h"/* GPDMA1 init function */void MX_GPDMA1_Init(void){ /* Peripheral clock enable *

Hello,I am using nucleo F767zi to run LwIP_HTTP_Server_Netconn_RTOS.According to the MX configurator and according to DocID029041 Rev 6 (SM32F767xx Electrical characteristics) page 143 Fpll_should be [0,95-2,1Mhz].The mentioned example generates (IMHO) .32 Mhz well outside the forementioned interval.Details:/* Enable HSE Oscillator and activate PLL with HSE as source */ RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE; RCC_OscInitStruct.HSEState = RCC_HSE_ON; RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON; RCC_OscInitStruct.PLL.PLLSource = RCC_PLLSOURCE_HSE; RCC_OscInitStruct.PLL.PLLM = 25; RCC_OscInitStruct.PLL.PLLN = 400; RCC_OscInitStruct.PLL.PLLP = RCC_PLLP_DIV2; RCC_OscInitStruct.PLL.PLLQ = 9; RCC_OscInitStruct.PLL.PLLR = 7;   // so => Fpllin = 8 Mhz / M = 8 Mhz / 25 = 0,32MX configurator comes to the same conclusion:It is a bit strange that an ST example designed (?) for the 767zi board does not comply with the specs?In the same line the example specifies:

Hello,I was trying to setup a prototyping project using the NUCLEO-L031K6 examples. But the current CubeMX version 6.7.0 does not seem so know about this dev board at all.Is this a bug or is this nucleo board not fully supported by CubeMX?

Hello everyone,I am currently trying to connect a APS51208N PSRAM to a STM32U575ZIT6 using the OCTOSPI interface. I followed the steps for the first example in application note AN5050 (chapter 5.2.5, number 1). However when I step through the program, it goes into hard fault the second it has to read from the OCTOSPI2 memory bank at 0x70000000 (tried the OCTOSPI1 bank at 0x90000000 too, same result). The debugger shows an error when trying to access this memory too.Additionally, there is a sporadic error when stepping over the EnableMemoryMapped function too, which says "Target is not responding, retrying..." and the debugger becomes non-reponsive. To be more precise, this is the line where the problem occurs (in HAL_OSPI_MemoryMapped):MODIFY_REG(hospi->Instance->CR, (OCTOSPI_CR_TCEN | OCTOSPI_CR_FMODE),                (cfg->TimeOutActivation | OSPI_FUNCTIONAL_MODE_MEMORY_MAPPED));I have tested the

I have setup STM32F429i Disco With 7" TFT 800x480 LCD (RGB) and 18 Bit Interface but I am getting very low frame rates as shown in video

Hi, I work for a CEM in the UK and we've run into a problem when reflowing an STM32H757XIH6 BGA onto a PCBA. Under optical microscope inspection we're seeing that the center of the component is further away from the PCB surface than the corners. The component is bowing in the middle, with the solder balls more visible in the centre than at the corners, I've attached the below picture to show what we're seeing. To give greater context, we're currently using an Essemtec RO300 reflow oven (3-zone), we're using Alpha OM353 Type 5 solder paste (SAC305 lead free), the components were placed using a Europlacer iineo pick and place machine, the components were baked prior to reflow as per IPC/JEDEC guidelines for MSL 3 parts.We were able to lessen the degree to which these BGAs were bending by reflowing the PCBAs a second time. While this does help decrease the warping, it also slows our production down by half so is not an ideal solution.Any tips, tricks, advice or pointers would be grea

hello. I've never used STM32 before.I'm trying to use it this time. It requires several pins of GPIO and 3 channels of I2C.I searched and the STM32F301 seemed suitable, so I designed a circuit using it.I tried setting the PIN using a setting tool called CUBEMX, but there seems to be something wrong.If I set up I2C3 of STM32F301 using cubemx, exclamation marks appear on all I2C channels.can i know what is the problem?

..