STM32CubeMX (MCUs)

Posted on October 10, 2017 at 23:15I know it's kind of stupid. But I still want to make sure if the repository folder can be changed? Because the capacity of my C is not big enough.#stmcubemx

Posted on November 07, 2017 at 12:53Hello everyone, In this project I just want to use the user button to toggle a LED on my board. The model is designed by using Simulink and initialization codes are generated by STM32CubeMX. During the experiment, I was facing to a big problem: I don't know how to correctly set the sample time of Simulink model Ts and how to correctly make the clock configuration in STM32CubeMX. Fig. 1: Simulink Model Sample Time

Posted on November 02, 2017 at 14:15Hello,I'm new to this exiting world of MCUs.I tried many installs from scratch, did all the available updates I found, but I still can't see my 'STM32F407G-DISC1' in the list of boards in STM32CubeMX.I find 2 'STM32F4DISCOVERY' with the only difference about the on-board ST-LINK version, one is 'V2', the other is 'V2-1'.Can someone give me a hint on how to get my board listed in the tool, please ?I also noticed that the boards listed are labeled 'MB997A' (top right of the picture), where mine is 'MB997D'.many thanks for your support,Cheers.PS : I read through similar questions, but nothing gave me the solution to add this specific board to the list.#stm32cubemx* #stm32f407g-disc1

Posted on November 02, 2017 at 18:18I am using NUCLEO-F767ZI board where I observe that when I use the internal clock (HSI), the mcu runs fine, but when I configure the cubeMX project to run on external 8MHz clock (HSE), the mcu fails to run. Following is the code generated by CubeMX when HSE is selected:/** System Clock Configuration*/void SystemClock_Config(void){RCC_OscInitTypeDef RCC_OscInitStruct; RCC_ClkInitTypeDef RCC_ClkInitStruct; RCC_PeriphCLKInitTypeDef PeriphClkInitStruct;/**Configure the main internal regulator output voltage */ __HAL_RCC_PWR_CLK_ENABLE();__HAL_PWR_VOLTAGESCALING_CONFIG(PWR_REGULATOR_VOLTAGE_SCALE1);/**Initializes the CPU, AHB and APB busses clocks */ RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE; RCC_OscInitStruct.HSEState = RCC_HSE_ON; RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON; R

Posted on November 02, 2017 at 17:16Hi everyone,I have been just getting started with the model-based design using MATLAB/Simulink with the Target Support Package for my STM32F407VGTx Discovery Board.But with the configuration for the MCU using STM32CubeMX done, there is no input port in the ADC_Read block availible.In my STM32CubeMX Project (in the attachment, Version 4.22.1) I actived three channels of ADC1 (IN0, IN1 and IN2). Principally, these three channels must be availible in my Simulink project. However, as shown below, CH0, CH1 and CH2 couldn't be checked.Is there anyone who can help me to solve this problem?Thank you!

Posted on January 23, 2017 at 10:02The latest Version of CubeMx (4.19.0) the 'FLASH_WaitForLastOperation' function causes errors if the HAL_GetTick() function is near its rollover point. The cause seems to be 'uint32_t timeout = HAL_GetTick() + Timeout', which causes an error of the comparison 'HAL_GetTick() >= timeout'. With a 1ms resolution the error happens after 49 days, which could cause a serious problem in real systems. It would be nice, if this could be corrected.best regardsThomas#cubemx

Posted on October 26, 2017 at 10:35Today I have just updated my STM32CubeMX to the 4.23 version.I migrated the project I am using currently. It uses a STM32F767VITx. So far, I was using the 4.21.1 version of STM32CubeMX.Today I made some changes in my STM32CubeMX project in order to change some settings. But when I was about to commit this changes to GIT, I noticed the file ''rtc.c'' (generated automatically by STM32CubeMX and never edited manually) had changed. So, I opened this file in order to see what it changed.In the image below, you can see the problem: STM32CubeMX now generates the variables ''sTime'' and ''sDate'' as global variables, but never initializes them. So all the settings you configure in the STM32CubeMX are never used. I looked for this variables over all my project and I didn't find any call or use, so these two variables are never initialized to any value.This error (I guess it is an error) have appeared

Posted on July 21, 2017 at 11:02I am trying to create a project for either the L469 Discovery or Nucleo-144 board using CubeMX.My setup is the following:CubeMX 4.22.0L4 Firmware v1.8.1Using STM32 AC6 latest versionIt appears as though CubeMX does not populate the FreeRTOS related directories with the required source files.Doing the same thing for an F4 board I have no problem, so I'm assuming it is an issue specific to either cubeMX or the latest version of the L4 firmware.Does anybody else have this issue?Anthony. #cubemx-project #stm32l4 #bug #cubemx #freertos

Posted on October 25, 2017 at 18:38I'm using an STM32F746VGT6 microcontroller configured from STM32CubeMX for all the clocks and I'm getting roughly 220% higher clock rates reported for SystemCoreClock when compiled. For instance I have an HSE crystal at 11.2896MHz with the following main PLL settings:PLLM /11PLLN *234PLLP /2PLLQ /5I have selected HSE for PLL source and PLLCLK as System Clock Source. Doing that in STM32CubeMX yields 120.080291MHz.However, after SystemClock_Config(), SystemCoreClock = 265909059.Due to that discrepancy, the microcontroller thinks it's working 220% faster than it actually is so all my timings are off by that much.My first clue was when I configured SAI_BlockA1 and measured MCLK to be double than expected.  Then testing an output with HAL_Delay(50) gave me actual delay of 110ms.Has anyone else seen this issue and what could be the problem here?

Posted on June 27, 2017 at 16:27Hello ST team,I think the STM32CubeMX code generator has a big problem with screen resolution. I'm using a laptop with 4K display, so my CubeMX appears like following screenshots, which are annoying in many cases: Almost half of most table rows appear vertically, the texts sometimes are too small or too large and so on:Can this problem fix?

Posted on October 17, 2017 at 07:54Hello GeeksI'm new bie with at STM, I need to read at-least 3 adc channel of STM32L152RC having interruptI've used Cubemx and generate the code having property ofscan->EnableNo of Conversion->3Global interrupt ->EnableRank from 1-3->48 cycle Sampling rateNow the problem is when i compile and load the code on MCU then it's working and shows 4095 Samples for 3.3V attached at IN0 but this result is same for all first 3 channel! it means all remaining 2 configured channel shows 4095 samples even they are floating!here is the debug logsADC_raw[0]--->4095 ADC_raw[1]--->4095 ADC_raw[2]--->4095 -----------------------------------------------ADC_raw[0]--->4095 ADC_raw[1]--->4095 ADC_raw[2]--->4095 -----------------------------------------------ADC_raw[0]--->409

Posted on October 24, 2017 at 06:21When I meet a bad block in a NAND flash,it will stop here forever.The 'tickstart = HAL_GetTick()' should put in front of 'while(HAL_NAND_Read_Status(hnand) != NAND_READY)'.#nand-flash-driver #stm32cubemx #bug

Posted on October 17, 2017 at 12:49Hi All,in order to build new project (using STM32l073v8t processor) folder, I used the STM32cubeMX.I've set all IOs, change the clock tree using its UI and etc' according to my project.When I check the generated code source folder I see that all files are updated while the system_stm32l07xx.c is old and doesn't modify also I change the clock tree parameters.Also, i can't find clock generator tool for this processor family.Please advise how should I modify the clock file.Thanks in advance,Moran.#stm32l073v8t #cubemx

Posted on July 25, 2017 at 11:08I found two issues with the latest (and updated) STM32CubeMX when generating a Makefile project for STM32F334 Nucleo64 board.1. I selected only the LL drivers but the Makefile had the 'USE_HAL_DRIVER' definition, so the project wasn't compiling (because there was no HAL driver files in the project as I have selected 'Copy only the necessary library files...' in the settings)2. The SystemClock_Config function had this line which was giving an error because RCC_LSEDRIVE_LOW is a HAL definition:LL_RCC_LSE_SetDriveCapability(RCC_LSEDRIVE_LOW);I had to change it to:LL_RCC_LSE_SetDriveCapability(LL_RCC_LSEDRIVE_LOW);Thanks!#ll #stm32cubemx

Posted on December 24, 2016 at 21:51Using STM32CubeMX version 4.18.0 on Windows 10 Pro (build 1607) with an UHD (4K) display results in tiny toolbar icons and a very tiny Clock Configuration diagram.  Please see attached screen capture image.  Not that this application window is not maximized.Is there any way to scale these images within the STM32CubeMX application so that I can see them with human eyes?Additionally, the screen looks the same even when I drag the STM32CubeMX application to a different, lower-resolution monitor.Any help would be appreciated.Thanks,Dale#stm32cubemx

Posted on June 03, 2017 at 20:12I have a board which was designed to use the STM32L433CCU6 and am attempting to use it with an STM32L452CEU6.  The board works perfectly fine with the 433, but I am struggling a bit with the 452.  The problem I was facing is that I am attempting (and failing) to use the HSI as the clock source for LPUART1.  The UART was transmitting but not being understood, and reporting errors when attempting to read.After a bit of work, I have it working fine with the PCLK1 (via HSE/PLL) at 38400bps, but I need to operate at 9600bps.   This cannot be done with an 80MHz clock.In order to see what was going on, I connected HSI to MCO and measured the frequency.  At an ambient temperature of 21C, the HSI on one MCU is running at 13.89MHz and another at 14.29MHz.  That seems excessively out of spec to me.  Doing some digging, it appears that the HSI is not being calibrated properly.

Posted on March 21, 2017 at 10:16Hi I have a NUCLEO F746ZG board. How I initialize ethernet using CubeMX and using MQTT Protocol to transfer my data to MQTT broker ?#ethernet #f746zg #mqtt #nucleo #cubemx

Posted on October 13, 2017 at 21:38NucleoF722ZE board, Stm32CubeMX ver 4.22.1, Eclipse Version: Neon.3 Release (4.6.3)I wanted to setup TIM6 as timer interrupt for 400usec sampling loop. In CubeMX : TIM6 clocked at 1Mhz and ARR = 400, TIM6 Configuration/NVIC settings/Enabled (TIM6 global interrupt), then in NVIC Configuration/enabled TIM6 global interrupt with Preemp Priority=10 and Sub Priority=0. Then Generate code. The generated code seemed to be OK, and it also had  set NVIC interrupt priority and enable as below.HAL_NVIC_SetPriority(TIM6_DAC_IRQn, 10, 0);HAL_NVIC_EnableIRQ(TIM6_DAC_IRQn);I added code to toggle the LED inside the ISR void TIM6_DAC_IRQHandler (void) and it never triggered.Result:TIM6  was counting OK (read TIM6.CNT and outputted on PWM pin for monito

Posted on October 05, 2017 at 08:56Hi all,I am using the latest stm32cubemx with a stm32f446re Nucleo board and I am trying to access a microSD card. I have soldered headers to a microSD to SD adaptor and connect all the pins to the corresponding pin on Nucleo. I made my project through stm32cubemx and I am using SD 4 bits wide bus as mode and enabled the FATFS Middleware. My problem seems to be in the lower level because I can�t even initialize the card.

Posted on October 09, 2017 at 12:22 I created a project with CubeMX 4.1, with a STM32F411VCTx. CubeMX generated a PLLN value of 100, which for RM0383 is correctsince the minimum PLLN value is 50: VCO output frequency = VCO input frequency × PLLN with 50 ≤ PLLN ≤ 432 Instead, since CubeMX has defined the following in the build settings: STM32F411xE The value of PLLN=100 produce an assertion error because the following macro states that the minimum PLLN value for STM32F411xE is 192: #if defined(STM32F411xE) #define IS_RCC_PLLN_VALUE(VALUE) ((192U <= (VALUE)) && ((VALUE) <= 432U)) #define IS_RCC_PLLI2SN_VALUE(VALUE) ((192U <= (VALUE)) && ((VALUE) <= 432U)) #else /* STM32F405xx || STM32F415xx || STM32F407xx || STM32F417xx || STM32F427xx || STM32F437xx || STM32F429xx || STM32F439xx || STM32F401xC || STM32F401xE || STM32F410Tx || STM32F410Cx || STM32F410Rx

Posted on October 30, 2016 at 22:27This is what I get when compiling an empty created CubeMX project (CubeMX 4.17.0, STM32F0 lib v1.6.0) with the CRC module enabled. File: stm32f0xx_hal_crc.c, affected lines: 470 -> *(uint16_t*) (&hcrc->Instance->DR) = ((uint16_t)pBuffer[4*i]<<8) | (uint16_t)pBuffer[4*i+1]; 474 -> *(uint16_t*) (&hcrc->Instance->DR) = ((uint16_t)pBuffer[4*i]<<8) | (uint16_t)pBuffer[4*i+1]; 506 -> *(uint16_t*) (&hcrc->Instance->DR) = pBuffer[2*i]; According to some googling, those pointers are accessing the memory of DR while interpreting it as uint16_t while DR originally is defined as uint32_t. This breaks the aliasing rules and should be avoided. See:

Posted on September 29, 2017 at 13:53Using CubeMx with automatic Makefile generation.I want to alter the build target name.Example:CubeMx creates a build target in the Makefile:TARGET = myfirmwareBut I want to append a version:TARGET = myfirmware_$(FW_VERSION)However my custom change is overwritten each time CubeMx auto generates a new makefile.Does anyone know how to work around this?I have not found documentation on how to protect parts of the Makefile from updating.#stmcubemx #makefile #cubemx-project

Posted on September 27, 2017 at 09:36Have good days...I am trying to connect my STM32F107VC EasyMx Pro V7 development board with Visualgdb. I am using Visual Studio 2015 Community. My example is LedBlink which is codes from STM32CubeMx. I did provisioning of STMCubeMx and VisualStudio. I don't have error message or warning when i build my codes in Visual Studio. My debug method is OpenOCD, programming interface is St-Link v2. When i check communication Stlink Detect and Test OpenOCD Settings, there is no problem. However i have error that is name 'No executable file specified. Use the 'file' or 'exec-file' command. Cannot resolve the address of _estack. Skipping stack pointer validity check.' when i try to debug with Visualgdb. And i was not able to find the solution. Would you mind help ing me this problem ? How to solve this debug error ? I already remain grateful your assistance...#stlinkv2-1 #debug #open

Posted on September 22, 2017 at 09:46 Hi there, i'm working on a STM32F103 MCU and I want to acquire 9 channels with ADC1. With STM32Cube I configured the ADC1 in this way: Scan conversion mode: Enabled.Enable regular conversion: Enable.Number of conversion: 9 These is the channel list: Vref IntTemperature SensorIN8IN9IN10IN11IN12IN13IN15 Also I configured the DMA to transfer the data from the ADC to a memory buffer. Mode: NormalIncrement Address: MemoryData Width: Word To start the conversion I use: HAL_ADC_Start_DMA( ADC1_ModuleHandler, ADC_1_B

Posted on September 25, 2017 at 03:42Hi All,I have been experimenting with my http://www.st.com/en/evaluation-tools/nucleo-l476rg.htmlI have generated some code with CubeMX for SW4STM32 and I am getting some problems with the code, ending up in an Error Handler sometimes (in main):void _Error_Handler(char * file, int line){  /* USER CODE BEGIN Error_Handler_Debug */  /* User can add his own implementation to report the HAL error return state */  while(1)   {  }  /* USER CODE END Error_Handler_Debug */ }This happens when I do the following:Use the main clock source for the PLL as HSI, and tick the option 'generate peripheral initialization as a pair of '.c/'h' files per peripheral', which I prefer to keep things ti