Solved

To whom it may concern: I am looking at your STEVAL-IPFC12C1 evaluation board schematic and there is a part that doesn't make sense to me. Why would "GND_BRG_SW" be connected to V_INPUT? Are you not connecting low voltage line to a high voltage line?  

Hello,   In the reference manual rm0481 (stm32h562) in chapters 7.11.38 and 7.11.51 it is stated that EDATAx_STRT Bits do not have any hardware effect. Can I assume that the corresponding bits in FLASH_EDATAxR_CUR are set from option bits only? In that case what is purpose of these bits in FLASH_EDATAxR_PRG? Are rhey also set from option bytes? What about the EDATAx_EN bit in FLASH_EDATAxR_PRG? Here the documentation is NOT stating that there is NO hardware effect. Is this correct? If yes, where does the actual setting of EDATAx_EN in FLASH_EDATAxR_CUR come from? By the way in Table 51 there is an DATA_EN1 bit in FLASH_EDATA2R option bytes. May I assume that this is a documentation error and it should in fact be DATA_EN2   Thank you  

Hi,I have derived this code from the ST25NFCLib, and the software works correctly when interfacing with the NUCLEO-L476RG board.However, when I connect the same setup to my proto board, I observe a difference during the following I2C transaction.During the initialization process, the master sends command 0xDF (Measure Power Supply) and then waits for the IRQ signal.In the working setup, the IRQ status registers (1Ah–1Dh) return the values:00, 80, 00, 00Whereas in the non-working setup, the IRQ status registers return:00, 00, 00, 00I am not sure why the IRQ response is different in the proto board setup.Please note the following:Both the working and non-working setups use the same ST25R3918 daughter board.Both setups use the same interface signals: 3.3V, GND, IRQ, SCL, and SDA.The I2C communication speed is identical on both setups.I am attaching the I2C transaction screenshots for reference:The upper transaction belongs to the non-working setup.The lower transaction belongs to the work

Hi ST Community, I am working on STM32H563 with external SDRAM connected through FMC. I am trying to use: heap in SDRAM global variables in SDRAM execution/data access from SDRAM DCACHE enabled Current SDRAM mapping: 0xC0000000 I noticed that in STM32F7/H7 examples there is support for: HAL_REMAPMEMORY_FMC_SDRAM() which remaps FMC SDRAM memory regions internally. I found this in STM32F7 HAL: __HAL_SYSCFG_REMAPMEMORY_FMC_SDRAM() But on STM32H563 I cannot find any equivalent remap mechanism or SYSCFG macro. My questions are: Is there any equivalent SDRAM remap functionality available on STM32H563 / STM32H5? Is SDRAM fixed permanently at 0xC0000000 on STM32H5 architecture? Does STM32H5 treat SDRAM at 0xC0000000 differently regarding: DCACHE burst accesses MPU memory attributes speculative accesses Are there any special MPU/DCACHE recommendations for using: malloc()/calloc() heap in SDRAM .bss/.data sections in SDRAM execution from SDRAM Current observations: SDRAM works correct

Hi, I'm using the STM32WBA54KG microcontroller to comunicate by BLE. In STM32CubeMX (v6.13.0), I have actived the STM32_WPAN packet and the configuration "USE_TEMPERATURE_BASED_RADIO_CALIBRATION" is "YES".I need to read the Vcore channel to know if the battery is low. How can I do it? Thanks.

Hi ST community i just searched the GUI for EV-VNF9Q20F but could not find it. Please tell us where can i get suitable GUI. and also i'm really glad if you could check the availability of SPC582B against EV-VNF9Q20F.

(and why is this a problem?)It looks like the backup ram can not be called through unaligned access on my STM32U585. The mighty internet says that this should not be completely unexpected since it is basically a peripheral and no standard Ram.I have set up the BKPSRAM in the linker file like this:#include "partition.h" /* Entry Point */ ENTRY(Reset_Handler) /* Highest address of the user mode stack */ _estack = ORIGIN(RAM) + LENGTH(RAM); /* end of "RAM" Ram type memory */ _Min_Heap_Size = 0x000 ; /* required amount of heap */ _Min_Stack_Size = 0x800 ; /* required amount of stack */ /* Memories definition */ MEMORY { BKPSRAM (xrw) : ORIGIN = 0x40036400, LENGTH = 2K SRAM4 (xrw) : ORIGIN = 0x28000000, LENGTH = 16K RAM (xrw) : ORIGIN = 0x20000000, LENGTH = NON_SEC_RAM_SIZE /* Secure is using end RAM3 (64k). Actual start is 0x20000000 and actual length is 768K */ FLASH (rx) : ORIGIN = 0x8000000 + APP_SLOT0_NON_SEC_APP_OFFSET, LENGTH = NON_SEC_APP_SIZE /* Memory is divided. Actual st

I am currently working on a resolver ad2s1210. I have selected the required pins generated the code and entered my code and now it does not seems to be running. As the screen shows this Kindly let me know whats seems to be the issue here and how to rectify it.

Hello ST TeamI am using the ST25R3911B-DISCO board with an ST25DV16KC tag.I am trying to communicate with the tag directly from Python using the ST25R3911DISCOComm.dll from STSW-ST25R001.My setup is:ST25R3911B-DISCOST25DV16KCWindows PCPython 3.13ctypesThe DLL loads successfully.Reader connection works correctly.RF initialization works correctly.These APIs return success:rfalInitializeiso14443aInitrfalFieldOnAndStarGTcheckConnectionThe ST GUI software works correctly and can:detect the tagselect the tagread UIDread tag dataFrom Python I cannot:detect the tagselect the tagread UIDread memoryThe DLL exports these APIs:iso14443aSelectiso14443aRATSiso14443aPPStxrxBytesnfcTxNBytesnfcRxNBytesrfalStartTransceiverfalTransceiveBlockingTxrfalTransceiveBlockingRxrfalTransceiveBlockingTxRxrfalISO14443ATransceiveShortFramerfalISO14443ATransceiveAnticollisionFramerfalIsoDepInitializerfalIsoDepStartApduTransceivepollInterruptObserved issues:iso14443aSelect causes access violation.t2tRead4Pages returns

Hello,In this file, the line:USBx_HC((uint32_t)ch_num)->HCSPLT |= USB_OTG_HCSPLT_XACTPOS_Pos;wrongly alters bits 1 to 3 of register HCSPLTThat can be fixed simply by removing this line, since middle payload is encoded by bits 00 in the XACTPOS field. 

Hello, I purchased an STLINK-V3PWR from Mouser. When I tried to use it, STM32CubeIDE 2.1.1 suggested updating the firmware. This failed, and the STLINK-V3PWR appears to be unusable (bricked). What can I do? Return the device for a refund/replacement? Or is there a way to re-flash the firmware using an STLINK-V3SET? If it is possible to restore the firmware by re-flashing it, where can I find the correct firmware? Kind regards, Jack.

Hello everyone,We are currently designing a decentralized Battery Management System (BMS) node for our Formula SAE electric car. We selected the L99BM114 due to its robustness in automotive environments and high measurement accuracy.Our architecture requires this specific node to monitor a 5-series (5S) cell module. Since the L99BM114 supports up to 14 series cells, we will have 9 unused channels.While reviewing Section 6.8 of the datasheet (Unmounted cells), the exact hardware implementation for our case felt a bit ambiguous. We want to ensure our schematic doesn't trigger false internal diagnostics, such as Cell Open Wire or Balancing Short/Open.Could anyone clarify the recommended wiring for the unused pins in a 5S configuration? Specifically:Voltage Sense Pins (C6 to C14): Should all these unused inputs be shorted together and tied to the highest active potential (C5)?Balancing Pins (S and B) & Filtering: How exactly should we handle the external filtering resistors (RLPF) and

Hi !I've using TouchGFX Designer for a while, only using Simulator project (which Board setting is PC) for sfx evaluation and learning. And I wanna try to flash my previous project running on a real microcontroller board like F429 discovery board.Here's my question: How to migrate my previous PC Simulator project to new CubeMX project based on real board project?I tried to find related settings in TouchGFX but failed. Is it the only way to migrate my previous ui into new project by doing all the steps in the new TouchGFX project？Thanks !

Hi,I created a project in STM32CubeMX 6.17.0 targeting the NUCLEO-G491RE and successfully generated the code. I then imported the project into STM32CubeIDE 2.1.1 and as far as I can tell it looks ok. The only apparent issue was that when I clicked on the .ioc file I thought that the STM32CubeMX project was supposed to open inside STM32CubeIDE but instead I get an error saying:So that's one issue. But when I come to build the project in STM32CubeIDE there is no Build All (CMD+B) option available, or indeed any other build options available.This is the folder structure:What is missing from this workflow to create a project that can be built in STM32CubeIDE please?Kind regards,Al    

Good afternoon,First post here, so aologies for any ignorance.I am trying to combine the subghz radio feature of WL55JC1 and the ST60 high frequency communication Full Duplex UART bridge.Ideally, I would be switching between these two functions.I have ported the ST60 example to the WL55JC1 dev board, and can get both running independently.But my problems arise because the subghz radio example uses the STM32 Sequencer utility, while the ST60 doesn't.When I try to integrate the sequencer into the ST60 code, it seems like the I2C comm/config channel for ST60 stops working.Does anyone have any guidance/direction in this area?Appreciate your time.

 Hi everyone,I am working on an STM32H523 MCU and I have recently observed some strange behavior regarding the PB14 and PC9 pins. I have the following setup:PB14 is configured as input (I use this for the TIM2_CH2 alternate function, but this does not affect the issue) and is externally pulled up using a 10kOhm resistor.The PC9 pin is configured as output.When the PC9 pin is unset, the PB14 is 3.3V, as expected. But when setting the PC9 pin, the voltage on PB14 drops to only 1.13V.  These pins are otherwise not connected, so 2 seemingly unrelated pins seem to have some dependency within the stm32h523 chip.  Another test was performed by configuring PB14 as output (without pullup). Now, when PC9 is unset and PB14 is set, the voltage on PB14 is 3.30V. When setting PC9, the PB14 voltage drops to 3.26V, which seems related... To make sure it is not caused by our own hardware, we did the same test on a STM32H5 Nucleo-144 board (MB1404C), this development b

I am using STM32CubeMX 6.16.1 to configure a project for STM32F415.I use the FATFS on SD card and set it up as:According to FATFS documentation (https://elm-chan.org/fsw/ff/doc/config.html#lfn_unicode), the data type TCHAR should translate to char in this case. However, CubeMX generates Middlewares/Third_Party/FatFs/src/ff.h in which TCHAR is defined as WCHAR, i.e. a 16-bit type:The _STRF_ENCODE is correctly defined as 3 in FATFS/Target/ffconf.h, which corresponds to UTF-8:Is this a bug? How can I ensure that UTF-8 uses the 8-bit data type correctly?

Flint is an accelerometer system in the Smithsonian Museum.  It is a MKI109 and MKI 210 pair.  It has been in place for about three years after a recommendation from your David Reynoldson, who is a really great guy and helps a lot. We have about six to ten such systems that were used and have now been pulled, but old Flint just keeps on working. It has a partially bespoke C# program.  The PI designed and manufactured some small boxes. But to hold the 210 onto the 109 I used a rubber band before it was boxed.  It worked well for three years and then broke. Flint had some minor problems:1. You have to use a USB Managed HUB to turn the device on and off if you reboot the computer.  The HUB is as expensive as the accelerometer pair.  Or you unplug the computer, the device does not reset to home if the computer is switched off - major design flaw in a complex system.2. You have to put a watcher program to monitor the accelerometer program that ca

I recently bought a STM32F446 64 pin chip and wired it up. The following circuit is made: I've installed 0.1uF capacitors between two power pins, and two I've not (It's difficult to do so)   it's consuming around 20 to 30 mA Pin 30 shows 1.132 volts (4.7uF cap is installed) voltage 3.298 v oscillator is working fine I tried bypassing the 15uH inductor as I thought that is too much, but neither way works The chip is perfectly soldered, checked for resistances multiple times   Tried uploading code from both usb to ttl converter and STM programmer from Nucleo f072rb board   all the wiring is correct according to me checked multiple times, but when I upload the code using arduino ide, I get this issue: Sketch uses 16576 bytes (3%) of program storage space. Maximum is 524288 bytes.Global variables use 1212 bytes (0%) of dynamic memory, leaving 129860 bytes for local variables. Maximum is 131072 bytes.NODE_F446RE not found. Please ensure the device is correctly connected.Faile

Hi,I'm having trouble getting my ST-Link V2 dongle to be recognized by Cube Programmer. It is recognized by Windows 10 in the device manager, I have been able to update the firmware, and I can get it to load in STM32 ST-Link Utility, but that program doesn't support the .elf file format I need.When I launch Cube Programmer, it does recognize something as shown by the voltage and the firmware (image attached), but when I click the refresh button next to the serial number it says "No ST-Link detected."I've read from others that there are a lot knockoffs of these dongles floating around that don't work anymore. That might be the problem with mine (this is the second one I've bought and tried). Can anyone point me to a good source to buy a legit one? In the products page, I've only seen the bigger ST-Link V2 unit and the smaller USB-C V3 unit, but not the V2 Dongle.I'm trying to flash a board for an Atari 2600 homebrew game I made and I attached a diagram of what the instructions show

Hello, I am designing a USB-C power sink using the TCPP01-M12 and STM32G071CBT6 (UCPD peripheral). The connector is a Molex 2171790001 receptacle. I have two separate issues and would appreciate guidance on both. --- ISSUE 1: No power at all with Type-C to Type-C cable When I connect a USB-C to USB-C cable between my board and a USB-C charger, the board does not power on. However, when I use a Type-A to Type-C cable (from a USB-A charger), the board powers up fine. Hardware setup:- J1: Molex 2171790001 (CC1 on A5, CC2 on B5 — both routed)- IC1: TCPP01-M12 (CC1C and CC2C connected to J1; CC1 and CC2 connected to STM32 PA8/PB15)- IC2: STM32G071CBT6 (UCPD1_CC1 = PA8, UCPD1_CC2 = PB15)- TCPP01 VCC (pin 12) is driven by STM32 PB12 GPIO (TCPP01_PWR net)- TCPP01 DB/ (pin 10) is connected to STM32 PB11 GPIO- C1 and C2 (330 pF each) are now soldered on CC1c and CC2c lines to GND- R8 and R9 (0 Ω, intended to connect UCPD_DBCC1/PA9 and UCPD_DBCC2/PA10 to GND) are NOT yet soldered — so DBCC1 and D

Environment:MCU: STM32WB09KE, Cortex-M0+Board: NUCLEO-WB09KEIDE: STM32CubeIDE 2.1.0STM32CubeIDE Build: 27993_20260219_1630 (UTC)STM32CubeMX Version: 6.17.0OS: Windows 11 HomeFirmware package: STM32Cube_FW_WB0_V1.4.0Example project used: BLE_DirectionFinding_Central_LocatorSetup:I am using the STM32WB09 Direction Finding example project on the NUCLEO-WB09KE board.The project is based on ST’s provided STM32CubeWB0 package and the NUCLEO-WB09KE board files available here: https://www.st.com/en/evaluation-tools/nucleo-wb09ke.html#cad-resources The goal is to use two GPIO pins as antenna-switching control signals for AoA direction finding:RADIO_ANTENNA_ID_0 -> PB0RADIO_ANTENNA_ID_1 -> PB1PB0 works correctly. When configured as RADIO_ANTENNA_ID_0, I can observe the expected switching signal on a Saleae logic analyzer. Screenshot provided here: https://imgur.com/a/uk8L8tq Not much here, but zooming in into each pulse shows rapid switching- you can trust me. PB1

When U-boot is going to startup at the entry point address = 0x84000000, then this happens.IAC ID 137 is RISAF4 - DDR-SDRAM.SERC ID 32 is USART2.I don't know why USART2 seems to write at the Optee address region (0x82000000 - 0x83FFFFFF) and it all lands on 0x83FFFF80. The optee address region is secure and USART2 seems to write on this address.I have attached my complete device tree and I wonder if the ST dev team can help me to find why USART2 is trying to access 0x83FFFF80 in DDR-SDRAM?My processor is STM32MP257FAK.Note 1: The difference between 0x84000000 and 0x83FFFF80 is 128, e.g one byte. So I guess that something is shifted wrongly here?Note 2: I'm using LDO2 as VDDIO_SDCARD and BUCK7 for 3v3 for VDD_SDCARD. Because my PMIC is the STPMIC25A and not STPMIC25D. F/TC:0 0 pmic_get_voltage:192 vddgpu_pmic: get voltage: 800000 uV D/TC:0 0 set_opp:67 set clock to 800000kHz I/TC: Primary CPU switching to normal world boot INFO: BL31: Preparing for EL3

I normally use 1.19.0 because of the MX sillyness...When compiling you get warnings - let's take stm32h723xx.h as an example.Line 2516 is - #define GPIOB ((GPIO_TypeDef *) GPIOB_BASE)In 1.19.0 you get a warning - Description Resource Path Location Type(near initialization for 'output_port[9]') stm32h723xx.h /Cube-Wave-723/Drivers/CMSIS/Device/ST/STM32H7xx/Include line 2516 C/C++ Problem In 2.1.1 you get an error - Description Resource Path Location Typeinitialization of 'long unsigned int' from 'GPIO_TypeDef *' makes integer from pointer without a cast [-Wint-conversion] stm32h723xx.h /Cube-Wave-723/Drivers/CMSIS/Device/ST/STM32H7xx/Include line 2516 C/C++ ProblemAs it is actually your generated code I do wonder how this has slipped through your 'testing' process.I was awaiting a news item reporting on ST employees being treated for burns as their ears caught fire after I found this ;) Andy.   

I have a Nucleo-WL33CC1 board which has been working fine, but after starting to work on a DEEP SLEEP implementation I can not connect any longer using SWD neither through Crossworks IDE nor CubeProgrammer. Any possibility to unbrick the board?