STM32CubeMX (MCUs)

Posted on February 22, 2017 at 14:43Hello. I am trying to integrate SD Card (Transcend 4GB) with STM32F407 Disc board. I had followed all previous discussion & made corrections yet i am getting Error. I have attached my clock configuration, Pin diagram of STM Cube MX & Detail Code. Can anybody tell me what extra changes i Need to do to get rid of error. Usually i am getting Disc error (Program is not going aheaf 'f_mount()'). When i press reset button it gives Disc Error. I changed all GPIOs to 'Pull high'. I am not sure if 3V power is enough for the Memory Card as i am directly connecting my VDD pin (STM32F4) to Memory Card. I have connected Memory Card by following way to board:1. Card Detect (PIN1) to PC2 2.CMD (PIN2) to PD23. Clock(PIN5) to PC124. VDD(PIN4) to 3V5. DAT0(PIN7) to PC8Any comments about Code & configurations will be highly appreciated.#

Posted on November 04, 2016 at 13:42 In STM32Cube MX 4.17 I have set up an empty STM32L476 Nucleo project with and created code for the Low-Layer API. The parameters were: LL_PWR_REGU_VOLTAGE_SCALE2LL_RCC_MSIRANGE_8 The function SystemClock_Config() of the generated code starts with void SystemClock_Config(void) { LL_PWR_SetRegulVoltageScaling(LL_PWR_REGU_VOLTAGE_SCALE2); LL_RCC_MSI_Enable(); /* Wait till MSI is ready */ while(LL_RCC_MSI_IsReady() != 1) { } LL_RCC_MSI_EnableRangeSelection(); LL_RCC_MSI_SetRange(LL_RCC_MSIRANGE_8); LL_RCC_MSI_SetCalibTrimming(0); LL_FLASH_SetLatency(LL_FLASH_LATENCY_2); if(LL_FLASH_GetLatency() != LL_FLASH_LATENCY_2) { Error_Handler(); } LL_RCC_SetAHBPrescaler(LL_RCC_SYSCLK_DIV_1); ⋮ The documentation (DocID024597 Rev 4, section 5.1.7 Dynamic voltage scaling management) reasonably states that the FLASH latency must be set up

Posted on November 23, 2016 at 17:30The absolute path of a CubeMX project is embedded in the .ioc file. This makes a little more difficult moving the project elsewhere or restarting with the project for example when retrieving it from a remote Git repository. It would be better having the option to keep the project location-agnostic and to regenerate the project-derived files in the directory which contains the .ioc file. #feature-request #stm32cubemx

Posted on February 26, 2017 at 19:34Hi.I have noticed some problems when generating code using STM32CubeMX 4.19.0. I included the zipped project in the attachments. In the Src/main.c file it generates the declaration of the FSMC init functionstatic void MX_FSMC_Init(void);but it is never defined. All the other functions get properly defined below the main function but this one does not. It would really help to have this code generated since using FSMC is tricky.There is also a second issue with the code generation. I have set up a DMA Memory to memory transfer and it generated some code for it but it didn't define the variable is uses. I had to put the variable definition manually in my private global variable definitions.static void MX_DMA_Init(void) {   ...    hdma_memtomem_dma2_stream0.Instance = DMA2_Stream0; /* <------ hdma_memtomem_dma2_stream0 is undefine

Posted on February 13, 2017 at 09:43Hello everybody,I'm working on a webserver application, and I use the lwip 1.4  tcp/ip stack generated from the Cube Mx older version. Unfortunatelly I don't remember which version of Cube Mx because it was a long time ago, when I generated this project.(2015) But I know that version of Cube Mx containes just the Lwip 1.4, while the latest version of Cube Mx already contains the LwIp 1.5. This project is an old project and sometimes I paused to develop other projects, but it's the time when I would like to finish it.I'm working on STM32F407 device. I implemented the binary file upload, which wasn't implement on the stack in default. Sometimes when I try to upload the files, get TCP retransmission and TCP Dup Ack error on network capture. Sometimes the file upload was succesfully and somtimes wasn't. Can You tell me somebody why it's caused? I didn't find the right solution up to now.The two ca

Posted on March 14, 2017 at 01:39Hello everyone,I'm using the STM32F767ZIT on a custom PCB with an external 25MHz crystal. The project greatly involves around receiving messages from three separate controller area network (CAN) buses at 1 Mbits.I used the STMCube to map the functions/pins to the hardware and to generate c-code for the inits. For some reason, I get stuck in the HAL_CAN_Init every time without even adding a single line of user code. CAN TX is connected to PB9 and CAN RX is connected to PB8.The microcontroller doesn't seem to reset the INAK bit and therefore gets stuck in the while loop at line 306 in the stm32f7xx_hal_can.c file. According to the reference manual,'This bit is set by hardware and indicates to the software that the CAN hardware is now in initialization mode. This bit acknowledges the initialization request from the software (set INRQ bit in CAN_M

Posted on December 06, 2016 at 21:19Cube slows down the point when it is pretty much very hard to use. Sometimes clock resolver ends up in an continous loop which leads nowhere. Also on chips with more pins like BGA packages Cube slows down noticeably. Not sure how it is on Windows or Linux as I only use OSX for development.#stm32cubemx

Posted on March 05, 2017 at 20:12Hi,I'm using STM32F4 as a USB Host for writing data to a mass storage (flash drive) in FS mode using CubeMX. As we know USB-FS nominal speed is 12Mbit/s and I set this speed in CubeMX for my application. However, the maximum writing speed that I reached is about 560 kbit/s!I don't know what is the reason. Is there any special setting in FATFS,USB_FS or USB_Host configurations that affects  speed?My code is similar to CubeMX example in repository,but I use FS Mode rather than HS used in example.Is there anything important with preparing data buffer for writing (that affects speed)? My writing code is:for(int16_t z=0;z<1024;z++) { sprintf(buf,'%5.5f,%5.5f\r\n',fbuf[z][0],fbuf[z][1]); res = f_write(&MyFile, buf, strlen(buf), (void *)&byteswritten); if((byteswritten == 0) || (res != FR_OK)) {Error_Handler();} }Thank

Posted on January 27, 2017 at 10:38I use STM32CubeMX ver. 4.19.0.I've configured DMA channel for I2S peripheral and saved the project. But when I try to open it again I get this warning:The project is attached.#bug #i2s #stm32cubemx #dma

Posted on February 15, 2017 at 12:22Hello everybody,I encountered the following problem when generating code from CubeMX for the USART peripheral of a STM32L476QEIx:SETUP: STM32CubeMX 4.19.0CubeL4 Version 1.6.0CPU STM32L476QEIxPROBLEM: USART1 is configured with Word length 9 bits (including parity) and Parity even (so I get 8 bits data and one parity-bit)But CubeMX does not set the parity information in the USART_InitTypeDef structure in the auto-generated function MX_USART1_Init()It  sets the values of the structure-element for the parity options none and odd though - see the attached screenshotsFor even parity the USART-registers are not correctly initialized, i.e. the Parity-Enable bit is not set and therefore no parity generated -> so this really is a problem and leaves the USART incorrectly initialized!Did anybody notice

Posted on December 31, 2016 at 08:52 Hi, I've created a very simple project in STM32CubeMX for the F3DISCOVERY board. The only things I changed from the default are enabling MCO, and setting the PLL multiplier to When I import the code into SW4STM32 and press build, I get the following error: 17:41:40 **** Build of configuration Debug for project test_64mhz **** make all Building file: ../Src/main.c Invoking: MCU GCC Compiler /Users/jeremy/stm32_test/rcc_64mhz/test_64mhz/Debug arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -D__weak=__attribute__((weak)) -D__packed=__attribute__((__packed__)) -DUSE_HAL_DRIVER -DSTM32F303xC -I'/Users/jeremy/stm32_test/rcc_64mhz/test_64mhz/Inc' -I'/Users/jeremy/stm32_test/rcc_64mhz/test_64mhz/Drivers/STM32F3xx_HAL_Driver/Inc' -I'/Users/jeremy/stm32_test/rcc_64mhz/test_64mhz/Drivers/STM32F3xx_HAL_Driver/Inc/Legacy' -I'/Users/jeremy/stm32_test/rcc_64mhz/test_64mhz/Drivers/CMSIS/Device/

Posted on January 21, 2017 at 19:42I'm trying to get familiar with CubeMX and STM32 development process and I'm a bit puzzled with the L1 Discovery.To do so, I'm trying to 're-create' the demonstration FW shipped with the board using CubeMX.When creating a new project for the L1 Discovery board, a number of pin are already defined, as they are used by the board design, which is normal.However, I cannot have the PINs properly assigned in CubeMX to reflect the board. For example, regarding the screen someof the segments are used by the touch sensors. I haven't found a way to tell the system to use some other PINs for the signals. The SEG 3 to 6 conflicts and the followings are shifted, preventing the declaration of the other SEGments.Would it be possible to  create the demo FW with CubeMX, or the board differ too much from the original design, it has to be made by hand?#stm32l152 #cubemx #discovery-l1

Posted on February 24, 2017 at 11:30Hi There seems to be a bug in the uart driver for the STM32L0, STM32F7 and STM32F4 but not for the STM32L1The bug is that you can't send while receiving on the uart:The code for STM32L0, STM32F7 and STM32F4:HAL_StatusTypeDef HAL_UART_Transmit_IT(UART_HandleTypeDef *huart, uint8_t *pData, uint16_t Size){    /* Check that a Tx process is not already ongoing */    if(huart->gState == HAL_UART_STATE_READY)    {The Code for the STM32L1HAL_StatusTypeDef HAL_UART_Transmit_IT(UART_HandleTypeDef *huart, uint8_t *pData, uint16_t Size){ uint32_t tmp_state = 0; tmp_state = huart->State; if((tmp_state == HAL_UART_STATE_READY) || (tmp_state == HAL_UART_STATE_BUSY_RX)) {or in overall, you can't use the RX if you are usi

Posted on February 21, 2017 at 23:10Hi.I am trying to generate code via STMcubeMX for UART via DMA. I have configured the UART and DMA correctly to my liking, but when I press generate source code the only code for the DMA is:/** * Enable DMA controller clock */static void MX_DMA_Init(void) { /* DMA controller clock enable */ __HAL_RCC_DMA1_CLK_ENABLE();}When I look into the logfile for STMcubeMX I can see when it is trying to generate the code for the DMA it gives these errors:[INFO] ImportTextPane:147 - (OptionalMessage_ERROR) IP (DMA) : Parameter (Channel) has Id (UART5_RX) currently not set[INFO] ImportTextPane:147 - (OptionalMessage_ERROR) IP (DMA) : Parameter (PeriphDataAlignment) has Id (UART5_RX) currently not setINFO] ImportTextPane:147 - (OptionalMessage_ERROR) IP (DMA) : Parameter (MemDataAlignment) has Id (UART5_RX) currentl

Posted on January 12, 2017 at 08:34hiI'm using CubeMX 4.18.0 recently.by the way, Every time An error occurs when creating a TrueStudio project using the CubeMX 4.18.0.Please, help.#cubemx #truestudio

Posted on February 13, 2017 at 18:23Hello!NUCLEO-F767ZI lost in STM32CubeMX 4.19.0 while it was introduced in 4.18.0.I have installed STM32CubeMX as standalone (on a different computer) and as a plugin for Eclipse (as update) - the same result: NUCLEO-F767ZI missing. What happened?Regards,Dmitrij#stm32cubemx

Posted on February 08, 2017 at 23:03STM32L082xx WLCSP49 Not in CubeMX - can the stm32l072czex be used instead? what is the difference between these two parts?#stm32 #cubemx #stm32l0x2

Posted on February 11, 2017 at 19:50 Hi, I'm trying to set up a SPI connection for an AS5311 sensor on my STM32F I want to use the hardware controlled NSS signal, which is working pretty well - but only for high baudrates. I am using CubeMX to configure my clocks and peripherals. If I set the baudrate above 1 MBaud and read the sensor data with the HAL_SPI_Receive_IT(...) function the NSS signal is used properly. But if I change it to a baudrate below 1 MBaud, NSS is not working anymore. I do not change anything on my source code. I olny use the prescaler setting for SPI in CubeMX. Does anyone know the reason for this? Unfortunatly the sensor does not support baudrates above 1 MBaud. See the pictures below to comprehend my problem #hal #cubemx #baudrate #nss #nss-cs #spi

Posted on February 11, 2017 at 09:10Hello All,I am using a single channel for AD Conversion from an analog front end on STM32L76. But I want a specific sampling rate of ADC. Currently, I am achieving this by using a timer enabling conversion at the frequency I want. But this implementation requires the usage of two peripheral: TIMER and ADC. Could you please help me to select ADC sample frequency? I am using STMCUBEMX for generating initialization code. If possible, then how do I select the specification from STMCUBEMX. Based on application, I sometimes need to change the ADC sampling rate from software end. So I need to understand the concept.#stmcubemx #stm32 #adc-sampling-rate

Posted on January 25, 2017 at 09:50 Hi everyone, I try to generate PWM signal usingSTM32F072B. I set the PA0 as TIM2 and set channel 1 to PWM Generation and set the GPIO maximum output speed to high. The other configurations aredefault. In the main function, I add theHAL_TIM_PWM_Start(&htim2, TIM_CHANNEL_1); before the while loop and change the number of thehtim2.Init.Prescaler,htim2.Init.Period andsConfigOC.Pulse.The PWM signal is generated but ithas 12us rise/fall time, the attachment the snapshot of the signal. The code below is generated by using CubeMx ver4. Anything I missed out? int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_TIM2_Init(); HAL_TIM_PWM_Start(&htim2, TIM_CHANNEL_1); while (1){} } void SystemClock_Config(void) { RCC_OscInitTypeDef RCC_OscInitStruct; RCC_ClkInitTypeDef RCC_ClkInitStruct; RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI; RCC_OscInitStruct.HSIState = RCC_HSI_ON; RCC_OscInitStruct.H

Posted on January 12, 2017 at 01:57Upgrading from 4.17 to 4.18 has silently removed the selection of external triggers from ADC2 on an F303RE. Not only are the selections missing from the generated code, the option in the UI is missing as well.Manually patching the generated 'main.c' file fixes the problem but it means that each time I regenerate the code I have to remember to hack it.I would also question the operation of the EOCSelection field as the UI allows 'ADC_EOC_SINGLE_SEQ_CONV' to be chosen but the HAL code itself says '/*!< reserved for future use */'#cubemx #adc

Posted on February 08, 2017 at 13:09Hi in CUBEMX for a L476XX I would like to set up a PWM channel. In the pinout tab of cube under TIM1 I can choose between 'PWM generation ch1' and  'PWM generation ch1N'. So is it like it just switches the pin for channel 1?What does ch1N stand for?In which document would I find the description?THX#cubemx-4.19 #timer

Posted on June 03, 2015 at 11:37Hi,I've recently try to use code generated by CubeMX to prepare simple USB<->UART converter. Everything goes almost ok but inside function CDC_Control_FS(...) [usbd_cdc_if.c] in case ''CDC_SET_LINE_CODING'' inside buffer I should have received setting for uart (set on PC by user) but the only one setting that is inside function buffer is baud rate, nothing more :( Could somebody tell my why, or what shall I do to deal with that?P.S Is there any maual for Cube library (I've found only sheet with about 58 pages)? #stm32f4 #usb #uart #cubemx #cdc

Posted on February 03, 2017 at 09:15Hello,I am guessing that code generation with LL drivers is not yet supported for product families such as F1 and F0, although it is a bit confusing that in New Library manager F0 drivers claim LL support from version 1.6.0 onwards. Does that mean that HAL based code is generated, but LL drivers are also included in the project?Can we expect LL code generation support in STM32CubeMX for F0 and F1?How soon can that be expected?Thank you and regards, Matic#stm32f0 #cubemx #ll

Posted on December 12, 2016 at 09:49Hi there,I have a set of 3 pcb's that i am testing I have written a programm that used to work on a previous versionof the pcb, and there have been minor changes between the 2 Version.The problem is that when i run the programm into debug mode ( ulink pro), the program runs fine on all three of them.8However, when i start the pcb in normal mode (i.a mcu is started without debugger, just when powering up the 3,3V on the input), only 1 of the 3 pcbs works, the other 2 not running (a led starts to blink when the program runs). Only a manual reset on the reset pin helps to start the program.The reset pin is linked to an external pull up resistor of 15k and a capacitor of 100nf ( as advisedin the datasheet ) Rising time of the 3,3V is 2-3us , rising time on the Reset pin is in the few milliseconds domain.We use all the recommanded capcitors on the VDD and VDDA pins , tied BOO