Solved

Heyho,still checking L1 for new project, next question:Are the L1's internal EEPROM register interface, erase, read, and write functions the same as on L0 (we're already using that) ?Obrigado!

 Hello STM Community,I’ve been struggling with an issue for some time and would appreciate your insights.I’m using an STM32WB55 MCU connected to an LTE modem via LPUART for cellular communication. The modem’s default baud rate is 115200.I use a ring buffer with interrupt-based reception:  HAL_UART_Receive_IT(&huart1, rxByte, 1);At 115200 baud, I can see valid TX/RX activity on the lines using a logic analyzer, but the MCU does not receive or process any data in my ring buffer.However, when I lower the baud rate to 9600, everything works perfectly — I can read and process all incoming data as expected. The only change I make is the baud rate; the hardware and code remain the same.Has anyone encountered similar behavior with LPUART on the STM32WB55. I’d like to maintain 115200 baud for my application’s performance requirements. Does anyone have an idea how should I proceed on with this?Best regards,

  Hi, I created a project on the STM32N6570DK and I only have the project "in (STM32CubeIde)", I don't have the FSBL and the Appli. How do I flash my firmware? I tried to use the fsbl provided by the official ST repository, namely "ai_fsbl.hex", but the program does not start

I am using STM32F401, I had an application which communicates via USART1 by using DMA2. Both RX and TX DMAs are working fine. So I added a bootloader and moved application to 0x08008100. Bootloader is using same USART1 and DMA2. Now bootloader is working fine but I have problem with application.All I changed in application is start address. Bootloader jumps to application, timer interrupt is working fine and toggles LED. When it receives or transmits a data via DMA it stops, LED is not toggling anymore. When debugging I tried these:* SCB->VTOR is already set as 0x08008100. Timer interrupt is working fine.* I changed application's start address back to 0x08000000 and its working fine. * I removed USART and DMA code from bootloader so it only jumps to application. It didn't solve the problem (it lloks like not deinitialize-initialize issue).* I added USART and DMA to bootloader back. In the application I didn't use DMA when sending data with USART, it could send without any probl

Hello everyone,I'm working on an In-Application Programming (IAP) solution for an STM32F303CC. I've divided the flash memory into two application areas (let's call them App1 and App2), and I want to rewrite the program in App2 from code running in App1.I have already implemented this, and it seems to be working correctly. However, I have some doubts and would appreciate it if anyone with knowledge on this topic could provide some clarification.Here is my implementation detail:The code that erases the App2 area is located in the App1 area.It executes the standard HAL sequence: HAL_FLASH_Unlock(), HAL_FLASHEx_Erase(), and HAL_FLASH_Lock().Global interrupts are not disabled during this process.Several interrupts are active, but I have confirmed that all of their ISRs are also located within the App1 memory area.My understanding was that the CPU should stall if an interrupt occurs during a flash erase operation, as it would try to fetch the ISR from a busy flash. However, this stall does n

I am using STM32f756 Nucleo board. I have an rgb lcd interfaced via 18 bit (rgb666) connection with the mcu. I have previously used pixel format L8 with CLUT and successfully produced output on the display. Now, I have changed the pixel format to rgb565, changed the frame buffer to 16 bit and populated it with rgb565 values for each pixels. But there is no output on the display unless I enable the CLUT again. I understand that CLUT is only useful for 8bpp. I don't understand why in RGB565 pixel format, the display doesn't show anything without enabling CLUT.My setup is as follows -The frame buffer is a 16 bit 240x320 array. The moment I comment out the 5 lines from the bottom, disabling the CLUT and the frame buffer is updated with rgb565 values, there is no output. When these lines are un-commented and the frame buffer is populated with 8 bit values, I can see the output on the display.Any idea what might be causing this issue? 

Chip Model: STM32F030RBT6HAL Version: HAL Package "FW.F0.1.11.0", Patch="FW.F0.1.11.5"Symptom: After writing Data0 and Data1 to the Option Bytes (OB), debugging becomes unavailable. When checked with a programming tool, the protection level of the OB field changes to "BB". The system returns to normal after rewriting the protection level to "AA".Analysis:HAL API Function: HAL_StatusTypeDef HAL_SLASHEx_OBProgram (FLASH-OBProgramInitTypeDef * pOBInit) The parameters, uint8_t RDPLevel; There is no complement.and then, another function was called to rewrite configuration: FLASH-OB_RDP_LevelConfig (pOBInit ->RDPLevel); The register written here is only an 8-bit protection mode parameter whitout complement code. During option byte loading, the bit-wise complementarity of the option byte and its corresponding complemented option byte is verified. In case of failure, an option byte error (OPTERR) is generated and the corresponding option byte is considered as 0

Could anyone give me some advice on debugging the AIS2120 accelerometer sensor? I've included my CRC check function above, as well as the data sent and received via SPI, but I still can't read the correct sensor ID. Thank you very much for your help!

I was looking to wire these 2 items together to acquire a LiDAR 3d point cloud data set for a research project im working. I wanted to get some input, feedback and guidance on utilizing this hardware for LiDAR 3d point clouds? VL53L8CHV0GCP-NUCLEO-53L8A1

Is this the correct way to calculate the CRC check code?

Hi,I have the STM32MP257F-EV1 and I would like to load a kernel patched with X-LINUX-RT. I am after the PREEMPT_RT functionality.I have followed the instructions from https://wiki.st.com/stm32mpu/wiki/X-LINUX-RT_expansion_package#How_to_install_X-LINUX-RT_in_the_OpenSTLinux_Developer_Package so that I can patch the kernel and load it to my board.I have followed these instructions and also applied the patches and fragments from https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP2_boards/STM32MP257x-EV1/Develop_on_Arm%C2%AE_Cortex%C2%AE-A35/Modify,_rebuild_and_reload_the_Linux%C2%AE_kernel#Prepare_the_Linux-C2-AE_kernel_source_codeThe build happened fine but when I load the kernel and modules to the board I get the following error and get stuck in boot loop:[ 24.393964] Time out check load galcore module expired [ 25.312479] stm32mp_pm_domain power-domain-d1: sync_state() pending due to 48280000.gpu E/TC:0 Panic 'Watchdog' at /usr/src/debug/optee-os-stm32mp/4.0.0-stm

I want to install the codesys linux SL runtime on a STM32MP157-DK2.Dynamic libraries needed by the CODESYS Control Runtime binary:libm.so.6libpthread.so.0libdl.so.2librt.so.1libc.so.6libgcc_s.so.1Third-party requirements: - libc >= 2.27 (required by CodeMeter Runtime)Is it possible to install this on OpenSTLinux ?

Hi, I started working on my own dev board for a flight computer based on the STM32H747BIT6.At first, I struggled a bit to connect the board to the computer, only managing to do so using the hot plug mode in order to get some info from the microcontroller. My problem comes when trying to write something to the flash: it gets stuck on erasing internal memory sector 0. This means it is unable to write or modify the flash memory. Also, when I connect the board to the STM32CubeProgrammer, it shows me the flash memory, but every address is at 0, which makes sense given that I haven’t uploaded any code to the microcontroller.I’m not really sure what this means — I’m able to read it, but not write to it.The thing is, I started measuring the power source pins just in case I spotted something weird, and I sure did: my VCAP pins are at 2.2V, which is strange because they should be at 1.2V according to the internal LDO regulator.My guess is that this may be the source of the problem — an incorrect

This is for an STM32F303.I've reduced my MX configuration down as much as possible so that it only has SWD and a button on GPIO PA8 configured and the incorrect behaviour still occurs. The intent is for PA8 EXTI falling edge to start a timer, and for that timer to in turn interrupt on expiry. I do get an interrupt (for both EXTI and the timer), but the duration of the timer is always wrong (sometimes instant, sometimes quite slow), and when on interrupt I check instance->CNT it is always a random value.Following https://community.st.com/t5/stm32cubeide-mcus/hal-tim-periodelapsedcallback-firing-very-prematurely/m-p/588486 I am issuinghbuttonDebounceTimer->Instance->SR &= ~TIM_SR_UIF;during USER CODE 2 (after init, before the main loop), and it has no effect.My ISRs look likevoid HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim) { if (htim == buttonDebounceTimer) { HAL_TIM_Base_Stop_IT(htim); } } void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin) {

Hello,It seems that the library MotionMC_CM7F_wc32_ot_hard.a is missing the called function, here the error :c:\st\stm32cubeide_1.6.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_2.0.0.202105311346\tools\arm-none-eabi\bin\ld.exe: ../Middlewares/ST/STM32_MotionMC_Library/Lib\MotionMC_CM7F_wc32_ot_hard.a(motion_mc.o): in function `MotionMC_Initialize':motion_mc.c:(.text.MotionMC_Initialize+0xde): undefined reference to `MotionMC_SaveCalInNVM'c:\st\stm32cubeide_1.6.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_2.0.0.202105311346\tools\arm-none-eabi\bin\ld.exe: motion_mc.c:(.text.MotionMC_Initialize+0x1fc): undefined reference to `MotionMC_LoadCalFromNVM'I'm just doing like the example, I erased and reinstalled MEMS and this library at the previous version but nothing changes, can you help me ?Here the call :#define VERSION_STR_LENGTH 35#define SAMPLE_TIME 20/* Magnetometer

Hi, Can anyone recommend a development board that has ZIO headers and on-board SDRAM as well? I can't seem to find any.I have some other requirements as well:-> Needs to have a system clock > 180Mhz-> Advanced DMA Features-> Needs to have on chip ADC and DAC -> Nice to have ethernet support. Thanks in advance,Disha

I am having issues with Ethernet+LwIP+FreeRTOS on the NUCLEO-H7S3L8.  I was able to get Ethernet+LwIP to work on baremetal, but adding the RTOS and threading is having issues. I have attempted to follow the process here, but am still having issues.  I pulled the reference projects here, and attempted to merge the `ETH_CODE` code blocks over.  Still, the NUCLEO-H7S3L8 doesn't respond to my pings.  However, I am able to run the reference projects on a NUCLEO-H753 without an issue.  Note that I have disabled the MPU and Data cache for the time being.My IOC and STM32CubeIDE project are attached.  Does anyone have similar issues with the latest CubeMX/CubeIDE?

I’m trying to open a ticket through ST’s online portal, but I keep getting the following error when I attempt to submit it: Review the errors on this page.Case_trigger: execution of AfterInsert caused by: System.DmlException: Update failed. First exception on row 0 with id 003Ty000009rRzNIAU; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, US zip codes must start with 5 characters: [] Class.CaseUtility.addInfoToContactAndLead: line 231, column 1 Trigger.Case_trigger: line 38, column 1 I have tried using both Chrome and Edge browsers, but the error still occurs. I updated my contact on the ST profile with valid US ZIP code but that did not resolve it. Could you please advise how I can successfully submit a ticket?

Following up from my previous post, I am having issues with code generation - it seems to complete, but I don't see anything changed in the code.Here attached you will find the ioc file. I modified pin names for PB10 to PB12, but after generating the code I don't see any of the name in the project (should be in main.h, but I did a search in the whole project just to be sure). I am using STM32CubeIDE 1.16.0 on mac Sonoma 14.2.1 with M1 chip.

I'm trying to use STM32CubeMX directly or via STM32CubeIDE, and I can't find a way to configure ThreadX + USBX Host for STM32WBA65 boards such as NUCLEO-WBA65RI or STM32WBA65I-DK1.    Only Device classes show up.I've also tried to do it using the part directly instead of a board or example, and even then I only see Devices under X-CUBE-AZRTOS-WB > USB USBX > USBX from the Software Component view.I have noticed a few thingsThere is no X-CUBE-AZRTOS-WBA  only WB under select Components, but they are both there under Manage Software PacksI must change HSE to Bypass to have USB_OTG_HS enabled under connectivty.Even after configuring USB_OTG_HS to Host Only there are no UX Host parts showing in the Compnents under X-CUBE-AZRTOS-WB > USB USBX > USBX.Pinout & Configuration there is a separate THREADX and USBX between i-CUBE-wolfTPM and X-CUBE-AI which looks like I can turn on at the same time as the normal ThreadX per MCU Line.Is there an example of USB Host on

Title edited by a ST moderator to reflect the content. Hello, STM32CubeMX Version:6.15.0 STM32CubeH7 Firmware Package V1.12.0 / 30-October-2024 This Is My QSPI Configure in STM32CubeMX 1、When I Start QSPI Work in main function,The QSPI Will always work。QSPI work on CM4-Core。 source:   The QSPI CS signal wave，which Delta Time is 13us，not big than 1s according code： 2、When I Start QSPI Work in FreeRTOS Thread，The QSPI-CS signal Always High，and clock is always out 。QSPI work on CM4-Core。 source：   The CS Signal is always High, And clock signal is always output.The next is qspi-clock signal:   My Question is: 1、When I Start QSPI transmit-receive in main() function, It will always work, no stop. It's CS-signal always output low and high. Why? 2、When I Start QSPI transmit-receive in FreeRTOS thread, It does not work, CS-signal is always High, and clock is always output. I Have No Idea to solve it after many trial, Could You Have Some Idea?

My project is using an STM32U575. I have been studying the DfuSe file format and wondered if this can be used to change the values of option bytes. I can see that CubeProgrammer_API used strings such as "-ob nSWBOOT0=1" with sendOptionByteCmd(). If I were to include a target in a DfuSe file whose address is one of the option byte registers, would this successfully change the option bytes? That is to say, is the bootloader smart enough to handle writes to option bytes (presumably by spotting the target address)? In firmware, this is more complicated than writing to regular flash. For context:  We are performing firmware update over USB using the built-in ST bootloader. The update is initiated in the firmware by changing the nSWBOOT0 option bit and resetting, which runs the bootloader. So far, we have then used STM32CubeProgrammer to connect to the device and send the latest BIN image. After that, we use STM32CubeProgrammer to change the option bit again, and then reset to run

What's the difference between the following sensor variants:VL53L7CHVL53L7CXFrom what I've seen from going through the available product documents, they are all the same, performance-wise (range, frequency, FoV etc).Difference between the CH and CX seems to only be the firmware with the CH being able to output histogram data?Is this correct?Can the CH still output the normal processed data? 

Hello,I am trying to set up an external flash memory (MX25V1635F) on a Nucleo-U575ZI-Q.I have successfully used the low-level drivers (LLD) from the manufacturer Macronix and integrated them into the Levelx functions:UINT lx_stm32_nor_custom_driver_initialize(LX_NOR_FLASH *nor_flash) { UINT ret = LX_SUCCESS; ULONG total_blocks = 0; ULONG words_per_block = 0; /* USER CODE BEGIN Init_Section_0 */ total_blocks = 32; words_per_block = 16384; nor_flash->lx_nor_flash_base_address = 0; /* USER CODE END Init_Section_0 */ nor_flash->lx_nor_flash_total_blocks = total_blocks; nor_flash->lx_nor_flash_words_per_block = words_per_block; /* USER CODE BEGIN Init_Section_1 */ /* USER CODE END Init_Section_1 */ nor_flash->lx_nor_flash_driver_read = lx_nor_driver_read; nor_flash->lx_nor_flash_driver_write = lx_nor_driver_write; nor_flash->lx_nor_flash_driver_block_erase = lx_nor_driver_block_erase; nor_flash->lx_nor_flash_driver_block_erased_verify = lx_nor_

Hi!I have set up and connected a LSM6DSV16X via I2C to my raspberry pi, its on bus 10, address 0x6a. The sensor seems to have been detected via an I2C dump but the identifier (which should be 0x70) is stuck at 0x00 and I'm not sure why. azlan@argo:~ $ i2cdetect -y 100 1 2 3 4 5 6 7 8 9 a b c d e f00: -- -- -- -- -- -- -- --10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --40: -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- --50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --60: -- -- -- -- -- -- -- -- -- -- 6a -- -- -- -- --70: -- -- -- -- -- -- -- --azlan@argo:~ $ i2cdump -f 6 0x6a0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef00: 48 05 3d 3a 20 13 5e 9d 03 44 93 e2 80 13 00 00 H?=: ?^??D????..10: 00 00 00 08 39 ff ff ff ff ff ff ff ff ff ff ff ...?9...........20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff