Solved

Posted on June 01, 2017 at 15:15 I have generated a GPDSC project with CubeMX 4.0 for an STM32F103C8Tx which utilized the SPI1 peripherial. In the output XML the following section is present: <component Cclass='Device' Cgroup='STM32Cube HAL' Csub='SPI' Cversion='0.2.0'> <description></description> <files> <file category='header' condition='' name='Drivers\STM32F1xx_HAL_Driver\Inc\stm32f1xx_hal_spi.h'/> <file category='source' condition='' name='Drivers\STM32F1xx_HAL_Driver\Src\stm32f1xx_hal_spi.c'/> <file category='header' condition='' name='Drivers\STM32F1xx_HAL_Driver\Inc\stm32f1xx_hal_spi_ex.h'/> <file category='source' condition='' name='Drivers\STM32F1xx_HAL_Driver\Src\stm32f1xx_hal_spi_ex.c'/> </files> </component>�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�? However the stm32f1xx_hal_spi_ex.h is not present in the Drivers\STM32F1xx_HAL_Driver\Inc folder: mm@mm-imac:/tmp/pocs$ ll Drivers/STM32F1xx_HAL_Driver/I

Posted on March 20, 2018 at 06:46Does SPC5studio support print debug message on CONSOLE window by coding, not print message on serial port?

Posted on June 16, 2017 at 14:59The original post was too long to process during our migration. Please click on the attachment to read the original post.

Posted on January 24, 2018 at 01:26STM32CubeMX upgrade to 4.24.0 version, STM32F1 series RTC module will be garbled. Unable to compile.the details as attached file.

Posted on February 07, 2018 at 17:11Hi, I have a problem with STMCubeMx v4.24.0.My problem is : I cannot open a new project created with STM32CubeMx v4.24.0. This project was created from scratched. After I finish editing the file, I save it and close the software. When I re-open the project file, nothing happens. My mouse cursor is transformed into a blue circle (busy). It's impossible to close the tool  without forcing (ctrl-alt-supr or task manager).In STM32CubeMX.log I have these errors : 2018-02-07 16:57:00,996 [INFO] ImportTextPane:155 - (OptionalMessage_ERROR) IP (RCC) : Parameter (ADCFreq_Value) has invalid value (96000000)2018-02-07 16:57:00,997 [INFO] ImportTextPane:155 - (OptionalMessage_ERROR) IP (RCC) : Invalid parameter (FamilyName)When I open the .ioc file, I have these value for these attributes :RCC.ADCFreq_Value=96000000...RCC.FamilyName=MI am sure to configure correctly my clocks before I close the file. My ADC clock is 80MHz and not 96MHz. If I

Posted on January 30, 2018 at 16:59Hi,when I generate a example for the nucleo32 L432kc everything is fine, until I check the option freeRTOSAfter this the includes are not correct anymore:>>>>>Src\freertos.o: In function `StartDefaultTask':E:\Workspaces\Atollic9\432kcTest\Debug/..\Src/freertos.c:118: undefined reference to `HAL_GPIO_TogglePin'E:\Workspaces\Atollic9\432kcTest\Debug/..\Src/freertos.c:119: undefined reference to `osDelay'Src\freertos.o: In function `MX_FREERTOS_Init':E:\Workspaces\Atollic9\432kcTest\Debug/..\Src/freertos.c:99: undefined reference to `osThreadCreate'Src\gpio.o: In function `MX_GPIO_Init':E:\Workspaces\Atollic9\432kcTest\Debug/..\Src/gpio.c:80: undefined reference to `HAL_GPIO_WritePin'E:\Workspaces\Atollic9\432kcTest\Debug/..\Src/gpio.c:87: undefined reference to `HAL_GPIO_Init'Src\main.o: In function `SystemClock_Config':E:\Workspaces\Atollic9\432kcTest\Debug/..\Src/main.c:156: undefined reference to `HAL_RCC_OscConfig'E:\Workspaces\Atoll

Posted on February 02, 2018 at 10:11Hello everyone, i guess this is not the right place to ask, but official Atollic TrueSTUDIO forum gave me no answers. Maybe someone here had same problem as me. Yesterday i moved from Keil to TrueSTUDIO IDE since it is free for STM32. After base code generation using STM32CubeMX i can't get over the error after building Debug. It does not find reference to any HAL and FreeRTOS functions. If i try to build Release the errors does not appear. Also then i try to RUN my project i get 'The selection cannot be launched, and there are no recent launches.'. What could be wrong? P.S I am junior developer and never used debugging tools. Does Debug build and run is just as same as flash + use of debug tools?

Posted on January 30, 2018 at 12:52Hi.When configuring the HAL_NAND driver you need to set the PageSize and SpareAreaSizes values; /* hnand1.Config */  hnand1.Config.PageSize = 2048;  hnand1.Config.SpareAreaSize = 64;   hnand1.Config.BlockSize = 64;  hnand1.Config.BlockNbr = 1024;  hnand1.Config.PlaneNbr = 1;  hnand1.Config.PlaneSize = 1024;  hnand1.Config.ExtraCommandEnable = ENABLE; HAL_NAND_Init(&hnand1, &ComSpaceTiming, &AttSpaceTiming);Does anyone know if these values are for the whole device or just the page?The typedefs in the HAL NAND driver suggest these are large values as they are in kB, so suggesting these are for the whole device. For my device the SpareAreaSize for a page is 64 bytes, so you can't set 0.0625 !!In stm32f7xx_hal_nand.h:uint32_t ;       /*!< NAND memory page (without spare area) size measured in K. bytes */uint32_t ;  /*!< NAND memory spare area size measured i

Posted on March 20, 2018 at 14:35Hi everybody,i'm tryng to wake up MCU STM32L051T6 from stop mode using a GPIO pin. The pin is PB4 on Rising edge.This is the code:void stopMode(void){ DBGMCU -> CR |= DBGMCU_CR_DBG_STOP;RCC -> APB1ENR |= RCC_APB1ENR_PWREN; RCC -> IOPENR |= RCC_IOPENR_GPIOAEN;EXTI -> IMR |= EXTI_IMR_IM4; EXTI -> RTSR |= EXTI_RTSR_TR4;NVIC_SetPriority(EXTI4_15_IRQn, 0); NVIC_EnableIRQ(EXTI4_15_IRQn);PWR->CR |= PWR_CR_CWUF; // clear the WUF flag after 2 clock cycles PWR->CR &= ~( PWR_CR_PDDS ); // Enter stop mode when the CPU enters deepsleep RCC->CFGR |= RCC_CFGR_STOPWUCK; // HSI16 oscillator is wake-up from stop clock SCB->SCR |= SCB_SCR_SLEEPDEEP_Msk; // low-power mode = stop mode __WFI(); // enter low-power mode}The isr never goes!Can someboby help me?ThanksDamiano#exit-stop #ll-gpio #exti #wake-up

Posted on March 08, 2018 at 00:58 Hi everyone, Since a couples days ago I'm trying to set a project in which I can use a micro SD card using the nucleo board L476RG. I'm using CubeMX 4.24 and the HAL library 1.11 for L4 for making all the settings and I also checked the example that is provided for the L476 eval board. I think that all the settings are right, I compare it with the example and it is almost equal. Some captures from cubeMX: After doing all the configurations I generated the code, So I copied some parts of the example and added to my code. I started with this: if(retSD == 0) { if(BSP_SD_Init() != HAL_OK) { Error_Handler(); } res = f_mkfs(SDPath, FM_ANY, 0, workBuffer, sizeof(workBuffer)); if (res != FR_OK) { Error_Handler(); } } But the function f_mkfs always returned FR_DISK_ERROR. So I check the forum and I find that changing the name of the SD callback functions could help to avoid the error. So I changed from sd_diskio.c: //void BSP_SD_ReadCpltCa

Posted on March 20, 2018 at 07:43FSS[4:0] contains the unread samples stored in the FIFO. So when the EMPTY is 1, the FSS[4:0] is 0. But when the OVRN_FIFO is 1, the FSS[4:0] should be 32 but it can't. So when FSS[4:0] is 31 we should check the OVRN_FIFO flag to judge the real unread sample number. Is that correct?

Posted on March 19, 2018 at 20:11Hi,Today's F1 v1.6.1 HAL driver pack fixed all issues I had with GPIO so decided to move forward with TIM3 and LL.The goal: use TIM3/PWM to blink the BLUE LED (PC8) - STM32VLDiscovery.CubeMX generated code:/* TIM3 init function */static void MX_TIM3_Init(void){  LL_TIM_InitTypeDef TIM_InitStruct;  LL_TIM_OC_InitTypeDef TIM_OC_InitStruct;  LL_GPIO_InitTypeDef GPIO_InitStruct;  /* Peripheral clock enable */  LL_APB1_GRP1_EnableClock(LL_APB1_GRP1_PERIPH_TIM3);  TIM_InitStruct.Prescaler = 24000;  TIM_InitStruct.CounterMode = LL_TIM_COUNTERMODE_UP;  TIM_InitStruct.Autoreload = 1000;  TIM_InitStruct.ClockDivision = LL_TIM_CLOCKDIVISION_DIV1;  LL_TIM_Init(TIM3, &TIM_InitStruct);  LL_TIM_DisableARRPreload(TIM3);  LL_TIM_SetClockSource(TIM3, LL_TIM_CLOCKSOURCE_INTERNAL);  LL_TIM_OC_EnablePreload(TIM3, LL_TIM_CHANNEL_CH3);  TIM_OC_InitStruct.OCMode = LL_TIM_OCMODE_PWM1;  TIM_OC_InitSt

Posted on February 08, 2018 at 20:22Hi everybody!The current datasheet (https://community.st.com/external-link.jspa?url=http%3A%2F%2Fwww.st.com%2Fcontent%2Fccc%2Fresource%2Ftechnical%2Fdocument%2Fdatasheet%2Fgroup3%2Fc4%2F02%2Fe5%2F87%2F1c%2Fd2%2F4f%2Ff8%2FDM00328568%2Ffiles%2FDM00328568.pdf%2Fjcr%3Acontent%2Ftranslations%2Fen.DM00328568.pdf) does not give any indication to which direction that the LEDs should be going other than the name says LED Drive: module running, LED Drive: Wi-Fi Link Up, and LED Drive: power Up. This may indicate that the pin should source the LED and the reference schematic (http://www.st.com/content/ccc/resource/technical/document/data_brief/group1/f4/06/e8/8b/99/10/4d/b4/DM00375570/files/DM00375570.pdf/jcr:content/translations/en.DM00375570.pdf) also shows that the pin is sourcing the LED but they do not blink when that is the case. The LEDs only seem active when the WiFi module is sinking from the LED. Is this the proper way?Thank for the help!

Posted on March 17, 2018 at 20:45 Hi, A piece of code from STM32CubeMX v4.0 and latest F1 drivers generated for STM32VLDiscovery (the button is pulled-down by external resistor): static void MX_GPIO_Init(void) { LL_GPIO_InitTypeDef GPIO_InitStruct; /* GPIO Ports Clock Enable */ LL_APB2_GRP1_EnableClock(LL_APB2_GRP1_PERIPH_GPIOC); LL_APB2_GRP1_EnableClock(LL_APB2_GRP1_PERIPH_GPIOD); LL_APB2_GRP1_EnableClock(LL_APB2_GRP1_PERIPH_GPIOA); GPIO_InitStruct.Pin = LL_GPIO_PIN_0; GPIO_InitStruct.Mode = LL_GPIO_MODE_FLOATING; LL_GPIO_Init(GPIOA, &GPIO_InitStruct); } and the results from the Keil debugger: So commented the line below to prove that there is only one line of code used for GPIOA initialization: // LL_GPIO_Init(GPIOA, &GPIO_InitStruct); and got as expected (the default settings for GPIOA) It seems that the LL_GPIO_Init gives messy config on more than one pin. Am I wrong? Have no luck with F1 line and LL drivers - this issue seems to be continuation of m

Posted on January 30, 2018 at 11:32Hello,I have encountered a problem with my STM32L452VE - when I set up USB with CDC, it sometimes connects, sometimes not. When it doesn't connect, Windows clasically show yellow exclamation mark.Increasing heap size and chaning packets size didn't solve this issue.I have tried sniffing USB communication and problem seems to be the same every time - SET_CONFIGURATION is sent from host (PC) but no response is received. Upon closer inspection, I tried to modify HAL libraries by adding an extra delay, which miraculously solved the issue and now it succusefully connects every time.As this this fix appears to be highly temporary, does anyone know the root of the issue?

Posted on March 18, 2018 at 12:44Hi,   I am just Getting started with STM32F767ZI using a Nucleo F767ZI dev board. Prior to that I have only used in commercial project PIC24H family of Microchip and embedded C language. Can anybody help with how to get started with it.Following are the question which are coming into my mind and struggling to find much online material . How to add MCU specific header files. (Any libraries need to be added such SPL?)How to use it without using HAL libraries.Where to find example codes tutorial specific to above model.Could not figure out how to just create not generic but MCU specific code just to blink an LED or control its inputs outputs.Any other evaluation tools recommended for the above MCU to get started ?Please Help.#getting-started-with-stm32

Posted on March 16, 2018 at 19:50 I'm writing a crude memory diagnostic for SDRAM (just to see if I can). The code accesses SDRAM using a pointer. __IO uint32_t * SDRAM_ptr; SDRAM_ptr = (__IO uint32_t *)0xC0000000; Using this pointer in a loop, I can write and read the first 2 megabytes reliably, but more than 2 megabytes causes the program to hang (sits and does nothing after the SDRAM read starts). I assumed that the program would fail beyond 0xC0800000, but its failing when beyond 0xC0200000. The LCD display is not enabled. CPU clock is set to 200 MHz. Initialization was done with HAL and BSP functions. Another curious behavior is that if I set the diagnostic to test 2 megabytes (0x00200000), I can set SDRAM_ptr to any of 0xC0000000, 0xC0000004 and 0xC0000008 as a starting point and the diagnostic works meaning that at least 8 bytes beyond 0xC0200000 seem to be accessible. If I set to 0xC0000010, it fails. The program writes data values starting at 0x00000000 and incrementin

Posted on March 02, 2018 at 14:25Hi Folks,I´ve got a task for which i have to implement a NFC Reader(CR95HF) into a casing, so I decided to order the above mentioned board to help me get into it.Now I´m searching for a suitable tag and antenna and I got a little confused about the difference between the so called ST25 Dynamic NFC Tags and the ST25Tx series NFC Tags. Is there any big difference at all or can I just take one of them?The tag should be passive and  the operating range distance should be 0.1m.Thank you

Posted on April 08, 2017 at 08:29Hello, I recently installed cubemx 4.20 latest version 4.20.1I can generate the project only 1 time, later if i try to update the project by adding new peripherals, i can not able to generate the code, the whole application is stuck in 'Generating user source code '. the only way i can close this application is killing it by 'Task manager'. it happens every time. Please help 

Posted on March 03, 2018 at 08:35I want to RSS this content, but it always return me this...Cariati.Francesco‌Some of the RSS function is not working?please fix.#rss

Posted on March 15, 2018 at 17:31Hi everyone,My name is Dario and I'm getting the error above when I try to compile my project. What I'm doing is as follow: I'm trying to take advantage of the P2P demo released for the F4 nucleo and based on the IDS01A4 radio shield, but when I try to activate the ADC peripheral on the Nucleo board there is an error in the linking phase. I realize that the stm32f4xx_hal_adc.h is not in the driver files even if I try to add it through a path different from the ones used by the demo project (preprocessor tab). I also tried to eliminate stm32f4xx_hal_adc.c and add it directely to the Application folder, the problem still persist. Could anyone help me for that kind of problem? Thank you so much#ids01a4 #hal_adc #stm32f4

Posted on March 15, 2018 at 19:43Hi all,I'm facing an odd behavior working with an L4/Nucleo64/CubeMX/HAL. RTC peripheral. Same result w/ and w/o LSE oscillator.Basically, a code like this:while (1) {   HAL_RTC_GetTime(&hrtc, &sTime, FORMAT_BCD);    HAL_RTC_GetDate(&hrtc, &sDate, FORMAT_BCD);    printf('DateTime ......', ......, sTime.Hours, sTime.Minutes, sTime.Seconds);   HAL_Delay(1000);}Results in:DateTime - 1/1/2000-1-0:0:0DateTime - 1/1/2000-1-0:0:1DateTime - 1/1/2000-1-0:0:2DateTime - 1/1/2000-1-0:0:3DateTime - 1/1/2000-1-0:0:4DateTime - 1/1/2000-1-0:0:5DateTime - 1/1/2000-1-0:0:6DateTime - 1/1/2000-1-0:0:7DateTime - 1/1/2000-1-0:0:8DateTime - 1/1/2000-1-0:0:9 DateTime - 1/1/2000-1-0:0:16DateTime - 1/1/2000-1-0:0:17DateTime - 1/1/2000-1-0:0:18DateTime - 1/1/2000-1-0:0:19DateTime - 1/1/2000-1-0:0:20DateTime - 1/1/2000-1-0:0:21DateTime - 1/1/2000-1-0:0:22DateTime - 1/1/2000-1-0:0:23DateTime - 1/1/200

Posted on March 15, 2018 at 14:05Hi everybody,i'm using STM32L051T6 MCU and i need to wake up from stop mode using I2Ci've read the last datasheet version and it is possible but there is an errata sheet that reports thati it is impossible.The datasheet is from September 2017 and the errata from February 2016.Do you know if now it is ok ?Thanks Damiano#stop-mode-wake-source #i2c #wake

Posted on March 15, 2018 at 18:34Dear everybody,in my code, i am not able to set my Port PD2 as output.As can be seen, I stopped debug at line 294.In lines 287 and 289 GPIOD->MODER and memory adress 0x4800 0C00 should be set to some value unequal zero,but it keeps on zero.Tried with different hardware, and tried with IAR and Keil.I am stuck !Any hints ?Thx a lot, Jens

Posted on March 13, 2018 at 10:20I have been using ST Visual develop for months, with the same MCU: STM8L, compiling and debugging with no problem.Then yesterday I started getting a message to say that it can't start GDB :Starting debug session... -> Failed to start GDB.(see also attached picture for message boxes).I have checked that the file path is correct Tools->Options : Toolset Tool set : STM8 CosmicRoot path : C:\Program Files (x86)\COSMIC\FSE_Compilers\CXSTM8I even tried uninstalling and re-installing, same error.Occasionally I have seen a popup saying that there is a lack of memory - but there is plenty available.I am running :Windows 10ST Visual develop (two version numbers given in the about box : 4.3.12, 3.6.5.2 Build 4 Aug 2017#st-visual-develop #gdb