Solved

typedef struct{ uint8_t data[10]; uint8_t time[10]; uint8_t description[10];} FileString;FileString Datalogger_FileString;Datalogger_FileString.data[0]=0; //ERROR: expected '=', ',', ';', 'asm' or '__attribute__' before '.' tokenWhat do I should do to access the array inside a struct? Thank you

My UART example works very well.  But, I want to do with the UART interrupt.  Currently it does not work because it always jumps to an infinite loop in the start up assembly code.Infinite_Loop:  // startup_stm32f411retx.s b Infinite_LoopHere is my source code. It works great without USART receive interrupt enabled.  USART2_IRQHandler is never executed. I have put a breakpoint inside it. Instead, it always jumps to the Infinit_loop line. What did I do wrong? Why your HAL / LL examples work?  I looked into the HAL / LL code.  It is very similar to my source code.Thank you for any help you can provide.Michael//#include "my_stm32f4_uart_driver.h" // No NVIC_SetPriority, NVIC_EnableIRQ#include <ctype.h>#include "string.h"#include "stm32f4xx.h" // I need to use this library for NVIC_SetPriority, NVIC_EnableIRQint main(void){RCC->AHB1ENR |= 1; //Enable GPIOA clockRC

..

I just created a project in STMCubeIDE for STM32MP157A-DK1 and am trying to run MCU debugging in ENGINEERING MODE and PRODUCTION MODE. I use an ST-LINK wire and an Ethernet Over USB connection. SSH and the UART command line work well. In engineering mode, I get the hardware breakpoints error. In production mode, all breakpoints that are set to an infinite loop do not work...this is very strange. What did I miss?

Hi,here I am trying to Communicate with two x-NUCLEO-NFC05A1 Board For P2P Communication.STM32G071RB Nucleo Kit Board using for this Main MCU. Getting the demo.c file from this below LinkConnect two X-NUCLEO-NFC05A1 with Peer to Peer (p2p) connection. (st.com)using this Example demo.c. i can read Passive NFCA type tags . But Not to see any NFCF Passive P2P device found.Here our application is data File Transfer from one Controller to Another by NFC P2P Mode.  Pls Give the guidance how to data Exchange from one to another.? 

MX_RTC_Init(); if (HAL_RTCEx_BKUPRead(&hrtc, RTC_BKP_DRX) != 0X2233) { printf(" Set Date and Time \r\n"); SetDateTime(); }void SetDateTime(void) { RTC_TimeTypeDef sTime = { 0 }; RTC_DateTypeDef sDate = { 0 }; /* USER CODE BEGIN Check_RTC_BKUP */ /* USER CODE END Check_RTC_BKUP */ /** Initialize RTC and set the Time and Date*/ sTime.Hours = 0x19; sTime.Minutes = 0x45; sTime.Seconds = 0x30; sTime.DayLightSaving = RTC_DAYLIGHTSAVING_NONE; sTime.StoreOperation = RTC_STOREOPERATION_RESET; if (HAL_RTC_SetTime(&hrtc, &sTime, RTC_FORMAT_BCD) != HAL_OK) { Error_Handler(); } sDate.WeekDay = RTC_WEEKDAY_FRIDAY; sDate.Month = RTC_MONTH_MARCH; sDate.Date = 0x25; sDate.Year = 0x22; if (HAL_RTC_SetDate(&hrtc, &sDate, RTC_FORMAT_BCD) != HAL_OK) { Error_Handler(); } HAL_RTCEx_BKUPWrite(&hrtc, RTC_BKP_DRX, RTC_BKP_DATA);}

The RTC program is tested with LSE

Hello. I work in CubeIDE 1.9.0 with the stm32f429i-disco device. The problem arises about firmware and debugging. I made a simple example to check. During debugging, strange behavior was noticed when executing HAL_Delay (line 95). When executing Step Over on this line, Debug Current Instruction Pointer remains on the same line. If you put a breakpoint on this line and Resume, the LEDs are reset to the initial (off) after each iteration, although they should change their state every 250 ms. Previously, I worked with bootloader on this board. I also noticed that the user USB LED lights up when power is applied in the absence of firmware in the memory of the microcontroller. Keil faced the same problems that were described above. Tell me, please, can this be the result of mechanical damage to the board or is it something else and how to fix it?/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main

Hello everyone,I am trying to upload a program via the Cube Programmer to my STM32f647g_Disco board.When using CubeIDE it works flawlessly, but when I try to flash the HEX files with CubeProgrammer, it is showing the following message: " 18:10:01 : Error: Data mismatch found at address 0x900002F3 (byte = 0x00 instead of 0x04) 18:10:01 : Error: Download verification failed"I think it does not save the new software to the external flash memory of the board.Do you know a workaround for this?In the appendix there are two logs, one from CubeIDE (with functioning flashing), one from cubeProgrammer.Until now, I was using the HEX file that get´s generated in (ProjectName\CubeIDE\Debux\ProjectName.HEX)Do I have to use a different one, or a second one for the external memory?I also noticed that the BIN File (in the same folder directory) has more than two GB. IS that normal?Thanks for the Help!

I'm using the Nucleo-32 on another project and have found the schematics in UM1956 helpful in certain debugging scenarios, as well as a kind of reference design to help me get started on my own board design.

As noted on the documentation the VL53L5CX could integrate a microcontroller with an internal oscillator/PLL clock source. This could have a high frequency value in order to handle the ns-scale timing of the FlightSense technology and the histograms processing.I am investigating the EMI spectrum of a product integrating a VL53L5CX and I should consider all the possible noise contributions.Thank you

..

So the question is: Whats the best way to import an example project into CUBEIDE and have access to the CUBEMX view?Background:I want to use one of the STM32 examples with CUBEIDE. Specifically the example is "LwIP_HTTP_Server_Netconn_RTOS". Anyways I am able to import the project into cube IDE and run the project in the debugger with a couple of really minor fixes. This does not produce the IOC file that can be opened in the CUBEMX view.Thanks!!

We've just changed the way our system is powered: Previously the accelerometer was powered from a 1.8V regulator, now it's powered directly from a 3V coin cell (schematic part attached).With the change, we have started to observe a strange ramping which is visible from about 2V upwards and increases with an increase in VDD. Attached is an image of the current ramping, with VDD set to approx 2.9V. The larger thin spikes belong to a BLE module, the very tiny spikes are all I would expect to see of the accelerometer in operation - in fact that is the case when running at 1.8V.The accelerometer is configured to capture in FIFO mode, the gyro is off. The IRQ is used to notify FIFO events and to flush the buffer. Same ramp is visible, regardless of power mode (ultra low, normal, high-perf). We are only ever capturing at 12.5Hz. No extended functionality is enabled (motion event, etc). We use SPI Mode 1 to communicate with the device, both IRQ pins are connected to our Micro. Is this expected

I've just tried on an 'L031 - after writing LSEDRV to 0b00 (using debugger), I can rewrite it freely to any other value, and the oscillator's behaviour follows the value written.Can ST please comment.JW

I have enabled PA3 as ADC1 channel 15, and for some reason the Clock Configuration view in the Cube IOC Generator is always grayed out.Attached is my IOC file and a screenshot of the issue:

Hi.I need to design a custom board for LoRa 923MHz network.The AN5457 provides the example for 923MHz network. (A.1.6)​I can get output Impedance from this example(AN5457).But I can't find LNA (Differential) Input Impedance for UFBGA73 package @923MHz.​Could you please give me input Impedance data of this package and this frequency?​

Hi Community,While selecting the MCU or board, instead of Board Selector can we select using MCU/MPU Selector? Because I am using STM32F769AI, which is not having any board package to create a touch GFX project. So, how to create a Touch GFX project using STM32CubeIDE? which is not under the board selector?

i'm using the  stm32u5 iot eval board BU585IIO2A and want to use USART3 on Arduino connector CN14i successfully got the PWM working on PIN7 of CN14 but i fail to get anything sent / received on UASRT3 (Pins 1 and 2 of CN14)are there any hints / samples how to get this working ?thx, peter

I assisted to "NFC charging: the tiniest solution for wireless charging" webinar about NFC WLC (NFC specification with energy transmission features). There was a video where it was shown a pair of evaluation boards called WLC-poller (transmitter, using a ST25R3916) and a WLC-listener (receiver, using a ST25DV-I2C. Are that proof of concept boards going to be available to buy?If not, which alternatives are there?I've seen that ANT7-T-25DV64KC could be used for the receiver, but in the information given by ST says that it can be used in conjuntion with board: DEMO-CR95HF-A. The problem is that it's obsolete and impossible to obtain...In our application we want to transfer data bidirectionally and to charge a battery with an ST25 chip in the receiver.

I need to convert STMCubeIDE project to IAR Embedded Workbench. I found here (https://www.st.com/en/embedded-software/stm32-standard-peripheral-libraries.html#products) STM32 Standard Peripheral Libraries, which include templates for also IAR Embedded Workbench. But there is no library for the G0 (STM32G070RB to be exact) processors. Is the file startup_stm32g070rbtx.s for IAR anywhere available, or do I need to create it myself? Or is there even an easier way to import STMCubeIDE project for G0 to IAR Embedded workbench, than to migrate the code to IAR Embedded Workbench as instructed in this video (https://www.youtube.com/watch?v=xtmpmy8t19Q)?

Hello,I am trying to use an LSM6DSOX through SPI communication, but I am having some problems due to the length of the cable. I'm using a cable about 2 m long but the sensor is not working well. I have tried using different LSM6DSOX chips but the result is always the same, sometimes information is lost in the sensor response and other times it generates interference with another sensor that is connected to the same SPI bus (a MAX30003 ECG sensor).I suspect that the problem is caused by the cable length because I have also tried using a shorter cable (about 30 cm) and there is not problem with that configuration. Therefore, I want to know what is the maximum distance supported by the SPI bus to connect this sensor and also what could you suggest me to avoid the communication problems when using a long cable to connect the sensor to the master device.Additional information:I am using a Raspberry Pi 3 model B as master device.The sensor has the suggested configuration with the decoupling

I've planed use UART1 in "only receive" mode and i used all possible UART1_TX pins for another purposes. In that case UART1 config is bocked and user can't config single wire modes, like "only receive" or "single-wire half duplex " (possible thanks RX/TX Swap). There are few workarounds:1) give up UART1 config by cubeMX and write your own code (possible best way)2) prevent that situation by configuring UART first, before blocking UART1_TX pins by other peripherals

Hey,I have been using the x-cube-nfc3 demo for Nucleo-l496ZG 144 pin board along with a CR95HF. In SPI mode I can successfully initialise and read the ID from NFC tags. I attempted to change to UART mode by adding #define ST25R95_INTERFACE_UART 1to platform.h. I also changed the macros in platform.h from huart1 to huart3 because it saved soldering of additional headers. With these modifications the device initialises successfully over UART however I cannot get it to detect any NFC tags. Are there any more modifications needed?