Solved

I've been debugging a custom designed board that has an FT4232 USB IC on it with a JTAG interface. STM32Cube IDE up to 1.3.1 could successfully debug this through openocd. Version 1.4.0 wants to force firmware verification so I can no longer program and debug my board. How can I disable the ST-Link firmware check?

When generating code on an existing Makefile project any existing C_DEFS are corruptedC_DEFS = \ -DUSE_HAL_DRIVER \ -DSTM32F301x8 becomes-DC_DEFS = USE_HAL_DRIVER \ -DSTM32F301x8 so the definition of C_DEFS is lost and random errors result from the dangling defines.This is on version 5.6.1 but is has been an issue for a long time (at least a year).I've also seen other strange behaviour on Makefile - like "# compile gcc flags" gets repeated every time the code is generated - one makefile now has the string 15 times on one line!!Another is -isystem for system include file path, CubemX insists on prefixing it with -I so it fails with -Iisystem ....I'll save all the other bugs I've found for another day! - the above are the most annoying!

..

Hello,I'm working with the NUCLEO-F722ZE EVB on STM32CubeIDE.My design has a DAC output connected via a jumper wire to an ADC input (see the red wire in the attached picture.The DAC is successfully generating a sawtooth wave - verified via an oscilloscope.However the ADC isn't working properly. I'm using a break point to stop the code and I see "semi constant" values.By "semi constant" I mean that the reading is changes between compilations but is constant during runtime and seems to be unaffected by the DAC that's driving it.What am I doing wrong ?This is my code:#include "main.h"   ADC_HandleTypeDef hadc3; DAC_HandleTypeDef hdac; UART_HandleTypeDef huart3; uint32_t voltage_in = 0 ; uint32_t voltage_out = 0 ;   void SystemClock_Config(void); static void MX_GPIO_Init(void); static void MX_USART3_UART_Init(void); static void MX_DAC_Init(void); static void MX_ADC3_Init(void); int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_USART3_UART_Init(); MX_DAC_I

Hello!I created a project for NUCLEO-F429ZI with two ethernet interfaces.The first interface is the card's own ethernet connection.The second is a USB-RNDIS virtual ethernet port.The two ethernet interfaces work, but only if I enable software checksum generation on both interfaces.Is there a way for the physical ethernet interface to use hardware checksum generation and the virtual one to use software checksum?

I'm currently using a STM32F030CC and i need a Bootloader and Main App structure. The problem is that i can't find in system_stm32f0xx.c constant VECT_TAB_OFFSET to change. Also SCB->VTOR is missing. I'm currently using SMT32CUBEIDE v1.4.1. Any ideeas ?

Hey,I'm adding a bootloader to my project that sits in the first 2 sectors of internal flash. while trying to preform the update it seems that i can't erase sector 3 all other sectors that follow this sector are erased properly.this is the code I'm using to erase the specified sectors: uint32_t SectorError = 0; FLASH_EraseInitTypeDef EraseInitStruct; HAL_StatusTypeDef flashStatus = HAL_OK;   /* Fill EraseInit structure*/ EraseInitStruct.TypeErase = FLASH_TYPEERASE_SECTORS; EraseInitStruct.VoltageRange = FLASH_VOLTAGE_RANGE_3; EraseInitStruct.NbSectors = 8; EraseInitStruct.Sector = FLASH_SECTOR_3;   /* Perform Erase Sector */ do { flashStatus = HAL_FLASHEx_Erase(&EraseInitStruct, &SectorError); } while(flashStatus != HAL_OK);I also tried disabling write protection with: FLASH_OBProgramInitTypeDef OBStruct= {0}; HAL_StatusTypeDef status = HAL_OK; HAL_FLASH_Unlock(); HAL_FLASH_OB_Unlock(); /* Bank 1 */ OBStruct.Banks = FLASH_BANK_1; OBStruct.WRPSector

..

Can someone tell me if this is accurate when using freertos! using lots of ram and i'm only getting started so I'm trying to gauge how i'm going. I plan to move the heap too CCM ram if i get stuck.Thanks​

HelloI am a beginner in the control of BLDC motors.I am trying to use the ST Motor Control program to control the motor but I have a problem.I have the EVSPIN32F0601S3 board.STM32CubeIDE cannot compile the program generated by ST Motor Control and the following errors appear:1. "hdd.elf section` .text 'will not fit in region `FLASH'"2. "FLASH 'overflowed region by 19608 bytes"Can someone help me or point me where to look for a solution?

Hi, I have STM32L4S5 (STM32 Discovery Kit - IoT mode), Part number: B-L4S51-IOT01A.https://www.st.com/en/evaluation-tools/b-l4s5i-iot01a.htmlThis is the first time I am using this device. When I plug this device into Windows 10 machine, I am not able to connect to the device. I do not see any COM port in Device manager and also Tera Term serial port option is greyed out.I did install STSW-LINK009. I have tried this is 3 windows device and getting same issue.I noticed that Red line is blinking on the board, while green light is stable. Device managerTera termInstalled ST programs portsThanks,Ajay

I’ve been using these examples for a long time, but I’ve never been able to open them and rebuild them right after importing without an error or missing path of header and source files. For simple examples, this is not so much a problem, but for more complex ones (such as an Ethernet communication) it would be good if it worked without any problems. Now specifically, it would be good if it works with: STM32Cube_FW_H7_V1.7.0 \ Projects \ NUCLEO-H743ZI \ Applications \ LwIP \ LwIP_HTTP_Server_Netconn_RTOS(STM32CubeIDE version is 1.4.0)The compiler can't even find the main files after importing. And the example project files are simply not opened by the IDE. Even if I tried to follow user guide instructions (STM32CubeH7GettingStarted.pdf included in the package).

Hi here,I have made a prototype with STM32L476RG on Nucleo-board - MCU are doing some task and go to standby mode with wakeup from RTC (1 Hz counter). The code was migrated into my own board with STM32L476RC - RTC doesn't work correctly - MCU goes to Standby, but never wakeup. I have made the simplest one project for test - only RTC and UART3 for debuging. It works very strange. Source was generated by CubeMX 1.4.0. HAL_RTC_GetTime(&hrtc, &currentTime, RTC_FORMAT_BCD) returns the same time. But if I do hard reset (f.e. flash new firmware) it gets new time (I'm not set time in the app) - RTC runs! But wakeup doesn't work. RTC works in both case from LSI.static void MX_RTC_Init(void) {   /* USER CODE BEGIN RTC_Init 0 */   /* USER CODE END RTC_Init 0 */   /* USER CODE BEGIN RTC_Init 1 */   /* USER CODE END RTC_Init 1 */ /** Initialize RTC Only */ hrtc.Instance = RTC; hrtc.Init.HourFormat = RTC_HOURFORMAT_24; hrtc.Init.AsynchPrediv = 127; hrtc.Init.Syn

Hello,MCU: STM32F429ZI I am building a bootloader for my project to upgrade the application firmware from SD card.Everything works fine but the total time for a ~2MBytes .bin file is almost 45 seconds. So, i am trying to check each step and try to reduce its time.Sector Erase TimeSectors erasing takes up to 25 seconds, is there a way to reduce it? I am using the below function:EraseStruct.NbSectors = (uint32_t)(NbOfSectors); if(HAL_FLASHEx_Erase(&EraseStruct, &SectorError) != HAL_OK) { . . }  Flash Writing TimeWriting to Flash (+ time to read from file) takes about 20 seconds. Is there a way to write more than doubleword to reduce the time?if (HAL_FLASH_Program(FLASH_TYPEPROGRAM_DOUBLEWORD, Address, FileData) == HAL_OK) { . . . } Thank you.

STM32Cube\Repository\STM32Cube_FW_G4_V1.2.0\Projects\NUCLEO-G431RB\Examples_LL\TIM\TIM_PWMOutputThis project runs fine. However, it uses TIM2. I tried to port to TIM1 so I could be interrupted every 10 periods, rather than have to count them in an isr. I did allthe obvious things. Any tricks? My project outputs nothing. I relocated to PA1 from PA5, and made the required changes. No go. What additional init is required for TIM1 that is missing from TIM2?

I've been working with STM32F407 httpd POST for the last week. I've got everything with the POST working but I have one problem that I can't resolve. I don't know if it is a C problem or an LwIP problem, but I suspect it is LwIP.I have code that I send to the POST functions that check the password that I enter on the login page. If the password matches the system password that is stored in EEPROM, I advance to the next web page of my app. If the password is incorrect, I simply return to the login page. That process works as designed as long as a good password and a bad password are the same length.The POST function that handles the login is this:err_t httpd_post_receive_data(void *connection, struct pbuf *p) { p->payload holds the password when function is called password check code. at end of check code: pbuf_free(p); }Assume the good password is test123. I enter a bad password of test4567 which is one character longer than test123. I return to the login page and enter test123

I am on windows 10 and would like to use sub-system for linux (WSL) to cross-compile OpenST. So far i made it trough all the steps...until i saw that the cubeprogrammer is using a GUI installer...witch doesnt work on WSL....Are there plans to make that cubeprogrammer available in "non gui" installer?Thanks

I am new to TouchGFX, so I am starting with something simple, displaying an image on the screen. I am using a custom STM32H753 board, where the display is hooked up through the LTDC interface. The display is working properly; when I write manually to the frame buffer, then the data gets displayed correctly. I was using the TouchGFX designer to create the screen with the image, and I set it as boot display. However, the image never appears on the screen. I checked that the task for touchgfx is created and also entered. Also the LTDC line interrupt is generated correctly. I am not sure in which part of the code, which TouchGFX is generating the actual drawing take place. So far I could not locate any code, which actually draws to the frame buffer. I found some shells for drawing functions, but they are all doing nothing. So something seems to be fundamentally wrong here, and I am missing the starting point where I can look. Can someone give me a hint why I am not getting anything drawn o

Hi , we have made the custom PCB for ST25R3911B with AVR AtMega328P Controller.The board works totally fine when runs at 3V3. But for low power design , when ever we try to power up the board on 2.8V , the controller resets.On debugging we have found the problem in RFAL Library at the function rfalCalibrate() as described below:1. Adjust the regulators so that Antenna Calibrate has better Regulator values */     st25r3911AdjustRegulators( &resValue ); --This works great2. st25r3911CalibrateAntenna( (uint8_t*) &resValue ); --This also works3. st25r3911AdjustRegulators( &resValue ); On call to this function the code gets stucked upWhat am I missing here?

AN2834 Rev 4, point 4.2.9 Temperature-effect compensation says:One method is be to fully characterize the offset and gain drift and provide a lookup table in memory to correct measurement according to temperature change. This calibration involves additional cost and takes time.The second method consists in recalibrating the ADC when the temperature change reaches given values, by using the internal temperature sensor and the ADC watchdog.A quick web search turns up the following API:HAL_ADCEx_Calibration_Start (ADC_HandleTypeDef *hadc, uint32_t SingleDiff)Perform an ADC automatic self-calibration CalibrationHowever I can't find this API in the HAL-LL drivers that came with STM32CubeF4 Firmware Package V1.25.0. Is this API available on F4 machines? If not, is there a similarly straight-forward API or method to perform automated calibration of the internal ADCs on F4 machines?

Reading Embedded Flash memory chapter of RM0316 and can't grab how the write protection is supposed to work.a) 4.3.2 Write protection says:It is activated by configuring the WRP[1:0] option bytesEach other instances where WRP is mentioned says i'ts either WRP[3:0} or, in FLASH_WRPR register description, it's 32 bits, so I guess [1:0] a typo.b) Okay so we have 32 bits for write protection, and 4.3.2 Write protection saysThe write protection is implemented with a granularity of 2 pages.According to 4.2.1 Flash memory organization:The memory organization is based on a main memory block containing 128 pages of2 Kbytes in STM32F303xB/C and STM32F358xC devices, 256 pages of 2 Kbytes in theSTM32F303xD/EHow exactly do 32 bits describe protection of 128 pages (let alone 256 pages), 2 pages per bit?Thanks,JW

Hi, I recently adquired a ST25R3911B-EMVCO Reference Design Board. In order to study the design I would like to have access to the Schematic. In Resources, Technical Documentation (https://www.st.com/content/st_com/en/products/evaluation-tools/product-evaluation-tools/st25-nfc-rfid-eval-tools/st25-nfc-rfid-eval-boards/st25r3911b-emvco.html#resource) I can not see it.It it possible to have access to firmware image too? We would like to recover the default status in case we flash some broken image.Thanks,Regards

I have generated the I2C code using cube-mx. My slave device is I2C based DIGI-POT. when I check with HAL_I2C_IsDeviceReady() function - it is always coming busy flag.These below are the Hardware and Firmware checks I have done:HW checks -DIGIPOT is getting 5v voltage.Checked the pull-up resistors values - fine - using 4.7kohmFw checks - 1. address - 0101 1000 - 0x582. Read state of SCL and SDA pins - Both are logic high.3. Voltage on the both the pins - 3.3v4.Some people are facing same issue - suggested in the internet to do first I2C clock enable and then GPIO init - Not working this as well. This is linkhttps://electronics.stackexchange.com/questions/272427/stm32-busy-flag-is-set-after-i2c-initialization.

Hi, starting from the documentation :"The UVLO, TH_WRN, TH_SD, OCD, NOTPERF_CMD and WRONG_CMD flags are latched: when the respective conditions make them active (low or high), they remain in that state until a GetStatus command is sent to the IC. "My understanding is that when a "warning" occurs, its bit goes to 1. This bit will not change until I read the status register. After reading the value, each bit will be set the its current physical value which can be the same or the other.Is that right?Regarding the flag pin :"By default, an internal open drain transistor pulls the FLAG pin to ground when at least one of the following conditions occurs:  Power-up or standby/reset exit  Overcurrent detection  Thermal warning  Thermal shutdown  UVLO  Switch turn-on event  Wrong command  Non performable command."The documentation does not state on how flag goes to 1. When all flags have ended? after a read? (in this case, does flag goes to 0 if at least on flag is still 1?)ThanksJu

Please see the attached picture. Our company is using L6470H chip for our design. According to the typical application in the datasheet, we want get 3V on the ADCIN pin. Our Vs is 24V and the voltage divider resistors that we chose are Ra= 13K and Rb= 91K. Since we didn't find the leakage current of L6470H's ADCIN pin through datasheet, we don't know whether these resistors' value that we chose are too large. Could you please tell me the leakage current of L6470H's ADCIN pin and help us to see whether we chose the appropriate values for these resistors?Thank you so much!