STM32 MCUs Software development tools

Here's the problem when updating STM32CubeIDE from the Help->Check for Updates option on a Linux Mint 20.3 (Una).Any hint please?gaston

Are there any plans to repair the CubeMX system and to re-enable the configurations of STM32G4 firmware version 1.2.0? I tried version 1.3.0 and 1.4.0, and both don't allow to configure an OPAMP as follows: hopamp5.Instance = OPAMP5; hopamp5.Init.PowerMode = OPAMP_POWERMODE_NORMAL; hopamp5.Init.Mode = OPAMP_PGA_MODE; hopamp5.Init.NonInvertingInput = OPAMP_NONINVERTINGINPUT_IO2; hopamp5.Init.InternalOutput = ENABLE; hopamp5.Init.TimerControlledMuxmode = OPAMP_TIMERCONTROLLEDMUXMODE_DISABLE; hopamp5.Init.PgaConnect = OPAMP_PGA_CONNECT_INVERTINGINPUT_NO; hopamp5.Init.PgaGain = OPAMP_PGA_GAIN_32_OR_MINUS_31; hopamp5.Init.UserTrimming = OPAMP_TRIMMING_FACTORY;This was generated with CubeMX version 5.6.1 and STM32G4 firmware version 1.2.0. I am using this in an actual project and because of the bugs in 1.3.0 and 1.4.0 can't change to newer versions.

STM32CubeIDE 1.10.0 was released today on st.com as well as an in-tool update patch.Caution: The in-tool update does not allow updating debug probe drivers and ST-LINK server tool. Full installer is required for this.What is new in 1.10.0?Target support updated in-sync with STM32Cube ecosystem in general. In particular:New STM32MP131, STM32MP133, and STM32MP135 microprocessors New STM32WBxxxx microcontrollers – New STM32L4xxxx microcontrollersNew STM32MP135F-DK Discovery kitNew B-WB1M-WPAN1 Discovery kitNew STEVAL-ASTRA1B and STEVAL-STWINBX1 Evaluation boardsEclipse® update 2022-03Including dark theme support improvementSEGGER J-Link update 7.66Micro

Processor STM32F746ZGTHello,When I use FreeRTOS (CMSIS_V2) in STM32CubeIDE 1.9.0, I get the prompt when generating code (as in the previous versions):The USE_NEWLIB_REENTRANT must be set in order to make sure that newlib is fully reentrant. The option will increase the RAM usage. Enable this option under FreeRTOS > Advanced Settings > USE_NEWLIB_REENTRANTIf I perform the requested setting, as I did in the previous versions, the code is generated without any hint. However, when compiling, I get the following error message:c:\st\stm32cubeide_1.9.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.10.3-2021.10.win32_1.0.0.202111181127\tools\arm-none-eabi\bin\ld.exe: c:/st/stm32cubeide_1.9.0/stm32cubeide/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.10.3-2021.10.win32_1.0.0.202111181127/tools/bin/../lib/gcc/arm-none-eabi/10.3.1/..

..

(((Yes, I'm still using Atollic, STM32CubeMX, and HAL. Now is not the time in this project to change these things.)))I'm individually driving my AN0..AN5 analog inputs, and I've confirmed that the ADC results are showing up in ADC_DMA_BUFFER[1..6]. I would have expected them in ADC_DMA_BUFFER[0..5]. Meanwhile, I'm configured for 7 conversions, the 7th being AN14. It's not showing up in either ADC_DMA_BUFFER[6] (the normally expected location) or ADC_DMA_BUFFER[7] (an otherwise buffer overflow location that was hinted at by the behavior of the first 6 channels). Finally, I'm unable to test if AN14 is erroneously going into ADC_DMA_BUFFER[0] (which would be a looped-back index location).I've analyzed everything and I believe it's all lined up properly. Why might this be happening? Below is select cut/paste/images from my code and circuit. Thanks in advance for your help!----------------------------------

STM32CubeIDE v1.9.0 (and 1.8.0) is generating MX_DMA_Init() AFTER MX_DAC_Init() and this causes the functionality (DMA driving data to the DAC to play a wav file) to fail.

Hello Everyone,I was trying to communicate my board with a device over USART module. My MCU is STM32G051K8TX. But I hadn't been succeed until I notice a STM32CubeMX bug. Let me show you:I used alternate function of PA9, and PA10 for USART_TX and USART_RX from STM32CubeMX. When I generate code, it prepares HAL_UART_MspInit code without alternate function of the USART pins. I intert extra code inside the /* USER CODE BEGIN USART1_MspInit 1 */ and /* USER CODE END USART1_MspInit 1 */ tags. It reinitialize the PA9, PA10 as alternate fuction USART.You can see the code below:/** * @brief UART MSP Initialization * This function configures the hardware resources used in this example * @param huart: UART handle pointer * @retval None */ void HAL_UART_MspInit(UART_HandleTypeDef* huart) { GPIO_InitTypeDef GPIO_InitStruct = {0}; RCC_PeriphCLKInitTypeDef PeriphClkInit = {0}; if(huart->Instance==USART1) { /* USER CODE BEGIN USART1_M

Hi,I am using ADC function on STM32H750IBK6 and everything worked perfectly.But after migration to CubeIDE v1.9.0 and SDK v1.10.0, ADC can't work any more.From "Clock Configuration" view, "ADC clock mux" is gray out for some reason.Related clock source selection has been removed after code generation.Is there any one can help me how to enable "ADC clock mux" correctly?T

Hello,I have recently encountered an issue after updating STM32CubeMX to the most recent version 6.5.0.The said version seem to have missing ADC "Clock Prescaler" in the configuration menu and ADC clock generation is locked disabled in the "Clock Configuration" menu even when ADC is set enabled.The issues are gone when downgraded to 6.4.0.Please have a look on this issue.Thank youBoard: Nucleo STM32H755ZI-QFirmware: STM32Cube FW_H7 V1.10.0Image 1: No "Clock Prescaler" menu in the ADC configuration menuImage2: ADC clock configuration is locked disabled even when ADC1 is set enabled.

The problem exists for ADC1, ADC2 and ADC3. It works with Firmware V1.16.0

Hello,I want to report that using the STM32CubeMX functionalities with an STM32G061 I found that configuring the USART1 using PA9 and PA10 there's an issue that prevents it to work properly.More precisely, in the generated function HAL_UART_MspInit, the alternate function is not configured for UART 1. I paste a snipped where the UART1 and UART2 are configured:void HAL_UART_MspInit(UART_HandleTypeDef* uartHandle) {   GPIO_InitTypeDef GPIO_InitStruct = {0}; if(uartHandle->Instance==USART1) { /* USER CODE BEGIN USART1_MspInit 0 */   /* USER CODE END USART1_MspInit 0 */ /* USART1 clock enable */ __HAL_RCC_USART1_CLK_ENABLE();   __HAL_RCC_GPIOA_CLK_ENABLE(); /**USART1 GPIO Configuration PA9 ------> USART1_TX PA10 ------> USART1_RX */ GPIO_InitStruct.Pin = GPIO_PIN_9|GPIO_PIN_10; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_LOW;

I am using an STM32F429IIT6 with SDRAM connected to SDRAM 2, SDCKE1+SDNE1, Byte enabled "Disabled" do to the pin conflict with the LTDC settings for the display, a 480x272 RGB888 display connected to LTDC. I can read and write the SDRAM with code such as  uint32_t *externalRAM = 0xd0200000; const uint32_t size = 120000; //write external RAM for(int i = 0; i < size; i++) {   externalRAM[i] = i;}reading the SDRAM back in the same way confirms ability to read and write SDRAM. If I fill the frame buffer after setting up the rest of the system using the generated code from STM32CubeIDE the SDRAM data is written to the display showing the solid color I programmed into the SDRAM. I realize since all the values are the same in SDRAM I don't know yet if the the DMA transfer is 16 or 32 bits wide yet. But most of the system is working.I can see with the debugger that the SDR

An error occurred while collecting items to be installedsession context was:(profile=STM32CubeIDE, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).No repository found containing: osgi.bundle,com.st.stm32cube.common.mx,6.2.1.202103241236No repository found containing: osgi.bundle,com.st.stm32cube.common.mx.oss,6.2.1.202103241236No repository found containing: osgi.bundle,com.st.stm32cube.common.mx.stinsider,6.2.1.202103241236No repository found containing: osgi.bundle,com.st.stm32cube.common.projectcreation,1.6.1.202103171520No repository found containing: osgi.bundle,com.st.stm32cube.ide.documentation,1.6.1.202103260948No repository found containing: osgi.bundle,com.st.stm32cube.ide.mcu.ide,1.6.1.202103171520No repository found containing: osgi.bundle,com.st.stm32cube.ide.mcu.rcp,1.6.1.202103171520No repository found containing: osgi.bundle,com.st.stm32cube.ide.mpu.linux.ide,1.6.1.20210326

So in trying to sort an unrelated problem out, I updated to 1.9.0 and have been having serious trouble with it all morning (I've restarted it about 10 times and counting).In selecting "List compatible MCU's" it would load maybe 30% then lock up / stop, sometimes show "Running low memory", and eventually crashed with an "Out of memory" error despite the fact my PC has loads of free memory (>16Gb free)After a fair bit of googling and digging I modified the .ini file (C:\ST\STM32CubeIDE_x.x.x\STM32CubeIDE\stm32cubeide.ini for anyone playing along at home) to increase the defaults by about 4x, which seemed to help a little but it's now sat here thrashing my CPU to death loading a list of 103,000 MCU's which it appears I can do nothing about (EG set filter options) until it's finished.Seriously ST, this is a mess. Which programmer thought it would be a good idea to load gigabytes of data up front before we can select any options? I'm on

Hello I am using stm32h750vb. I want to use an interrupt to read the adc value, but in the interrupt and dam mode the adc unit does not work. In polling mode, it shows the correct value only once after the microcontroller reset and then a constant value. Only displays the correct value if I use the following function to read the adc value. Using this method causes the microcontroller to heat up in a short time.​uint16_t adc_read_value(void){ static uint16_t Value = 0; HAL_ADC_Init(&hadc1); HAL_ADC_ConfigChannel(&hadc1, &sConfig); HAL_ADCEx_Calibration_Start(&hadc1, ADC_CALIB_OFFSET, ADC_SINGLE_ENDED); HAL_ADC_Start(&hadc1); HAL_ADC_PollForConversion(&hadc1, 100); Value = HAL_ADC_GetValue(&hadc1); HAL_ADC_DeInit(&hadc1);   return Value; }​​ I have used the adc unit several times in the stm32f1 and stm32l1 series but have not encountered such a problem. I used

 "A regression was detected in the previous STM32CubeMX version 6.3.0 (STM32CubeIDE Version: 1.7.0 ) generating a wrong order of initialization functions.This issue was fixed in the latest STM32CubeMX version 6.4.0. Thus, newly created project with this version will generate the correct initialization functions order."https://community.st.com/s/question/0D53W00001EzCmCSAV/mxdmainit-order-in-the-mainc-file-generated-by-stm3

Hello!I want to make a basic remote control with the SPSGRF-915 module, but as far as I can understand I need the X-CUBE-SUBG1 extensión software to control it.I have already downloaded the software from ST (en.x-cube-subg1_firmware) and on the STMicroelectronics tab from the Embedded Software Package Manager in CubeMX, I can´t find the extensión package, so I tried to upload from the local .zip previusly downloaded but the following error appears:The following file is not recognized as being valid ...Thanks for your attention

When I migrate my Project to CubeMX 6.5.0 LwIP gets disabled and cannot longer be enabled as long as mbedTLS is enabled. FreeRTOS is enabled and this configuration worked fine with CubeMX 6.4.0.I tried to cycle all relevant settings, switched cores but haven't found a way to get both mbedTLS and LwIP to be enabled.How can I fix this?

..

With this configuration :nbr of conversion : 2scan conversion mode : EnableContinious Conversion Mode : cannot set to Enable !!!Discontinious Conversion Mode : ucannot set to Disable !!!Unless I am mistaken, I see no indication in the STM32U5 reference manual that does not allow this configuration (Scan conversion and Continuous Conversion).I guess a cubeMX bug?STM32CubeIDE 1.9.0, STM32CubeMX : 6.5.0-RC4,STM32U5 package version 1.1.0.

When trying to use the "List pinout compatible MCUs" feature to move an existing CubeMX project to a different MCU I get incorrect clock calculations in the clock configuration tab.For example, starting with a project for STM32L451RETx and then using "List pinout compatible MCUs" to switch to an STM32L451RCTx I lose the existing clock configuration and have to redo it manually.In the original project it looked like this:after switching MCU and reconfiguring I get this:

Dear all, I used STM323H742VGT in one of my cards and I would like to configure it with ST Cube MX V6.5.0. According to the reference manual ADC clock source and pre-scaler can be set using ADCx_CCR register.I would like to use asynchronous clock source which is adc_ker_ck_input. However, I couldn't find any setting in ADC section of CubeMX. There aren’t any settings also for pre-scaler. I am familiar with STM32F7 and I could select pre-scaler over Cube MX.On the other hand, ADC_Clock is not enabled in Clock Configuration page in Cube MX. I don't know why. Normally, if I set a peripheral, related clock is enabled and I can change parameters in Clock configuration page. I added some screen shuts and if you can help me, it would be great. If I cannot set in ST cube MX, I need to write driver for it. I prefer ST Cube MX should do it for me. I may miss one thing to set and spend days to figure out.Best Regards

I have problems porting a H743Zi2 code to a H753. When using the .ioc file editor with the ADC the option to set the ADC clock prescalar is not present for the H753. It is there for the H743. The coeersponding line in the main.c code is not present either. Not surprisingly, a simple test program that was a polled ADC read did not work. Copying the setup code for the ADC and placing it after /* USER CODE BEGIN ADC1_Init 2 */ and then manually edting in:hadc1.Init.ClockPrescaler = ADC_CLOCK_SYNC_PCLK_DIV4;  // <-- Missing lineafter the line:hadc1.Instance = ADC1;was a workaround that worked.Is there a was to automatically add in such corrections? I need to for my pulse spectroscopy application to poke about quite a bit with the hardware configuration. So it takes a lot of time.

Dear All,I would like to report an issue in Cube MX V6.5.0. I have an .ioc file which is built with previous version of Cube MX. It was migrated to the latest version and I realized IWDG Timer Block is not seen in Clock configuration page. I thought it is about migration because I know that Cube MX V6.5.0 has some bugs and they were reported already. I re-built a project from scratch with V6.5.0 and IWDG timer block connected to LSI. I saved the new project and closed it. However when I re-opened the project, it disappered again. Please fix the issue. It is not about migration because I created a new project and it was ok. However when I saved and closed the project and re-opened it disappered.Regards