Solved

I'm working with the "NUCLEO-U575ZI-Q" development board and I compile using STM32CubeIDE 1.6.1. My project uses FreeRTOS and if I debug my project and halt execution, then I can see the currently executing thread's stack trace in the upper left part of STM32CubeIDE and the current line of code of execution is highlighted. Is there a way to someone (not necessarily inside STM32CubeIDE) show the stack traces of all threads? And, as a bonus, is it possible to show/highlight the lines of code that each thread last executed on?

I need a small form factor RF ID Reader (max space available for reader antenna is 60mm x 40 mm) and max tag size is 55mm x 13 mm. Can someone help me to find out the best possible RF ID reader and Tag solution (LF/HF/UHF)? Any design consultant?

The original project was compiled and maintained in Atollic 9.3.0 for a STM32F030C8. We are trying to add a vendor stack that is written in C++.We began by adding the #include <new> to the main to insure the compiler could see the needed include paths. arm-atollic-eabi-gcc -c ..\src\main.c -mthumb -mcpu=cortex-m0 -std=gnu11 -DHSI_VALUE=8000000 -DSTM32F030 -DUSE_STDPERIPH_DRIVER -I../src -I../Libraries/CMSIS/Include -I../Libraries/CMSIS/Device/ST/STM32F0xx/Include -I../Libraries/STM32F0xx_StdPeriph_Driver/inc -IC:\Program Files (x86)\Atollic\TrueSTUDIO for STM32 9.3.0\ARMTools\arm-atollic-eabi\include\c++\6.3.1 -IC:\Program Files (x86)\Atollic\TrueSTUDIO for STM32 9.3.0\ARMTools\arm-atollic-eabi\include\c++\6.3.1\arm-atollic-eabi\bits -Og -ffunction-sections -g -fstack-usage -Wall -Wfatal-errors -specs=nano.specs -o src\main.o In file included from ..\src\main.c:22:0: C:\Program Files (x86)\Atollic\TrueSTUDIO for STM32 9.3.0\ARMTools\arm-atollic-eabi\include\c++\6.3.1/new:39:28:

Hi,I am using STM32CubeProgrammer version 2.12 running on Windows 10 to connect to the STM32MP157F-DK2 board ST-LINK connector CN-11.I managed to connect and when I click "Firmware upgrade" the STLinkUpgrade 3.4.0 window opens.However, when I press "Open in update mode" I get the error message:Error connecting to device ST-LINK/V2-1 (error 0x3); check USB connection and refresh the device listAt this point the connection is dropped and I have to connect again.I also noticed that the "Current Firmware" was not listed as I expected from my experience of upgrading the ST-LINK firmware on other NUCLEO and DISCOVERY boards.Maybe the current version of STM32CubeProgrammer doesn't yet support the STM32MP157F-DK2 board ?Any help would be much appreciated.Kind regards,Steinar

Why am I unable to read NDEF information in the STSW-ST25001 APP using the following code, with no messages being displayed?

Hello,I am try to control an external DAC system with the SPI interface. The clock signal shape looks like the attached file. I didn't figure out the meaning of the signal. Yellow is the clock signal and the blue is CS signal.

What is the recommended footprint for this device?The TN1171 technical note is next to useless, so please don't direct me there.What is the width of this pad please, as I cannot decipher your data sheet for this information  Frankly, I'm a little disappointed this information is so confusing and hard to extrapolate.

I'm using the STM32MP157F-DK2-ND evaluation board and getting an error when I try to enable SPI5.I have researched previous posts with this errorhttps://community.st.com/s/question/0D53W000006FjAUSA0/error-activating-spi-module-in-yocto-linux-projecthttps://community.st.com/s/question/0D53W00000GZlRVSA1/enabling-devspidevxx-on-openstlinuxhttps://community.st.com/s/question/0D53W00000RS3ynSAD/how-can-i-enable-spi5-on-stm32mp157dk1And reviewed relevant documentationhttps://wiki.st.com/stm32mpu/wiki/How_to_use_SPI_from_Linux_userland_with_spidevhttps://wiki.st.com/stm32mpu/wiki/SPI_overviewhttps://wiki.st.com/stm32mpu/wiki/SPI_device_tree_configurationI've also ensured these options are checked in make linux-menuconfighttps://wiki.st.com/stm32mpu/wiki/SPI_overview#Kernel_configurationStill, I cannot figure out why the clock isn't running.[ 1.533147] spi_stm32 44009000.spi: clk rate = 0               [ 1.536942] spi

Hello all,I am facing a strange issue where the kernel sometimes fails to reboot the system. Here is what I am seeing.I use busybox reboot -f from the command line so that the reboot request goes directly to the kernel, i.e. no init/systemd involved. This simplifies things.I am tracing the reboot syscall up to the psci_sys_reset function of the PSCI device driver (drivers/firmware/psci/psci.c). I am toggling a GPIO just before invoking invoke_psci_fn:static int psci_sys_reset(struct notifier_block *nb, unsigned long action, void *data) { pr_info("reset!\n"); if ((reboot_mode == REBOOT_WARM || reboot_mode == REBOOT_SOFT) && psci_system_reset2_supported) { /* * reset_type[31] = 0 (architectural) * reset_type[30:0] = 0 (SYSTEM_WARM_RESET) * cookie = 0 (ignored by the implementation) */ invoke_psci_fn(PSCI_FN_NATIVE(1_1, SYSTEM_RESET2), 0, 0, 0); } else { // TOGGLE GPIO HERE invoke_psci_fn(PSCI_0_2_FN_SYSTEM_RESET, 0, 0, 0); }   return NOTIFY_DONE; }The gpio i

I'm using the development board STM32L4P5G-DK. My development board uses display type RGB222(6bits) <--device configuration tool(its the only option). My LCD display makes use of 24bit RGB data(RGB888 input format). Controller uses the following outputs: R7,R6,G7,G6,B7,B6. I have connected it to R7,R6,G7,G6,B7,B6 of the display, the rest of RGB data signal of the display is connected to ground. In device configuration tool of STM32Cube IDE i use the pîxel format RGB888(layer 1). I only use one layer.About lcd-image-converter:1)Wich image format(png,bmp,jpeg,etc) is recommended to use for converting an image to C for STM32?2)Wich "main scan direction" to use(top to bottom, bottom to top, left to right,etc)?3) In the application note 4161 they recommend to use Image -->block size: 32 bit: is this correct?4)Wich preset option to use, "R8G8B8" or an other?5)In Image-->Common -->application note 4161 shows to use "split to rows". Is this correct?Could someone help me.

I am working with an App developer to read/write to an ST25DV Dynamic Tag. The project does the following:1 App writes to the ST25DV a short NDEF Text record (15 bytes), the App then goes into some kind of wait mode2 Host micro reads the tag using I2C3 Host decodes data read and sends a reply record using I2C4 After approx 1 second the App reads the ST25DV tag.This works perfectly with phones running Android 8 and Android 11 but does not work properly with Android 13. The ST25DV is written OK. The host micro read/writes properly but the the app returns an error message Last Exception,"Bad state:no Element".What does this message mean and wht would I get it when the older Android versions seem to work fine.Any help would be great.

By default, in Windows, STM32CubeIDE downloads all firmware dev packages for all MCUs used into a Repository folder under the User folder for the user installing it, e.g.: C:\Users\User Name\STM32Cube\Repository.I don't want it there, actually not even on that drive at all.How do I change that Repository path?

Hello,I am having accuracy issues on TIM2 (32Bit Timer). I am feeding the PLL with an HSE 32MHz crystal (which seems to be fine when I measure the MCO frequency). I have setup the Prescalers to reach a frequency of 240MHz for the APB1 Timer clocks (where the TIM2 belongs to). The thing is, after some timing measurements I get an error of 0.4% in TIM2, if I set the prescalers before the timer higher (D2PPRE1) but reduce the Prescaler within the Timer the accuracy worsens. I am a little bit puzzled, since I thought I would get something similar to the 25ppm of the HSE.Some additional info, I have in the TIM2 a prescaler of 240 and therefore each count is equivalent to 1us. Any clue about this phenomenon or hint about what I could be doing wrong?Thanks

I made a prototype board using STM32H7A3LIH6Q.Before the firmware was written, a current of 500mA flowed(@+3.3V).VDD and VSS were not shorted.​Q1)Have there been such cases in the past?Q2)Are there any mistakes in the wiring of the circuit?Q3)VFBSMPS is plane on the inner layer of the board, is there any problem?​

STM32L071CBT wakeup power button PC13, PWM signal = PA11I have a device that wakes every 20 seconds then goes to sleep, it can also wake when the power button is pressed, part of it's wake cycle it to check the servoInt pin for activity.pin setup /*Configure GPIO pin : servoInt_Pin */ GPIO_InitStruct.Pin = servoInt_Pin; GPIO_InitStruct.Mode = GPIO_MODE_IT_RISING_FALLING; GPIO_InitStruct.Pull = GPIO_NOPULL; HAL_GPIO_Init(servoInt_GPIO_Port, &GPIO_InitStruct);   /*Configure GPIO pin : powerButton_Pin */ GPIO_InitStruct.Pin = powerButton_Pin; GPIO_InitStruct.Mode = GPIO_MODE_IT_RISING; GPIO_InitStruct.Pull = GPIO_NOPULL; HAL_GPIO_Init(powerButton_GPIO_Port, &GPIO_InitStruct);stop mode is calledif(HAL_RTC_SetAlarm_IT(&hrtc, &RTC_AlarmStructure, RTC_FORMAT_BIN) != HAL_OK) { ErrorHandler(ERR_RTC_ALARM); } HAL_PWR_EnterSTOPMode(PWR_LOWPOWERREGULATOR_ON, PWR_STOPENTRY_WFI);IRQHandlervoid EXTI4_15_IRQHandler(void) { if(__HAL_GPIO_EXTI_GET_FLAG(servoInt_Pin) != RESET

My idea is that:I want to put a resistor and a capacitor on BOOT0 pin. When normal code is running and i will go to update the firmware, i will send a command to USB. When MCU will receive this command, MCU will set BOOT0 pin to high state and charge the capacitor. After that MCU will runs an autoreset command.Could be it works?How much time BOOT0 pin must be stay high for entering in boot mode?Thank you for all.

No mention of HAL_UARTEx_RxEventCallback in UM1905 (Description of STM32F7 HAL and low-layer drivers, rev 4, 2020). Some commentary would be welcomed. Suggest your documentation be updated. It looks like the same function is missing in the F4 HAL UM, and possibly others. Thank you for your attention to this.

..

the Dead Battery Signals have been selected in stm32cubeMX, but when it run to "MODIFY_REG(SYSCFG->CFGR1, (SYSCFG_CFGR1_UCPD1_STROBE | SYSCFG_CFGR1_UCPD2_STROBE), ConfigDeadBattery);",SYSCFG->CFGR1 keeps default value.the clock is enabled.

Hello everyone, I have a B-L475E-IOT01A board and I'm trying to configure I2C to communicate with a digital barometer (LPS22HB). But I have a problem, I can't get the SCL signal to be generated. I appreciate your help in solving my problem#include <stdio.h> #include <stm32l4xx.h>   void system_clock_msi_init(void) { RCC->CR |= RCC_CR_MSION; // MSI clock enable RCC->CFGR |= RCC_CFGR_SW_MSI; // MSI oscillator selection as system clock while((RCC->CR & RCC_CR_MSIRDY) == 0); RCC->CR &= RCC_CR_MSIRANGE_Pos; RCC->CR |= RCC_CR_MSIRANGE_7; // MSI clock ranges 7 around 8 MHz RCC->CR |= RCC_CR_MSIRGSEL; // Internal Multi Speed oscillator (MSI) range selection while((RCC->CR & RCC_CR_MSIRDY) == 0); }   void clock_enable_init(void) { RCC->APB1ENR1 |= RCC_APB1ENR1_I2C2EN; // enable I2C Clock RCC->AHB2ENR |= RCC_AHB2ENR_GPIOBEN; // enable GPIOB Clock RCC->CCIPR |= RCC_CCIPR_I2C2SEL_0 ; // System clock (SYSCLK) selected as I2C

Hi there,I am a beginner of using customize board to build a project for reading a ISO 144443-4 card .Due to the environment require a higher power output of the reader, therefore i chose ST25R3917 as my rfid SOC. But during the firmware developing stage, i am still confuse while reading the data sheet.First question for the glance, could ST25R3917 support reading ISO 144443-4 card, which protocol should i config? My goal for this project is read as much imformation from the card as possible, like the UID, CRC etc.Next question, about just reading the card(not involve writhing or other function), which command should i use? After sending a command , according the datasheet of st25r3917, i should reading the fifo output as long as i can ,right? Thanks for taking time to read my questions.

So here Usart1 is shared in the code generated though we have defined in the CM7 and CM4 main.c files:UART_HandleTypeDef huart1;The uart is setup in the CM4 main:static void MX_USART1_UART_Init(void) {   /* USER CODE BEGIN USART1_Init 0 */   /* USER CODE END USART1_Init 0 */   /* USER CODE BEGIN USART1_Init 1 */   /* USER CODE END USART1_Init 1 */ huart1.Instance = USART1; huart1.Init.BaudRate = 115200; huart1.Init.WordLength = UART_WORDLENGTH_8B; huart1.Init.StopBits = UART_STOPBITS_1; huart1.Init.Parity = UART_PARITY_NONE; huart1.Init.Mode = UART_MODE_TX_RX; huart1.Init.HwFlowCtl = UART_HWCONTROL_NONE; huart1.Init.OverSampling = UART_OVERSAMPLING_16; huart1.Init.OneBitSampling = UART_ONE_BIT_SAMPLE_DISABLE; huart1.Init.ClockPrescaler = UART_PRESCALER_DIV1; huart1.AdvancedInit.AdvFeatureInit = UART_ADVFEATURE_NO_INIT; if (HAL_UART_Init(&huart1) != HAL_OK) { Error_Handler(); } if (HAL_UARTEx_SetTxFifoThreshold(&huart1, UART_TXFIFO_TH

I am currently using:STM32CubeIde 1.8.0STM32F7 1.16.2Touchgfx 4.18I am trying to upgrade Touchgfx 4.18 to 4.21.3. I know I have to update and regenerate the code from STM32CubeIde and from Touchgfx Designer. Howerver once I regenerate the code form STM32CubeIde I can no longer open the .application.touchgfx file. As this error appears: The steps I have followed are:Open the .touchgfx with the designer and upgrade to 4.23. Modify code that has incompatibilities. (I am able to run the simulator)Open .ioc file and I can see that X-CUBE-touchgfx is already pointing to version 4.21.3Regenerate codeI can no longer open the .touchgfx file with 4.23.3Second attemp:Open .ioc and change X-CUBE-touchgfx version to 4.23.3Click the try and accept buttonRegenerate codeI open the .touchgfx with the designer.The update popup appears and I accept The update process failt with the same message and I can no longer open the file

I cannot get the Phy_802_15_4_Cli example project working on our custom board (as part of certification). Seems like there is something wrong with the CM0 / CPU2 core, but I have no idea what the return codes mean.Only things I have changed in the example project are:UART parametersUsing LPUART1 as CLI interface insteadEnabled the relevant clocksCFG_DEBUG_TRACE = 0 CFG_FULL_LOW_POWER = 0CFG_LPM_SUPPORTED = 0CFG_LED_SUPPORTED = 0CFG_BUTTON_SUPPORTED = 0Changed the various GPIO pin mappingsGPIO_TX_PINGPIO_HARD_FAULT_PINGPIO_MCO_PINI need to get this to work with CubeMonitorRF, but it is also running into the same issues.================================= (STM32WB55) RF 802_15_4 LLDs test ================================= Trace is de-activated M0 FW Type : 802.15.4 and radio PHY validation CLI (v1.16.0) for Target WB55 802.15.4 driver version : v2.2.0 HW/system info : CUT 2.1 - Dev ID 0x00000495 - Package info 0x0A - UID64 0x0186C461 0x0080E126 802.15.4 valid cli > InitLLD Execute co