STM32CubeMX (MCUs)

Posted on May 13, 2014 at 07:23 Hi! I'm sure there is a bug inHAL_Delay() when current time returned by HAL_GetTickis close to overflow (0xFFFFFFFF). Check out this code: http://ideone.com/MAdwBN Second version ofHAL_Delay() is my suggestion, it's pass the test. //----------------------------------------------------------------------------- #include <stdio.h> #include <inttypes.h> //----------------------------------------------------------------------------- #define __IO static uint32_t Ticks; /// Debug version of HAL_GetTick() static uint32_t HAL_GetTick() { return Ticks++; } //----------------------------------------------------------------------------- #if 1 /// Original HAL_Delay() from CubeMX void HAL_Delay(__IO uint32_t Delay) { uint32_t timingdelay; timingdelay = HAL_GetTick() + Delay; while (HAL_GetTick() < ti

Posted on April 24, 2014 at 13:32Tired of changing project settings after each code generation from MX. Is there a chance of modifying Keil-project template? Thanks. #keil-cubemx-code-generation

Posted on April 24, 2014 at 04:50Greetings all,I have a couple of problems with STM32CubeMX-V1.1.0 with the following options: * STM32F439 * FreeRTOS * LwIP  The first problem is a bug in the sys_mutex_lock function which is generated as:    void sys_mutex_lock(sys_mutex_t *mutex)    {        sys_arch_sem_wait(*mutex, 0);    }It's calling the sys_arch_sem_wait function which has a prototype of:    u32_t sys_arch_sem_wait(sys_sem_t *sem, u32_t timeout)    As can be seen here; both sys_mutex_lock and sys_arch_sem_wait both expect to receive a 'sys_mutex_t*'; however sys_mutex_lock dereferences the pointer rather than passing it across correctly. The correct implementation of sys_mutex_lock is:    void sy

Posted on September 02, 2013 at 13:14Hi Folks I'm working with the 32F4 discovery board and I've been looking for some examples of mixed Input and output pins on the same port, however they seem a like hard to find!! I checked the Ref Manual and does seem possible to put input and output on the same port. I'm using the following setup code - is this the right way to go about it?? (the strut was declared earlier) - The outputs (3,4) seem to work fine, but I get no pull ups on the inputs....  GPIO_InitStruct.GPIO_Mode = GPIO_Mode_OUT;  GPIO_InitStruct.GPIO_OType = GPIO_OType_PP; GPIO_InitStruct.GPIO_PuPd = GPIO_PuPd_DOWN; GPIO_InitStruct.GPIO_Speed = GPIO_Speed_25MHz; GPIO_InitStruct.GPIO_Pin = GPIO_Pin_3 | GPIO_Pin_4; GPIO_Init(GPIOE, &GPIO_InitStruct); GPIO_SetBits(GPIOE,

Posted on April 08, 2014 at 11:51 Hi, I can't get the USB Host code generated by STMCube to work. When I connect a device, none of the interrupts get triggered - the software doesn't seem to recognize it at all. The peripheral clock is enabled and the interrupts are getting set, I see this function get called in usbh_conf.c in the debugger: void HAL_HCD_MspInit(HCD_HandleTypeDef* hhcd){ GPIO_InitTypeDef GPIO_InitStruct; if (hhcd->Instance==USB_OTG_FS) { /* Peripheral clock enable */ __USB_OTG_FS_CLK_ENABLE(); /**USB_OTG_FS GPIO Configuration PA11 ------> USB_OTG_FS_DM PA12 ------> USB_OTG_FS_DP */ GPIO_InitStruct.Pin = GPIO_PIN_11|GPIO_PIN_12; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_LOW; GPIO_InitStruct.Alternate = GPIO_AF10_OTG_FS; HAL_GPIO_Init(GPIOA, &GPIO_InitStruct); /* Peripheral interrupt init*/ /* Sets the priori

Posted on April 01, 2014 at 12:38 STM32CubeMx generate code for STM32F407VGTx I chek box '' DMA2 Stream0 global interrupt'' in '' NVIC Configuration'' STM32CubeMx not add in stm32f4xx_hal_msp.c - HAL_NVIC_EnableIRQ: void HAL_ADC_MspInit(ADC_HandleTypeDef* hadc){ GPIO_InitTypeDef GPIO_InitStruct; if (hadc->Instance==ADC1) { ... HAL_NVIC_EnableIRQ(DMA2_Stream0_IRQn); // No Add } } #stm32cubemx-dma-interrupt-nvic

Posted on March 22, 2014 at 01:39 Hello. I am currently trying to build a project using the STM32F429 iDisco. The toolchain I am using is the arm embedded gcc, under Eclipse IDE. I am trying to use STM32Cube to write the initialization part for me. Initially I want to use CDC to loopback data sent from a pc (host) to the board (device). Later I want to implement communication between pc and board to control sensors. I'm fiddling with the various callbacks that Cube puts in usbd_conf.c. Since my first problem is the fact that the host pc cannot recognize the connected board (Windows has stopped this device because it has reported problems. (Code 43)A request for the USB device descriptor failed.) I am playing with HAL_PCD_ConnectCallback, but I am not sure what I should be doing there. I tried opening a bunch of endpoints (with HAL_PCD_EP_Open()), but to no avail. Using the board's LEDs to give me output depending on the device state, tells me tha

Posted on February 21, 2014 at 15:09Hi all,I have installed ST32CubeMX tool and I was wondering if there are any ''pre-built'' project files for STMicro evaluation boards such as ST32F407 Discovery board. I don't know the exact configuration of the ST32F407 chip on the Discovery board. I have tried to select all the possible peripherals but I get conflicts when I assign the pinouts.Best Regards,Mohamed #st32cubemx #discovery

Posted on March 12, 2014 at 22:17I am trying to use the STM32CubeMX tool to select and generate initialization code for the encoder interface.  I am using the Discovery board (STM32F407VGT) and trying to configure timer 5, but not sure how to get it to allow me to select this interface.  It is grayed out and not sure how to resolve it.  Anyone been able to do this?  Also there does not seem to be an motor encoder example using the new HAL layer,  if any one can point me to one, to would be helpful.  Thanks #motor-encoder #st32cubemx

Posted on March 04, 2014 at 19:42HiI'm exploring the STM32F405 and for this, i wanted to create the initial project with the Cube MX tool. I've settet all the things up to my configuration. In minimal i just set the hole clock thing up.I've burned this down to the chip just to make sure if the thing going to my while(1).But the generated code leads to the Hardfault error handler.I discovered that the fault is happening somewhere around when it calculates the latency for flash read write. This is in the beginning of the method: HAL_RCC_ClockConfig  located in stm32f4xx_hal_rcc.cIt jumps directly after command '' if(RCC_ClkInitStruct->SYSCLKSource == RCC_SYSCLKSOURCE_HSE) ''  (Line 782) to Address 0I don't think that i have to change some lines in the lib