STM32CubeMX (MCUs)

Posted on February 01, 2017 at 16:15In the last CubeMX version (4.19) the USE_TICKLESS_IDLE option is missing. This disables the configUSE_TICKLESS_IDLE flag and the low power configuration.Is it a bug? Is any workaround available?PS: I've checked the 4.17 version and it has this option available. I don't have the 4.18, so I can't check it.#cubemx #freertos #cubemx-4.19

Posted on January 11, 2017 at 18:02In an IAR/EWARM environment, when I use STM32CubeMX 4.18.0 Project/Generate Code function the program seems to correctly generate its own files but deletes user (that is, my files) from both the EWARM project and from the file system.It appears this was reported for some earlier CubeMX versions too ( https://community.st.com/0D50X00009Xkf15SAB for ex). Anyone else suffer and fix this issue? EDIT 170112 confirmed as a regression --- non-cubic sources preserved with 4.16.0. Not sure about 4.17.0.....

Posted on February 02, 2017 at 09:31I found several posts like http://www.openstm32.org/forumthread339, using syscalls.c, but I don't have this file in my project... I generate the code with CubeMX v4.18.0.#qt-creator #cubemx #stm32 #arm-none-eabi

Posted on January 27, 2017 at 10:22There seems to be a problem downloading the stm32cube_fw_l0_v180 from within the newest STM32Cube. See the attached screenshots. It seems to me it tries to unzip 'stm32cube_fw_l0_v180.zip' to a folder named 'stm32cube_fw_l0_v180.zip' which obviously does not work. Does anyone else have this problem?#stm32cube_fw_l0_v180 #stm32cubemx

Posted on January 09, 2017 at 21:58Summary of 2 days investigations for CubeMX and System WorkbenchFor success build without errors imported project generated in CubeMX, need fix generated symbolsIn Project->Properties->C/C++ Builds->Settings->MCU GCC Compiler->Symbols__weak=__attribute__((weak))__packed=__attribute__((__packed__))need set values __attribute__((XXXXX)) in double quotes - '__attribute__((XXXXX))'Sample:__weak='__attribute__((weak))'__packed='__attribute__((__packed__))'Else you can see follow errors after import23:19:10 **** Incremental Build of configuration Debug for project blink **** make all Building file: ../Src/main.c /bin/sh: -c: line 0: syntax error near unexpected token `(' /bin/sh: -c: line 0: `arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -Dweak=a

Posted on February 01, 2017 at 15:24Hello,In order to use DFSDM as lowpassfilter for my potentiometers I would like to route the ADC raw values to the DFSDM and finally get the results by DMA..Is CubeMX the right tool to prepare that? If yes, where is the setting for choosing the source of DFSDM??THX!#stm32cubemx #dfsdm

Posted on January 20, 2017 at 01:33On my Mac, I notice that STM32cubeMX has very high cpu usage on the Clock Configuration screen, but not other screens. Is this a known issue?#stm32cubemx*

Posted on December 07, 2016 at 16:41I notice that whenever I am in the Clock Configuration tab of CubeMX 4.18 the CPU activity goes to 100%. This is on macOS 10.12.1 and Java 1.8.0_111. Changing to any other tab reduces CPU to just a few percent. Not a crushing issue but probably not the intended behavior so thought I would mention it.If it helps, I've attached the project ioc file.#cubemx #mac-os

Posted on January 24, 2017 at 09:27I am new to ARM and STM32CubeMXMy goal is to use this very interesting boardhttp://www.st.com/en/evaluation-tools/32f429idiscovery.htmland use one internal 16bit counter for time and one 16bit counter for QEI(QEI=Quadrature Encoder to track angle of crankshaft)These two counters should have an external reset to zero when each new revolution startsThe datasheet http://www.st.com/resource/en/datasheet/stm32f429zi.pdf   says: Up to 17 timers: up to twelve 16-bit and two 32-bit timers up to 180 MHz, each with up to 4IC/OC/PWM or pulse counter and quadrature(incremental) encoder inpu

Posted on December 14, 2016 at 19:36The Nucleo_F767ZI board has 4 crystals onboard: X1:     8 MHz      connected to the JTAG-chip on the STLinkX2:     32 kHz    connected to STM32F767ZI for real time clockX3:     Not solderedX4:     25 MHz    connected to STM32F767ZI for HSE input clockFrom this information, it is only logical to conclude that the 25 MHz crystal is connected to HSE input of the microcontroller. However, CubeMX fills in 8 MHz by default for the Nucleo board. It looks like that is plain wrong:I currently work with

Posted on January 19, 2017 at 22:12This board is not shown in the board selector list.My workaround is to copy an 'old' *.ioc file, migrate it and clean it.#cubemx #nucleo-f767zi #bug

Posted on January 07, 2016 at 10:26Possible bug Introduced in STM32Cube FW_F7 V1.3.1 for the Serial Audio Interface.I am developing an application for the STM32F745VG using STM32CubeMX.This uses a SAI operating in Transmit mode, with ''Free'' protocol, and 16 Slots active.The code functioned correctly when generated with version 1.2.0 of STM32CubeF7.The code didn't function correctly after I upgraded to version 1.3.1 of STM32CubeF7(no SAI data was present and no DMA complete interrupts were being generated).Comparison of the code generated for 1.2.0 and 1.3.1 shows a problem in the initialization of the SLOTR register within stm32f7xx_hal_sai.c : HAL_SAI_Init().With 16 slots enabled, the value contained with hsai->SlotInit.SlotActive = 0xFFFF0000.In the 1.2.0 version of the function, SLOTR is initialized as;hs

Posted on January 03, 2017 at 18:47Hi All,Are the 64pin versions of the stm32f7 chips in cubeMX?I can find the 100 pin parts but not the 64 pin partsMark#stm32f7 #stm32cubemx

Posted on January 23, 2017 at 03:31I just created a project for the stm32f0-discovery board including FreeRTOS and building with OpenSTM32/eclipse. The path to cmsis_os.h was missing and easily fixed by adding 'Middlewares/Third_Party/FreeRTOS/Source/CMSIS_RTOS' to the include paths. I have attached the .IOC file for your viewing pleasure. (Apologies for misnaming it - it should have been myMX19proj but it seems that once saved, it cannot be changed.)Thank you for your continuing support of Cube on Linux.best,hank#stm32cubemx #freertos

Posted on January 19, 2017 at 21:19I'm compiling and running GPIO_EXTI example code for Nucleo-F767ZI board (on SW4STM32). The handler that blinks LED1 isn't connected and this matches what readme.txt says:In this example:    - EXTI_Line15_10 is connected to PC.13 pin      - when falling edge is detected on EXTI_Line15_10 by pressing User push-button, LED1 toggles onceOn STM32F767ZI-Nucleo:    - EXTI_Line15_10 is connected to User push-buttonSo, handler isn't set for the Nucleo board. When I push user button and pause (debugging) the program, it is then in default handler / infinite loop. All correct.However, the program never goes beyond those lines of EXTI15_10_IRQHandler_Config(void):  /* Enable and set EXTI line 15_10 Interrupt to the lowest priority */  HAL_NVIC_SetPriority(EXTI15_10_IRQn, 2, 0);  HAL

Posted on January 19, 2017 at 14:36CubeMX provides a library for using CDC but its not very clear and also i couldn't find any good descriptions of functions and what they are supposed to do so can anyone point me to a good tutorial i'll be glad#usb_cdc #cube-mx #stm32 #stm32f4-discovery #keil-uvision

Posted on October 30, 2016 at 18:46 I use STM32CubeMX v 4.0 to configure CMSIS SPI Driver. I believe I do right DMA configuration: But after code generation file MX_Device.h hasn't defines to enable DMA for SPI. /* DMA Configuration */ /* DMA SPI2_TX */ /* DMA SPI2_RX */ So, I have to modify it to enable DMA: /* DMA Configuration */ /* DMA SPI2_TX */ #define MX_SPI2_TX_DMA_Instance DMA1_Stream4 /* DMA SPI2_RX */ #define MX_SPI2_RX_DMA_Instance DMA1_Stream3 #stm32cubemx #dma #bug

Posted on January 19, 2017 at 01:39I have setup the STM32CubeMX project.. (STM32F302RExx)I use the ADC in continues / scan mode.I have DMAContReq = true..I then setup DMA on ADC1-CH1 with HIGH prio..but when i generate my Cube-code... i don't see ANY code for the DMA setup ??The ADC's works fine if i poll them.This : 'DMA_HandleTypeDef hdma_adc1;' I see..but thats IT .. no more references.. i have all in my MainFile..Any clues ?/M.H.p.s..I'm guessing i am missing something like THIS (THIS IS NOT TO FIND IN CUBE-GENERATED CODE):hdma_adc1.Instance = DMA1_Channel1; hdma_adc1.Init.Direction = DMA_PERIPH_TO_MEMORY; hdma_adc1.Init.PeriphInc = DMA_PINC_DISABLE; hdma_adc1.Init.MemInc = DMA_MINC_ENABLE; hdma_adc1.Init.PeriphDataAlignment = DMA_PDATAALIGN_WORD; hdma_adc1.Init.MemDataAlignment = DMA_MDATAALIGN_WORD; hdma_adc1.Init.Mode =

Posted on January 20, 2017 at 01:51 I want to get UART Interrupted data to vary LED blinking speed. For example,If I send 1 then speed 100ms or send 2 then speed 200ms. I made a cod using CubeMX and Interrupting with just pressing ''Enter'' works perfect(Not sending any data) (I pressed ''Enter'' 3 times in Line Sender) but If I send some character like below, It iterrupts just one time and never interrupt again with my further interrupt action.

Posted on July 20, 2016 at 09:43Hi, in the last time I played with the power modes of the STM32L0 and discovered an issue with the GPIO-HAL driver. The used version of the HAL is 1.7.0 with a STM32L053 nucleo board. I discovered that the initialization of USART-TX and -RX pins will increase the power consumption in STOP mode considerably. So I tried to deinitialize the pins to their reset state with the function HAL_GPIO_DeInit() before going into STOP mode. But the consumption remains the same so I looked into the DeInit-function and recognized the line where the I/O mode is changed (line 327 in stm32l0xx_hal_gpio.c):GPIOx->MODER &= ~(GPIO_MODER_MODE0 << (position * 2U)); The I/O mode is changed to ''input'' but the reference manual for the controller (RM0367) says in chapter 9.4.1 that the reset state for the I/O mode is ''Analog'' . Acco

Posted on January 13, 2017 at 14:51 edit: previously I wrote that problems occurs with freertos, I checked without it and I am having the same problem (ending in dead loop after sending more than 8 characters). Steps to reproduce: Create project in CubeMX for STM32F4DISCOVERY, enable USB_FS Device only. Configure clock: PLL_N = 72, PLL_Q=3, that gives me 48 MHz for usb, other settings remain unchanged. In configuration I enable CDC device with default parameters. Generate code for SW. I add some led toggle in order to know it it is running. /* StartDefaultTask function */ void StartDefaultTask(void const * argument) { /* init code for USB_DEVICE */ MX_USB_DEVICE_Init(); /* USER CODE BEGIN 5 */ /* Infinite loop */ for(;;) { HAL_GPIO_TogglePin(LD3_GPIO_Port, LD3_Pin); osDelay(500); } /* USER CODE END 5 */ }�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?

Posted on December 21, 2016 at 14:31Good morning,In my project I use STM32F303RC and I have two ADCs working with DMAs and triggered by a timer. ADC1 has two analog channels to be sampled, ADC4 only one. While I was working with CubeMX 4.17 I had no problems.Then I updated CubeMX to 4.18. I did not change my program at all, but ADC1 stopped working correctly.For some reason in the ADC1 configuration CubeMX added this part:/**Configure the ADC multi-mode */ multimode.DMAAccessMode = ADC_DMAACCESSMODE_DISABLED; multimode.TwoSamplingDelay = ADC_TWOSAMPLINGDELAY_1CYCLE; if (HAL_ADCEx_MultiModeConfigChannel(&hadc1, &multimode) != HAL_OK) { Error_Handler(); }This caused the ADC1 to work correctly only in DEBUG mode but not in RUN mode. It took me a bit to find out that this was the cause. When I remove this initialization everything works fine again.Now, my ques

Posted on January 12, 2017 at 10:59Hi !First, I use the version 4.18.0 STM32Cube V1.0, and Atollic True Studio 7.0.1, so both are (normally) the last ones.I try to generate, with CubeMX, a project on STM32F417VG, using several libraries, the STM32_USB_HOST_LIBRARY for MSC being one of them. My problem is that I cannot use this project !I generate the project -> I compile -> Works !I generate the project -> I add these lines in the main.h :&sharpinclude ''usbh_def.h''USBH_HandleTypeDef hUSBHost;I doesn't change anything else, and I don't write anything else but it doesn't compile, I have some strange errors. Four of them are about four different macros (USBH_MAX_DATA_BUFFER, USBH_MAX_NUM_ENDPOINTS, USBH_MAX_NUM_INTERFACES, USBH_MAX_NUM_SUPPORTED_CLASS) in the file ''usbh_def.h'' with this message :Macro undeclared here (not in a function)But those macros are declared in usb

Posted on October 23, 2015 at 16:47There seems to be a bug in the new 4.11 release of STM32CubeMX. Previously in 4.10, regenerating an EWARM project with CubeMX kept the files manually added to the project. Now in 4.11, regenerating an EWARM project resets the project entirely. Is this a bug, a removed feature, or am I missing a setting somewhere in 4.11? I even reinstalled 4.10 to check that it keeps user files. Unfortunately 4.10 won't open files modified in 4.11 #bug-stm32cubemx

Posted on October 17, 2016 at 21:38 Hi ! I'm using freeRTOS with STM32CubeMX. While playing with signals for inter-thread communication I came across the different return value of function osSignalSet() The CMSIS standard states: int32_t osSignalSet(osThreadId thread_id, int32_t signals) Parameters [in] thread_id thread ID obtained by osThreadCreate or osThreadGetId. [in] signals specifies the signal flags of the thread that should be set. Returns previous signal flags of the specified thread or 0x80000000 in case of incorrect parameters. But STM32CubeMX creates: /** * @brief Set the specified Signal Flags of an active thread. * @param thread_id thread ID obtained by \ref osThreadCreate or \ref osThreadGetId. * @param signals specifies the signal flags of the thread that should be set. * @retval osOK if successful, osErrorOS if failed . * @note MUST REMAIN UNCHANGED: \b osSignalSet shall be cons