STM32CubeMX (MCUs)

Posted on March 24, 2016 at 20:33Hi, When compiling my project raises some compiler warnings. I use a makefile to compile with the following settings: WARNINGS_FLAGS  = -Wall WARNINGS_FLAGS += -Wextra WARNINGS_FLAGS += -Wfloat-equal WARNINGS_FLAGS += -Wlogical-op WARNINGS_FLAGS += -Wundef WARNINGS_FLAGS += -Wwrite-strings ♯ ♯ -Wall WARNINGS_FLAGS += -Wno-sign-compare Follows the compiler output warnings: stm32f100(v 1.3.1): Drivers/STM32F1xx_HAL_Driver/Src/stm32f1xx_hal_pwr.c:435:38: warning: unused parameter 'Regulator' [-Wunused-parameter] Drivers/STM32F1xx_HAL_Driver/Src/stm32f1xx_hal_rtc.c:1066:96: warning: unused parameter 'Alarm' [-Wunused-parameter] Drivers/STM32F1xx_HAL_Driver/Src/stm32f1xx_hal_rtc.c:1108:77: warning: unused parameter 'Alarm' [-Wunused-parameter] Drivers/STM32F1xx_HAL_Driver/S

Posted on July 11, 2014 at 10:34Hi,I'm using STM32CubeMX for a STM32F205 MCU.There is a problem with the use of the TIM8 configuration, regarding BDTR config register.The DeadTime does not appear in the config of TIM8. And then, its code is not generated either. The problem is that in the libraries, sBreakDeadTimeConfig.Deadtime is not initialised ; and then it contains a random value at reset. Since the initialisation of the register is made like this :   htim->Instance->BDTR = (uint32_t)sBreakDeadTimeConfig->OffStateRunMode  |                                     sBreakDeadTimeConfig->OffStateIDLEMode |                

Posted on March 13, 2015 at 10:37Hi,There is an error in the file stm32fxx_hal_tim.c, for TIM3 and TIM4 capture compare.We never enter in the callback because of this error.    * @file    stm32f2xx_hal_tim.c  * @author  MCD Application Team  * @version V1.0.1  * @date    25-March-2014Line 2749 and 2770 => you must replace CCMR1 by CCMR2.      /* Input capture event */      if((htim->Instance->CCMR2 & TIM_CCMR2_CC3S) != 0x00)      {                  HAL_TIM_IC_CaptureCallback(htim);      }      /* Input capture event */      if((htim->Instance->CCMR2 & TIM_CCMR2_CC4S) != 0x00)     

Posted on September 05, 2014 at 14:53Hi, stm32cubeMX is a very convinient tool that generates code and projects for some commercial IDEs. Unfortunatelly I'm not using those IDEs so I'm left alone with a huge amount of C Code and no instructions how to use it :) Does anyone out there know any simple method to import that code into a working project in eclipse ide? Or maye you have any scripts for converting for example TrueStudio project into Eclipse one? Thanks! #eclipse #stm32cubemx #import

Posted on February 16, 2016 at 14:58The MX_FATFS_Init function is beeing called in the main function and again in the default task. After the second call the SD_Path is invalid. I'm using CubeMX 4.13.0 with the STM32F417IGH6, the configuration is in the attachments.int main(void){  /* USER CODE BEGIN 1 */  /* USER CODE END 1 */  /* MCU Configuration----------------------------------------------------------*/  /* Reset of all peripherals, Initializes the Flash interface and the Systick. */  HAL_Init();  /* Configure the system clock */  SystemClock_Config();  /* Initialize all configured peripherals */  MX_GPIO_Init();  MX_DMA_Ini

Posted on February 26, 2016 at 03:09 With STM32CubeMX v4.0 and STM32CubeF0 v1.5.0 the GPIO initialization for a hardware NSS pin has changed and doesn't match the information in the reference manual. For example SPI1_NSS from STMCubeF0 v1.2.1 was initialized: GPIO_InitStruct.Pin = GPIO_PIN_15; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_PULLUP; GPIO_InitStruct.Speed = GPIO_SPEED_LOW; GPIO_InitStruct.Alternate = GPIO_AF0_SPI1; HAL_GPIO_Init(GPIOA, &GPIO_InitStruct); NowSPI1_NSS from STMCubeF0 v1.5.0 is initialized: GPIO_InitStruct.Pin = GPIO_PIN_15; GPIO_InitStruct.Mode = GPIO_MODE_INPUT; GPIO_InitStruct.Pull = GPIO_PULLUP; HAL_GPIO_Init(GPIOA, &GPIO_InitStruct); Receiving data on SPI using DMA is working intermittently. I'm seeing weird issues like entire data blocks shifted by 1 bit. I've had to manually change the GPIO initialization code to get SPI transfer

Posted on March 08, 2016 at 19:21Hi, I wanted to check out the WIFI Expansion for Cube MX. But I am failing at integrating it into CubeMX as I cannot find any information on how to integrate the downloadable expansions into CubeMX. Any help is appreciated ;) Kind regards Hans #cubemx-stm3-wifi

Posted on March 08, 2016 at 11:08Hello guys, Can somebody share a list of all possible variables that I can use in FreeMarker templates inside of STM32CubeMX with me? I am working on a Makefile and .ld (because existing have not very nice license ;)) ) template. And a it is possible to achieve filename of generated file based on a variable? It looks like that existing templates have an external logic, but it could be nice to have the same for custom templates as well. #freemarker #stm32cubemx #cubemx

Posted on March 03, 2016 at 14:28I have the STM32F303RE Nucleo evaluation board, and I've used CubeMX to configure & generate the HAL drivers. I've configured a DAC on one of the timers, and everything compiles/runs fine, except when I enabled ''USE_FULL_ASSERT'' then I get the following compile error. ../Src/main.c(329): error:  &sharp20: identifier ''HAL_REMAPTRIGGER_DAC1'' is undefined     __HAL_REMAPTRIGGER_ENABLE(HAL_REMAPTRIGGER_DAC1_TRIG); This comes down to the following code generated in stm32fxx_hal.h: &sharpdefine IS_HAL_REMAPTRIGGER(RMP) ((((RMP) & HAL_REMAPTRIGGER_DAC1)  == HAL_REMAPTRIGGER_DAC1)       || \                                 &n

Posted on February 24, 2016 at 13:56 I am really got tired after so many attempt to use this hal drivers for ADC sampling in dual mode and send data over uart. For god sake plz help me. I did whatever user manuals said but still no output. This is the code: /** /* Includes ------------------------------------------------------------------*/ include ''stm32f4xx_hal.h'' /* USER CODE BEGIN Includes */ include < stdio.h > /* USER CODE END Includes */ /* Private variables ---------------------------------------------------------*/ ADC_HandleTypeDef hadc1; ADC_HandleTypeDef hadc2; DMA_HandleTypeDef hdma_adc1; DMA_HandleTypeDef hdma_adc2; UART_HandleTypeDef huart3; /* USER CODE BEGIN PV */ /* Private variables ---------------------------------------------------------*/ //__IO uint16_t ADC_val[2]={0}; char senddata1[20]; char senddata2[20]; __IO uint32_t ADC_val=0; __IO uint16_t ADC1_val=0; __IO uint16_t ADC2_val=0; /* USER CODE END PV */ /* Pri

Posted on February 28, 2016 at 20:14It would be nice if you could move into a header the definition of GPIO_MODE, GPIO_MODE, ... GPIO_CR_CNF_ANALOG, GPIO_CR_MODE_INPUT, GPIO_CR_CNF_ANALOG, ...GPIO_CR_CNF_AF_OUTPUT_OD currently in stm32fNxx_hal_gpio.c These definitions may be useful to automatically generate configuration functions with external tools. CubeMX does a great job if you've to configure pins once but HAL_GPIO_Init() may be not as efficient as it has to be if you've to switch GPIO configuration in the middle of an interrupt and assigning pin functions manually is so '90 and is terribly error prone. Having to cut&paste code from stm32fNxx_hal_gpio.c is annoying and error prone as well. thanks #hal. #cubemx #headers

Posted on February 27, 2016 at 01:00Using channel4 of TIM5 sets up ARDUINO_PWM_CS_D10_Pin where actually thesignal is on D5ARDUINO_PWM_CS_D10_Pin is defined as pin PI_0 which is the correct pin however.------------- so I am expecting generated code to be:in mxconstants.h&sharpdefine ARDUINO_PWM_D5_Pin GPIO_PIN_0&sharpdefine ARDUINO_PWM_D5_GPIO_Port GPIOIin tim.c    /**TIM5 GPIO Configuration        PI0     ------> TIM5_CH4     */    GPIO_InitStruct.Pin = ARDUINO_PWM_D5_Pin;---------- also TIM1_channel1 generated code  attempts to use the D5 pin, it is likely to have the converse problem #stm32f746-cubemx

Posted on February 22, 2016 at 19:16Under ''slave mode'' the timer configuration of the TIMx_SMCR register: ''Combined Reset + trigger'' mode cannot be reached using the available menu items whereas ''reset mode'' or ''trigger mode'' are available.It could also be that the encoder modes are not available as well. #stm32f7xx-stm32cubemx

Posted on February 26, 2016 at 02:46So eagle eye'd son pointed out that the publicity picture for CubeMX shows its logo sprawled across the face of Apple's MacBook Pro. And yet there are logos for Windows and Linux next to it.So, when is CubeMX going to be supported on MacOS? It works really well, except for getting updates.Thanks,Andrei from The Great White North. #cubemx-macos

Posted on February 22, 2016 at 16:25I have two UARTs configured as follows (code generated by CubeMX).UART_HandleTypeDef huart2;UART_HandleTypeDef huart4;// Pins (Rx/Tx): PA3 / PA2 - Asynchronous (UART)void MX_USART2_UART_Init(void){ huart2.Instance = USART2; huart2.Init.BaudRate = 115200; huart2.Init.WordLength = UART_WORDLENGTH_8B; huart2.Init.StopBits = UART_STOPBITS_1; huart2.Init.Parity = UART_PARITY_NONE; huart2.Init.Mode = UART_MODE_TX_RX; huart2.Init.HwFlowCtl = UART_HWCONTROL_NONE; huart2.Init.OverSampling = UART_OVERSAMPLING_16; HAL_UART_Init(&huart2);}// Pins (Rx/Tx): PA1 / PC10 - Asynchronous (UART)void MX_UART4_UART_Init(void)

Posted on February 16, 2016 at 09:02My tools: STM32f072rb (NUCLEO) MCP2200 uart to usb board STM32CubeMX (4.12.0) Keil uVision 5 (5.17) What I'm trying to do: Running a program in the main loop and reading UART transmission into a ring buffer. (as soon as Rx signal is present, an interrupt is triggered which reads the incomming data) Init code was generated using CubeMX, setting up UART2, 8Bits 9600 Baud, no HW flow control, on STLink debugger UART1, 8Bits 9600 Baud, no HW flow control, on MCP2200 One attempt of mine was connecting the Rx2 pin to EXTI6, triggering a GPIO interrupt and readingfrom there. (Receiving char on UART2, echo it to UART1) This worked well for only one char and is imo. a really dirty solution. In CubeMX, under NVIC the UART2 global interrupt through EXTI l

Posted on February 12, 2016 at 15:42 Hello, I've been working with ST HAL libraries for an STM32F030R8T6, using the NUCLEO board, and I'm having some problems with the I2C API. Probably it's a configuration issue but for the love of me, I can't find it. The problem: I call the function HAL_I2C_Master_Transmit_XX with address 0x3E. I attach a logic analyzer to the output to check the lines, and the address does not match. The address I see on the line is 0x1F. My main test code is the following. (Just to reproduce this situation) It is a direct copy from the NUCLEO examples. I skip over the SystemClock_Config and MspInit, since I can see data on the lines (I2C is sending data correcly) and they don't provide information for my current problem. #define I2C_ADDRESS 0x3E #define I2C_TIMING 0x00A51314 uint8_t bTransferRequest = 0; //(other stuff) int main( void ) { HAL_Init(); /* Configure th

Posted on February 07, 2016 at 19:25Hello, I use the USB device CDC class. I do transmit data. But while I give the the data to the CDC_Transmit_FS function. The application must not overwrite data on those buffer until the transmit is finished. Potentially there are several USB packets to be sent until all data transmitted. What I miss is a trigger for the application to reuse the buffer used in the CDC_Transmit_FS function. I assume in the file usbd_cdc.c in function USBD_CDC_DataIn there you could put a function call to callback function: CDC_TransmitCplt_FS the callback function could be added to USBD_CDC_ItfTypeDef. This way it could callback to usbd_cdc_if.c module. Right now after automated code generation I have to patch usbd_cdc.c and usbd_cdc_if.c in order get signals data_received and data_transmit_completed into the application.

Posted on August 11, 2014 at 14:27To avoid glitches at the output, we initialize in the following order: 1. GPIOx clock enable 2. Set output registers to defined value 3. Perform initialization Now we would like to use STM32CubeMX. Is it possible when initializing the GPIO to initialize the output level? Example of implementation: In source:   /*Configure GPIO pins : PE2 PE3 PE4 P

Posted on January 12, 2015 at 11:38Hello all. Bed path: java.io.FileNotFoundException: /home/krzysiek/STMicroelectronics/STM32Cube/STM32CubeMX/db/plugins/projectmanager\stm32tck.cfg (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:146) at java.io.FileInputStream.<init>(FileInputStream.java:101) at java.io.FileReader.<init>(FileReader.java:58) at convertor.Convertor.getTplVer(Convertor.java:1152) at convertor.Convertor.setTemplates(Convertor.java:536) at convertor.Convertor.setDataPath(Convertor.java:1495) at com.st.microxplorer.plugins.projectmanager.model.ToolchainGenerator.setDllDataPath(ToolchainGenerator.java:116) at com.st.microxplorer.plugins.projectmanager.engine.ProjectBuilder.createToolChainFolders(ProjectBuilder.java:934) at com.st.microx

Posted on February 04, 2016 at 11:25Hi all, Quite new in the development with LWIP, there is a question I have not found any answer so far; What is the minimum / maximuum frequency at which the main LWIP process function shall be called? I'm talking about the one generated by CubeMX: MX_LWIP_Process. We don't run it as seen in examples, that is in a simple while(1) loop in the main program. We want (and need) to use it from an IT. Thank you for your help #lwip-process-cubemx

Posted on January 19, 2016 at 11:33Hello,I couldn't find bug/issue tracking system for CubeMX, so I place report here.Description:  When generating initialization code for TIM4 in input capture mode (channel 1 direct, channel 2 indirect), HAL_TIM_Base_MspInit() function is being generated in stm32f1xx_hal_msp.c file. This is incorrect function for input capture mode, as far as I understand, which leads to timer not capturing signal. CubeMX project file is attached Expected behaviour: HAL_TIM_IC_MspInit() function should be generated.Notes: I've added HAL_TIM_IC_MspInit() manually, which fixed the problem for me.Additional info: CubeMX version: 4.11.0 MCU used: stm32f103c8t6 Library version: STM32CubeF1 Firmware Package V1.2.0 / 31-July-2015 

Posted on February 08, 2016 at 05:05 I found incorrect code in SD_write andSD_read code (sd_diskio.c). This conversion will fail on sectors above8388608 (4GB): (uint64_t) (sector * BLOCK_SIZE) It should be (uint64_t) sector * BLOCK_SIZE (uint64_t) sector * BLOCK_SIZE (uint64_t) sector * BLOCK_SIZE It should be #sdio #sd_diskio #cubemx #sdio

Posted on February 05, 2016 at 13:01Hi, I am using the current version (4.12.0) of STM32Cube. Every time I open a *.ioc file, it is immediately regarded as changed -- it's marked by a star in the window title and if I want to exit, I get a warning about unsaved changes. If I save, I get a file which is byte-by-byte identical to the previous one. And if want to generate a report, I get the message ''The Report will be based on a modified version of the project. Would you like to save <projectname> project first?''. If I do not save, I get a remark about modifications in the report. If I save, my project file contents is not changed, but the file time stamp IS changed, which I do not want. At present, I just set the file to r/o. Than I can ''save'' without error message (!), but the file time stamp is not changed. Not a good solution, though. I think this is bad behaviour and should be fixed.

Posted on January 28, 2016 at 22:18I used Stm32CubeMx with STM32Cube_FW_F0_V1.4.0 to generate my project on STM32F030CC with FreeRTOS and EWARM toolchain. In debug mode. I only have the generated code at this time. It first crashes on HAL_TIM_PWM_ConfigChannel() call. It seems to loop inside a strange memory area around 0x1FFFDA7C, or so says the debugger. Log window displays ''The stack pointer for CSTACK (currently 0x20000A78) is outside the stack range (0x200000B8 to 0x200004B8). I decided to comment MX_TIM3_Init() in main.c, but to no avail. I ended up commenting all MX_() calls to keep it as simple as possible, now it crashes with the same behaviour, but on the line __DSB() inside vPortYield(). I then tried to stard without any other initialisation besides osKernelStart(), still won't work. Decided to see if any ISR are being called, and the answer is none, not even PendSV_Handler() nor SysTick_Handler(). Res