Solved

HiMy board has, among other things, an STM32F401RBT6 and a full-size USB B (device) connector. System clock is an external 25MHz TCXO. I have verified that the hardware is working correctly, because I have already implemented a compound device class containing USB Audio device and Communications Device class and that all works perfectly. When I try to flash a project containing a very simple MSC Device class with a 16K RAM Disk, nothing happens. Specifically I followed this ST Video tutorial: https://www.youtube.com/watch?v=GjQqZd1keBo which is very clear and he literally only writes/changes 5 lines of code. Yet when I plug in the USB cable to the PC I see nothing at all on the PC. I have tried on Linux, nothing shows up, even on an lsusb command typed in a terminal. I have tried on the only Windows machine I have, which is a WinXP Laptop. Again, nothing... The video tutorial is written for a STM32F446 on a Nucleo board; the only changes I made compared to the video were:1) Reduce the

I implemented a code of output compare mode for TIM3. However, it does not work as I expected.ky017ledmodule_config.h#ifndef KY017LEDMODULE_CONFIG_H_ #define KY017LEDMODULE_CONFIG_H_   #include <stddef.h> #include "stm32f4xx_hal.h"   #define RED_LED GPIO_PIN_0 #define GREEN_LED GPIO_PIN_1 #define BLUE_LED GPIO_PIN_4     void KY017_Module_Init(void); void KY017_Module_Led_Blinker(uint16_t Pin); void KY017_Module_Toggle_Led(GPIO_TypeDef *Port, uint16_t Pin); #endif /* KY017LEDMODULE_CONFIG_H_ */tim_oc_config.h/* * tim_ic_config.h * * Created on: 2 Mar 2023 * Author: anil */     #ifndef TIM_IC_CONFIG #define TIM_IC_CONFIG   #define __HAL_RCC_TIMx_CLK_ENABLE __HAL_RCC_TIM3_CLK_ENABLE() //#define TIMx TIM3 //#define TIMx TIM3   void tim_oc_init(void); void tim_oc_start(void); void tim_oc_start_it(void);   #endiftim_oc_config.c#include "stm32f4xx_hal.h" #include "tim_oc_config.h" #include "ky017ledmodule_config.h"   T

The CubeIDE 1.12.0 release notes post mentions this:"GCC update enabled – Updates GCC 11, which is already available on the Eclipse® p2 update site"I have just updated CubeIDE to 1.12.0, but GCC stays on version 10.When I click "Check for Updates" it says "No updates found". What does it mean that the update is "enabled"? Do I need to perform a specific procedure to update it, or should it be updated automatically?

uC: STM32H725AEIxFW-Package: STM32Cube FW_H7 V1.10.0CubeMX-Version: 6.6.1IOC-File: Attached (SPI_bug.ioc)I tried to generate code with CubeMX for my project. I set up SPI2 as Full-Duplex Master without hardware NSS with the follwing pin config:SCK: PB13MISO: PC2MOSI: PC3The code generated in `void HAL_SPI_MspInit(SPI_HandleTypeDef* spiHandle)` looks like the following for MOSI and MISO:GPIO_InitStruct.Pin = SPI_MISO_Pin|SPI_MOSI_Pin; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_MEDIUM; HAL_GPIO_Init(GPIOC, &GPIO_InitStruct);Although it should look like that:GPIO_InitStruct.Pin = SPI_MISO_Pin|SPI_MOSI_Pin; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_MEDIUM; GPIO_InitStruct.Alternate = GPIO_AF5_SPI2; HAL_GPIO_Init(GPIOC, &GPIO_InitStruct);=> The configuration for `Alternate` is missing!With the generated code, the MOSI and MISO lines do

Hello,I am using the STM32H7B3IIT6 MCU to control a master control board, which has a push button connected to PB11 with the following hardware: My objective for this is the following:When the system is running and I press this button, the MCU puts the entire system into standby (Sends stop signals to components, puts CAN and LCD display into standby, then puts the MCU into standby to minimize power consumption by the system's battery).When the system is off and I press this same button, the MCU resets to a new "run" of the firmware and turns everything back on again.According to another forum post I made, any pin connected to an EXTI line can be used to do this, so I selected PB11. However, I'm looking through the reference manual and they just refer to "wakeup pins" and don't define what they are or how to configure them as wake-up pins. Can anyone please explain to me how to do the following steps:Configure PB11 as a wakeup pin from standby modeSend the MCU into Standby mode wh

..

Once again.....trying to implement an Azure RTOS NX TCP Server application on the F7 Nucleo board (since H7 processors will not be available any time soon). I ran into a hard fault at the HAL_GetTick instruction below: /*-------------------------------- PLL Configuration -----------------------*/ /* Check the parameters */ assert_param(IS_RCC_PLL(RCC_OscInitStruct->PLL.PLLState)); if ((RCC_OscInitStruct->PLL.PLLState) != RCC_PLL_NONE) { /* Check if the PLL is used as system clock or not */ if(__HAL_RCC_GET_SYSCLK_SOURCE() != RCC_CFGR_SWS_PLL) { if((RCC_OscInitStruct->PLL.PLLState) == RCC_PLL_ON) { /* Check the parameters */ assert_param(IS_RCC_PLLSOURCE(RCC_OscInitStruct->PLL.PLLSource)); assert_param(IS_RCC_PLLM_VALUE(RCC_OscInitStruct->PLL.PLLM)); assert_param(IS_RCC_PLLN_VALUE(RCC_OscInitStruct->PLL.PLLN)); assert_param(IS_RCC_PLLP_VALUE(RCC_OscInitStruct->PLL.PLLP)); assert_param(IS_RCC_PLLQ_VALUE(RCC_OscInitStruct->PLL.PLLQ));   /* Disa

I have a program running on NUCLEO-L4P5ZG board. The USB device VCOM runs fine on STM32CubeMX v6.5.0 (STM32CubeIDE v1.9.0). It was broken since STM32CubeMX v6.6.0 (IDE v1.10.0). The problem still exists in STM32CubeMX v6.7.0 (IDE v1.11.2). My workaround is to use the Core\Src\stm32l4xx_hal_timebase_tim.c file from STM32CubeMX v6.5.0. I attached the three files for helping fixing the problem. stm32l4xx_hal_timebase_tim_cz.c is from STM32CubeMX v6.5.0. stm32l4xx_hal_timebase_tim.c is from STM32CubeMX v6.7.0.

..

I have a strange problem booting from eMMC (Kingstone EMMC04G-M627-X03U) on STM32MP153CAA Rev.Z.By boot failure I mean fallback to serial boot (DFU over USB). Situation is as follows:Cold start never fails (Power-on Reset).Reset pin (Pad Reset from NRST) - have noticed issue maybe just once - not 100% sure.System reset generated by MPU or IWDG2 Reset - fails very often but not always. Haven't noticed any system in this behaviour.Setting both primary and secondary boot sources to eMMC greatly reduces chances of failure but does not eliminate the issue completely.Attached Boot ROM traces (without and with primary/secondary sources set) and current OTP values. Any help appreciated, thank you!

Hello team!I am newbie in STM32 world so probably i am missing something but please clarify this for me. I have found conficting informations:Datasheet "DS11532 Rev 7" at p. 47 says "Battery Charging Specification Revision 1.2 support"Reference Manual "RM0410 Rev 4", p. 1579 - "supports charging port detection as described in Battery Charging Specification Revision 1.2 on the FS PHY transceiver only." the same manual at p. 1638 describes registers related to BCD functionalityhowever:the same manual again says at p. 1581 that this MCU doesn't support BCD at allthere are no BCD related functions in stm32f7xx_hal_pcd_ex filesthere are no BCD related registers in stm32f767xx.h fileso i am little bit confused about that.BR.Lukasz

I am attempting to use TraceX in my NetXDuo application. But when I enable TraceX in the Software Packs of CubeIDE (TX_ENABLE_EVENT_TRACE) I get compiler errors in all of the calls to save a tracex event. The macros that defines the calls to tracex services appear in nx_api.h, but are not defined, and hence the _nx_trace_event_ service is never defined.  I saw a discussion of this same issue over in the Renesis community where a workaound fixed the compiler issue. https://community.renesas.com/mcu-mpu/embedded-system-platform/f/forum/10314/undefined-reference-to-nx_trace_in_line_insert-when-arp-probeBut t his workaround did not fix the STM code.Can anyone suggest something that may help?Thanks,MikeH

..

I am rather new to STM32. Ιn my project, I am using an STM32L072KZU6 and I want to debug the firmware using the ST-LINK/V2-ISOL. I connected both SWDIO and SWDCLK pins to pins 7 and 9 of the ST-LINK/V2-ISOL, along with +3.3 V on pin 1 and ground on pin 4. (Pin 2 is connected to +3.3 V, too.) In ST32CubeProgrammer, I can connect to the target MCU without problems:However, when I try to use Keil uVision v5.37.0.0 and click on Start/Stop Debugging Session, I get a dialog box with the message "Trace HW not present":and, when clicking on OK button, another dialog box appears with the message "Error: Target DLL has been cancelled. Debugger aborted!":Any clues, anyone?Here are the settings for ST-LINK debugger in Keil: 

..

In the peripheral's User Constants tab, unhighlighted IP Handle Label values are in light gray, which makes them illegible. On my monitor at least.

I did not tested if this is specific to all MCU but for U5 familly this is sure:How to reproduce : Launch cubeMX, (6.7.0)select U5 board like nucleoGo to project manager, and select under Toolchain - Makefile.--> Bug, the Makefile genereted is missing some details on CPU, so cannot build.To solve it add : CPU = -mcpu=cortex-m33after ####################################### # CFLAGS ####################################### # cpuMoreover, and i am not sure about this but I think I read somewhere that U5 was using : fpv5-sp-d16 and not fpv4-sp-d16 as in generated makefileso I replaced FPU = -mfpu=fpv4-sp-d16by this : FPU = -mfpu=fpv5-sp-d16Please review the makefile generation under cudeMX seems to have some mistake for U5 series at least.Hope this help and avoid other to lose time to spot this.

Dear ST,Could you please help me on that how can I solve the below issue?After updating the HALL firmware in teh Cube MX to FW F4 V 1.27.1 when i am regenerating the code. In the place where the FREE RTOS componens are created before a headline of the main.c is generated instead.Do you know is the Firmware update reset some settings?Thank you,David

Hello,I using STM32CubeIDE to create my Code with STM32CubeMX.With version STM32CubeMX V6.6.1 there where no problems.Now with the update V6.7.0 and the project migration all the freeRTOS initialization stuff will no more generated. Following code:/* Create the queue(s) */ /* creation of mailboxCanRx */ mailboxCanRxHandle = osMessageQueueNew (32, sizeof(CanRxMsgStruct), &mailboxCanRx_attributes);   /* creation of mailboxCanTx */ mailboxCanTxHandle = osMessageQueueNew (64, sizeof(CanTxMsgStruct), &mailboxCanTx_attributes);   /* creation of mailboxEemCmd */ mailboxEemCmdHandle = osMessageQueueNew (64, sizeof(EemJobStruct), &mailboxEemCmd_attributes);   /* Create the thread(s) */ /* creation of taskMain */ taskMainHandle = osThreadNew(osTaskMain, (void*) &taskMain_attributes.stack_size, &taskMain_attributes);   /* creation of taskWatchdog */ taskWatchdogHandle = osThreadNew(osTaskWatchdog, (void*) &taskWatchdog_attributes.stack_size,

I selected LDO power supplyBut frequency is still limited to 400MHz.

According note of page 27 of datasheet only is possible VOS2 and VOS3. But in STM32CubeMX is possible selections of VOS0, VSO1, VSO2 and VSO3.Thank you in advance

Using an STM32U575 on our own design. Aim is to put it into Stop2 Mode and wake up from three sources: a) GPIO pinb) Wake up timer (RTC)c) AlarmA (RTC) I have these three sources setup as interrupts and when the CPU is running (i.e. not stopped) these interrupts fire and are handled correctly. However, when entering stop mode, the device cannot be woken when any of these 'interrupts' occur - those of you familiar with this will recognise that while the interrupts don't wake up the CPU, these interrupt sources are used to wakeup the CPU when they occur after which the interrupt will be serviced. Debugging in low power mode is troublesome, so my best insight comes from using the STM32Cube Programmer, attaching in 'hot' mode and examining the SFRs. Here I can see the WUTF and ALRMAF are set, but still no wake-up. Frustratingly, I have used the examples referred to in this rather good tutorial and based on this I can (using a Nucleo board) enter Stop2Mode and exit is su

Dear ST HelloI am using timer 6 to calculate the time for timer interrupt triggering,I am using the example for the board from the cube BSP folder,\STM32Cube\Repository\STM32Cube_FW_F4_V1.27.1\Projects\STM32F429I-Discovery\Examples\BSP\SW4STM32\STM32F429I-DiscoveryIn this project, I disable some functions and want to add an interrupt using timer 6.I generated the code using another project for the interrupt and timer configuration and I integrated the hal timer and timer ex to build the project, I also defined the HAL_TIM_MODULE_ENABLED.here is the code: /* Configure USER Button */ //BSP_PB_Init(BUTTON_KEY, BUTTON_MODE_EXTI); MX_TIM6_Init(); /*##-1- Initialize the LCD #################################################*/ /* Initialize the LCD */ //BSP_LCD_Init(); /* Initialize the LCD Layers */ //BSP_LCD_LayerDefaultInit(1, LCD_FRAME_BUFFER); //Display_DemoDescription(); HAL_TIM_Base_Start_IT(&htim6);       static void MX_TIM6_Init(void) {   /* USE

If BLB2=1, hardware maps the System memory to address 0. The bootloader might've remapped it when it detects "valid code" in either bank, but it apparently does not do it, as witnessed by footnote to SYSCFG_MEMRMP.MEM_MODE description:1.When BFB2 bit is set, the system memory remains aliased at @0x0000 0000IMO, this should be added - maybe also as a footnote - to Table 5. Boot modes.The reason is, that the combination of default VTOR=0 and System memory mapped at 0 causes the users to complain of "my code crashes at 0x1fffxxxx", which we see here quite often.---SYSCFG_MEMRMP.MEM_MODE description is common for all three Cat devices; however, the BFB2 bit is present only in Cat.3 devices according to in which Flash chapter is it present at all. Shouldn't this fact be reflected in the abovementioned footnote?---Only Cat.3 devices are documented to have BFB2 in option bytes. However, factory-progrmmed value for Cat.2 and Cat.4 devices have the bit at this position set to 0, which is surpri

When VL53L5CX Time-of-Flight sensor is in threshold detect mode, will it trigger only on what would be a Status 5 valid distance? Thanks! -Doug