Solved

I have this timer that is configured to generate an interrupt after every 15.625 µs, i.e., when it’s period elapses. The timer elapsed callback function contains the code below. The requirement is that new data be transmitted via SPI every 15.625 µs but a single iteration of this callback function is taking 17.95 µs currently. The clock speeds are at the maximum frequency I can achieve with the internal clock. I’ve also tried to reduce the length of the code as much as I can (There’s no code in while (1)). I believe if I use an external oscillator to achieve a higher SYSCLK frequency, the callback execution time will reduce. I wanted to know if there’s anything else I can try before redesigning the board. void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim) { if (htim == &htim2) { DAC_EN; HAL_SPI_Transmit(&hspi1, &wave_data[index], 3, 1); DAC_DIS; index += 3; if (index >= 1535) { index = 0; } } }

I have the FMAC working enough to produce values readable from RDATA, but they are acting strangely and giving small positive and negative values and 0. As a minimal test, I created the below code to have X1 and X2 be all 1s. A buffer length of 18 should produce an FIR result of 18.  The below code produces a result of 0 which I read out via STLink from an unused register on TIM20.If I let my code to progress such that X1 contains real changing data, the RDATA value changes minutely above and below zero.I suspect I have addressing errors of some sort, but if I loaded only 1s into everything, I should still get 18...?Did I miss anything in the below code? //FMAC ConfigFMAC->X1BUFCFG = 0x000012DC; //no threshold, 18 buffer length, 220 as base address.FMAC->YBUFCFG = 0x000001FF; //no threshold, 1 buffer length, 255 base address.FMAC->CR|=0x00010000;//reset//write X2 vectors..18 long 12 total: 0-204 in FMAC memfor(int i=0;i<12;i++){FMAC->X2BUFCFG = 0x00001200+i*18;

I'm rewriting some of my old LL code to use HAL and having trouble getting the RTC to read time correctly. I have a simple test project where I'm calling HAL_RTC_GetTime() and HAL_RTC_GetDate() before and after a call to HAL_Delay() with the expectation that the difference in the 2 RTC calls will be something close the the HAL_Delay but that isn't happening.  I running on a custom SOM we've developed that uses a STM32H7A3LIH6Q with a 24 MHz HSE crystal and a 32.767 kHz LSE crystal. Here's my code:  #include "main.h" #include "rtc.h" #include "gpio.h" void SystemClock_Config(void); int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_RTC_Init(); /* USER CODE BEGIN 2 */ RTC_TimeTypeDef newTime1; RTC_DateTypeDef newDate1; RTC_TimeTypeDef newTime2; RTC_DateTypeDef newDate2; //Delay to get some non-zero value in newTime and newDate HAL_Delay(4500); //Initialize newTime1 and 2, newDate1 and 2 HAL_RTC_GetTime(&hrtc, &newTime

Hello All, I am new to the STM32 platform and trying to learn.  I am working with a STM32F070F706 MCU.  I would like to use the MCU internal clock to support my peripherals  (I2C and USB 2.0).  The clock configuration tool cannot resolve the issue itself, so I modified the prescalers on my own and the issue seems (to me) to be gone. However,  if I select. "Resolve Clock Issues", STM32CubeIDE tells me it can't find a solution.  It will generate code for me, but warns me:  "- Main Config: These peripherals still have some not configured or wrong parameter values: [Clock]".  Does anyone see an issue with the clock configuration shown below?  To me, everything seems to be configured satisfactorily.  

I'm the hardware guy on a 32F413 project where we have a lot of impulse noise nearby on the PCB.  Because of this I've been on a campaign to make certain that all microcontroller I/O pins are equipped with pull-up or pull-down resistors.The project has reached the stage where our quality assurance folks get cranky whenever I try to add a resistor to this PCB.  So when I find a 32F port pin that is missing a pull up/pull down resistor (as I did this week) it becomes a crisis of meetings and memos.Remind me to never work again in a medical equipment company.So I approached our firmware guy and asked him to alter his code to make certain the offending port pin is equipped with either an internal pull-up or a pull-down during his sleep mode,Firmware guy replies:  "No can do, hardware guy.  The micro is in its deepest sleep state and the port pins flap in the breeze during deep sleep.  You must fix that undefined I/O state with an external resistor. Luv ya, big guy.

I am facing an issue with my custom-made STM32F4x minimum system board. I am experiencing unstable connections with the STLink. I am using an AMS1117 for power supply, and I have found that when the STLink supplies power at 5V to the AMS1117, it cannot connect properly. Similarly, when I directly connect the 3.3V output to VDD, it still does not connect properly. Although all the voltage readings at various points are correct (VDD is 3.3V, and VCAP is 1.25V), I cannot establish a connection with the STLink. However, the STM32 is booting up normally, and the LED flashing program I previously burned is running. Additionally, I can connect and burn using the serial port, but only the STLink connection fails. I have also tested reducing the SWD frequency to 5kHz, but it still cannot connect. The logic analyzer shows some errors and no replies in the SWD response, but there are a few ‘OK’ responses as well. Occasionally, I find that I can connect properly, but it seems to happen randomly wi

I recently got a STM32F410RB. The block diagram shows "DAC1 as AF". I have been looking up the datasheet to find the alternate function pin for the DAC module in the "Alternate function mapping" table, but I'm unable to. Also, I see DAC1_OUT under the Alternate function column of the "Pin description" table. I am unable to ascertain the AF type hence. Any help would be highly appreciated. I am very new to STM32 programming, and have done it using the registers (no HAL).Here is the datasheet I'm referring to: https://www.st.com/resource/en/datasheet/stm32f410rb.pdfThanks!

Hello forumI'm trying to implement a project that takes the sensor data and saving it into a USB flash Drive,for that, I'm trying to use the MX system to activate:USBPD - Type C only, TIM2, enabled USB support USBX - Host CoreStack FS, Host Controller FS, MSCUSB_OTG_FS - Host OnlyFileX - FileX Corewhile creating the files, before even editing anything, I get a contradiction error between ux_port.h and fx_port.h,if I try to delete one of them it disables the entire respective library.Is there anything I'm doing wrong? any working example of what I'm trying to do?I really appreciate any help you can provide. 

I am using STM32H743IIT6 MCU to drive HDMI display using LTDC peripheral and Texas Instrument TFP410 for RGB to HDMI conversion. Issue I am facing is I use external crystal as clock source then I see disturbance on my HDMI monitor and its display blinks randomly, say screen is proper for some 5-10 sec then it will flicker and turn off and on then again be stable for some time and these repeats. My guess is that some HDMI timing related parameters are not matched and that's why this behavior on monitor. Surprisingly, this issue resolves if I use internal CSI RC oscillator as clock source.  I even tried doing the PCB layout again using an external agency, but same issue persists in that layout as well. What could be the issue here that it works with internal CSI RC clock source and not external crystal ? Please find below related parameters configured in my project. I have also attached my projects CubeMX .ioc file for reference.Clock Source: External Crystal 25MHzFMC: External

I am using STMCubeIDE v1.7 on MacOS 10.15.7 and connecting to my target via an STLINK V3. I updated CubeIDE to v1.7 and it suggested an update to the STLINK. Since doing that update I am not able to connect to my target (STM32F405). Errors given are:STMicroelectronics ST-LINK GDB server. Version 5.9.1Copyright (c) 2021, STMicroelectronics. All rights reserved.Starting server with the following options:    Persistent Mode      : Disabled    Logging Level       : 1    Listen Port Number     : 61234    Status Refresh Delay    : 15s    Verbose Mode        : Disabled    SWD Debug         : Enabled    InitWhile         : EnabledTarge

Can failed to reinit after deinit. 1. Two cans was used for my projects which was generated by stm32cubemx 2. after run for a short while , I turn off both cans by HAL_CAN_DeInit 3. then I reinit both cans by MX_canx_init and found it failed in HAL_CAN_Init 4. I have tried to pull both can rx and tx pins but does not work 5. Before reinit I have checked both rx and tx pins is high Questions: 1. Possible reason for can reinit failed. 2. Any checlist for reinit?   Thank you & BR

If the LSE 32.768KHz crystal is disturbed after the system starts with MSIS auto calibration, and the MSIS clock is used by the PLL for the SYSCLK, the frequency of SYSCLK loses its 0.25% accuracy and starts to drift.Is there any register or interrupt that can be used to detect this situation (MSI_PLL_UNLOCK and LSECSS not available for Rev X - RM0456 Table 184 & 187), and if so, what steps can re-setup the clock to be auto calibrated once again?I can simulate it by touching the LSE crystal when it is running, the SYSCLK changes from 159.91Mhz (stable) to about 161.59 - 161.2 (unstable), even though the 32.768khz returns to being stable after the disturbance.I am currently evaluating using both the NUCLEO-U575ZI-Q board and the B-U585I-IOT02A board, both with Rev X parts fitted. Is Rev X currently in production, or is there a newer/fixed revision available?

Hello @STTwo-32 ! Thank you so much for clarifying everything! I am really thrilled with the STM32WBA Nucleo board. Could you please let me know, if it is compatible with the FP-AUD-BVLINKWB1 pack? If not, are there any code examples on how to implement Bluetooth audio on it? Such as pairing with headphones et cetera?  

Hello,I am using the STM32CubeIDE to write software to test the STSAFE (Nucleo-F401RE + Nucleo-SAFEA1). I am trying to get a basic software working and trying to use one of the STSAFE functions, but I am running into a strange error when I try to compile it. Based on all the searches I've done, this is typically a linker issue. However, I verified that the file that declares this function. I think I'm getting tunnel visioned, but I cannot see what part I haven't linked properly. Does anyone know where else to look? Open Declaration:

Hello!I'm porting a working code from H750VB to H730VB, generating a new HAL core from STM32CubeMX, but right after entering on "SystemClock_Config" function at debug mode, I've got the message "Break at address 0x46bd3718 with no debug information available, or outside of program code". Going step-by-step, the issue happens on "HAL_RCC_ClockConfig", at the second "D1PCLK1 configuration" calling:if ((RCC_ClkInitStruct->APB3CLKDivider) < (RCC->D1CFGR & RCC_D1CFGR_D1PPRE)){ assert_param(IS_RCC_D1PCLK1(RCC_ClkInitStruct->APB3CLKDivider)); MODIFY_REG(RCC->D1CFGR, RCC_D1CFGR_D1PPRE, RCC_ClkInitStruct->APB3CLKDivider);}I'm using the same custom board and pinout as H750 one and the app is quite simple: a few GPIOs, UART and SPI. I've also tried just a "blink LED" code, same break on "SystemClock_Config". Two different boards, same issue.Did anyone face the same problem?Thanks!

Please, answer was anyone trying to use RTC with the G071RB microcontroller? I am powerless now. The code generated by cube does not initialize RTC. I checked the entire initialization procedure if it is consistent with the documentation. Everything is correct and does not seem to be a mistake in HAL. The problem for me in the RTC_EnterInitMode function is the line SET_BIT (hrtc-> Instance-> ICSR, RTC_ICSR_INIT) ;. The INIT bit and the INITF flag are not set so that RTC does not enter the initialization mode. I am asking for an answer because the problem is not in my code only in the code generated by the cube. Is RTC initializing for you or is the problem in my microcontroller? I will add that there is no difference which source of RTC clock will be chosen.

Hello everyone, I am Erdem.I am trying to use FlexCan with the SPC560B-DIS development board. I ran the example project "SPC560Bxx_RLA CAN Test Application for Discovery," but I didn't want it to operate in LoopBack mode. When I disabled the LoopBack mode, I couldn't read anything from the PeakCan cable. I created a new project from scratch and wanted to send a simple CanBus message, but there was no communication. I am sharing the settings and code from my project in the images. I would be very grateful if you could help. Thank you.    

STM32CubeMX - STM32 Device Configuration ToolVersion: 6.10.0-RC9Build: 20231120-2037 (UTC)  Unless I cannot see the forest for the trees, the prescale setting is not there.  /** Common config */ hadc3.Instance = ADC3; hadc3.Init.Resolution = ADC_RESOLUTION_16B; hadc3.Init.ScanConvMode = ADC_SCAN_ENABLE; hadc3.Init.EOCSelection = ADC_EOC_SEQ_CONV; hadc3.Init.LowPowerAutoWait = DISABLE; hadc3.Init.ContinuousConvMode = DISABLE; hadc3.Init.NbrOfConversion = 3; hadc3.Init.DiscontinuousConvMode = DISABLE; hadc3.Init.ExternalTrigConv = ADC_SOFTWARE_START; hadc3.Init.ExternalTrigConvEdge = ADC_EXTERNALTRIGCONVEDGE_NONE; hadc3.Init.ConversionDataManagement = ADC_CONVERSIONDATA_DMA_CIRCULAR; hadc3.Init.Overrun = ADC_OVR_DATA_OVERWRITTEN; hadc3.Init.LeftBitShift = ADC_LEFTBITSHIFT_NONE; hadc3.Init.OversamplingMode = DISABLE; if (HAL_ADC_Init(&hadc3) != HAL_OK) { Error_Handler(); } /** Configure Regular Channel */ sConfig.Channel = ADC_CHANNEL_TEMPSENSOR;

My project was generated a few months ago (LWIP + FREERTOS on M7). The project was working without an issues. A few days ago I wanted to include CAN interface and after converting IOC to latest version, I have issue: LWIP was deactivated. I am not able to activate LWIP just for M7. LWIP can be activated M7 + M4. If I active LWIP on both cores, I am not able to use FREERTOS

Posted on June 26, 2014 at 16:31 Hi, I tried to configure my STm32F207 using the ''Cube'' to use the CAN2 and I found a bug. This is the initialization code generated by the ''Cube'': void HAL_CAN_MspInit(CAN_HandleTypeDef* hcan) { GPIO_InitTypeDef GPIO_InitStruct; if (hcan->Instance==CAN2) { /* Peripheral clock enable */ __CAN2_CLK_ENABLE(); /**CAN2 GPIO Configuration PB12 ------> CAN2_RX PB13 ------> CAN2_TX */ GPIO_InitStruct.Pin = GPIO_PIN_12|GPIO_PIN_13; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_LOW; GPIO_InitStruct.Alternate = GPIO_AF9_CAN2; HAL_GPIO_Init(GPIOB, &GPIO_InitStruct); /* Peripheral interrupt init*/ /* Sets the priority grouping field */ HAL_NVIC_SetPriorityGrouping(NVIC_PRIORITYGROUP_0); HAL_NVIC_SetPriority(CAN2_RX1_IRQn, 0, 0); HAL_NVIC_EnableIRQ(CAN2_RX1_IRQn); /* Sets the priority grouping field */ HAL_NVIC_SetPriorityGrouping(NVIC_PRIORITYGROUP_0); HAL_NVIC_SetPri

Why is MX_MBEDTLS_Init called twice at startup when using stm32CubeMx code generation?

Hi,I'm using the IIS3DWB accelerometer to get triaxial waveform.I just want to know what is the best approach to detect over range.I tried to compare sample by sample in each channel with the maximum possible positive value (>32766) and the maximum negative value (<-32767) but I didn't get overflow detection when the peak acceleration > range.When I set the limits to +/-16384 (half) my detection routine works (with an instantaneous acceleration value > range/2).What is the measured acceleration value when the acceleration is over the full-scale range?Does the accelerometer limit the the value to the maximum?Best regards 

I have a working project with its .ioc file.Now I need to port the project codebase to another project that uses exactly the same processor, but with different pinout: the peripherals in the project will be the same, mapped on some other pins.I need to have a complete codebase with its ioc file for both projects.What is the best course of action to duplicate the original project?It would be ok if I'll have to mess around with cubeMX to manage both ioc files.

Hey All, I cannot seem to uncheck the option "save power of non-active UCPD - deactive Dead Battery pull-up" Everytime I generate code I have to manually comment out (disable) (HAL_SYSCFG_StrobeDBattpinsConfig(SYSCFG_CFGR1_UCPD1_STROBE | SYSCFG_CFGR1_UCPD2_STROBE);)to make it workKind Regards,Sparsh

HII use Cube MX with STM32U585RIT6. When I use ADC4 In3 In4 In9 In22 and In23, the  channel In9 is not properly initialised. I must add this manually :/* USER CODE BEGIN ADC4_Init 2 *//** Configure Regular Channel*/sConfig.Channel = ADC_CHANNEL_9;if (HAL_ADC_ConfigChannel(&hadc4, &sConfig) != HAL_OK){Error_Handler();}/* USER CODE END ADC4_Init 2 */With the STM32U585VIT, I have the same problem with channel9 dont work Then it work. I have this probleme in CubeMX from 6.9 to 6.11 versions.