Solved

Hi I was trying to store the status of certain pins on flash memory so that I can read from flash and resume after power cycle, I have successfully written data in flash memory, I chose the last page starting address to store my data. void write_array_to_flash(uint8_t* data, uint32_t size) { check_write_protection(STATUS_ARRAY_ADDRESS); HAL_FLASH_Unlock(); // Erase the sector before writing (if necessary) FLASH_EraseInitTypeDef eraseInitStruct; uint32_t pageError = 0; eraseInitStruct.TypeErase = FLASH_TYPEERASE_PAGES; eraseInitStruct.Page = (STATUS_ARRAY_ADDRESS - FLASH_BASE) / FLASH_PAGE_SIZE; eraseInitStruct.NbPages = 1; if (HAL_FLASHEx_Erase(&eraseInitStruct, &pageError) != HAL_OK) { // Handle error HAL_FLASH_Lock(); return; } // Write the array to flash uint64_t data_quadword[2] = {0xFFFFFFFFFFFFFFFF, 0xFFFFFFFFFFFFFFFF}; memcpy(data_quadword, data, size); // Ensure the address is aligned for a quad word write if ((STATUS_ARRAY_ADDRESS % 16) !=

  Hi ST Community, I am currently working with the STM32H7S7DK development board and am configuring the LAN LWIP stack using RMII for Ethernet communication. However, when I run the code, the system encounters a HardFault. I am using STM32CubeMX for code configuration and STM32CubeIDE as the debugging environment. I would appreciate any assistance or guidance regarding this issue. If anyone has a basic project setup for configuring LAN LWIP with RMII on the STM32H7S7DK, it would be extremely helpful if you could share it with me. This would allow me to better understand what might be causing the HardFault. Thank you in advance for your help! Best regards, Vijay Kushwahvijaykushwah1112@gmail.com Edited by ST moderator: moved to the right destination

Hello, I have a question for NFC R/W mode (read/write EEPROM with ST25DV16K)tag : ST25DV16K - Nfc tag 4 clickreader : STM32 + X-Nucleo_Nfc08a11. When writing data to the ST25DV16K board via RF, how long does it take to read the data via I2C?2. It takes 5ms to write 1Block data with RF as shown in DataSheet. Is the writing time 5ms? Or does it mean that I should read it after 5ms of writing? Thank you!!!  

HII am using the STM32G474 MCU and ran into a problem with my code stopping execution.In my application, I have a level 0 priority interrupt that takes 1.34us to execute that occurs once every 6.66us.  In the final code, I will need 3 of these running, 1 every 2.2us (still leaving about 37% of the MCU bandwidth for other tasks).When I have 2 of these interrupts every 6.66us, all seems to work fine, but when I add a third, my code stops executing.  After a lot of debugging, I have found that my code is stuck at the following line of code:  ATOMIC_SET_BIT(huart->Instance->CR3, USART_CR3_TXFTIE);  in the HAL_UART_Transmit_IT() function.  Normally, when writing low level interrupt handlers for serial I/O, when I need to change the UART interrupt flags, I would disable interrupts make the change then enable the interrupts again.  Doing that, it is very clearly safe for a single core MCUs like the STM32G474.  However, when I examined the STM driv

Hey Community!I am trying to build a BMS for a 333V Battery using AEK-MCU-C4MLIT1 as the Master MCU, AEK-COM-ISOSPI1 as the translator and multiple AEK-POW-BMS63EN boards in a daisy chain.Although there are various examples provided in the SPC5Studio that one can use to get started with the BMS System. However, I am still finding it difficult to use the API functions effectively. I feel that although there are a lot of functions available in the API, their definitions are still absent in the documentation. Is there any other documentation which one can read to understand the data structures and different functions present in the API for the AEK-POW-BMS63EN?Thanks,Vipul

Using he STLINKV3MOD, I2C, UARTs,  GPIO and using ti for SWD are all working fine without without errors for over a month and quite intensive useThe CAN code follows the same settings in  the example code:InitCAN is successful.WriteMsgCAN(&canTxMsg, dataTx, size); fails  with error 0x14 BRG_TARGET_CMD_TIMEOUT  = Timeout error during Bridge communication Which conditions can cause this error ?  References:Ubuntu Linux Bridge 0 PID: 0X3753 SN:00240041343151093739.....Selected Bridge STLink serial nmber:0024004134315109......Bridge voltage: 3.274617 VBridge Firmware: v3 B5Test Clock Command...SPI input CLK: 48000 KHz, ST-Link HCLK: 192000 KHzI2C input CLK: 192000 KHz, ST-Link HCLK: 192000 KHzCAN input CLK: 48000 KHz, ST-Link HCLK: 192000 KHzGPIO input CLK: 192000 KHz, ST-Link HCLK: 192000 KHzPIO Test OKTest CAN...CAN prescaler initializedCAN initialized and message reception succeededCAN filter initialization succeededCAN loopback test loop

Hello,I would like to use the BLE_p2pServer_ota example with the STM32WBA55CG as a template for a project. Since I do not have an LSE available here, I would like to use the LSI. Which settings (defines) do I have to change?If I use the LSI with 32,000kHz, the advertising works, but I cannot establish a connection.

Dear Members,Is there any guidelines to select the values or size of three parameters in STM32cubeMX, middleware (USB device, CDC) to achieve the highest speed on CDC? I am using STM32L4P5VGT. My application streams the sensor data to the Laptop using USB CDC class, once powered on.To understand the question more in detail, I attached my current settings, are acceptable or can be optimised by reduction or increase, same time, need to avoid wastage of RAM also, so it can be used for other purposes if I am using too much.Regards 

Hi there, I am designing a product using an STM32H7RS-series MCU, and am looking for some clarification about the operation of the HSE oscillator. I see the H7RS has the option of an "analog" external oscillator in HSE bypass, in addition to the usual "digital" HSE bypass of previous products, and I am very interested in using that analog mode to use a lower voltage clipped sinewave output external oscillator, such as an NDK NT2016SE. My question is do I need anything in series between the STM32H7RS OSC_IN pin and the output pin of the analog (clipped-sine in this case) TCXO? I would assume I'm not supposed to use a series capacitor like the datasheets of these oscillators tend to show, because the STM32H7RS appears to be looking for a DC-biased signal, but before I make a board with no provision for such an inline passive and find out it doesn't work I figured I should double check here. Thanks!

Hi, to whom it may be concerned,I have a question about how to debug. I recently moved my successed project from stm32u585ci without smps with QFN to this lower mass and lower power consumption package, stm32u585ciy6qtr. This is my first time doing smps, and I think I wrongly connected the vss_smps directly to one of the vss. And I did not put extra 0.1uf caps for VDD_11, only those 2.2uf.  Because of the fabrication limits, we only have two layers of FlexPCB.I can see that the I2C2 and I2C3 work well, but ONLY I2C1 is blocked when the core is doing the computing work, and the ramp-up time is more than 1000ns in the oscilloscope. Even after we used a very small (<300ohm) value pull-up resistor and closely connected to the i2c1 pin area, the I2C1 still has a very high ramp-up time (fast mode) and will be blocked by core computing. However, the I2C1 can send out data by DMA. Then, I tried reconnecting the VLX_SMPS, VDD_SMPS, and VSS_SMPS to VSS/GND and connecting those two V

im looking in the bsp folder for the stm32f429i-disc in the stm32cube_fw_f4 folder and i see a file stm32f429i-discovery_eeprom.c why is this here as i dont believe there is a eeprom on this board 

The chip I use is STM32G031G8U6, and there seems to be no HAL_GPIO_EXTI_Callback () function in STM 32G00xx _ HAL _ GPIO. C file. What's the matter? The general function of my code is to eliminate the jitter generated when the rotary encoder rotates. Please take the trouble to answer your questions. If there is anything wrong with the following code, please correct it!  ;)   /*注意！ 单片机上电后A、B相默认输出高电平，第一次转动后A相先产生下降沿再产生上升沿，所以应当先判断A相的下降沿， 再判断A相的上升沿。如果先判断上升沿并检测这时候的B相电平就会导致第一次向新方向旋转时无效！ */ void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin) // 通用EXTI回调用于判断旋钮左转or右转 { static uint8_t B_last_level = 0; // 检查中断源是否为 KEY3_EXIT15_Pin if (GPIO_Pin == KEY3_EXIT15_Pin) { // 获取当前A相电平 uint8_t currentA = HAL_GPIO_ReadPin(KEY3_EXIT15_GPIO_Port, KEY3_EXIT15_Pin); if (currentA == GPIO_PIN_RESET) /* A相先下降，触发第一次中断，检测并记录B相的电平状态 last */ { // 记录B相旧的电平状态last B_last_level = HAL_GPIO_ReadPin(KEY5_Input_GPIO_Port, KEY5_Input_Pin); } else if (currentA == GPIO_PIN_SET) /* A相后上升，检测此

Good morning. I am working with the Discovery kit with STM32H7B3LI MCU and want to get its internal resistance. I want to use 10 buttons, each with one resistance, and then get the correct value for my MCU. I already know how to get the values between 12000 and 64000. but I do not get what Voltage they describe. I saw on the datasheet of the Chip that it has a linear relation with the voltage and receives a voltage between 1.62 and 3.6V. Still, I have no accurate Information on the internal resistance to calculate my voltage divider. I can do it with the information I have, but I feel like I am missing something. When I put a 120-ohm resistance or shortcut directly to the ADC with 3.3V, it also gives me the maximum value.

Hello, I wanted to try I2C communication on my Nucleo board since I'm planning to use it in one of my designs. I connected together pins of I2C1 and I2C2, turned on internal pull-ups on both sides for all the pins and wanted to transmit "HELLO" from one to the other.Code for transmitting:HAL_I2C_Slave_Receive_IT(&hi2c1 ,(uint8_t *)RX_Buffer, 5);status = HAL_I2C_Master_Transmit(&hi2c2, 72 << 1, *data, 5, 80000000);After receiving the data however, even though status is set to HAL_OK it is completely garbled: I looked at the signal waveforms on my osciloscope with the logic analyzer enabled, and it shows that it's exactly what was transmitted:After that I thought that it might be an issue of the internal pull-ups not being strong enough, so I added 1K resistors on both data and clock lines, but the data in the receiving buffer is exactly the same. Does anybody know what am I doing wrong? 

I recently got another bluepill board (stm32f103c8t6) to replace the old board, and I could not connect to it using stlink. Using OpenOCD: Open On-Chip Debugger 0.12.0+dev-00600-g090b431b1 (2024-09-13-19:14) [https://github.com/STMicroelectronics/OpenOCD]Licensed under GNU GPL v2For bug reports, readhttp://openocd.org/doc/doxygen/bugs.htmlInfo : Listening on port 6666 for tcl connectionsInfo : Listening on port 4444 for telnet connectionsInfo : STLINK V2J45S7 (API v2) VID:PID 0483:3748Info : Target voltage: 3.262724Info : Unable to match requested speed 8000 kHz, using 4000 kHzInfo : Unable to match requested speed 8000 kHz, using 4000 kHzInfo : clock speed 4000 kHzInfo : stlink_dap_op_connect(connect)Info : SWD DPIDR 0x2ba01477Info : [STM32F103C8Tx.cpu] Cortex-M3 r2p0 processor detectedInfo : [STM32F103C8Tx.cpu] target has 6 breakpoints, 4 watchpointsInfo : [STM32F103C8Tx.cpu] Examination succeedInfo : starting gdb server for STM32F103C8Tx.cpu on 3333Info : Listening on port 3333

Hello,  I am working with STM32G030K8T6 microcontroller and I am using an independent watchdog (IWDG). The device goes into standby mode under certain conditions, but since I cannot turn off the IWDG, I am trying to reset the IWDG by waking up with RTC wake-up before the watchdog expires. The reset time of the IWDG is set to 32.8 seconds, so I am trying to set the RTC wake-up timer to 30 seconds so that the device wakes up before the IWDG expires. During normal operation I disable RTC wake-up, before going into standby I enable it and after 30 seconds I expect the RTC wake-up interrupt to run and reset the IWDG with the “HAL_RTCEx_WakeUpTimerEventCallback” function. However, after standby the system seems to reset completely and the wake-up callback function does not work, so the device resets without resetting the IWDG. My thought was that the “HAL_RTCEx_WakeUpTimerEventCallback” function will work while in standby and then it will go back to standby mode. But it doesn't work lik

I am using the latest version of CubeIDE (1.17.0), a STM32F765 Nucleo board with Ethernet. I am configuring the project to run lwIP using the internal Ethernet MAC. I am using FreeRTOS (CMSIS V2). CubeMX configures this LWIP_RAM_HEAP_POINTER to a default value of 0x30004000 which is NOT a valid address in the processor. I have gone through the reference manual to find out that nothing is present on this address and it is a reserved address. This causes a hardfault whenever I execute the code. However, if I comment the definition of LWIP_RAM_HEAP_POINTER, in that case lwIP uses normal buffer declared in RAM as heap and my code runs without any problem. I am making a course on this, so I just wanted to confirm if this is a bug in CubeMX or what?  

Hi everyone! I'm here with my devkit and trying to have FDCAN working properly! I compiled the Yocto distribution for the board and I followed all the tutorials in the wiki ( https://wiki.st.com/stm32mpu/wiki/Category:CAN ) and here's what I came up with: I initialized m_can1 &m_can1 { pinctrl-names = "default", "sleep"; pinctrl-0 = <&m_can1_pins_b>; pinctrl-1 = <&m_can1_sleep_pins_b>; status = "okay"; };I used the pins_b configuration because looking at the datasheet they were the only possible exposed pins on the PI_GPIO extender (CN2) on the board (overwriting I2C5 pins for the Arduino). I also removed the pullup resistors for i2c (R166 and R167). On the kernel side I tried the loopback and seems to work fine: root@stm32mp1:~# ip link set can0 up type can bitrate 1000000 dbitrate 2000000 fd on[ 1602.982564] m_can_platform 4400e000.can can0: bitrate error 0.3%[ 1602.988958] m_can_platform 4400e000.can can0: bitrate error 0.3%[ 1602.994593] IPv6: ADDRCONF(

Hi,I was able to successfully use arm_math.h in stm32cubeIDE and I did the same for the touchgfx application generated cubeIDE project.But when I tried compiling the same with touchgfx , it was showing an error  "arm_math.h" not found however , building the stm32cubeIDE project generated by touchgfx builds fine. I am totally lost how to integrate DSP library to touchgfx so it can flash along with UI

Hi all,I would like to keep RTC value (and keep the RTC working) during power off of the disco board, so I am planning to cut SB16 (soft bridge) from+3.3V and solder an external CR2032 +V battery to the board. My first questions are:How will I know that the battery is connected to VBAT pin of the MCU during initialization of RTC (from software)? The initialization generated by STM32CubeMX overwrites the date and time registers of the RTC. If the battery is connected the initialization could not modify the RTC clock value and I think it should do nothing with the battery backup RTC... I guess if the RTC is enabled during power on initialization then I have skip RTCInit(). Is this okay?Is there any example or tech paper how to use external battery for RTC and backup RAM? (Hidden secrets)Is the +3V CR2032 battery good pick (the 3V voltage) for backing up RTC?Any notes are welcome!Thanks,Louis  

Hello,I looked through the data sheets of multiple efuses and cannot really find reliable values of Iq (quiescent current) values (somtimes only leakage for certain pins is given). Even the product selector does not show any listings of Iq. Every other vendor (TI, AD, Onsemi, etc.) offers that. Or is it that I just couldn't find it?My requirements are:- max 10V input- lowest Iq possible in always on or when disabled- current limit: > 1.2AThank you.Best,Andy

Hi there,I am trying to set up UART3 to receive and transmit using Interrupt.My setup is simple to verify the issue. These are the steps that I did:1. Add Uart3 in .ioc file with the configuration as:2. In main(), before entering while(1) loop, I start receive_IT as:HAL_UART_Receive_IT(&huart3, bufTemp, 1); 3. Add Callback function as:void HAL_UART_RxCpltCallback(UART_HandleTypeDef *huart) {HAL_UART_Receive_IT(huart, bufTemp, 1);}The problem that I am running into that is if I send "1234\r\n", my HAL_UART_RxCpltCallback() only triggers twice, and I can see "1" and "2" in my buffer. I also verified ErrorCode before HAL_UART_Receive_IT() is called in the callback function. It turned out the error was an Overrun Error.Could someone please give me some suggestions on how to solve this issue? Sincerely, 

I tried to provision Secure Manager 1.2 to my DK board, and got the following error messages in the provisioning.log:2024-11-10 15:49:30,796 - root - DEBUG - Error: SFI command is not supported for the current device configuration using STLINK interfaces !2024-11-10 15:49:30,796 - root - DEBUG - Error: Cannot launch RSSe...2024-11-10 15:49:30,796 - root - DEBUG -2024-11-10 15:49:30,796 - root - DEBUG - Error: C:\Users\cbens\STM32Cube\Repository\STM32Cube_FW_H5_V1.3.0\Projects\STM32H573I-DK\ROT_Provisioning\SM\Binary\SecureManagerPackage.sfi SFI file Install Operation Failure! Please, try again.2024-11-10 15:49:30,796 - root - DEBUG -Then I booted the DK board in DFU mode, and used the programmer 2.17 to program the sfi, but still failed either "could not connect to the device" if SW1=0, or the following errors if SW1 = 1 (I know according to the instructions it should not be 1.)17:23:44 : Erasing memory corresponding to segment 0:17:23:44 : Not flash Memory : No erase done17:23:44

Does anyone have info or know how to determine the part #'s or specifications for lcd's used on STM32F746G-DISCO and STM324291-Eval1 boards?

Hello,Maybe you can help me, I am not able to start debug session with STLINK-V3MINIE.Context is: Windows 10 64bit, Intel(R) Core(TM) i5-9400STMCubeIDE V1.17.0 Tried with 2 different STLINK-V3MINIEthe STLINK-V3MINIE is seen and updated correctly to V3J15M7 using STLinkUpgrade 3.15.7 toolWhen trying to open a debug session, I get the message "No ST-LINK detected! Please connect ST-LINK and restart the debug session"I tried >20 times, connecting on different USB ports, different USB cables, 2 different STLINK-V3MINIE. I tried to switch OFF the firewall.When I use my old STLINK-V3MINI it is working fineWhen I use a Nucleo board, it is working fineAny idea what I should do? Thanks