Solved

Hi ST team,I am using X-CUBE-SBSFU V2.8.0, project: Device: STM32H753Base example: NUCLEO-H753ZI 2_ImagesI ported UART pins/port for my H753 EVAL board.ProblemBuild fails in SECoreBin with GNU14.3 toolchain:C:/.../2_Images_SECoreBin/Src/se_crypto_bootloader.c:222:(.text.SE_CRYPTO_Decrypt_Init+0x16): dangerous relocation: unsupported relocation However , Then i shifted to 13.3 tool chain , then everything works fine for me.  Please confirm whether this is a known GCC 14.3 compatibility issue for SBSFU v2.8.0 key generation. If yes, could you share an official patch for prebuild.sh / key assembly generation so generated key symbols are fully compatible with newer GNU/binutils?

Hello ST Community,I am reporting a 100% reproducible build failure when using the latest STM32CubeWBA SDK and tools for the NUCLEO-WBA55CG. It appears the default configuration generated by STM32CubeMX for the BLE_p2pServerThreadX application results in a RAM overflow and linker warnings.Environment:MCU: STM32WBA55CGUxBoard: NUCLEO-WBA55CGSDK: STM32Cube_FW_WBA_V1.9.0STM32CubeMX: v6.17.0STM32CubeIDE: v2.1.0 (with GNU Tools for STM32 14.3.rel1)Steps to Reproduce:Open the example .ioc file located at: STM32CubeWBA\Projects\NUCLEO-WBA55CG\Applications\BLE\BLE_p2pServerThreadX\BLE_p2pServerThreadX.iocIn STM32CubeMX, generate the project for STM32CubeIDE.Open the project in STM32CubeIDE v2.1.0 and perform a Clean Build.Observed Error (Scenario A - Default settings):The linker fails with a RAM overflow of 17,288 bytes:ld.exe: BLE_p2pServerThreadX.elf section `.bss' will not fit in region `RAM'ld.exe: region `RAM' overflowed by 17288 bytes Observation (Scenario B - Manually adjusting RAM

I have been attempting to get a GPS lock with the TESEO-LIV3F, and I am not able to.  I am fairly certain that it has to do with how I designed the signal chain from the chip antenna to the RF-IN pin on the LIV3.  I have ensured that it was outside with a clear view of the sky, I have sent the $PSTMCOLD, 6 command to it.  I have tried to initiate with this command; $PSTMINITGPS,3912.826,N,11939.993,W,1487,17,02,2026,21,11,30, but then later sent $PSTMRESTOREPAR to reset it.  I do not have teseo-studio seeing as I am on linux.  Any help will be appreciated.

Dear STMicroelectronics Community, I am an electronics engineer seeking for technical help. My problem is that I want to reverse engineer an old STi7101 CPU based Set Top Box with HDMI output or say it less complicated, a Dish Antenna Receiver Box. My problem is that I need an Board Support Package for STi7101 board. I already had look for the datasheet of STi7101, and there is written that the CPU supports Windows CE. My plan is to run Windows CE on the box. Is there a way to make it work? Thank you.    

Hey I am having trouble tryng to connect my stm32g473 to a canbus. I am using a l9616 as a transceiver and the bus is functions as I have connected to it with an stm32f722re with the same l9616.The clock is 64Mhz,Ive used the canbit time calculation website to define the values of nominal time 1 and 2 to achive 500kbs.Also using NVIC and it seems to be configured fine. When tested in loopback the interrupt is called and the messages are received.This is the init with the filter config,as I ve understand I am not filtering anything and any of the messages on the bus should get to my uC.When running the state of hfdcan1 is Busy and also no error code show up.FDCAN_HandleTypeDef hfdcan1; /* FDCAN1 init function */ void MX_FDCAN1_Init(void) { /* USER CODE BEGIN FDCAN1_Init 0 */ /* USER CODE END FDCAN1_Init 0 */ /* USER CODE BEGIN FDCAN1_Init 1 */ /* USER CODE END FDCAN1_Init 1 */ hfdcan1.Instance = FDCAN1; hfdcan1.Init.ClockDivider = FDCAN_CLOCK_DIV1; hfdcan1.Init.FrameFormat =

Require IBIS model for ECMF2-40A100N6 CMC. Please provide if available.

Hello Community,I am migrating a prototype CMake application to TrustZone for a test board targeting the STM32U575VGT6 MCU.  Launching a debug session for my project generates the following errors.  `I've attached verbose console error output in the attached file (console_error_output.txt).CubeProgrammer confirms I have the set Option Byte for TZEN .The debug configuration should be flashing the secure image before the non-secure.GTZC_NS/S are enabled. I have been following the tutorial Develop TrustZone enabled applications on STM32L5 ARM MCUs with STM32CubeIDE - Webinar Replay .  The instructions at 20:00 are completely arcane and I realize I am out of my depth of expertise to get this small project to work (.ioc attached).Does anyone have an application note or tutorial, pertinent to the U5 series, that explains how to flash and launch debugger sessions for a pure CMake + TZ project using only STM32CubeIDE 2.1.0, CubeMX 6.17.0, and CubeProgrammer 2.22.0

Dear all and ST Tech Support,I am writing to report a concerning inconsistency I encountered while migrating an older project to the latest version of STM32CubeMX (v6.17.0).Background: I recently reopened a project originally created about two years ago with STM32CubeMX v6.8.1 for the STM32H742VGTx MCU. My goal was to review the Timer 4 settings to use them as a reference for a new design.The Issue: Upon inspecting the Clock Configuration tab, I noticed that the APB1 Timer Clock was displayed as 120 MHz. Based on my original project notes, this value should have been 240 MHz.When I calculated the Timer 4 period using the 120 MHz figure, the resulting timing was twice as slow as it should be. While checking the documentation, I confirmed that Timer 4 is connected to the APB1 bus. In the CubeMX interface:The D2PPRE1 divider was set to /2, resulting in an bus clock of 120 MHz (which is the limit).However, the Timer Multiplier was stuck at x1, leading to an APB1 Timer Clock of 120 MHz.Obse

I am using Nucleo-F446RE board and trying to verify the TIM1 update interrupt and PWM, the PWM is generated but if i put a break point in the update interrupt it does not halt, what is the reason?int main(void) { /* USER CODE BEGIN 1 */ /* USER CODE END 1 */ /* MCU Configuration--------------------------------------------------------*/ /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init(); /* USER CODE BEGIN Init */ /* USER CODE END Init */ /* Configure the system clock */ SystemClock_Config(); /* USER CODE BEGIN SysInit */ /* USER CODE END SysInit */ /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_USART2_UART_Init(); MX_TIM1_Init(); /* USER CODE BEGIN 2 */ HAL_TIM_PWM_Start_IT(&htim1,TIM_CHANNEL_1); /* USER CODE END 2 */ /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) { /* USER CODE END WHILE */ /* USER CODE BEGIN 3 */ } /* USER CODE END 3 */ } i have put a break point in the

We are working on a project that uses MbedTLS v4.0.0, which contains some ASM code, and when we try to compile the project with gnu-tools-for-stm32 14.3.1+st.2, the compilation fails with the following error:[build] FAILED: [code=1] Middlewares/Third_Party/mbedtls/tf-psa-crypto/drivers/builtin/CMakeFiles/builtin.dir/src/bignum_core.c.obj [build] C:\Users\Parminder\AppData\Local\stm32cube\bundles\gnu-tools-for-stm32\14.3.1+st.2\bin\arm-none-eabi-gcc.exe -DDEBUG -DESC_TRL_REMOVE_DBG -DESC_USER_BUILD_CONFIG_CUSTOM=SC_vendor_platform.h -DSTM32L475xx -DTF_PSA_CRYPTO_CONFIG_FILE=\"C:/smartconnect-h300/H300/mbedtls_porting/crypto_config.h\" -DUSE_HAL_DRIVER -IC:/smartconnect-h300/Middlewares/Third_Party/mbedtls/tf-psa-crypto/drivers/builtin/src -IC:/smartconnect-h300/Middlewares/Third_Party/mbedtls/tf-psa-crypto/drivers/builtin/include -IC:/smartconnect-h300/Middlewares/Third_Party/mbedtls/tf-psa-crypto/include -IC:/smartconnect-h300/Middlewares/Third_Party/mbedtls/tf-psa-crypto/core -I

Hello all,  I need user manual for ST10F269 controller. Can you please share link or document? Thank you in advance.

I have come across an issue which I believe is a bug in the implementation of the osThreadFlagsWait function. Scenario A thread is waiting on a flag (e.g. 0x2u) for a timeout above 0, before this timeout should occur, there are multiple other flags set on the thread (e.g. 0x1u) using osThreadFlagsSet, this results in the osThreadFlagsWait function returning with a value of osErrorTimeout sooner than the set timeout. Cause The xTaskNotifyWait function which is called by osThreadFlagsWait returns each time the 0x1u flag is set, resulting in this section of code being run: Note that t0 is set to the return value of xTaskGetTickCount() at the start of the wait loop, so is the start time, tout is a timeout value passed to xTaskNotifyWait, which is originally the set timeout, but is adjusted each time the xTaskNotifyWait function returns. The issue with the code above is that the value of td is the total time that the thread has been waiting, this is subtracting fro

In the document UM3234 we see the following description of clock configurationOn my Nucleo board, I haven't blown any fuses and measured a clock frequency of 32 MHz. Since the XSPI is configured to have a prescaler of 2 by BOOTROM (also mentioned in UM3234), this implies that the board is using the default clock scenario. The document also mentions this regarding the nominal scenario."During secure boot, the boot ROM sets up PLL1 to switch to CM55, APB, AHB, and AXI clocking at the nominalboot frequency"Does this mean that if i dont have secure boot enabled yet, ill get the default clock, and as soon as I enable secure boot my clock frequency will increase to 400 MHz?. 

I've got a problem with MCU Selection not showing any options.Tried Reinstalling whole program also reinstalling Cosmic, I've got a working license for Cosmic also. Also with my professor we tried copying all files from his computer where it is working without problems (we are working both on windows 11). After that we used Revo Uninstaller to try and download both ST Developer Studio and Cosmic again but that didn't fix anything.We've run out of ideas why it isn't working. Even after connecting STM8S208RB and trying while it is connected didn't do anything.

Greetings! So I have a personal project, using a STM32U585 MCU, with a self-designed board, in which I have a bootloader and the main firmware. So basically I implemented a protocol for communicating with the board, I have a C program that sends a command and the board sends data (around 20Kb), using USB.The scenario is the following: I flash the firmware with the bootloader, after flashing, the bootloader jumps into the main program and starts running, I send a command (via host) to get data and the board sends me data and everything is running smoothly. The problem starts when I unplug the board and plug it again, when I send the command to get data, the board starts to send it and then it completely freezes. Another curiosity, this situation only happens when I plug the board in a USB hub... if I plug the board directly to the laptop, I won't have any problem. Any clue of what can be the problem? Power related? Is there any issue with the jump to the main pr

On STM32Hxx and STM32N6 families I have faced a situation where I need to modify startup assembly code  (startup_stm32xxx.s) to copy code (.text) into ITCM or clear RAM/TCM areas, for clean data or to prevent ECC error (on STM32N6). But next time CubeMX generates code, those changes are overwritten. Same story with SystemInit function in system_stm32xxx.c. So either manual restoration or script must be done. But it's getting quite annoying after several projects. I believe the purpose of CubeMX is to ease development, so I make a feature request:Please add user code begin/end comment sections that exist in main.c also into startup_stm32xxx.s assembly and system_stm32xxx.c source files.For startup assembly I wish the user sections are:User symbols definitions.User data copy.User zero fill.For system file I wish the user sections are quite similar to main.c:User includes.User defines/constants/variables.In SystemInit() function:In the beginning.After VTOR settingAt the end.User func

I just started looking at the STM32C071 family as an alternative to the STM32F042 and STM32F072 we currently use. To my disappointment the USB stack for the C071 is a total mess (dozens of files and complete spaghetti) and on top of that it seems to be written by Microsoft. So there is absolutely no way we are going to use that.Did I miss some other option for the USB device library? This USBX stuff definitely is no option at all.At first glance it looks like there are no significant differences between the USB hardware of the C0 and F0 if only used as device not host. So I am wondering if I can simply use the F0 libraries (which we have debugged and optimized…) on the C0. Or are there any hidden traps?

Currently, questions are going in the Interface and connectivity ICs forum, but there don't seem to be any suitable labels:I don't think 'Low Power RF Solutions' really covers it?The Product Page on the main website comes under 'Wireless connectivity > Long range > NB-IoT products':So I guess that would be a good set of labels?

Hi Folks, I'm working on pattern generation on GPIO pins and I've done it successfully using bare-metal programming approach. I used TIM1 to trigger DMA2 to take data from a buffer and send it GPIOA->BSRR.  But when I try to change the timer from TIM1 to TIM2 and change the respective DMA stream, the same code does not work. code:   uint32_t signal1[6]; //pattern no included // Enable clocks for GPIOA, TIM2, and DMA1 RCC->AHB1ENR |= RCC_AHB1ENR_GPIOAEN; RCC->APB1ENR |= RCC_APB1ENR_TIM2EN; RCC->AHB1ENR |= RCC_AHB1ENR_DMA1EN; // Configure GPIOA Pins 0-5 as output GPIOA->MODER &= ~0x00000FFF; // Clear mode for PA0-PA5 GPIOA->MODER |= 0x00000555; // Set PA0-PA5 as General Purpose Output // Configure TIM2 for DMA requests on update event TIM2->PSC = 0; // Set prescaler to 0 TIM2->ARR = 999; // Set auto-reload value (adjust for timing) TIM2->DIER |= TIM_DIER_UDE; // Enable update DMA request TIM2->CR1 |= TIM_CR1_CEN; // Enable TIM2 // Configure

Hello,Using a NUCLEO H7S3L8, I'm trying to run a test where, using circular DMA with a linked list, I'm trying to send a buffer in memory over to the SAI for audio playback, using an external DAC. This configuration is based on either other tutorials or the reference manual, but it always throws a User Error flag and calls the DMA's IRQ handler, right after the HAL_DMAEx_List_Start_IT() call (whether done on its own after the necessary configuration, or as part of HAL_SAI_Transmit_DMA()). Even with some changes, it always yields the same results. The only one that seemed to have any effect was setting the Transfer Event mode to trigger the TC flag for each linked list item, which confirmed that a transfer might have been completed, despite the error flag.I have also seen GPDMA being configured with circular, using both Standard Request Mode and a Linked List, but haven't gotten any success out of that myself (with even TC flag not being raised).In case it causes any comp

Hi all,I'm unable to install Cube IDE under W10.I tried to play with permissions/administrator/... I always get an error:NSIS error : Error launching installer.All other items (CubeMX, Programmer, Monitor ) were installed without any problem.Thanks for help.

I am working with the X-NUCLEO-NFC04A1 expansion board (based on the ST25DV04K) and I have some questions regarding the Energy Harvesting (EH) capabilities.My Setup:Hardware: X-NUCLEO-NFC04A1 connected to a host MCU. Observation: When measuring the V_EH pin directly, I see a very low continuous current (in the 0.3µA range), which seems insufficient to drive my target peripheral directly. My goal: I am trying to trigger an external circuit that requires approximately 7 mA for a period of a few ms. I understand that the ST25DV cannot supply this current continuously, but I have seen applications that use a reservoir capacitor to obtain high pulse charges that can be used to trigger the system.My questions:Is the low DC current at V_EH normal? Was the V_EH pin designed strictly to slowly charge a capacitor, rather than directly drive a load?Is it possible to increase the EH current? In addition to optimizing the antenna adjustment and coupling distance, is there any setting in t

Hello,We are experiencing corruption of our external IS66WVO32M8 PSRAM while executing x-cube-ai generated code on target device STM32U585AIIxQ. This corruption happens consistently when running the model (i.e. running the ai_*_run() generated function), but cannot be replicated outside of it. Please see the issue description below. ContextWe are using the STMicroelectronics.X-CUBE-AI package version 10.2.0 (STM32CubeMX version 6.16) running the .a static library generated by the cubemx tool on our STM32U585AIIxQ target. This is a Keras neural network that has been successfully analyzed and "validated on desktop" using the tools provided through the cubemx X-CUBE-AI gui. The model requires 1.5MB of RAM, and for this we have an external PSRAM device (IS66WVO32M8DALL ISSI Octal PSRAM). Everything is apparently configured correctly, and we are able to initialize the model and run the inference using the interface provided at X-CUBE-AI/App/app_x-cube-ai.c/h in the generated code.

I am currently performing the bring-up of a custom PCBA using the STM32H755ZIT3.My design is intended to use the Internal LDO only, bypassing the SMPS to reduce component count (i.e. one less inductor in my layout).Here's few details about the MCU power section of my SCH (also, please check attached capture):SMPS Pins: As per the Reference Manual for "LDO-only" mode, I have grounded VFBBSMPS, VSSSMPS and VDDSMPS, whereas VLXSMPS is floating.VCORE/VCAP: I have placed the required 2.2uF decoupling capacitors on VCAP_1, VCAP_2, and VCAP_3. No external inductor is present on the layout.What I'm observing is that at power-on, VCORE remains at 0V. Consequently, the target is not detected by the ST-LINK. If I instead "jumpstart" the board by applying an external 1.2V to the VCAP nodes, the MCU becomes reachable via SWD, and I can successfully modify registers. I suspect a conflict between my hardware layout and the factory default reset value of the PWR_CR3

Dear ST Support Team,I am working on a reliability calculation for an industrial hardware design. I need the official failure rate data for the following components:STM32C092GCU6: FMEDA report and FIT rates LIS2HH12TR: Reliability report and FIT rates at 85°C.These values are required to calculate the system's MTTFd and MTBF according to ISO 13849-1.Could you please provide the available documentation for these parts?Best regards,