STM32CubeMX (MCUs)

Posted on January 30, 2017 at 12:21HiI am trying to setup a new touch sense project and have  question:I configured certain pins as TSC, how do I add the the middleware TSC LIb in CubeMx now? For my Nucleoboard L053R8 CubeMX under middlewares doesnt show TSC but only: USB_device/FREERTOS/FATFS.Thx#tsc #tm32-cubemx

Posted on December 17, 2017 at 23:43I was setting up a project which uses 3 UARTs + USB on a F103.CubeMX reports a conflict on UART 1 when USB is configured.I checked the ref man and datasheet but was unable tosee from what this conflict should arise.There are no shared pins between these IPs.I also diffed the generated code between variants with USART1disabled or enabled and did not see obviuos diffs which do not originatedin the fact of wether USARt1 was configured or not.Is this a false positive on CubeMXes' side?Thanks.#usb #cubemx-project #stm32f1-uart

Posted on March 04, 2017 at 03:36hello. I am  luis.Recently I use stm32f051x touch sensing feature that setup touch sensing with CubeMx(the latest ver.).but after test touch sensing, I get touch sensing value only '1'.Searching St community, i have a question.I setup touch sensing code only using CubeMx provided Hal_tsc .. Do I need add another touch sensing library??And where I get touch sensing Full example code??Best regards.#cubemx #stm32f051x #touch-sensing #touch

Posted on December 13, 2017 at 11:43hello,i am trying to send data to pc over the otg used as a virtual com port. The data is received with a terminal program (HTerm). In order to send data i am using the function CDC_Transmit_FS. For a basic test the string 'start' is sent to the pc. Therefor i use the following code. The code is implemented in the while loop of the int main function:while(1){if(((USBD_CDC_HandleTypeDef*)(hUsbDeviceFS.pClassData))->TxState==0){while(CDC_Transmit_FS(((uint8_t*)&'start'),sizeof('start')) != USBD_OK);}}This works and i can receive the data on the terminal program on my pc.What doesn't work: If i try to send 'stop' after the 'start' string.while(1){if(((USBD_CDC_HandleTypeDef*)(hUsbDeviceFS.pClassData))->TxState==0){while(CDC_Transmit_FS(((uint8_t*)&'start'),sizeof('start')) != USBD_OK);

Posted on December 14, 2017 at 13:25In the generated GPDSC file, information about preprocesor definitions and include paths are missing. This needs further manual processing of the build proces generated from GPDSC.What is missing, e.g. for attached .ioc file List of include directories need to build the project IncDrivers/STM32F0xx_HAL_Driver/IncDrivers/CMSIS/Device/ST/STM32F0xx/IncludeDrivers/CMSIS/IncludePreprocesor deffinitions to correctly build the project USE_FULL_LL_DRIVERSTM32F030xCIn other project types, all these informations are available.MCU: STM32F030F4PxPC OS: LinuxCubeMX version: 4.23.0Firmware package: STM32Cube FW_F0 V1.9.0#gpdsc #stm32cubemx #bug

Posted on December 14, 2017 at 13:00I have generated GPDSC file from the attached IOC project and the output has wrong items. Real source files are not under correct Csub component. RCC is under USART, EXTI is under RCC, DAC and GPIO (both .c and .h files)Some files are multiple times in the output lige stm32f0xx_ll_rcc.h, stm32f0xx_ll_exti.c, ...some source files are wrongly categorised as header files like stm32f0xx_ll_utils.cHere is part of generated GPDSC file with highlighted errors (blue are duplicates, red are wrong categories), see the attachement for complete IOC and generated GPDSC.    <component Cclass='Device' Cgroup='STM32Cube HAL' Csub='USART' Cversion='1.7.0'>      <description></description>      <files>        <file

Posted on December 08, 2017 at 21:56After CubeMX griped that my software was too old, I tried to upgrade from the New Libraries Manager, but there was an error downloading the file. I fetched the file manually, then tried installing using the New Libraries Manager 'local' function. I get a 'Problem during unzip of file', though the file unzips fine under 7Zip.Can anybody provide an alternate method of installing this library? This is preventing me from even _starting_ a project.#cubemx-zip-file-new-library-manager

Posted on December 10, 2017 at 11:16Hii'm config evboar  nucleo with CubeMX  the send  data work fine but  recive data with HAL_UART_RxCpltCallbacki's work one time and second time is stuck in  loop anddon't reach to HAL_UART_IRQHandler(&huart1) again ;i don't know why it's working one time(  maybe is relevant to RXN flag  )thanks static void MX_USART1_UART_Init(void){  huart1.Instance = USART1;  huart1.Init.BaudRate = 115200;  huart1.Init.WordLength = UART_WORDLENGTH_8B;  huart1.Init.StopBits = UART_STOPBITS_1;  huart1.Init.Parity = UART_PARITY_NONE;  huart1.Init.Mode = UART_MODE_TX_RX;  huart1.Init.HwFlowCtl = UART_HWCONTROL_NONE;  huart1.Init.OverSampling = UART_OVERSAMPLING_16;  huart1.Init.OneBitSampling = UART_ONE_BIT_SAMPLE_DIS

Posted on November 10, 2016 at 16:01Pin user label disappears when I change the pin function in the cubeMX GUI. This is not an expected behavior, since the already given name of the pin has not changed. #cubemx

Posted on October 26, 2017 at 13:12As I explaned inhttps://community.st.com/0D50X00009XkXviSAF, I have found another big error in the code generation of STM32CubeMX 4.23.In this case, the bug is related to FATFS + SDMMC. In my case, I am working with an STM32F767 microcontroller.I updated an old project to change some config settings, and when I regenerated the project files with STM32CubeMX 4.23, my SDMMC peripheral stopped working correctly. So far, it was working nice with the code generated by an older version of STM32CubeMX.So, (thanks to GIT) I checked which files changed since last release, and I noticed that the problem was in 'SD_initialize' function in 'sd_diskio' file (inside Src folder).The code that the newest version generates is:DSTATUS SD_initialize(BYTE lun)

Posted on December 06, 2017 at 19:03In CubeMX (ver: 4.23 mcu: STM32F427) I'm trying to define two ports PE10 and PB10 as GPIO_EXTI10 (I need to get edge interrupt on either one).However, in the 'Pinout' view, when I click GPIO_EXTI10 for PB10 and then for PE10, PB10 is erased (the green turn white). Am I trying to do something that is not possible at all or is it only a limitation of CubeMX?Is there another way to do it in CubeMX?#cubemx #stm32f4 #exti

Posted on December 05, 2017 at 22:33I am setting up a USB OTG based project on the STM32F4 Discovery Board.  I am using STM32CubeMX 4.23.0 and STM32Cube_FW_F4_v1.18.0.  This is the same set up on my Windows 10 and Linux Mint 18.2 PCs and both have the same error.The clock configuration tab is always indicating that the clock set up is in error.  In the PLL Source Mux,  the HSI input is selected and has a red box around it with the message 'PLL Mux should have HSE as input selected'.  The HSE button is, of course, grayed out.  It generates the code but I get warnings about an invalid clock configuration.Is this a problem with STM32CubeMX?  Is there actually an invalid clock configuration?  Is the generated code safe to use?#stm32f4-discovery #usb #stmcubemx

Posted on November 26, 2017 at 12:30My settings:Board: STM32F100RBOS: Windows 10 x64Version: STM32Cube V1.0 - 4.20.0IDE: Coocox CoIDE 1.7.8 Problem:   I noticed that after regenerating the code I just couldn't access the board, messages like 'Please, connnect the cable' or  'Board was not found' started prompting after downloading others code to the board. The only way to restore the access was using STLink Utility (Holding the reset button (Black button,RST, in the board) and erasing all the memory).   However, this issue also happened when checking the option to Create peripheral separate pairs in .c and .h, something like that, this time the code blocks the access just after the download.   In both cases the code keeps running but you cannot debug, reset or download new ones. Solution:    After some tria

Posted on December 02, 2017 at 10:36Hello,CubeMX is a good software but there are many things it's still missing, it'd be very neat to have these options implemented:1- A Timer calculator similar to the external tool by mikroelectronika but for all MCUs and for all Timer modes.for example i just want a timer to count a limited time(without interrupts) but i have to read the datasheet just for that.it could be as simple as what we have for SPI clock or just more advanced to have all the option illustrated with a simple text(or GUI)2- All peripherals could benefit a description section which can be modified inside CubeMX.(for example just to comment what that specific timer is used).3- in Clock Configuration window it would be very nice to have the option to know which peripherals are connected to which APB bus. currently it shows some of them and for example for timers we need to read the datasheet.4- datas

Posted on November 29, 2017 at 14:41I'm trying to create a MSD for the STM32L073RZT6, and want to use 64K of the flash memory as storage.I've tried to get the erase/write correct, but Windows says the format fails...Can anyone spot the obvious mistake?&sharpdefine EEPROM_START    0x8020000&sharpdefine EEPROM_LENGTH 0x0010000&sharpdefine STORAGE_LUN_NBR 1&sharpdefine STORAGE_BLK_SIZ 0x200&sharpdefine STORAGE_BLK_NBR (EEPROM_LENGTH / STORAGE_BLK_SIZ)int8_t STORAGE_Read_FS (uint8_t lun, uint8_t *buf, uint32_t blk_addr, uint16_t blk_len){ /* USER CODE BEGIN 6 */ uint32_t newAddr = (STORAGE_BLK_SIZ * blk_addr) +EEPROM_START; memcpy(buf, (void *) newAddr, blk_len * STORAGE_BLK_SIZ); return (USBD_OK); /* USER CODE END 6 */ }int8_t STORAGE_Write_FS (uint8_t lun, uint8_t *buf, uin

Posted on November 27, 2017 at 10:40hi,I set external interrupt 3 on cubemx to Rising edge and need to change of trigger level that on its routine.I write this code on interrupt 3 routine, but it always trigger by rising edge (down't execute falling edge) (PLEASE: see attach image)how can I fix this problem with HAL driver command?void EXTI3_IRQHandler(void){  /* USER CODE BEGIN EXTI3_IRQn 0 */switch(valuee){    case 10:    HAL_GPIO_WritePin(RLED_GPIO_Port,RLED_Pin, GPIO_PIN_SET);    CLEAR_BIT(EXTI->RTSR,0X03);    SET_BIT(EXTI->FTSR,0X03);    valuee=15;    break;        case 15:    HAL_GPIO_WritePin(RLED_GPIO_Port,RLED_Pin, GPIO_PIN_RESET);    CLEAR_BIT(EXTI->FTSR,0X03);

Posted on November 12, 2017 at 10:03Hello.I want to teach simple programming for my friend, and guess what, none of DSI examples for STM32F469i-Disco worked from CubeMX folder.\STM32Cube_FW_F4_V1.16.0\Projects\STM32469I-Discovery\Applications\Display\LCD_PaintFor the love of god, discovery kits suppose to give simple examples how to use device, and I spend 2 hours trying all DSI examples, none of them worked. This is not right.Had to rewrite it in SPL, it start to work, but  touchscreen porting was to difficult, so i have to switch to STM32F429i to make it work.Please ST, fix this problems, and please, use SPL for H7 and F7 series, we love SPL, and we don't need CubeMX bugs ruing our lifeI only use CubeMX for footprints and AF functions, that it !#bugs #hall-with-bugs #hall-does-now-work #hall-sukcs #cubemx #where-is-spl

Posted on November 24, 2017 at 16:09There is an issue with the PLLI2S initialization in generated Code from CubeMx 4.23.0. It is skipped under certain conditions detailed below.The clock network given in the picture is initialized with the following struct field in SystemClock_Config():PeriphClkInitStruct.PeriphClockSelection = RCC_PERIPHCLK_PLLI2S | RCC_PERIPHCLK_USART3  | RCC_PERIPHCLK_CLK48; The PeriphClkInitStruct is then passed to HAL_RCCEx_PeriphCLKConfig(RCC_PeriphCLKInitTypeDef  *PeriphClkInit) in stm32f7xx_hal_rcc_ex.c. This function checks each bit of the bitfield and initializes the corresponding clock if necessary. However, the bit for PLLI2S is not checked properly. Here is the faulty code:  /*-------------------------------------- PLLI2S Configuration ---------------------------------*/  /* PLLI2S is configured when a peripheral will use it as source clock : SAI1, SAI2, I2S or

Posted on December 21, 2016 at 09:01Hello. I found something strange in my STM32F100RC controller. I made a clean project in latest CubeMX to show this error.When I try toswitch my MCU from full JTAG (reset state) to use only SWD pins the programming/debug interface stops working completely. I was forced to reflow two ICs before I found there is the error with init procedure.The code:int main(void) { uint32_t initPauseCounter = 0xFFFFF; // pause that helps us to burn new firmware while(initPauseCounter--); // before SWD stops working /* 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_USART1_UART_Init(); __HAL_AFIO_REMAP_SWJ_ENABLE(); printf('AFIO->MAPR state: 0x%08lX\n', READ_REG(AFIO->MAPR)); printf('AFIO_MAPR_SWJ

Posted on November 23, 2017 at 11:27Hi HAJJEM.Oussema after some time CUBEMX brings in trouble in an IAR project in a way that 'go to definition of variables or functions' no longer works. CPU usage of IAR keeps growing and growing.  Can you reproduce this?1. generate any project with cube2. Add you own user files AND directories3. add some timers or what ever in cube4. regenerate project5. loop steps 2-4 couple of times6.the following feature is broken in IAR ->  'go to definition of ' variables or functions. This feature  in IAR becomes in stable. 99% of the time it will be broken.When I look at ewd/ewp files of IAR, with every CUBE MX generation the file grows. Why does CUBEkeep adding  <state></state>?Basically ewp files grows in content for no reason!Workaround:1. delete EWP/EWD files.2. Regenerate projec

Posted on May 20, 2017 at 15:56Hi,After generation of code with STM32CubeMx (release 4.21.0), Error_Handler() interface present in main.h is not specified to be used in C-style linkage as it's done in the rest of the code.This performing a linkage error with IAR C++ compiler.Please, fix it in the next release.Thx and Regards#main.h #c-style-linkage #stm32cubemx-4.21.0 #error_handler()

Posted on September 07, 2017 at 18:31I am trying to compile the CubeMX expansion for AWS, but I get an Error[Lp050]: placement includes both uninitialized sections (example 'ro data section UNINIT_FIXED_LOC in iot_flash_config.o symbols: [lUserConfig]') and sections with content (example 'initializers for P3'). Does anyone know how to fix this?#cubemx #aws

Posted on November 13, 2017 at 23:41Hi,I am working with STM32F072RB and I am developing composite device. The device consists of 3 different interfaces but only one has in and out endpoints. It's custom HID with input and output report of 64 bytes. Really nothing special. My code includes many define switched so I can easily switch from composite device with 3 interfaces to simple Custom HID device. So to my question...I am sending data from PC to device. If I am using device as a custom hid device I can receive data and DataOut function gets always called. static uint8_t USBD_HID_DataOut (USBD_HandleTypeDef *pdev, uint8_t epnum){...}Received data is valid.Then I switch to composite device configuration and that same Custom HID is just one those 3 interfaces in that composite device. In that case I experience strange behaviour...The first packet I send from PC to device has all zeros insi

Posted on November 10, 2017 at 08:05I am using the STM32F765BIT micro controller(208 pin package) in our custom board, I am using STM CubeMx generated code. I have selected two SPI (SPI1 & SPI2) interface both are with same configuration. with SPI2 I can able to access external SPI-device (both read write is working).But when I tried with SPI1 I can't able access same device . I also cross checked the signal levels of SPI1 interface , No signal is coming (CS,CLK,MOSI). Is there any additional configuration needed to use SPI1 interface. Can you please give some brief details regarding this.Thank youBest regards Maheshwar#keil-mdk5 #stm-32f7 #cubemx #stm32-f7 #spi-write-and-read

Posted on October 17, 2017 at 22:27Hello,I am trying to estimate power consumption on the stm32h7. The use case i am interested in is sampling 6 channels using ADC3 and transferring the sampled data to memory using BDMA, all this while D1 and D2 domains are in stop mode and only D3 is working. The thing is that i am not able to configure the D1&D2 to stop modes. If i set the power mode to RUN, then D1 has only two options - DRUN/CRUN and DRUN/CSLEEP, in which case D2 only has DRUN. If i set the power mode to STOP, then D1 has DSTOP/DSTANDBY, D2 has DSTOP/DSTANDBY and D3 only has DSTOP.The power consumption in the first case looks too high to me - 17mA. And off course in the second case D3 is in DSTOP, so it is not what i want.I am doing something wrong with the configurations, or is it because STM32CubeMX Version 4.22.1 does not support this work mode in power consumption