Solved

I just unpacked NUCLEO64 C031C6 board and .. no code is working. Debugging I found all the code was stuck at SystemClock_Config / HAL_RCC_OscConfig.I checked and by default in the ioc file the HSE and LSE are set to "Crystal/Ceramic". For now I found a workaround - in the clock configuration I chose using the internal HSI, but I'd expect the boards to be working out of box with external clock source what is even declared on the board description (24 MHz or 48 MHz HSE)Later I found in the user manual (6.7 OSC clock sources):"HSE, which is the 8 MHz oscillator for the STM32 microcontroller. This clock is not implemented on the STM32 Nucleo-64 board" I have as well nucleo32-l432kc where the HSE seems to be present and working.I'd like to just confirm - is the HSE crystal really not there? Or did I miss something?Thank you for any insight

Hi,at the moment on the STM32U5G9 we have the SWD pins (SWDIO and SWCLK) set to DEBUG, but we would like to also use them as GPIO after programming. How do we switch them to GPIO at runtime? Thank you 

Hi ,I am not sure but my development board STM32H750B-DK may have some issues and I need some help to find what it may be .  As per the readme.txt (there is very less literature that I could find on this board) , I could dump the ext_mem boot bin into the Internal flash and I did not face any issue there. I am now trying to flash the IO toggle image onto the QSPI flash present on the development board and I always face the same error. I feel that there maybe a hardware issue on the board but I could be wrong. Your help is highly appreciated. I have attached the error image.  

Hello,I am using the BLE_p2pServer_ota example from the STM32Cube_FW_WBA_V1.4.1 firmware package.For testing purposes I would like to set different channels/frequencies for TX/RX (2402, 2440, 2480 ... MHz). Where can I find the corresponding functions for setting them?  

Hello,I have successfully implemented a Touchgfx based UI app using cubeMX and freertos on the STM32U599 chip. This is a basic application with multiple screens, a number of components all in ARGB2222. I am now in the process of porting my app from FreeRTOS to the zephyr platform. I am able to initialize touchgfx and start the process.Using gdb I verified the touch gfx process going through my first screen setup and invalidate it. But at some point in touchgfx::Application::draw(touchgfx::Rect&), a hard fault is produced.I have two theories on how this could be happening:1- Linker issues. At first zephyr was trying to allocate my UI elements where it saw fit. So I looked at the '.list' generated by cubeIDE to understand where my sections should be placed. Doing so I was able to put together the following linker sections and passed it to zephyr using cmake:SECTION_PROLOGUE(TouchGFX_Framebuffer, (NOLOAD),) { . = ALIGN(4); __TouchGFX_Framebuffer_start = .; KEEP(*("TouchGFX_Framebuf

Hello,I'm busy working on my first touchGFX project and I am using flex buttons instead of toggle buttons. I set the trigger to toggle and change the color of the button which works really well. The issue I am facing is that if I set a button to the off state when its default state in on and change screens the buttons will all reset to on when returning to the screen.I notice the same thing happens even with toggle buttons. Is there any way to save the state of the button when leaving the screen so that when I return it will still be in the correct state?Thanks in advance.

How would I be able to create a binary for this project or run it through CubeIDE? For some context I have taken this project from the FP-AI-VISION1_V3.1.0 pack, made some modifications, and would like to flash my H747i board with it. I can build the CM4 and CM7 files but when it comes to running the entire project or creating a binary for it I am at a loss. Thank you!

I am currently working with the VL6180X proximity sensor and would like to inquire about its long-term performance characteristics:      1. What is the expected Light/Luminous Depreciation time frame for the VL6180X's VCSEL source? Could you                provide any data regarding its lumen maintenance curve or L70/L50 specifications?     2.How does Light/Luminous Depreciation affect the sensor's performance over time?        Specifically:                 1. Does it primarily manifest as a reduction in return signal rate?                 2. Are there any observable changes in measurement accuracy?                 3. What are the typical indicators that Light/Luminous Depreciation has occurred?      3. Are there any recommended compensation strategi

I’m using a VL53L5CXV0DH/1 sensor in my current setup (see pictures). The goal is to detect a ball rolling between the sensor and the background. The red box is about 12cm apart.The settings is 4x4 for speed, i also noticed that 60 is not the highest scan frequency in code : status = vl53l5cx_set_ranging_frequency_hz(&dev,60);if i set 120 this works too, while scanning seems to be lot faster and just as accurate, why is 60 defined as maximum in the datasheet?However (even at 60), I often see target_status = 255 for 3-4 pads, without the ball passing and wonder why this happens. When this occurs, the distance information is apparently correct but the datasheets states that the distance readings become unreliable, and I want to ensure I get the most accurate and dependable measurements.When the ball passes i see 255 in even more status records.What could be causing this issue?Additionally, I’d appreciate any advice on settings or adjustments to improve detection, especially

I'm starting from the X-CUBE-SBSFU release v2.6.2, using the B-L475E-IOT01A - 2_Images_ExtFlash as a reference.  I've done the minimum porting required to run this on an STM32L4A6 target.I'm seeing an inconsistent issue where the SBSFU boots up and attempts to verify the Active Slot fw header signature, but fails.  The inconsistency seems tied to the build process, specifically the final step of building the UserApp + postbuild script to generate the combined SBSFU_UserApp.bin.On a 'good' build, I can flash the SBSFU_UserApp.bin onto the target and it will consistently boot successfully, regardless of the number of re-flash or reboot attempts.On a 'bad' build, I can flash the SBSFU_UserApp.bin onto the target and it will consistently fail to boot successfully, regardless of the number of re-flash or reboot attempts.= [SBOOT] SECURE ENGINE INITIALIZATION SUCCESSFUL= [SBOOT] STATE: CHECK STATUS ON RESETINFO: A Reboot has been triggered by a Software reset!= [SBOOT] STATE: CHECK

Hello, I am using CubeIDE v1.16.1 and I want to export a modified project from the firmware package STM32Cube_FW_WBA_V1.4.1. I modified the project directly in the corresponding example folder and it works successfully. Then I wanted to export the project. I tried different methods (copy, export & import), but I always got error messages when I tried to compile the exported project. My STM32Cube_FW_WBA_V1.4.1 firmware package is located in C:\Users\Frank\STM32Cube\Repository and I know that the projects use relative paths to the Drivers folder. But is there a way to export the project?    

Hello, I am facing an issue where the rendered frame buffer is printed on the display as gibberish pixels.I'm using the Nucleo F746ZG and interfacing it (over SPI) with an external display controller that writes to a 240*320 display. I was not able to locate the exact color depth of the display in the datasheet, but the information suggests that each pixel has 2ddot. Given RGB, I assumed 6bpp is the correct format.Initially I set up touch gfx to render a 16bpp frame buffer. With the 16bpp rendering I used the following code segment to send the rendered gibberish buffer to my display controller and get some random pixels printed.In TouchGFXGeneratedHAL.cpp:void TouchGFXGeneratedHAL::flushFrameBuffer(const touchgfx::Rect& rect) { uint32_t ibaseaddr = (uint32_t)getClientFrameBuffer(); uint16_t istride = lcd().framebufferStride(); uint16_t HParam = 1; uint16_t WParam = 1; uint16_t HScale = 100*HParam; uint16_t WScale = 100*WParam; uint16_t rot = 128;//<< rotates 90 degrees

Hello there,I would like to know where the NDEF middleware for X-NUCLEO NFC10 can be found.The X-CUBE NFC10 appears only to possess the RFAL middleware. 

I need to calibrate a VL53L4CX and have been reading UM2923. The functions described do not seem to bear any obvious relationship to the functions in the STM32Cube middleware which was generated for my project, which I find confusing. I it is not clear which functions I should be calling in order to satisfy the flow charts in UM2923. I have found essentially no other useful information about this device or its specific set of registers. I'm usually a huge fan of ST devices and documentation... The first sticking point is how to properly understand what to do with calibration settings. Am I supposed to store them in my own flash somewhere? That seems to be implied by UM2923. I can do this, but imagined the device would have its own NVM storage on board, since it is calibrated in the factory anyway. Is this the case? I thought so because the wrapper function VL53L4A2_RANGING_SENSOR_OffsetCalibration() ends by writing a data structure over the I2C interface from a function called VL53LX_s

Hello,I am working with [STM32 MCU model, e.g., STM32U5G9ZJT6Q], and I downloaded code from GitHub (link:https://github.com/STMicroelectronics/STM32CubeU5/tree/main/Projects/STM32U5G9J-DK2/Applications/USBX/Ux_Device_CDC_ACM ).While running the project, the code gets stuck in the tx_application_define() function, specifically in the while(1) loop after the USB initialization MX_USBX_Device_Init().Here is the relevant portion of the function:VOID tx_application_define (VOID *first_unused_memory){        UINT status = TX_SUCCESS;         VOID *memory_ptr;  if (tx_byte_pool_create( &tx_app_byte_pool,  "Tx App memory pool",  tx_byte_pool_buffer,     TX_APP_MEM_POOL_SIZE) != TX_SUCCESS)  {      while(1);  }    memory_ptr = (VOID *)&tx_app_byte_pool;    status = App_ThreadX_Init(memory_ptr);    if (status != TX_SUCCESS)   {    whil

I BOUGHT STEVAL- MKBOX PRO AND AM THINKING OF USING IT.I have a wireless function, but please tell me the status of technical conformity approval for use in Japan.There was no conformity mark on the package.

Hello,I'm designing a custom board with a LIS2DW12 accelerometer for motion detection. I want to use INT1 to send a signal to the MCU when it detects movement, which should wake up the whole system. The accel supports both i2c & SPI communication but I intend to use SPI. I would like to verify how I plan to make my connection between the accelerometer and MCU. Please refer to the images below.Note: VBAT is sourced from a 3V CR 2032 coin cellQ1) I'm aware that the datasheet mentions that to enable SPI communication, the CS pin must be set to logic '0' as seen in the image below. Is it okay if I directly connect the CS of the accel to a GPIO pin on the MCU through ACCEL_CS or should I add a pulldown resistor on the ACEEL_CS connection? Q2) The datasheet mentions using 100 nF (C6) ceramic and 10 µF (C5) aluminum decoupling capacitors for pin 9 (VDD). Is it okay if I use a 10 µF ceramic capacitor instead. I'm constrained for both real estate and budget on this project?Q3) Are

Hello ST Team,                              Currently i am using STM32H523RCT6 mcu for one of my application. Some times mcu goes into "hardfault handler/nmi handler". Can you suggest what will be reasons behind that problem.   Thanks with Regards DEEPAK

Hello,I would like to know how to send a ZIP file in a private message. I don't have this option at the bottom of the pageBut I have only theses option at the Top of the page :And with this options, I can't send anything.Thank you

Hi,I am working on a custom ISPU code for LSM6DSO16IS and I want to generate interrupts on INT1 and INT2. I checked all the examples in x-cube-ispu/Ispu/ism330is_lsm6dso16is at main · STMicroelectronics/x-cube-ispu generates an interrupt only on INT1.Is it possible to generate interrupts on INT1 and INT2 at the same time? Thanks a lot :)Chen

Hi,i use the example BLE_p2pServer_ota with STM32WBA55. When i scan the device, i get the advertising elements in this order:I want to swap the first both elements. How and in which file can I change this order?   

Hello,I try to build a 'PDO SINK' project on B-U585I-IOT02A and I have watched the video How to build an USBPD Sink application using the X-Cube-TCPP software pack - YouTube.Issue:After build project on STM32CubeMX 6.12.0 and opened project in STM32CubeIDE 1.13.2, there is errors shows '../TCPP/App/app_tcpp.h:26:10: fatal error: usbpd_ADC_SNK.h: No such file or directory'.Could you please review attached screenshot and let me know if there is something I'm missing in my project setup.Best regards,Robert

I modified an FSBL example to get to the root of the problem (everything else being as in the example).   volatile int rrr = 0; void SGI0_IRQHandler(void) { while (1) { rrr++; }; } int main() { HAL_Init(); SystemClock_Config(); IRQ_Disable(SGI0_IRQn); IRQ_SetPriority(SGI0_IRQn, 0); IRQ_Enable(SGI0_IRQn); while(1) { GIC_SendSGI(SGI0_IRQn, 1, 0); } }   This works perfectly in thumb mode, but when I switch to ARM (that probably should give slight performance boost for my DSP task), the interrupt is stuck in Vectors section, without doing anything.The LR is weird, and I cant get my head around how is it possible that is has LR = 0x2ffe0106 (not multiple of 4)As if the core switched to thumb mode without address being odd and started executing instructions in 16 bit mode.Thanks for any advice :)

Hello together,I'm a little bit confused by the NVIC and EXTI description in the RM0503.The NVIC vector table says the RTC / TAMP interrupts are combined EXTI lines 19 & 21 (on page 302).But when looking at the EXTI line connections table (on page 309) the RTC source is on line 28 and TAMP on line 29. 

Hi, recently I had a problem using STM32CubeMX to modify the pre-configuration of an STM32F746 processor made by TouchGFX for the STM32F746G-DISCO Discovery board. I was disoriented with the configuration of a particular GPIO pin needed by my application on the Arduino connector of this discovery board (PG7), which was free but "invisible" (i.e. not listed at all) in the table of the GPIOs in the Configuration form of the Pinout & Configuration view. Undoubtely, the problem was generated by my limited experience with CubeMX, but I think that this can be a common problem with new users of the current interface. IMHO it could be a good idea to add on top of the GPIOs table in the Configuration form a checkbox to enable/disable the visualization of ALL GPIO pins, also the unused ones, as well as a "filter row" where the user can write search strings to filter the listed items (). In the current version of CubeMX, the uninitialized pins are not visible at all in the table and the "Sear