STM32CubeMX (MCUs)

Pretty much the code is generated by Cube.I am reading 11 adc's some on adc1 and some on adc2. If I put the pins to 0 gnd i have consistent reading 0. All pins to 3.3v I have But reading in a looppa7,pa7,pa7,pa7,pa7,pa7pa7 4095pa7 4095pa7 4031pa7 4031pa7 4032the value varied from 4032 to 4095Now in a 3.3v/2 divisor varies from 1965 to 1929pa7 1929pa7 1929pa7 1930pa7 1950pa7 1965pa7 1964pa7 1965then all pins to 0 pa7 0 for gndpa1 0pa0 0pa5 0pa6 0pc0 0pc1 0pc2 0pc3 03.3v all pins reads different valuespa7 4028 for 3.3vpa1 4020pa0 4017pa5 4032pa6 4026pc0 4020pc1 4013pc2 4018pc3 4017I have a termistor and calc formula gives temp errors in orders of 10 degressMy adc init is for both adc's:static void myInit_Adc(ADC_HandleTypeDef* hadc) { hadc->Init.ClockPrescaler = ADC_CLOCK_ASYNC_DIV1; hadc->Init.Resolution = ADC_RESOLUTION_12B; hadc->Init.DataAlign = ADC_DATAALIGN_RIGHT; hadc->Init.ScanConvMode = ADC_SCAN_DISABLE; hadc->Init.EOCSelection = ADC_EOC_SINGLE_CONV; hadc-&g

In version 4, it was selected for each peripheral under Project > Settings > Advanced SettingsIn version 5, I can't figure out where it is?!? The docs haven't been updated, they still show the version 4 screenshots.

There used to be a checkbox "use fifo" where i could chose duble buffer dma, but now there is no such function. (see screenshot) Why? Can anybody say me please, you havent this too?PS: New CubeMX 5.0.0 design is so terrible ((

Hello,I'm generating code for a project targeting the stm32767zi Nucleo. When I run the generated code, I encounter an assert_failed due to the PLLR not being configure to the correct value. If I look at the generated SystemClock_Config() function in main.c, there is no code generated to configure the PLLR, but there is code to configure other aspects of the PLL such as PLLM,Q, etc. So I believe that this is the cause of the failure.I'm using the default clock configuration, and using the latest version of CubeMX and the HAL.Is there a reason that the PLLR is not being configured? Is this a bug, or is there a setting somewhere I need to change?Thanks

I beleive that I have discovered a bug where CubeMX v4.27.0 generates incorrect code for GPIO initialisation.Here is the story:Pins have been preconfigured via Pin Configuration menu in the CubeMX app the following way:PC14 as Input with Pull-UpPC15 as Output (push-pull) with Low Initial StateHere is the code generated for MX_GPIO_Init() function with my comments added: /**/ LL_GPIO_ResetOutputPin(GPIOC, DO_5V_ENABLE_Pin); // DO_5V_ENABLE_Pin is set to be LOW here   /* ... skipped ... */   /**/ GPIO_InitStruct.Pin = DI_5V_FUSE_STAT_Pin; GPIO_InitStruct.Mode = LL_GPIO_MODE_INPUT; GPIO_InitStruct.Pull = LL_GPIO_PULL_UP; LL_GPIO_Init(DI_5V_FUSE_STAT_GPIO_Port, &GPIO_InitStruct);   /**/ GPIO_InitStruct.Pin = DO_5V_ENABLE_Pin; GPIO_InitStruct.Mode = LL_GPIO_MODE_OUTPUT; GPIO_InitStruct.Speed = LL_GPIO_SPEED_FREQ_LOW; GPIO_InitStruct.OutputType = LL_GPIO_OUTPUT_PUSHPULL; LL_GPIO_Init(DO_5V_ENABLE_GPIO_Port, &GPIO_InitStruct); // DO_5V_ENABLE_Pin goes HIGH

​Where to download the new version of STM32CubeMX release 4.27.0？Currently the official seems to only downloadSTM32CubeMX release 4.26.1​

Posted on January 29, 2018 at 20:33Hello!I am using KEIL MDK 5 and it is compiling very very slow.CubeMX  v4.24STM32CubeF4 v4.19.Any ideas  ??ThanksSasha#cubemx-4.24 #keil-mdk5

I need to get data from 2/4 regular channels of ADC1 at every TIM4_CC4 event and save it with DMA. But always every time I receive ADC OVR error.When I start ADC with HAL_ADC_Start_DMA I receive 1 immediate conversion with transfer. Then I start TIM and with the fisrt event receive ADC_OVR, then conversion starts at every event, but DMA doesn't work.I've tried a lot of combinations of ADC and DMA settings (Cont./discont. modes, circular/normal, EOC at every conversion/at the whole conversion). I've also tried to configure DMA manually, then to start ADC with HAL_ADC_Start and HAL_ADC_Start_IT commands. But none worked.How to configure it right due my goal?

Each time I add __FPU_PRESENT and AMR_MATH_CM4 to symbols to get project compile properly, yet getting 30 warning about __FPU_PRESENT redefined.Project is made straight-forward: configure pins, select TrueStuido, pressing "generate code". Opening project in TrueStudio, build. Getting errors, adding __FPU_PRESENT and AMR_MATH_CM4 to symbols, building again with warnings.

Posted on December 19, 2016 at 22:17I'm using CubeMX 4.18 to generate my code for an STM32F407VG for the System Workbench using the arm-gcc. Works great, except for in socket.h it complains about redefinion of struct timeval.When I manually set&sharpdefine LWIP_TIMEVAL_PRIVATE 0in socket.hand do a&sharpinclude <sys/time.h>in cc.h as suggested, it builds.But of course every time I make changes to my CubeMX project, it gets overwritten and I have manually edit again.Please fix this in the next release!Otherwise great tool!Markus#code-generation #lwip #cubemx-bug #cube

Hello I'm testing implementation of sdcard / FatFS on F446.First I started with the example. It works.Now, I'm trying to implement a basic test app created from scratch with CubeMx.I configured a simple project with fatFS, SDIO, no DMA, no OS.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();   /* USER CODE BEGIN Init */   /* USER CODE END Init */   /* Configure the system clock */ SystemClock_Config();   /* USER CODE BEGIN SysInit */   /* USER CODE END SysInit */   /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_DMA_Init(); MX_SDIO_SD_Init(); MX_FATFS_Init(); /* USER CODE BEGIN 2 */   testSD();   /* USER CODE END 2 */   /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) {   /* USER C

..

Hi all,I am using stm32l486 MCU and trying to use stmcube internal flash example code. As i see we have API "HAL_FLASH_Program" to program word or double word. Is it possible to write byte data by doing type casting and increasing the address by 1?Could anyone help on this.Thanks,John

After the latest CubeMX update, where are the packages now stored? I have been using revision control on 'C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeMX\packages' and am curious, I no longer see updates here

Why does Keil run crash when debugging with KEIL project generated by STM32CubeMX 5.0?

How can I access the example peripheral projects for the STM32F091RC? I am using TrueSTUDIO & System Workbench and have looked exhaustively, are these available?

Hello,I am trying to interface USB Mass Storage with external Flash. I have implemented the complete structure that is necessary as below,typedef struct _USBD_STORAGE { int8_t (* Init) (uint8_t lun); int8_t (* GetCapacity) (uint8_t lun, uint32_t *block_num, uint16_t *block_size); int8_t (* IsReady) (uint8_t lun); int8_t (* IsWriteProtected) (uint8_t lun); int8_t (* Read) (uint8_t lun, uint8_t *buf, uint32_t blk_addr, uint16_t blk_len); int8_t (* Write)(uint8_t lun, uint8_t *buf, uint32_t blk_addr, uint16_t blk_len); int8_t (* GetMaxLun)(void); int8_t *pInquiry; }USBD_StorageTypeDef;     USBD_StorageTypeDef USBD_MSC_Template_fops = { FLASH_Init, FLASH_GetCapacity, FLASH_IsReady, FLASH_IsWriteProtected, FLASH_Read, FLASH_Write, FLASH_GetMaxLun, (int8_t *)UMSC_FLASH_Inquirydata,   };In addition, I have defined all the functions that performs flash operations (i.e read/write operations, initialization etc). I have also passed the structure to USB register,

Posted on October 10, 2017 at 21:22 I would like to see CubeMX support for SD cards + FatFS using an SPI driver option. Both for MCUs that don't don't support SDIO and also on MCUs that have SDIO but where SPI fits the project better. FatFS is there as 'user defined' forall. SDIO option is there where supported. Why not add SPI option under FatFS? Seems like would be pretty minor to the follow the templates used in SDIOfor SPI. Certainly would make it easier to get an stm32 project doing FatFS on SD! #cubemx #sdio #spi #sd-card Note: this post was migrated and contained many threaded conversations, some content may be missing.

..

Hello,i try to get a most simple I2C driver to work. So, i setup I2C1 with CubeMX and select code generation.In the resulting main.c, all i have to do is to add something like that: /* USER CODE BEGIN WHILE */ while (1) { uint8_t value = 0;   for (uint32_t i = 0; i < 100000; i++) asm("NOP");   HAL_I2C_Master_Transmit(&hi2c1, (uint16_t)(0x27 << 1), (uint8_t*)&value, 1, 100);This should be enough to see anything an my data logger, shouldn't it?But all i see is SCL and SDA staying hijgh - no glitch no change.Before you ask: The hardware is working as expected. I have this same device running with a Standard Peripheral Library driver (where i did hardware initialization by myself) wijthout problems.So, what do i miss in this CubeMX project?Best regards,SF49ers

Title says almost all:I have had a project which needs support package migration. I hit cancel and the project disappeared from the home screen and the File -> recent projects menu as well. I am using 5.0.0 version on Linux

Hello all,I'm encountering an issue with a custom board I've made with a STM32L011D3 MCU on it.I am trying to run a very simple blink program to check the global functionalities. It looks like the code generated with STM32CubeMX does not work for the systick config, as my code uses HAL_Delay and never returns from the function. I am using STM32CubeMX with makefile, then a Bla*ck Mag*ic Probe with gdbserver on it to load my .elf software on the STM32L0. I can debug my software and I can see I get stuck in HAL_Delay(500) function call.I think there is some configuration for the clock that I must have missed in STM32CubeMX ? Here is my main.c code : /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** ** This notice applies to any and all portions of this file * that are not between comment pairs USER CODE BEGIN and * USER CODE E

Hi,I was working with CubeMX v4.27.I've installed CubeMX v5.0.0, and loaded an existing project.When trying to generate code I encounter problems during download some item CubeMX requires.Please find attached screen shots.Thanks,Aviv

I believe I have found a serious code creation bug in STCubeMX concerning PLL initialization on (at least) STM32F767ZI MCUs. Additionally, I take issue with some pre-processor macros used for register manipulation that allowed the code creation bug to become a very serious issue. Please read the detailed description.We created code using the CubeMX tool and have soon discovered the following symptoms:With compiler optimizations enabled (-O3), the MCU's timers ran with double frequency after a power-cycle. If you reset (while keeping the power enabled) the timer frequency would be correct.Analysis showed, during init of the RCC subsystem some register values are set incorrectly. Namely the RCC_DCKFGR1 register, which controls some clock muxes and prescalers for peripherals. Please have a look at this piece of Cube generated init code taken from the SystemClock_Config() function in "main.c"Exhibit A: PeriphClkInitStruct.PeriphClockSelection = RCC_PERIPHCLK_USART1|RCC_PERIPHCLK_SAI1|RCC_P

I generate a project for processor: STM32L4A6​VGT6 and open it in Atollic TrueStudio and start debugging with ST-Link (V2). The processor excutes, stops at main, as it should. I can step through the initializations correctly. After the last function (in a very simple project) the SystemClock_Config() function starts execution and at the end of this funcion, instead of going to the next C instruction of "while(1) " the processor goes somewhere from where it does not returnAm I  missing some a step in using the CubeMx generated project in TrueStudio?