Solved

HiI am trying to implement a fault filter for the HRTIM on a stm32G474.I am using the LL libraries and the Reference manual.I find the table 234 in the reference manual completely unreadable and confusing. Could someone please explain how it is suppose to be interpreted.Lets take an example.my Fhrtim is 170 mhz and I have done the followingLL_HRTIM_FLT_SetPrescaler(HRTIM1, LL_HRTIM_FLT_PRESCALER_DIV2);   LL_HRTIM_FLT_SetFilter(HRTIM1, LL_HRTIM_FAULT_1, LL_HRTIM_FLT_FILTER_4); How do i calcualte the filter length?Best regards Martin

According to the overview it is possible to get up to 16 kB of flash memory. However I can't find a reference to this.

Hi everyone!I'm using a nucleo H755 boardI'm basically trying to debug my code from RAM. I already set the linker to use the autogenerated ld file (STM32H755ZITX_RAM.ld). When I try to debug, the application initializes, however It does not go beyond HAL_Init().Has anyone else had this problem before?

Hi, we started using MP34DT05TR-A on our board, and as part of the manufacturing of the board we used to clean the board from flux residues after the assembly process, to prevent corrosion and leakage.I know that the MEMS microphones may be problematic to cleaning due to its porthole, but I could not find any special restrictions or prohibition in the datasheet regarding cleaning this component.I would like to know if such restrictions are exist?Is it safe to cover the porthole with tape and remove it after the cleaning?Maybe this component can be ordered with pre-mounted tape?Or better I manually assemble this component only after cleaning the board, although this is not the preferred method because there will be again flux residuals.

Hi,I want to use the ETR to count pulses and set a second timer, so every ... seconds the value from the ETR counter is red and renewed like discribed in this ExampleSTM32 Frequency Counter – LAB10 https://deepbluembedded.com/stm32-counter-mode-example-frequency-counter-timer-in-counter-mode/The code is#include "main.h" uint32_t gu32_CounterTicks = 0x00; uint32_t gu32_Freq = 0x00; uint8_t gu8_MSG[40] = {'\0'}; TIM_HandleTypeDef htim2; TIM_HandleTypeDef htim5; UART_HandleTypeDef huart1; void SystemClock_Config(void); static void MX_GPIO_Init(void); static void MX_TIM2_Init(void); static void MX_TIM5_Init(void); static void MX_USART1_UART_Init(void); int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_TIM2_Init(); MX_TIM5_Init(); MX_USART1_UART_Init(); HAL_TIM_Base_Start(&htim2); HAL_TIM_Base_Start_IT(&htim5); while (1) { } } void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef* htim) { if(htim->Instance == TIM5) { gu32_CounterTicks = TIM2

Hello all,This is not a common question. It is just to report a "bug" I encountered, to get feedback from the forum about my solution and a warning to others that may face this same problem =)I suffered some strange "behaviors" when executing a simple test with TouchGFX Designer v4.16 generated project for the board 32L4R9IDISCOVERY[1]. The display simply stop working after a while.What I have done:I created a project on TouchGFX version 4.16 for this board. Then I designed a screen with just an animated image.On the main file, I created other 4 tasks that only have a delay and asm("nop") (code on below).Behavior:After running for a while, the display simply hangs out. But the firmware is running normally (the tasks are still running).My analysis:We found that in the generated (by the example board, not the TouchGFX) file "TouchGFXHAL.cpp" has some "if" on interrupt calls that caused this behavior.When checking the if (osKernelGetState() == osKernelRunning)its assumption that the

Hi,I'm planning to use STEF01 as a high-side switch plus an external MOSFET for blocking inverse current from load. Is this feasible or I would be wrong?gaston

Trying to synchronize in time three different STM32F446RE MCUs. I first tried to look how internal oscillators drift compared to each others.The datasheet says that the precision of the oscillations are of 500ppm (parts per million). So every 1000000 oscillations there can be a 500 oscillation shift compared to what a million oscillations should bring us, am I right ?However, I observed with the code in annex that the parts per million are a lot more than expected so I was wondering if I was missing something.I can observe 4000ppm with one of the three MCUs I use and 2000ppm and 1000ppm for the two others.Using the PLL or not to change the oscillations frequency output doesn't change anything and the parts per million observed stay the same.Can someone help me understand where I am missing something please ?

Hi, I am developing firmware on the STM32MP157C-DK2 in engineering mode and using STM32Cube_FW_MP1_V1.4.0 and STM32CubeIDE. I must say this is my first project with a STM device and the tools. I am unable to direct printf to the UART4 linked to the onboard VCP of the STLink debugger. The cube package example 'UART_Receive_Transmit_Console' seems to directing printf to USART3 port, not the UART4. After reading the application note 'AN4989 Rev 3: STM32 microcontroller debug toolbox', printf redirection to uart port seems quite simple task. But since UART4 cannot be assigned to the CortextM4, it is shared port. I am unable to figure out where the handle of UART4 port is defined, which is essentially needed to redirect printf command. Thanks in advance for any help in making it work. Kind regardsHafeez

The eeprom I am using has no status byte/bit. In order to know if the device is busy you have to look for an ACK when repeatedly sending the address byte.I cannot find an easy way to do this using the CUBEIDE and the HAL. All the low level i2c routines are static to the libraries.Any ideas?ThanksRich

1 . what does means System Clock in MCU?does it mean electronic device in a MCU that issues a steady high-frequency signal that synchronizes all the internal components?​I want the exact meaning of System clock.2 . what is To Power(MHz) SYSCLK ​in Clock Configuration of STM32CubeMX connected to To Power(MHZ)What is To Power ?please reply to question. Thank you ***Moderation Edit: please do not post your email address on this website***

I'm running PC-Lint as an external tool with the results going an output console. I'd like to be able to double click on a PC-Lint error message in the console and have the appropriate source file / line displayed as per compiler errors. I have PC-Lint error messages formatted the same as complier errors but the IDE ignores double clicks on these messages.Is there any way to configure CubeIDE to get the desired behaviour ?

I can enable git in Atollic TrueStudio by setting Customize Perspective.

..

I use a ST-LINK/V2 and have tried to connect using ST-link utility program. This did not work so I assumed something was wrong with the hardware. But now I have tested to connect using STM32CubeProgrammer instead (I use the same ST-LINK/V2), and then everything works as expected. Is the ST-link utility program not supporting STM32G4 MCUs?

Hi,Looking at the reference manual, en.DM00327659.pdf, page 3929 it seems the simple way of debugging previous M4 processors using printf() redirect to the ITM and then using the SWO pin/STLINK interface could be used on the MP1 M4 core as well.But there isn't simple mention of the ITM functions in the STM32Cube_FW_MP1_V1.0.0 release, and there is not even a single declaration of the ITM HW in the stm32mp157cxx_cm4.h file(not even the 0xE0000000 base address).Can you provide some code example please, it will be much better starting point than the vague description of the ITM operation in the reference manual. Thank you!Edit: ST-Link utility connected to the STM32MP157C-DK2 dev board seems not able to connect (loaded with latest V2.J34.M25 firmware) to the MP1. It does reset it though, so printf in the SWO viewer is out of the question. Maybe there is a way to redirect ITM to the M4 core ?Second, seems the M4 ITM hw is loosely based on the STM32F469/479 ITM core(at least register addres

Hello,I have started working on the STTS22H and noticed that, at least for my part, the datasheet I2C addressing directive seems to be inverted. Aside from the fact that the datasheet and the evaluation kit have different addressing directives, the evaluation kit seems to have the ADDR pin connected to VDD which would mean the 7-bit address is 0111 000. However, when testing out the sensor it would only respond when using the 7-bit address 0111 111, which is the configuration for when the ADDR pin is connected to ground as pointed out in the snapshot from the datasheet below.Could that mean that there is an issue with the datasheet or could that be an issue with the kit I have got?On another unrelated topic, what is the default value of if_add_inc in the CTRL register on boot?Thanks.

Hi,I finished the board bring up introduction: Board Bring Up Introduction | TouchGFX Documentation without any troubles. I can also write and read to the external flash through DMA2D by using the following function:LL_FillBuffer(LTDC_LAYER_1, (uint32_t *)(hltdc.LayerCfg[LTDC_LAYER_1].FBStartAdress), 1024, 600, 0, (uint32_t) 0xFF008000);static void LL_FillBuffer(uint32_t LayerIndex, void *pDst, uint32_t xSize, uint32_t ySize, uint32_t OffLine, uint32_t ColorIndex) { /* Register to memory mode with RGB8888 as color Mode */ hdma2d.Init.Mode = DMA2D_R2M; hdma2d.Init.ColorMode = DMA2D_OUTPUT_RGB888; hdma2d.Init.OutputOffset = OffLine;   hdma2d.Instance = DMA2D;   /* DMA2D Initialization */ if(HAL_DMA2D_Init(&hdma2d) == HAL_OK) { if(HAL_DMA2D_ConfigLayer(&hdma2d, LayerIndex) == HAL_OK) { if (HAL_DMA2D_Start(&hdma2d, ColorIndex, (uint32_t)pDst, xSize, ySize) == HAL_OK) { /* Polling For DMA transfer */ HAL_DMA2D_PollForTransfer(&hdma2d, 10);

I think I got the setup for the Real-Time-Clock (RTC), but how do I verify it is working?Is there a way to output the timestamps or check through a file? I am using the STM32WB55 Nucleo Board, and currently using the STM32 IDE.

I'm using ST-Link_CLI.exe command line to programming our product in test jig, the previous tester is using Win7, it seems works reliable, but now update to Win10 and get problem with power up the tester.When powerup the tester, the PC can detect the ST-Link, but can't detect the STM32MCU, I must unplug the USB and plug in it again, then it can detect the STM32MCU, it will be very annoying to unplug and plug the USB for every unit. I update the ST-Link to latest firmware, it still the same.I use "STM32 ST-Link Utility" to check , the Win 7 PC works stable when power off/on, but Win 10 PC very often can't connect to my STM32MCU (40 % possibility).My Win 10 "STM32 ST-Link Utility" is the latest version: ST-Link Utility: V4.6.0.0 STLinkUSBDriver.dll V5.1.2.0 ST-LINK_CLI.exe V3.6.0.0I'm using "ST-LINK_CLI" and "STLinkUSBDriver.dll" for my tester coding, should I add something extra for Win10? There is "en.stsw-link009", should I add this to Win 10?RegardsSam

It's mean St-link Utility will disapear and will be unavailable on ST site? If so, how much time I have to start using CubeProgrammer?Thanks for any answears.

Hi!Just purchased a SensorTile.Box, and moving now to use it on Pro Mode.On the SensorTile.Box user manual, it is mentioned that the product includes an adapter board - however, the one that I purchased did not include one. Does anyone know how can I obtain this adapter board? Doesn't seem to be available at ST website...Many thanks in advance.Miguel

or if I must write my own code, how to do itThank you,

I try to create a project based on CAN bus but the CAN option is disable in CUBEMX ide.*Controller - stm32f042g6u8 *Cube mx ide version - V 4.24i want to know how to create a CAN BUS project using cubemx & without it,Examples are suggested for better understanding