Solved

Hello!I recently bought an STEVAL-WESU1 sensor unit. However, when I connected the USB cable to the circuit board, the on board RED LED keeps blinking. According to the documentation it should be steadily lit to indicate charging. Would you be able to give me any tips in debugging? I apologize for the trivial nature of the question. I thank you very much in advance.

..

I have a capacity of 40nF on the S2 pin, charged to a voltage of 3.3V.The D pin is at GND. The 40nF is then discharged through the analog switch. The peak current will be around 6.6A for a very short time (if the analog switch has 0.5 Ohm resistance). But the datasheet specifies 500mA max. Will the analog switch survive that?

..

hi,i'm trying to compile a program in STM32CubeIDE that i wrote that cotnains calls located in libgpiod. but i'm getting linker errors as shown below. do i need to create the library myself or do i need to set a path in the CubeIDE's environment?i selected the option to install STOpenLinux to be embedded inside of CubeIDE.Invoking: MPU G++ Linkerarm-ostl-linux-gnueabi-g++ -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=/home/vbuonassisi@ostendo.local/.eclipse/com.st.stm32cube.ide.mcu.rcp.product_1.6.0_1935172119_linux_gtk_x86_64/plugins/com.st.openstlinux.sdk.openstlinux_5.4_dunfell_mp1_20_11_12_5.4.0.202011171729/tools/sysroots/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi -o "NearEGSoftware" ./gpio_test.o ./main.o   -Wl,-Map="NearEGSoftware.map" -Wl,--gc-sections/home/vbuonassisi@ostendo.local/.eclipse/com.st.stm32cube.ide.mcu.rcp.product_1.6.0_1935172119_linux_gtk_x86_64/plugins/com.st.openstlinux.sdk.openstlinux_5.4_dunfell_mp1_20_11_12_5.4

I want to know can I use touchGFX without LTDC and with FMC (because I use SSD1963)? I don't want change my hardware.And is it easy to use touchGFX without operating system (bare metal)? or no, it's recommended to use touchGFX with os?Thank you.

..

Hello,I don't find on the STM32H730ZB datasheet a clear information about the maximum current output for the DAC ( with or without a OPAMP in follower). I plan to drive a LED from 100µA to 10mA maximum.Today, I have an externaI op-amp & mosfet but I would like to reduce the footprint of my board and the BOM cost ThanksBertrand

I have set :hostname_pn-base-files = "new_host_name"in my conf file.This seems changing /etc/hostname in base-files image. However, there is log message telling:"[   7.249795] systemd[1]: Set hostname to <stm32mp1-disco>."Also, /etc/hosname contents is "stm32mp1-disco".I can't find what other recipe/module is dealing with hostname settings.

Hello, how to let touchgfx font support emoji unicodes?

How is the curve in Figure 4 in the datasheet measured? I noticed in Figure 5 that the 20 us pulse has a 8 us rise time and the 1000 us pulse has a 10 us rise time. The 10 ms pulse doesn't even have a specified rise time. Is each point in the Figure 4 graph just a standardized square wave with the same rise time and incrementing the pulse width, or does each measurement have a different rise time? If so what is the rise time for the pulses measured?

..

I use the 'cut off' STLINK board from a Nucleo 446 module to program other STM boards using the STMcube programer software. This works fine for all my STM processors. However, I cannot connect to the STEVAL-PTOOLV1 motor control eval board - cannot find the target. I have verified that the STLINK board works ( it programs a separate Nucleo446 fine) - I have checked the wiring to make sure SWclk, SWdio, NRST, VDD, gnd are all wired one to one between STLINK and PTOOLv1 board, etc. I have powered the PTOOLv1 board and enabled the 'trigger' to put power on the processor. Cube programmer sees the STLINK module, set to SWD port, latest firmware loaded to STLINK, etc - never connects to PTOOLV1 processor...Any ideas?

Hi, I use TouchGFX in my HMI project, I want to create an instance of an object (ig. a button) in runtime (dynamically), so I could destroy it later and free it's allocation memory.I tried create it in a method but it seems to have runtime error:void Screen1View::create_button() { touchgfx::Button button1; button1.setXY(0, 0); button1.setBitmaps(touchgfx::Bitmap(BITMAP_BLUE_BUTTONS_ROUND_EDGE_SMALL_ID), touchgfx::Bitmap(BITMAP_BLUE_BUTTONS_ROUND_EDGE_SMALL_PRESSED_ID));   add(button1);   button1.invalidate(); } Does anyone have any solution?

I'm trying to get a STM32Cube project compiled using arm-none-eabi-gcc and a Makefile. The FW builds without problems.but when I boot the MCU i get stuck in Hard Fault. Any ideas what could be wrong?Reset_Handler: ldr sp, =_estack /* set stack pointer */   /* Copy the data segment initializers from flash to SRAM */ ldr r0, =_sdata ldr r1, =_edata ldr r2, =_sidata movs r3, #0 b LoopCopyDataInit   CopyDataInit: ldr r4, [r2, r3] str r4, [r0, r3] adds r3, r3, #4   LoopCopyDataInit: adds r4, r0, r3 cmp r4, r1 bcc CopyDataInit /* Zero fill the bss segment. */ ldr r2, =_sbss ldr r4, =_ebss movs r3, #0 b LoopFillZerobss   FillZerobss: str r3, [r2] adds r2, r2, #4   LoopFillZerobss: cmp r2, r4 bcc FillZerobss   /* Call the clock system initialization function.*/ bl SystemInit /* Call static constructors */ bl __libc_init_array

Below CubeProgrammer's window is gdb displaying the real content of BKPSRAM. JW

There is a similar open issue in another post. https://community.st.com/s/question/0D53W00000EndiI/stm32g030-adc-issue​My MCU STM32F446 is set to read 9 channels' value by ADC1 with DMA2_Stream4. Settings are as below. Using StdDriver @version V1.8.0, 04-November-2016.​ RCC_AHB1PeriphClockCmd(RCC_AHB1Periph_DMA2, ENABLE); RCC_APB2PeriphClockCmd(RCC_APB2Periph_ADC1, ENABLE);   DMA_DeInit(DMA2_Stream4);   ADCDMA_InitStructure1.DMA_Channel = DMA_Channel_0; ADCDMA_InitStructure1.DMA_PeripheralBaseAddr = ((uint32_t)(&(ADC1->DR))); ADCDMA_InitStructure1.DMA_Memory0BaseAddr = (uint32_t)&(adc_monitor_sample_raw_data[0]); ADCDMA_InitStructure1.DMA_DIR = DMA_DIR_PeripheralToMemory; ADCDMA_InitStructure1.DMA_BufferSize = ADC1_OCCUPY_CHANNEL_AMOUNT; ADCDMA_InitStructure1.DMA_PeripheralInc = DMA_PeripheralInc_Disable; ADCDMA_InitStructure1.DMA_MemoryInc = DMA_MemoryInc_Enable; ADCDMA_InitStructure1.DMA_PeripheralDataSize = DMA_PeripheralDataSize_HalfWord; ADCDMA_Init

Using AN5651 Update procedure and configuration in DTM firmware for X-NUCLEO-BNRG2A1, I upgraded the firmware image to the latest stack image. I connected the ST link V2 and flashed the "BLUENRG-M2SP_DTM_SPI.hex" file with the BlueNRG ST link utility. After the device was flashed successfully, the ST link V2 lost connection to the device and could no longer connect to the target. The SWD settings are the same as before: 100kHz, low power mode enabled, etc. I have tried restarting the application, power cycling the board, and trying different SWD frequencies, but nothing seems to work.The interesting thing is that the M2SP is fully functional. The BLE application on my main nucleo board still functions with the BNRG2A1 as before, so I know that the new FW was flashed correctly. In fact, I verified the reported FW version from the M2SP had changed to the new version number when debugging my nucleo board application. It seems that the new FW image I flashed has somehow disabled SWD.

The maximum frequency I can set is 200 MHz.STM32H743VIT6CubeIDE 1.6.1

My project uses SBSFU template ported to my STM32L496 board. I need to call the crypto library from the user app. UM2262 mentions cryptographic middleware support in sections 6.2.3 and 6.2.4, but it is vague. Are there other documents that explain better, or perhaps specific examples for calling the crypto lib from the user app?

Hi ST!I am working with Rust on your STM32MP157. While we have this working already, this is cumbersome as we have to figure all register addresses and layouts manually. Normally, in Rust, we parse the SVD file corresponding to a chip and go from there which is a huuuge improvement to doing everything manually. Unfortunately the SVD files available for the STM32MP157 are highly incomplete and wrong at times. Could you please fix & update the SVD files? Thanks a lot!Best,Noah

I've built a simple STM32CubeIDE project with just the SDMMC1 peripheral mapped, a GPIO pin for the SD Detect pin and the FatFs middleware enabled with DMA per a discussion elsewhere on this forum. I have a Waveshare microSD card jumpered to what I'm pretty sure are the right pins on the Nucleo board. The program gets all the way to the f_mkfs call which eventually winds up calling HAL_SD_WriteBlocks_DMA which, if I understand correctly, is supposed to eventually fire the BSP_SD_WriteCpltCallback if it completes the write correctly. Unfortunately, that WriteCpltCallback never gets called and the calling subroutines eventually times out and I'm not sure what event or IRQ is supposed to fire the WriteCpltCallbackI have the Waveshare microSD card jumpered with 6" jumpers to the Nucleo board which possibly presents a signal integrity issue which prevents the WriteBlocks_DMA call from completing correctly. However, I have gotten the Waveshare board to work on a Nucelo413ZH with the same jum

Good day,I would like to know if it is possible to change the value of the temperature offset of the LPS25HB.If so what register will need to be manipulated?Thank you

Hi,Does the LPS25HB sensor automatically compensate for temperature ?If not how does one go about programming for it?Thank youCesar

Hi, I want to synchronize the my threads execution using the mutex.here is my code /*---------------------------------------------------------------------------- * CMSIS-RTOS 'main' function template *---------------------------------------------------------------------------*/ #include "RTE_Components.h" #include CMSIS_device_header #include "cmsis_os2.h" #include "stm32f2xx_hal.h" #include "stm32f2xx_hal_gpio.h" #include "main.h" //osMutexId_t mutex_id; /*---------------------------------------------------------------------------- * Application main thread *---------------------------------------------------------------------------*/ __NO_RETURN void thread1 (void *argument) { (void)argument; uint32_t ii=0; osMutexId_t mutex_id1; __HAL_RCC_GPIOF_CLK_ENABLE(); // enabling the peripheral clock // gpio structure initialization GPIO_InitTypeDef GPIO_InitStructure; GPIO_InitStructure.Mode= GPIO_MODE_OUTPUT_PP ; GPIO_InitStructure.Pin= GPIO_PIN_0; G