STM32CubeMX (MCUs)

I was searching for smaller and cheaper MCU with CAN network. I have chosen the STM32F042F4P6 trough CubeMX but now when I try to enable CAN in CubeMX I cannot because it's grayed. What am I doing wrong?

Hello all,I have a NUCLEO-L073RZ with SX1272MB2DAS LoRa RF Expansion board and I’m not being able to run the firmware “End_Node�? provided in I-CUBE-LRWAN (1.2.0).The problem comes when “SystemClock_Config�? is called in main:void SystemClock_Config( void ){ RCC_ClkInitTypeDef RCC_ClkInitStruct = {0}; RCC_OscInitTypeDef RCC_OscInitStruct = {0}; /* Enable HSE Oscillator and Activate PLL with HSE as source */ RCC_OscInitStruct.OscillatorType     = RCC_OSCILLATORTYPE_HSI; RCC_OscInitStruct.HSEState           = RCC_HSE_OFF; RCC_OscInitStruct.HSIState           = RCC_HSI_ON; RCC_OscInitStruct.HSICalibrationValue = RCC_HSICALIBRATION_DEFAULT; RCC_OscInitStruct.PLL.PLLState       = RCC_PLL_ON; RCC_OscInitStruct.PLL.PLLSource      = RCC_PLLSOURCE_H

Dear friend,I've got two threads running on a STM32F107RCt6 MCU; One is a Modbus TCP Server thread with the stack size of 256 words and the other is a Modbus RTU thread with the same stack size.When there is no client connected to the Modbus tcp server, the RTU task works correctly and runs without any errors permanently but when a client is connected and reads/writes the Modbus registers, after 2 or 3 hours or more (less than 12 hours) , the Modbus RTU thread stops working in a way that you could say the TCP task terminates the Modbus RTU task.Could any one help me to find out why this happens and after working hours, the RTU taks stops?Is there any way to find out the current state of Modbus RTU task within the TCP task and if it was terminated, it restart it?I am using the latest version of CubeMX and HAL drivers.I use lwIP netconn APIs with freeRTOS and I config them on CubeMX.The total heap size of freeRTOS is 10KB.The priority of both tasks are the same.The client is a Monitoring

Hey everyone,I've got an SPI line setup on my stm32f722ze.Cache is not enabled. It worked and I'm not sure whether the code was changed, but it receives junk now. The DMA is triggered which shows that when I send data, it is receiving it, but not the correct data.I Have verified the data that's being sent via an oscilloscope.The stm's spi line is coupled to a esp32. The esp32 is the master and the stm is running as slaveHere's the relevant code for the stm32:Hal_msp.c:void HAL_SPI_MspInit(SPI_HandleTypeDef* hspi) {   GPIO_InitTypeDef GPIO_InitStruct; if(hspi->Instance==SPI1) { /* USER CODE BEGIN SPI1_MspInit 0 */   /* USER CODE END SPI1_MspInit 0 */ /* Peripheral clock enable */ __HAL_RCC_SPI1_CLK_ENABLE();   /**SPI1 GPIO Configuration PA4 ------> SPI1_NSS PA5 ------> SPI1_SCK PA6 ------> SPI1_MISO PA7 ------> SPI1_MOSI */ GPIO_InitStruct.Pin = GPIO_PIN_4|GPIO_PIN_5|GPIO_PIN_6|GPIO_PIN_7; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStr

I have a STM32F746 Discovery. I work on AC6, CubeMX, emWin. I'm generating WindowDLG.c. I add a further code to WindowDLG.c. After closing CubeMx and trying to reload WindowDLG.c, "Error reading widgets" is reported. So I can not develop the file in GUIBuilder any more. How to deal with this?

..

Just upgraded to STCubeMX v5 which appeared to successfully open a project I just started. After agreeing to the annoying "Project has been changed, do you want to save" pop-up, Atollic became non-responsive. Is this a known bug? You have coded a race condition between the timer pop-up and the main GUI thread...PS: "Update" from previous version of STcubeMX failed (lots of downloading and thrashing, error message flashed quickly onscreen, no installation). I had to deinstall the plug-in and then install the new version after manually downloading from ST site.PPS: Restarting Atollic, STCubeMX seems functional...PPS: Just repeated this problem. I was working in SPI configuration when annoying question popped up, I clicked "Save", and Atollic IDE went non-responsive. There's a race condition bug between the pop-up and editing...

HelloAn F4 project with a timer in output compare mode generates in main.c a call to   HAL_TIM_MspPostInit(&htim1);This function is implemented in stm32f4xx_hal_msp.c but is declared in main.c file.If I change main.c to main.cpp. It does not link.My opinion is that CubeMx should generate a stm32f4xx_hal_msp.h file containing the public functions declarations within an extern "C". Something like this :#ifndef STM32F4XX_HAL_MSP_H_ #define STM32F4XX_HAL_MSP_H_     #ifdef __cplusplus extern "C" { #endif   void HAL_TIM_MspPostInit(TIM_HandleTypeDef* htim);   #ifdef __cplusplus } #endif     #endif /* STM32F4XX_HAL_MSP_H_ */The main.c file should include it.My 2 cents.Julien

The pc is win10-64bit, I do not have this problem in win7-64. The STM32cubeMX GUI can only be closed in Task Manager where java JRE is reported as "Suspended". Windows java application logs indicate "hangup", timestamped to when I do the clicking. JRE 1.8.181-64bit is installed.Any advice would be appreciated.

Posted on September 09, 2017 at 06:39Update: As the below error appeared when I tried to make a Low Layer project for Nucleo L152RE board using STM32CubeMX in generating a code for a Makefile project, and, it was solved by an update to both STM32CubeMX and LL driver, the generated code remains unusable so, I chose a more appropriate title.Original topic:- undefined reference to `LL_RCC_GetSystemClocksFreq'This function is referenced inside LL_I2C_Init function. I am using the last version of STM32CubeMX and I'm writing code for Nucleo L152RE board using Low Layer drivers.I generated code for using the I2C1 peripheral, and I did a compilation without adding my own code. And it trows the error specified in the title at linker time. I also use the last version of ARM gcc compiler from the gcc-arm-none-eabi-6-2017-q2-update-linux.tar.bz2 archive under Linux Fedora 26. I attached the project archive.#stm32cubemx #i2c #timer #incomplete-code #undeleted-temporary-files #missin

I'm using an STM32F030K6 and I need to measure the time between the rising edge of 2 signals.The 2 signals (square wave) are not in phase and intended to use TIM1 to:* rising edge of signal 1, make timer start (internaly clocked);* rising edge of signal 2, capture the timer and trigger the DMA;* automatically stop at the timer to wait for the rising edge of signal 1 again.I find some information in sections 13.3.17 and 13.3.18, but not enough to understand the process and how I can prepare the setup using CubeMX.Could you please explain the process and recommend some specific reading on this example?Thank you

Dear Community,is it possible to download older versions of STM32CubeMX (4.X)? Unfortunately there are no links to archive downloads on the ST website. Thank you very much.Best regards,Emin Yagmahan

I am using stm32f429zi Nucleo board for Ethernet communication and using LWIP libraries.using this as an example "LwIP_TCP_Echo_Server", I am able to receive data from Hercules software and send back the received data to Hercules software, is there any option only to send data.

Hello.I'm experimenting with the Discovery board STM32F411E. The project is generated with CubeMX v5.0.0 + STM32F4-Package v1.23.0 and compiled with TrueStudio.After some experiments with timers, interrupts, LEDs and so on i tried to toggle an LED in a one-second period. I inserted the necessary values in the timer properties page. After compile and flash the LED toggled, but with a 24 second period instead of the wished 1-second period.After much google-research, trial and error i tried the HSI clock, instead of the default HSE clock. This finally produced the whished LED toggle period. After some further research i find out the "solution". The CubeMX property page for the RCC-module has as default setting for the HSE clock - "BYPASS clock source". After correcting this to "crystal/ceramic resonator", which i have on the STM32F411E-Discovery board - the combination HSE/PLL began to work and i got the right period of the LED-toggling.I'm not sure if the default setting "BYPASS..." is b

I am not sure if there is another place to submit this, some may have suggestions to solve this that I don't see.But these are the issues I have had with stm32cubeMX right out of the box, still haven't used it to a full extent, I was just testing the GUI.I am trying this now in my 720p 15.6" laptop. Next I am gonna test in a 24" 1080p screen. Everything being in the same window makes it so cluttered together.And so many time I try to minimize the peripheral configuration and end up with the image belowThen there are so many scroll bars in each window because they are so tiny!The independent windows were so useful for me. These aren't detachable.Plus they are hard to manage, the arrows (with the red ball draw) are so tiny that, as I said, I keep opening/closing stuff that I don't want. Once I closed the peripheral configuration window and it didn't open it again when I pressed a peripheral in "system view" - I had to maximize the peripheral config window manually.Btw, the shift+scroll w

Hello,Currently, with 4.26.1 version, it is not possible to use special functions in FreeRTOS about the Memory Protection Unit (MPU).I use the STM32F207VCT chipset with MPU functionality. Unfortunately, STM32CubeMX don't give me a way to use this functionality like, for example, MPU_xTaskCreateRestricted function.There is the function header, but no code present.It is too bad that have a important feature but I can't use it ...Thanks in advance for the information.Best regards.

Hello, As I am working on analog inputs I require ADC. STM32F334 Nucleo board has 12-bit ADC (2) with 21 channels, I am using ADC1 Channel 1.After programming without applying any input to the pin (PA0) I am getting some values through USART2.Can anybody help me out.Thanks in advance.

Dear STM32 community,I have an understanding problem with clock calculation for ADC unit.The ADC1 will be used with DMA by STM32F411 CPU.HSE_CLK = 8MHz, HCLK = 96 MHz, PCLK2 = HCLK/4 => 24MHz (for ADC clock).There are two ADC channel in use: 12 Bit, 480 sampling time => 12 + 480 = 492 clock per each channel.The ADC run in scan mode , continuous conversion mode. DMA interrupt is activated (DMA2_Stream0_IRQHandler)Therefore calculated ADC coversion period contain (1/24MHz) x 492 x 2 = 41usFor measuring purpose in DMA interrupt an LED is toggled. Surprisingly, if your meassuring time with osciloscope, the pulse or pause time contain 82us !!! (x2 from calculated time) Ok, in CubeMX settings for ADC DMA you can clear checkbox "use FiFo".In thhis case you will be surprised too, because on the osciloscope screen your will see the pulse time of 20,5us (1/2 from calculated time) Can anyone, please, explain this phenomenon ? What I do wrong ?Many thanks in advance !!!

I would like to add a wish list to STM32CubeMX. I recently installed the latest version 5.0.The user preferences menu has only the option send usage data. Can an option to change font and font size be added? Some of the pages have small fonts. Changing the display properties does not always provide an easily readable font size.

USSUE: RTC      STM32F767 / STMCube verion 4.27.0 / STM32Cube FW_F7 V1.12.0Time and date are reset when the ARM is started.if I compare the code with the STM32F405 and the STM32F767, then I see a difference:the row "if(HAL_RTCEx_BKUPRead(&hrtc, RTC_BKP_DR0) != 0x32F2){" is missing by the stm32f767Have I not set the settings of cubeMX something  correctly or is this a mistake in cubeMX ?-----------------------STM32F405----------------------------/* RTC init function */void MX_RTC_Init(void){ RTC_TimeTypeDef sTime; RTC_DateTypeDef sDate;   /**Initialize RTC Only    */ hrtc.Instance = RTC;if(HAL_RTCEx_BKUPRead(&hrtc, RTC_BKP_DR0) != 0x32F2){ hrtc.Init.HourFormat = RTC_HOURFORMAT_24; hrtc.Init.AsynchPrediv = 127; hrtc.Init.SynchPrediv = 255; hrtc.Init.OutPut = RTC_OUTPUT_DISABLE; hrtc.Init.OutPutPolarity = RTC_OUTPUT_POLARITY_HIGH; hrtc.Init.OutPutType = RTC_OUTPU

Hey guys,I have a very big problem. For a reason I don't understand, my CubeMX project which worked really fine and had no problem at all did now get the following error as I was regenerating code (I did this a hundreds of times without problem but since last thursday I get this error) : "The code has successfully been generated under ... but STUDIOproject generation have a problem".Since then my project is not working correctly anymore. For example my UART is not transmitting any data correctly but receiving. I tried to just save the project new and generate new code but the problem is the same and no TrueStudio project is generated.I noticed that STM made an update for CubeMX (5.00) and so I installed it and updated all the firmware packages and migrated my project in hope that this might correct the error but nothing changed.Now I don't know what to do. How do I get my project to work normal again? I also tried to make a new empty project with True Studio and just copy the generated

I have same trouble with this link --> https://community.st.com/s/question/0D50X00009XkYPHSA3/stm32cubemx-blank-new-project-page?t=1543518688382I have trouble with cubeMX when i try to create new project cannot see anything only white,blank and emty window, Java run time enviroment & cubeMX different version i tried but nothing.What am i do now? cannot use cubeMX anymore.

I started out with an example bare-metal project for the B-L475W-IOT1A Discovery board, that reads the HTS221 temperature and humidity, and LPS22HB pressure. Very straight forward. For ex, api to read temp: float HTS221_T_ReadTemp(uint16_t DeviceAddr). Only need to provide I2C ID to function call. NOTE: the api's came out of STM32LCube\STM_Discovery_STM32Cube\STM32Cube_FW_L4_V1.13.0\Projects\B-L475E-IOT01A\Examples\Lab2_PTH_FreeRTOS\Drivers\BSP\Components.Next, ran STM32CubeMX tool, created a new project set up to read same sensors (this process was not really straight forward - the GUI has weird nooks/crannies you need to dig thru to get the I2C set up). This project also included FreeRTOS. When CubeMX created the project, a new api was installed on my drive, C:\...\STM32Cube\Repository\STM32Cube_FW_L4_V1.13.0\Drivers\BSP\B-L475E-IOT01.This api is completely different than the one above. There is a huge gaping hole in the documentation for this new(?) api - there is no info on now to

Generated code not contains hcrc declaration.MX_CRC_Init func is empty (contains only comments)Сonditions:STM32L011D4 is used as mcucrc module in enabled in cube mxp.s.Please make version 4.x available for download from the site as an option.Forced beta testing can be very unpleasant.thank.