STM32 MCUs

Hi,Within VSCODE terminal my ninja build (from MX cmake project) will run just great.   But in the Winwows CLI I get 'cube-cmake '  is not recognised.....When I add %USERPROFILE%/.vscode/extensions/stmicroelectronics.stm32cube-ide-build-cmake-1.43.0/resources/cube-cmake/win32 to the PATH, windows says ''cube' command is not available in current context'I'm looking for some clues to understand the issue a bit better!Thanks in advance,Nick 

I'm trying to interface a TI ADC with an STM32U575ZI or STMU545RE (same issue on both Nucleo boards).The ADC has a "data ready" pin that needs to trigger a fixed-size transfer of 32bytes over SPI.  Given the overall sampling rate, only a few microseconds are available for overhead.  Seems like a natural fit for the autonomous mode + DMA features on the STM32U micros, but I can't seem to figure out how this is supposed to go together.I can get one transfer going no problem, sometimes two, but something always errors out.  Currently getting a MODF flag, which makes no sense based on the documentation as the NSS system is set to "software" and always at 1.Is there a document describing how the DMA and SPI modules interact under autonomous mode?  I'm clearly missing something important here.  Handshaking, what causes the TSIZE to reload the CTSIZE register, recommended DMA configs + trigger setups, anything?Working on putting together an example for people to disse

Hi, I am facing an issue while connecting to my board using STM32CubeProgrammer and ST-LINK. I would appreciate any help. Board: NUCLEO-F072RBProgrammer: ST-LINK (Onboard)Software: STM32CubeProgrammerConnection: SWDST-LINK Firmware: V2J46M31 Issue Description:STM32CubeProgrammer is unable to detect the target MCU. It shows errors like: Unable to get core ID No STM32 target found ST-LINK error (DEV_CONNECT_ERR) Observed Details: Target voltage showing around 0.29V Connection mode tried: Normal (SWD) Reset mode: Software reset Speed: Reliable Frequency: 4000 kHz Log Messages (Important Parts): Error: Unable to get core ID Error: No STM32 target found! ST-LINK error (DEV_CONNECT_ERR) Error: Problem occurred while trying to connect What I Already Checked: USB cable and port Reinstalled STM32CubeProgrammer ST-LINK firmware upgrade option checked Tried reconnecting multiple times Questions: Is the low target voltage (0.29V) the reason ST-LINK cannot

I'm migrating from Windows to Linux (Ubuntu 22.04) as my main OS, and I'm setting up the STM32CubeIDE for development.  I noticed that the Linux install of STM32CubeIDE (v2.0.0 downloaded from this site) is missing almost all of the ST specific features that make using the IDE worth it for me.  Is there a reason for this?  Is there a way to install these after the fact?The ST specific features I'm speaking of are the integration of STM32CubeMX and ability to generate all the initialization code for the various peripherals that I'm looking to use.   Specifically: I'm looking for the Linux install to have an option of File > New > STM32 Project, which then gives me the option to select a board (Nucleo, etc.) or a bare MCU (STM32U575xxx, etc). It then generates a .ioc file and eventually generates the code.  

I'm using the link below to select boot path and do secure boot device provisioning for my STM32H563 board:https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_STM32CubeMX_OEMiRoT_Boot_path_on_STM32H563Boot path is configured as follows:I have run provisioning.bat, the product state was set to PROVISIONED. The provisioning was successfull, with logs at the end of ob_flash_programming.log:OPTION BYTE PROGRAMMING VERIFICATION:Option Bytes successfully programmedTime elapsed during option Bytes configuration: 00:00:01.334Programming successHowever, inside ob_flash_programming.log, it also shows:PROGRAMMING OPTION BYTES AREA ...Warning: Option Byte: boot_ube, value: 0xB4, was not modified.Warning: Option Byte: hdp2_end, value: 0x0, was not modified.Warning: Option Byte: secbootadd, value: 0xC0000, was not modified.Warning: Option Byte: secwm2_end, value: 0x0, was not modified.Warning: Option Byte: sram2_ecc, value: 0x0, was not modified.Warning: Option Byte: sram2_rst, va

When I open STM32CubeProgrammer (v2.21.0) it displays an error modal "Old ST-LINK firmware version. Upgrade ST-LINK firmware. If I click the "Firmware Upgrade" button an STLinkUpgrade 3.16.8 shows up with Current firmware: (blank)Type: (blank)Version: UnknownUpdate to Firmware: Unknown.The upgrade button does nothing when clicked. How do I fix this?I downloaded the software here  https://www.st.com/en/development-tools/stsw-link007.htmlAfter running/usr/lib/jvm/java-17-openjdk-amd64/bin/java -jar stsw-link007-v3-17-10/stsw-link007/AllPlatforms/STLinkUpgrade.jarThere is another upgrade dialog with version 3.17.10 displaying the same firmware info as above, with the upgrade button greyed out.Other commands ive run$ ls -l /dev/bus/usb/001/019crw-rw----+ 1 root plugdev 189, 18 Feb 9 09:36 /dev/bus/usb/001/019$ lsusb | grep STBus 001 Device 019: ID 0483:374b STMicroelectronics ST-LINK/V2.1$ STM32_Programmer_CLI -l---------------------------------------------------------------

We have a design that has been working fine for some time now using STM32G071CBT6 in LQFP48 but a new batch is suddenly failing with ADC readings from VREFINT that are quite a way out of spec.Previous versions have always been slightly low - reading maybe ~3.15v on a ~3.25v supply voltage but that's always been "close enough", but now the latest batch of devices are dipping below 3.0v on the same ~2.35v supply and triggering our under-voltage detection.We are monitoring a few voltages using the ADC, including the supply voltage which is commoned with VDD/VDDA, VBAT and VREF pins - decoupling is per the power supply scheme shown in the datasheet DS12232.VREFBUF is disabled.Since we are not worried too much about absolute accuracy, we are not running the calibration routine on the ADC.System clock is 16MHz and ADC sampling is 79.5 cycles, ADC resolution is 12 bit.The ground pin is solidly grounded, supply voltage going into the pins is ~3.25v and I can't see any significant current being

Found a bug with RX_POOL buffers been permanently used. There are total of 12 buffers defined by default. Adding more buffers will prolong the operation, but eventually all of them will be permanently locked. Using the latest available from ST LWIP stack. Our configuration: enabled ARP, ICMP; TCP server with 5 available connections. As soon as a whole buffers are locked, the ethernet driver won't process any incoming packets. Soon after start the number of used buffers goes from 0 to 4 with no active TCP or UDP communication, just a normal network activity. Once TCP communication is started, and if there is no traffic congestion like opening several connections at the same time or sending too many packets, LWIP may function without a problem for days, which makes finding the issue with losing the ethernet communication difficult. The number of available buffers may go down one-by-one. Opening several connections simultaneously and starting the traffic on all of them locks the buffers i

I bought the STM32H7 dual-core EVAL board STM32H757I-EVAL and started with TouchGFX. I created some first buttons in TouchGFX Designer and flashed them to the board — that part works fine and runs without issues.Now I want to continue programming in STM32CubeIDE, but I cannot start the CM7 debug session. CubeIDE shows:“Launching STM32H747I-EVAL_CM7 Debug has encountered a problem”“Failed to execute MI command: load …\STM32H747I-EVAL_CM7.elf”“Error message from debugger back end: Load failed”The M4 upload/flash finishes without any error message, but it looks like the M4 application does not run. For M7, I always get the “Load failed” message above.I followed this YouTube tutorial, but without success: https://www.youtube.com/watch?v=k3mXhPZSaswQuestion: What is the correct workflow to flash/debug CM7 and CM4 on this EVAL board in CubeIDE (especially for TouchGFX projects)? Why does CM7 “load” fail while TouchGFX flashing works?

Hi everyone,I’m building a coffee machine project using STM32C071 (C0) mainly because it has USB. I need USB Host MSC to:Mount a USB flash drive (FAT)Read/write files (params/logs)Firmware update from USB driveThe “official” ST stack seems to be ThreadX + USBX + FileX. Since there’s no USB Host MSC example for C0, I used an STM32L4R5 example (much larger RAM) as reference and adapted it.Issue: To pass ThreadX/USBX init, I kept increasing stacks/pools until I’m using ~20 kB of RAM. Then, when I plug the flash drive, enumeration fails with out-of-memory errors (e.g., UX_DEVICE_ENUMERATION_FAILURE / allocation failure).Questions:Is ~20 kB RAM just to init (and still fail at enumeration) expected for USBX Host MSC + FileX, or does it strongly suggest misconfiguration?Is there any official guideline/table (ST/Azure RTOS) for typical/minimum RAM for USBX Host + MSC + FileX (FAT)?Is there a practical RAM “floor” to enumerate + mount FAT + read/write files (single device, no HUB)? Like “below

We are using an STM32G070 with 64 Pins.The clock comes from an external 32,...kHz crystal. For clock calibration, we enable the RTC calibration output PC13.Whenever this is active, reading the state of the input PA4 always returns false, although we activated the pullup. Measuring the pin gives us the expected 3.3VDisabeling the calib output makes PA4 readable again. We compared the PA4 port setting with/without calib-output, they are always the same. Do you know about this issue? I found an errate entry concering PC13, but not our situation. Best regards,Peter

We are facing an intermittent EWGF (Error Warning Flag) issue during CAN communication at 1 Mbps on multiple STM32 MCUs. The same hardware and software setup works reliably at 500 kbps without any CAN warnings.MCUs UsedSTM32L443VCT6STM32L443CCT6STM32F437ZGT6All devices communicate together on the same CAN bus.Issue DetailsWhen CAN bit rate is configured to 1 Mbps, the EWGF bit in CAN_ESR register gets set intermittentlyCommunication does not stop immediately, but error counters increase over timeAt 500 kbps, the issue is not observedSame CAN transceivers, wiring, and termination are usedCAN ConfigurationCommon SettingsCAN peripheral clock: 24 MHzGPIO speed for CAN TX/RX pins: High speedSame clock source and configuration across all MCUsFor Bit Rate 500KHzCANx->BTR = CAN_TSEG1(12) | CAN_TSEG2(1) | CAN_BRP(2) |CAN_SJW(0); For Bit Rate 1MHz (Tried for different TQ , but still getting CAN warning)TQ per bit = 8 TQCANx->BTR = CAN_TSEG1(5) | CAN_TSEG2(0) | CAN_BRP(2) |CAN_SJW(0);&

 Hi, Can i use the NUCLEO-N657X0-Q board as custom ASIC over an Octal SPI style bus? Thanks Atchaiah

Hello, I need a circuit schematic for the NUCLEO-L010RB development board, specifically for lighting up the LEDs.

I am working with a custom board that uses the STM32H7S38T chip. I am trying to use the SPI flash example from Zephyr to write to and read from the BY25Q16ES NOR flash. I am using the XSPI interface in normal SPI mode. I can read out the JEDEC ID (0x9F) as 0x684015, which matches the value given in the datasheet.   When reading the SFDP (0x5A), the MISO is pulled high after the dummy cycles. Have I overlooked something? The flash datasheet clearly states that the SFDP is available. Zephyr Debug output: ------------------------------------- [00:00:00.000,000] <dbg> flash_stm32h7: stm32h7_flash_init: Flash initialized. BS: 32[00:00:00.000,000] <dbg> flash_stm32h7: stm32h7_flash_init: Block 0: bs: 8192 count: 8[00:00:00.000,000] <dbg> flash_stm32_xspi: flash_stm32_xspi_init: XSPI Init'd[00:00:00.100,000] <dbg> flash_stm32_xspi: flash_stm32_xspi_init: Reset Mem (SPI/STR)[00:00:00.100,000] <dbg> flash_stm32_xspi: HAL_XSPI_StatusMatchCallback: Status Matc

Hi,On the STM32H563 Nucleo, I was able to flash an application using the UART bootloader.However, the application does not execute when triggered with the GO command.If BOOT0 is pulled low, the same firmware runs successfully.But Go command executes properly but the firmware is not runningThe firmware i am trying is led blinking application

So i have the stm32G0 usb-c disco board. https://www.st.com/en/evaluation-tools/stm32g071b-disco.html   I've flashed the latest USBPD_Analyzer software on the device and i have the latest UCPD monitor project.    The semi problem is that it's kind of frustrating that in SPY MODE by default the mico doesn't show as a USB device.  I only see the usb micro usb connection when i'm in Snk Mode.  Is there a reason why in spy mode the USB connection to the PC from the micro doesn't show up?   So what i have to do is.  Start in Snk mode.  Connect to the PC via the micro usb connector and connect to the UCPD monitoring program.  Then i can switch to SPY MODE then i can attach my devices to it.  Which can kind of be flakey some times.      

[PN]: NUCLEO-G431RB with EVLDRIVE102BH and custom motor [VERSION]: Version: 6.4.1 Build: 250722.104358[TOOL]: Motor Control Pilot[DETAILS]: Hello All, I have been working on getting a sensorless FOC driver to work. So far I am able to get the rotor to align and move under open-loop control and occasionally it can switch over to closed loop control. When the motor switches over and runs it is fairly stable. My main issue is that I am unable to get the motor to reliably make the switch from open loop to closed loop. When it fails I often get a speed error with FAULT_OVER. I am using the STO+PLL Observer and I have gone through the current loop tuning and I think that looks good, the speed loop could use a little more work once this is resolved, but if the issue is with the observer I don't want to spend too much time on it yet. I output the BEMF-A and BEMF-B signals through the DAC to an oscilloscope, and when the startup fails I see both the amplitude and the frequen

Greetings, I am looking for pointers to material describing recommended ways to interact with built-in flash memory for general data reading and writing.DS9716 indicates there are several memory-mapped regions that could suffice, but maybe block 6 (starting at 0xC000 0000) seems like a safe bet, since it is "Not used"?Since this is for data storage and retrieval only, not instruction storage and retrieval, is there any need to mark the region of memory in some way in the loader script?Also, I noticed the HAL functions have some flash-based functions (UM1725) - there is some good info in there but again I'm not sure what memory target would be best for these functions.Apologies if this has been written up somewhere already. I see several "lab" type resources on the web for demonstrating how to do this, but I haven't seen a recommended practice in the official documentation or the knowledge bases here.

I am using ST MotorControl Workbench 6.4.1 with the STM32G431CBUX** MCU for a motor control project. When configuring the current sensing module for Three Shunt Raw Currents topology with the option Internal OpAmps + External gain network, the code generation fails with an RCSConnect error.But when I choose the option  Internal OpAmps +  Internal PGA eveything is good.I am looking to understand:1. Is the Internal OpAmps + External gain network configuration officially unsupported for STM32G431CBUX in MC SDK 6.4.1?2. Or is this a hardware resource limitation (e.g., insufficient internal op-amps, pin conflicts) specific to this MCU that blocks this configuration?  

Not sure what is going on, im unable to toggle an IO and im not sure why...This is a very simply custom board, it uses I2C, CAN and USB. I've configured everything in CubeMX and double checked the pinout and gerber files several times but i can't find anything wrong. I've double checked the voltages on VDD and VDDIO2, both are 3.3V. I've tried configuring PD2 as Push-Pull and Open drain with and without pull-up but i get no change on the pin when measuring with my scope.PD2 is connected to the CAN STBY pin that has an internal pull-up, the pin remains high when the PHY is connected and low when the PHY is disconnected. This would indicate that there is no short on the board and that the electrical part is fine. I have physically probed the connections on the board and they are correct.What am i missing, do i need to configure something else? Below is the minimum CubeMX project. I2C and the EXTI work fine but PD2 does not.  int main(void) { /* USER CODE BEGIN

Hi all,I’m running into an issue with LPTIM1 when using LSE as the clock source. The exact same configuration works perfectly when I use LSI or PCLK, but with LSE the code gets stuck waiting for the ARROK flag after writing ARR.The code blocks forever at:while (!LL_LPTIM_IsActiveFlag_ARROK(LPTIM1)) {} So it looks like the ARR register update is never acknowledged when LSE is the clock.Important notesLSE is definitely running — it’s already used elsewhere in the system without issues.We are looking for low power applicationwe using STM32U073CBT6Clock configurationLL_RCC_SetLPTIMClockSource(LL_RCC_LPTIM1_CLKSOURCE_LSE); LL_APB1_GRP1_EnableClock(LL_APB1_GRP1_PERIPH_LPTIM1); LL_IOP_GRP1_EnableClock(LL_IOP_GRP1_PERIPH_GPIOC); NVIC_SetPriority(TIM6_DAC_LPTIM1_IRQn, NVIC_EncodePriority(NVIC_GetPriorityGrouping(), 3, 0)); NVIC_EnableIRQ(TIM6_DAC_LPTIM1_IRQn);LPTIM configuration/* Make sure timer is disabled before config */ LL_LPTIM_Disable(LPTIM1); /* Select clock & prescaler FIRST *

I referred to this article: “Bootloader jump to Application HardFault - STM32H563.”I am also using the STM32H563, and used the following function to jump to the application, but the jump does not succeed. My test program is very simple. After creating an STM32H563 project, I only configured the UART to print messages so I can identify which program is currently running./* Bootloader */ typedef void (*pFunction)(void); void relocate_exe(uint32_t app_addr) { uint32_t appStack; uint32_t appResetHandler; pFunction appEntry; appStack = *(volatile uint32_t *)app_addr; appResetHandler = *(volatile uint32_t *)(app_addr + 4); appEntry = (pFunction) appResetHandler; __disable_irq(); SysTick->CTRL = 0; SysTick->LOAD = 0; SysTick->VAL = 0; SCB->VTOR = (uint32_t) app_addr; __set_MSP(appStack); //__enable_irq(); appEntry(); } int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_USART3_UART_Init(); char msg[128]; sprintf(msg, "Bootloader!!!(%x)\

Hello ST Community, My MCU Part No. is STM32F103C8T6.My MCU Firmware Package is STM32Cube FW_F1 V1.8.6 and This Package CAN Communication is Working Fine and When Ever i Change one GPIO Pin and Generate the Code then CAN is Not Working What is The Problem Behind it ? If Any body Idea About That ? Thanks In Advance .

Hello,I have written a custom bootloader for my stm32u5 project and have been testing it for the last few months with multiple working firmware updates.  To give some context, I transfer an encrypted firmware image to an external flash chip over CANfd from the currently running firmware.  The next time the device boots, the bootloader looks for a new encrypted image on the external flash and if found it will decrypt the image, delete the internal flash where the application lives and then flashes the decrypted image. It will then de-init some peripherals and jump to the new application, fairly standard implementation.  All of this has been working flawless until I set RDP = 1(DC) in stm32cubeprog.  Also need to mention that I have set both passwords for RDP regression a while ago, I just have not been setting the RDP level beyond 0.With RDP = 1 the device will boot as it should, and I can send it a firmware update.  I will power cycle the device and it will per