Solved

Hi,I am new user of ST Microcontrollers. I am using STM32F4 Discovery board.Till now its default HSI oscillator I was using, now I am going to use the HSE clock of this.STM32F4 Discovery board have 8 MHz crystal, which is connected to the microcontroller. when I goto configure through STM32 CUBEMX configuration tool then it shows me a RED lndicator and it shows that clock must be greater than 14.2MHz.Why it is so? Datasheet says that we can use clock frequency ranging from 4-26MHz.Can someone explain me this? How to resolve this issue? 

Hello everyone, I am using TouchGFX 4.23.1 and I wonder how can I get the click force on display .I know there is the method "getForce" in ClickEvent class but there is no documentation that tells me how can I pass the Z-value (force) from my touchcontroller to TouchGFX library. Is there a method as "bool STM32TouchController::sampleTouch(int32_t& x, int32_t& y)" which I use to pass coordinate x and y to TouchGFX's driver? Thanks in advance 

I used buildroot to build the root file system and encountered the following error while running the qt example:penat(AT_FDCWD, "/dev/galcore", O_RDWR) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/dev/graphics/galcore", O_RDWR) = -1 ENOENT (No such file or directory) clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, 0xbe8ec8d0) = 0 write(2, "[ 1] Failed to open device: "..., 72) = 72I loaded galcore.ko, but there are indeed no galcore and graphics/galcore under/dev/:# dmesg | grep galcore [ 9.490473] galcore: loading out-of-tree module taints kernel. # ls /dev/galcore* ls: /dev/galcore*: No such file or directoryI used tslib to test touch and modetest to test LCD, both of which were normal. Why does my Qt still not run properly?

Hello, I see lot of data, but couldn't get it work.I got ST-Link /V2 ISOL and MCU: Nucleo F439. Want to debug in SWD1. CN4 jumpers removed in MCU2. on CN6:     pin 2 MCU (SWCLK) to pin 9 debugger    pin 3 MCU (GND) to pin 20 of debugger    pin 4 MCU (SWDIO) to pin 7 debugger3. Using CN1 usb to computer to power MCU4. When I start debug I get target not found. Please check steps and inform whats missing.  

I just started out a project with FreeRtos and followed this and managed to get it to work.How to redirect the printf function to a UART for debug messages I can also printF from the freertos.c StartXXXTask functions.But one of the start task functions i call my own method in my custom .C file i can't seem to printF from it. Within that function i can run this and it works, but not printF.HAL_UART_Transmit(&huart2, buf, strlen((char*)buf), HAL_MAX_DELAY); Wondering what am I doing wrong?

Please help:I have a developed pcb with an STM32WB55 on it.  I have been working with it for over a month with no issue.  I am using a Windows 11, with CubeIDE 1.12.0 and a STLINK-VSET3 that is plugged directly into the laptop (no hub).  The board when reflashed always use to load then sit at main() now however starting today after loading the board the code seems to now sit withinstartup_stm32wb55rgvx.sReset_Handler: ldr r0, =_estackAfter hitting the "run" button a few times it goes to main but then produces the following error within the console:Download verified successfullyFailed to assign value 80037b1, to register 0Failed to assign value 2002fff8, to register 0Failed to assign value 8001390, to register 0I have tried this on a second working board and get the same results.  I have powered down everything (including rebooting windows) and then I power up the board, power up IDE, plug debugger in and clean project.  Sometimes this briefly works in that I l

Hello, I am trying to achieve high throughput on a custom board. I partially replicated BLE_Throughput example for an initial testing.I am receiving the BLE data in MATLAB. In CubeMX, I use a custom ble template. I am trying send a payload 1000x times, in MATLAB i receive > 3000x randomly. (I mean  > (3000 x 244) Bytes of course, not 3000 Bytes).This is the main task for notification. Why I am receiving > 3000 Bytes while the transfer is limited by transfer_count? volatile uint8_t transfer_flow = 0; uint8_t transfer_count = 0; void SendActivityData_Task_Update(void) { uint8_t activity_buffer[244] = {0}; tBleStatus status = BLE_STATUS_INVALID_PARAMS; memset(activity_buffer, 0x11, sizeof(activity_buffer)); if (transfer_flow == 1 && transfer_count < 1000) { status = Custom_STM_App_Update_Char(CUSTOM_STM_ACTIVITYDATA_CHARINDICATE, (uint8_t *)activity_buffer); if (status == BLE_STATUS_INSUFFICIENT_RESOURCES) { transfer_flow = 0;

I looked through the DM00629856 User Manual UM2609 for this information.  Can someone point me in the direction of how I can find a table/graphic to define the symbols in the outline window pictured below.Thanks 

Hello,I am designing a product based on VL53L4CDV0DH/1 ToF sensor,when purchased an evaluation board NUCLEO-53L4A1 It contains a small cover IR windowI want to use it in mass production,There is off the shelf such IR cover ?P/N ?Thanks,Eduard    

I have a custom PCB I designed where I intend to use UART via PuTTy, however, I'm not entirely sure how to do this through the cube IDE. Normally with the Nucleo L476RG, the device is recognized and I upload code via USB, however, I need to flash the proper driver to be able to upload code on my current board. My schematic can be found here: https://pdf.ac/CP7hx. The board successfully bootloads and I can upload code via my ST-LINK and pogo pin header, but I'm not sure how to get the device recognized as an STM32 board, currently under my device manager its listed as a "USB Serial Port (COM4)". I found this video: https://www.youtube.com/watch?v=wGbiT6IxGP0&t=302s that shows how to install the STM32 USB bootloader, however, I don't know what file to download to the device. The device is recognized under the Flash Loader demonstrator, but here is the step I get stuck at:What do I put for the part highlighted in red? My UART IC is communicating with the USB connector s

Hi,I am fighting with the offset calibration of multiple VL53L1X. I use the API ULD with Arduino.I build a device to have 4 sensor[4] at 140mm far from a same plan. 2 of them give a good measure, 2 of them do not.I have tried the following process to calibrate for each sensor[4] ({xx,xx,xx,xx} are the value during the debug):sensor[i].GetDistanceInMm(&distance[i]); // distances are {115, 142, 143, 118} uint16_t OffSetToF; sensor[i].GetOffsetInMm(&OffSetToF); // returned values are {0, 0, 0, 0} sensor[i].CalibrateOffset(140, &OffSetToF); //returned values are {26, 65533, 65532, 23} sensor[i].SetOffsetInMm(OffSetToF); //with previous values {26, 65533, 65532, 23} sensor[i].GetDistanceInMm(&distance[i]); // distances still are{115, 142, 143, 118}Whatever the API (ST Ultra Light Driver or native ST_API), is the VL53L1X_GetDistance function (or GetDistanceInMm) supposed to give the measure corrected of the offset value calculated with the VL53L1X_CalibrateOffset function and

Hi, i find myself wanting to use stm bootloader instead of having to code my own.:| My setup consists in 4 identical nodes hooked up to a 2m long canbus.I can boot and talk with the canbus bootloader only when a single node is powered on in the bus.(the device enters its bootloader mode and waits for the 0x79 canbus command)Noone else in the bus is TXing anything only listening,BUT ....when more than one node is powered on ... the single node i want to boot doesnt reply to the 0x79 command (and i know is listening because as soon as i power off the rest of nodes and i send 0x79 trough canbus i get a reply from its bootloader)Extra weird thing this only happens with the initial 0x79 command, if i power on the rest of the nodes AFTER this 0x79 negotiation is done i am able to continue talking with the bootloader.I found this note in the AN3154 appnoteI dont use more than one node at a time....

Hi,When I used CubeMX, MCU could be switched to select[Pinout]→[List pinout compatible MCUs]→[OK, Import]However, in case of CubeIDE, the [OK, Import] button is not appeared.Is the "switch MCU function" deleted?Thanks your help,   

Hello, I enabled the generation of  debug filesystem by adding two variables in file build-openstlinuxweston-stm32mp15-disco/conf/local.conf as shown below to use with GDB. This step is  also mentioned in Yocto documentation (Link: https://docs.yoctoproject.org/dev/dev-manual/debugging.html#using-the-gdbserver-method ).  IMAGE_GEN_DEBUGFS = "1" IMAGE_FSTYPES_DEBUGFS = "tar.bz2" When this option is enabled I get below dependency(?) error, Does anyone know how to fix this?Additional information:Target HW : STM32MP157F-DK2Target image : st-image-westonThanks,  

Hi ST,     What tool generated the following data?Can you send me this tool? thanks. https://www.st.com/en/embedded-software/x-cube-cryptolib.htmlSTM32 cryptographic firmware library software expansion for STM32Cube. The path of the code is as follows:.\STM32CubeExpansion_Crypto_V4.2.0\Projects\NUCLEO-G474RE\Applications\ECC\ECDSA_SignVerify\Src\main.c    

I acquired some code for an STM32F3 that performs LIN communication over USART1.  Previously the code used DMA channels for both memory-to-peripheral and peripheral-to-memory transfers to/from USART1, but it had some problems that required restructuring the code so that USART1 instead interrupts on RXNE and the received bytes are read from the peripheral in the ISR.  Currently LIN transmissions are still driven by a memory-to-peripheral DMA channel.However, since I made that change I have not been able to get any LIN messages to transmit from USART1.  So my question is: can USART1 simultaneously support DMA for the memory-to-peripheral direction (transmit) and non-DMA (RXNE interrupt) for the peripheral-to-memory direction (receive)?  I was unable to find a definitive answer in the STM32F3 data sheet so I wanted to check that this should be possible before I dig into debugging.

I am trying to create a voltage divider to read a battery voltage of 2.5 - 3.8 V using a STM32L082KZ with a Vref of 1.8V. While calculating the required division to measure the range i wanted to include the influence the ADC measurement/loading has on my division but am unable to find a specification that shows this value. My question is, how high is the ADC resistance loading? I can see it is a SAR ADC so i would expect only parasitic resistance, but is this in the order of tens of kilo ohms or mega ohms?

Hi,Recently I had to replace the MCU in a device and I tried to upload the code using USB Bootloader, as it is available and requires very little stuff when you're on site.So, the MCU has been detected in the system (see PIC1.png), but the CubeProgrammer (v 2.5.0) could not properly connect to it via USB. Properly means that I'd get an accesss to anything - after a connection try, it changed state to connected, but the MCU ID, flash size etc are not shown, while they should be (see PIC2.png). Luckily I managed to connect using ST-Link (see PIC3.png) and the situation is partially resolved. The application does not use USB so I cannot do a fast check if the USB peripheral even works properly.What I noted is that the MCU revision is 2.0, while in the other device (which normally connects via USB) it is Z. Can this be a problem?Thanks in advance for any help, as I'd like to make the DFU via USB running back again.BR,Piotr Rutkowski

Hi @Imen.D  , @Khouloud ZEMMELI ,After updating the STM32CubeIDE to version 1.15.0 (today) I am observing below warning.The LD file has not changed. It has RAM and MRAM RWXC:/ST/STM32CubeIDE_1.15.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.win32_1.0.100.202403111256/tools/bin/../lib/gcc/arm-none-eabi/12.3.1/../../../../arm-none-eabi/bin/ld.exe: warning: xxx.elf has a LOAD segment with RWX permissionsMemory sections in LD file:MEMORY{ITCMRAM (xrw) : ORIGIN = 0x00000000, LENGTH = 64KFLASH (rx) : ORIGIN = 0x08000000, LENGTH = 2048KDTCMRAM (xrw) : ORIGIN = 0x20000000, LENGTH = 128KRAM_D1 (xrw) : ORIGIN = 0x24000000, LENGTH = 512KRAM_D2 (xrw) : ORIGIN = 0x30000000, LENGTH = 288KRAM_D3 (xrw) : ORIGIN = 0x38000000, LENGTH = 64KMRAM (xrw) : ORIGIN = 0x60000000, LENGTH = 1024K}Please help resolve the concern.Regards,Rajeev

Hi Everyone, I have a project utilizing a STM32G030F6P6 with a 32.768kHz crystal and the LSE to source the RTC clock. It is exhibiting 2% clock error (which is huge!) over a 10 minute period despite using a 20ppm crystal. I am measuring this error by interrogating the RTC and communicating it to the rest of my system via i2c. Now, I have read all of the crystal oscillator and load capacitor horror stories, but I have validated the actual crystal frequency by configuring the LSCO to output the LSE clock and it measures a stable 32.77 kHz (limited by the precision of my oscilloscope). In any case, much better than 2% error. What gives? Can anyone confirm the expected duty cycle of the LSCO signal (I am measuring 40% and cannot find documentation as to what I should expect). 

Hi, I'm working on ADC1, on a STM32U5 (on a Nucleo  board). In reference manual (RM0456) § 33.4.13 "Channel-wise programmable sampling time" we can read how to compute the total conversion time Tconv. The example is given for SMP = 5 ADC clock, at 55Mhz. It says: What I need is a confirmation about the statement I stressed in pink on the above picture "for 14-bit mode".Does it mean that if I set ADC1 to 12 bits or 10 bits resolution the computation is not done with 17 cycles but with something else (less than 17) ?Said differently: does the number of ADC clock for the conversion depends on the ADC resolution or is it fixed at 17 cycles for ADC1 ?My guess is that sampling time is programmable but conversion time is fixed whatever the resolution. Since in the RM I do not find any list of conversion time I tend to conclude I'm correct. But I'd like a confirmation to this.Best regardsPatrice.    

I'm using  stm32h5-nucleo144-board to develop USB (HID or CDC_ACM) application, I start with STM32Cube_FW_H5_V1.3.0 code by directory STM32Cube_FW_H5_V1.3.0\Projects\NUCLEO-H563ZI\Applications\USBX\Ux_Device_HID_Standalone.firstly, when I download the code into MCU and plug-in USB port(CN13) and change power supply to USB USER(JP2), it doesn't work. but when I plug-in stlink V3 USB(CN1), PC sussessful enum USB(STM32 HID Mouse Device) even without power change.  After this, I plug-out  stlink V3 USB(CN1), USB still here.BUT without ST MCU(3V3_STLK) running, USB doesn't work. I have do many times try, and think that is because STLINK MCU do something to let STM32H5 USB to work when the time plug-in? THE only connect between STLINK MCU & STM32H5 is SWD and VCP port, could someone tell me the LINK-MCU role in this application?  

Are there any plans to add Zephyr support for the STM32WB0X line of chips? Or is it already supported with the current HAL? I couldn't find any Zephyr related information on the product page.

Hi,we are working on NOD_WL55JC for LoRaWAN network with FUOTA.we are facing problem when at the following condition1) development kit used NOD_WL55JC, firmware ( en.stm32cubewl-v1-3-0.zip) - en.stm32cubewl-v1-3-0\STM32Cube_FW_WL_V1.3.0\Projects\NUCLEO-WL55JC\Applications\LoRaWAN_FUOTA 2) device is connected to LoRaWAN 1.0.4 (OTAA) to AWS server.3) connection is successful.4) multicast setup is successful5) multicast class C is successful6) switching to class C is successful.7) fragments are received at the end device( payloads at different locations in the function ProcessRadioRxDone are debugged) while fragments are downloaded, they are not getting forwarded to the case FRAGMENTATION_DATA_FRAGMENT in LmhpFragmentationOnMcpsIndication function.can you please suggest the reason for the same or can you please share the latest firmware which is working for FUOTA example.we have attached the device log for your quick reference.thank y

I use stm32CubeMX to generate usb code with HSI clock.Though I can config with usb clock to 48MHz, But stm32CubeMX software display there is clock issue as below:So I wonder can stm32f103cbt6 usb work under HSI clock?