Solved

Hello, I have a difficulty using MEMS studio. It says "board not identified" without any more hint what could be wrong. I use STM32G474 Nucleo board with IKS01A3 on Linux (Ubuntu).I have all firmware up to date, all pins mapped correctly according to documentation but still didn't manage to establish communication. From what I saw there is some communication on UART. I am able to read the sensors from the MEMS board using my code. I can compile it and the MEMS board works... But not with the MEMS studio. Weird.  Attaching the .ioc for more context.Thank you for any feedback.  

Hi,I have created a simple GUI using TouchGFX Designer for the STM32N6570-DK, generated the code, built it, and ran it. Everything works fine.Then I noticed that the TouchGFX_Framebuffer is located in internal SRAM. However, I plan to use that SRAM for the NPU and other purposes. So, I moved the framebuffer to PSRAM, and now the GUI becomes partially corrupted after pressing buttons or sliding.It seems that additional adjustments are needed when using the framebuffer in PSRAM. Could that be the case?Below is a snippet from *.ld: BufferSection (NOLOAD) : { *(TouchGFX_Framebuffer TouchGFX_Framebuffer.*) *(.gnu.linkonce.r.*) . = ALIGN(0x8); } >PSRAM /*FB_RAM*/ UncachedSection (NOLOAD) : { *(Nemagfx_Memory_Pool_Buffer Nemagfx_Memory_Pool_Buffer.*) *(.gnu.linkonce.r.*) . = ALIGN(0x8); *(Nemagfx_Stencil_Buffer Nemagfx_Stencil_Buffer.*) *(.gnu.linkonce.r.*) . = ALIGN(0x8); } >PSRAM /*CMDLIST_RAM*/ 

Hi, I have generated code for HSO on a workbench as recommended by the release note. I need to view definitions of following functions: But not able to view the definitions of these functions. Could you please help me to open these functions? As I need to port this code into STM32F4 Series code. Thanks, and Regards,Rahul D

Hi, everyone  This TDA2030A amplifier module use dual power supply ±12 Voltage See attached image file  Thanks  

Hello ST Community, I am encountering a persistent issue while attempting to program a new password for the user memory in AREA1 of an ST25TVxxXC NFC tag using an ST25R200 reader and the RFAL library. I have followed below procedures for setting the password:Get a 2-byte Random Number from the tag using rfalST25xVPollerGetRandomNumber() api.XOR the desired 64-bit password with the obtained Random Number, as per table 30 of ST25TV02KC datasheetUse the PresentPassword command to enter secure session mode with default password {0,0,0,0,0,0,0,0} using rfalST25xVPollerPresentPassword() api.Use the WritePassword command to set the new password using rfalST25xVPollerWritePassword() api.I have written a local function to perform XOR operation and confirmed that the XORed output matches as per below table of ST25TV02KC datasheet: Below is the code snippet for the same:platformLog("\r\nUSE CASE : Writing password.\r\n"); uint8_t rnd_num[ 1 + 2 + RFAL_CRC_LEN ]; /* Response Flags

I am using CAN on an STM32F042F6P6. I want to detect if an attached CAN transceiver is working or not. While there is no guarantee that there are other CAN nodes present on the bus, a 120 ohm termination resistor is always present. My original plan was to try transmitting something on the bus and checking for errors. If I only get an acknowledgement error, then the transceiver is probably OK. If I get a bit error, bit stuffing error or a bus off error, something is wrong with the transceiver. However, when I tried to put this in practice, I found that the STM was never throwing any errors. If I removed my transceiver and reattached it to simulate a failure, I found that although CAN transmission stopped, no errors were triggered and the hcan was stuck in HAL_CAN_STATE_LISTENING state. What could be going wrong here?   All parameters except Automatic Retransmission have been disabled in the ioc file. Global interrupt for CAN has been enabled. Attached code for reference. #incl

Hi,I am working on a project, where I want to maximize the speed when using the mailbox with the ST25xV commands.I use a ST25R3916B Reader and a ST25DV04K Tag.The data exchange process in my application looks like this:-(fast)write command-(fast)read dyn config (polling: wait until message owner has changed)-(fast)read responseI measure the time over the whole exchange and when I use the "fast" commands it somehow gets slower. I have read this forum post about the differences of the normal and "fast" commands. There it is mentioned that the fast commands double the response data rate. So I would expect at least a slight increase in speed and not it being slower. Can anybody explain this behaviour?Also: any recommendations on how to further increase speed are highly welcome.Rgds,Jonas 

what`s wrong?my spc5studio shows 

I have a flex button. I have an image for released and an image for pressed.The released image contains a drop shadow. The released image does not, but has a transparent boundary so the dimensions match.I want the clickable area to be the button image excluding the shadow and transparent edge. I want to set this clickable area as a rectangle.How do I do this?

Hi ,I see that the bandwidth of IIS2DLPC is 3200 Hz for low power mode 1 according to the datasheet (page 22 ). Also it mentions that the maximum ODR is 200 Hz for this mode. This looks contradictory to me as 3200Hz bandwidth won't be compatible with 200Hz output data rate. Could you please explain what exactly does this mean?Best regards,Kev

Hello,​I've been looking for a debugger to debug and program an SPC58xx MCU and I've found you offer both the new Stellarlink and the SPC5-UDESKT. I understand the SPC5-UDESKT requires a licence to be used with the Universal Debug Engine (UDE) which are available as either a year licence or a one-time purchase. I was wondering if I would also need one of these licences to use the Stellarlink with the UDE/SPC5Studio? It looks like the Stellarlink has more features supporting your Stellar Automotive line so would you recommend this for a new debugger/programmer purchase over the SPC5-UDESKT?Many thanks,Owen

In my project STM32WB55 uC is used and FW is generated by STM32CubeMX.Library (STM32Cube_FW_WB_V1.22.0) and BLE binary (stm32wb5x_BLE_Stack_full_fw.bin) are both version 1.20.My goal is to reboot only BLE stack on CPU2 without reset of CPU1.On community it is written in several places that aci_hal_stack_reset(or hci_reset?) can perform reset of the stack, but that it is necessary to do again full initialization of BLE stack: SHCI_C2_BLE_Init (or SHCI_C2_BLE_Reinit?), aci_gatt_init...I tried several ways to do that, but I was not successful. For example in debug some combinations of this functions works, but as soon I utilize Low Power mode, BLE will not start!Also I did not found any example code and/or exact procedure how to do that!Does someone know how exactly BLE reset is done and later reinitialized (documentation or source code)?

Hello,I am working on the STM32F103xx. I need to read out the 96 bit UDID (unique device ID) of the devices during production. Is there any way of reading this out from the serial bootloader on UART1 or through the SWD interface? I searched the AN3155 and AN2606 but could not find any details.I do not want to flash a temporary firmware just to read it out and then overwrite it again. Nontheless it no other solution is possible I guess its an ugly workaround. It needs to be automated. So using CubIDE is not possible. Thanks

Hi,I made a custom PCB with a STM32WBA54CGU6 to act as a Bluetooth LE Audio transmitter. This was going to be first "real" PCB since before I have only made much simpler designs (I know I was very ambitious). For the HSE, I used this document to decide on the NX1612SA crystal oscillator. The problem I am facing is that I can't seem to get passed the SystemClock_Config() function call, more specifically, the HAL_RCC_OscConfig() function returns HAL_TIMEOUT in this part indicating that the HSE is not getting ready. /* Wait till HSE is ready */ while (READ_BIT(RCC->CR, RCC_CR_HSERDY) == 0U) { if ((HAL_GetTick() - tickstart) > HSE_TIMEOUT_VALUE) { return HAL_TIMEOUT; } } } I know I have to trim the clock using the registers on the STM32 but I was unable to find how the value in the register maps to a specific capacitance. This led me trying every single possible value (0-63) but that made no difference. I have already resoldered a new crysta

I'm trying to use the LPBAM feature on the STM32U5 to perform I2C communication during STOP2 mode.I followed the official STM32 LPBAM example and implemented my code accordingly.Here is what I'm attempting:Use LPTIM to generate a PWM signal during STOP2 mode.On each rising edge of the PWM signal, trigger an I2C transmit operation via LPBAM.The I2C communication is transmit-only (no receiving).I confirmed that the PWM signal is working correctly using an LED.However, the LCD connected via I2C does not display any data, as if the I2C transmission never occurs.What could be the possible reason why the I2C data is not transmitted even though the PWM trigger is working?/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 STMicroelectronics. * All rights reserved. *

I'm using a VL53L4CD as a proximity switch but with a user selectable threshold. I began developing on XNUCLEO-53L4A1 on a NUCLEO-F401 but have since migrated to my own pcb using STM32C071. I am having difficulty with poor status reports from the ToF device at distances above about 300mm on my own board. Under 300mm I get a status of 0 but anything above that and it quickly deteriorates to 1, 2 or 4 and the distance becomes very erratic.Thinking that it was down to the specifics of the pcb I reverted to the F401/XNUCLEO arrangement and I now see it's not that much better and certainly nowhere near 1.2m. I can get to about 500mm with status 0 but much beyond that leads to a status of 1 or 2 and eventually 4. My maximum range is 500mm so it's barely okay on the F401 but not on my own pcb.I'm using the standard API with some mods which don't amount to very much (threshold hysteresis mainly). It doesn't seem to matter whether the (standard) cover glass is fitted or not. The application is

Hello I suspect I'm about to make a dumb question but I've been strugling for the past 2 days trying to just make a simple reading of the accelerometer. Just that get those values out of X, Y and Z axis...I can get the correct responses out of the WHO_AM_I register and the status from the other setup registers. No matter what I do, the readings from registers 0x28~0x2D keep returning zero. I need help to understand what I may be doing wrong...Code below:  #include <Arduino.h>#include <Wire.h>#define i2c_sda 8#define i2c_scl 9#define x_l 0x28#define x_h 0x29#define y_l 0x2A#define y_h 0x2B#define z_l 0x2C#define z_h 0x2Duint8_t addr;uint8_t outx_l;uint8_t outx_h;uint8_t outy_l;uint8_t outy_h;uint8_t outz_l;uint8_t outz_h;uint16_t X;uint16_t Y;uint16_t Z;uint16_t msb;uint8_t data;void setup() {  // put your setup code here, to run once:  Serial.begin(115200);  Serial.println("\nI2C Scanner");  delay(1000);  Serial.println ("I2C scanner.

Hello,I’ve been working on implementing a SWIM master using an STM8 device to interface with a STM8S105K6 target. This is part of a tester software project that was previously using the ST7 debug protocol and is now being ported to the STM8.I’ve followed the entry sequence described in UM0470, and I believe the waveforms match what's expected. Attached below is a screenshot from the oscilloscope:Yellow trace = RESET pinGreen trace = SWIM pinAs you can see:A long low pulse initiates the SWIM entry sequence.Followed by 4 x 1kHz pulses and 4 x 2kHz pulses.Then I set the SWIM line high and switch it to input mode to await the slave response (Step 4 per UM0470).However, no response is received from the target. The line stays high and never toggles.Below is the relevant code section (i use raisonance ride7 dev environment): unsigned char swim_entry(void){unsigned long a;unsigned char m = 1;char buf[1];swim_config(0);ADC_disable;RES(1);SWIM(1);delay_ms(10);RES(0);delay_ms(10);SWIM(0);del

Hello! I am trying to trigger an ADC sample to write to DMA via a timer and trigger a green LED on PB0 after every sample so I can use an oscilloscope to verify the sampling speed. However, I believe after trying to debug as best I can, I do not have the correct configuration for the ADC or there is a problem with the DMA requests. I have included all of the user code that I have placed inside the main.c file at the bottom of this post. I have also included a photo of my ADC settings. I wasn't able to include it but I have enabled the NVIC interrupts by clicking the check boxes. I can successfully build and flash the code to the device, that is the code I shared. I do not get back any errors during building, its just the LED doesn't flash. I have ensured the LED is working by just placing a simple toggle code in the while statement and running that. #define BUFFER_SIZE 2 /* USER CODE BEGIN 2 */ HAL_ADCEx_Calibration_Start(&hadc1, ADC_CALIB_OFFSET_LINEARITY, ADC_SINGLE_ENDED);

Hello! I'm trying to flash wireless stack into the STM32WB55 USB Dongle.I've successfully upgraded FUS to version 2.0.0.3.But now i cannot flash wireless binaries. Each time I try to do this, i'm getting the message, that image is downloaded, verified. Than that image found and authentic, but there's no space.ERROR: FUS_STATE_IMG_NO_SPACE.What am I doing wrong?My logs from CubeProgrammer are listed below... 19:56:30 : Old Firmware delete ...19:56:30 : Warning: Option Byte: nSWboot0, value: 0x0, was not modified.19:56:30 : Warning: Option Byte: nboot0, value: 0x1, was not modified.19:56:30 : Warning: Option Byte: nboot1, value: 0x1, was not modified.19:56:30 : Warning: Option Bytes are unchanged, Data won't be downloaded19:56:30 : Time elapsed during option Bytes configuration: 00:00:00.00019:56:30 : Succeeded to set nSWboot0=0 nboot1=1 nboot0=119:56:30 : Memory Programming ...19:56:30 : Opening and parsing file: 0x495_FUS_Operator.bin19:56:30 : File : 0x495_FUS_Operator.bin19

Hi, I'm wondering if there are any recommendations/guidelines when trying to measure power consumption on the Nucleo-N657X0-Q when running a neural network model, both with NPU acceleration and without on the CPU for comparison. I have access to both a X-Nucleo-LPM01A power shield and a STLINK-V3PWR and do not know which one to choose. Are both options rated for enough power to measure the board? And does any of the two options require removing components, as the board is borrowed so I would prefer a non-invasive solution. Thanks in advance!

I've requirement of reading 100 samples of ADC data using DMA whenever it's needed in regular mode and I see the read buffer is not having right values and also HAL_ADC_ConvCpltCallback is not hitting.But same if I try just with one sample data is proper and HAL_ADC_ConvCpltCallback is hitting but when I retrigger ADC_DMA_READ I see HAL_BUSY.I'm using NUCLEO-545REQ board /*GLOBAL VARIABLE*/ #define ADC_CONVERTED_DATA_BUFFER_SIZE ((uint32_t) 100) /* Size of array aADCxConvertedData[] */ /* Variable containing ADC conversions data */ uint32_t aADCxConvertedData[ADC_CONVERTED_DATA_BUFFER_SIZE]; int isADCFinished = 0; #define VDDA_APPLI (3300UL) uint16_t uhADCxConvertedData_Voltage_mVolt = 0; /* Value of voltage calculated from ADC conversion data (unit: mV) */ /* Init variable out of expected ADC conversion data range */ #define VAR_CONVERTED_DATA_INIT_VALUE (__LL_ADC_DIGITAL_SCALE(ADC1, LL_ADC_RESOLUTION_14B) + 1) /********************************************************************

Hello, Is there any example code available for Multichannel ADC1 in regular DMA mode for NUCLEO545REQ board. 

I didn't change anything in the device tree just compiled the arm-trusted-firmware-v2.4-stm32mp-r2 instead of arm-trusted-firmware-v2.4-stm32mp-r1 and I get the following on UART:PANIC at PC : 0x2ffcfd2bWhat is different between the two versions?

Hello,I am developing a board with the LIS2DUXS12 accelero.During testing after assembly, I saw that there was no reaction to I2C communication. Other devices on the bus work fine, with a logic analyzer I have seen that there is indeed traffic sent to 0x18. I desoldered the component and saw that during assembly, was too little paste on the VDDIO and the SCL pin. I corrected it and resoldered the component and saw there was good contact under the microscope. I have connected the STEVAL$MKI235AA to the pins and that responds correctly.I still see the same behavior, so my first question is this:1. Are VDD and VDDIO completely isolated from each other such that VDD won't internally be connected to VDDIO in the event of a bad connection to VDDIO, the digital interface pins are in danger of being damaged?2. I also am looking for a sanity check of my schematic. I have only 1uF + 100nF on the supply as 10uF seems extremely overkill for pulling <50uA and adds to the power rail capacita