Solved

..

STM32Cube_FW_H7_V1.11.0If you have wondered why the Board Support Package code for the STM32H743i_EVAL board is not able to properly switch the edge detection of the SD card switch using the MFX expander, it is due to an improper use of the AND function in the BSP_SD_DetectITConfig() function. At line 429, it reads:if(((uint32_t)BSP_IO_ReadPin(0, PinDetect[Instance]) && PinDetect[Instance]) != PinDetect[Instance])The simplification of this line is to compare the pin state with the pin location. The BSP_IO_ReadPin function returns the status of 0 when the switch closed and 32768 for when the switch is open. The pin location on the expander is also at 32768 (pin15). If the switch is closed then the code in the Detect function needs to set to a rising edge interrupt. If the switch is open then the falling edge is desired so the next time the switch changes state the expander interrupts the MCU, so the sd process code can act accordingly.The bug is the use of "&&" instead o

Hi, can anybody tell me what partnumber this is. The chip is a LGA-14 package with the "SO" marking. It is probably an accelerometer.I aslo tried to read the 2d matrix code and it says: 781120R903QE

I've created a TouchGFX (TouchGFX Designer v 4.21.1) project using the STM32H7B3I-DK board. The project has a couple of gauges where I'm able to manipulate their setting based on a load cell being read through an ADC. Everything is working fine. Now I need to add a UART, so I modified the TouchGFX generated CubeMX (ver 6.7.0) IOC file to add UART4, using pins PH13, PH14 (goes to header on the discovery board). NO DMA, NO INTERRUPTS. FreeRTOS is being used. After re opening the newly generated code in CUBEIDE (ver 1.7.0), I simply build to make sure all is still ok. I get multiple instances of the following error (about 34 of them)C:/TouchGFXProjects/TrailerTest/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_uart.c:659:8: error: 'UART_HandleTypeDef' {aka 'struct __UART_HandleTypeDef'} has no member named 'RxEventType'Other errors are generated as well such as:C:/TouchGFXProjects/TrailerTest/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_uart.c:3734:24: error: 'HAL_UART_RXEVENT_TC' undec

..

Hello,I am testing a STM32C0 MCU to see if it might be good for a project I'm working on attracted by the price point, but I have to say that I have some unexpected problem.Among several the most relevant is multichannel DMA based ADC conversion that, no matter what I do, I can't have working.The application runs the error callback at the first conversion start.The ADC is in single conversion mode triggered by software and I have set a timer running every 50 milliseconds to run the conversion. I have also tried to connect the timer directly to the ADC to trigger automatically the conversion but the result is absolutely the same.The system is running at 48MHz.The conversion works correctly in interrupt mode on a single channel.Can anyone help?This is my code:#define ADC_CONVERTED_DATA_BUFFER_SIZE ( 2UL)   /* Init variable out of expected ADC conversion data range */ #define VAR_CONVERTED_DATA_INIT_VALUE (__LL_ADC_DIGITAL_SCALE(LL_ADC_RESOLUTION_12B) + 1)     extern TIM_Ha

aI don't have a scope but i can measure from multimeter, if it is there. I am guessing there is a bug or I am doing something wrong. I think software focuses on Pulse value and does not recognize __HAL_TIM_SET_COMPARE command. I uploaded the code. Anyone have an idea?

I aim to load my application at 0x08002000 instead of 0x08000000(base address) and secure the first two sections which will be used to store CRC and other firmware update information.I use a post-build script to calculate the CRC using srecord utility on application firmware and embed it into the executable at the base address.I also change the vector table offset to #define VECT_TAB_OFFSET     0x00002000U.but don't know why it was not working, following is my observation:1)When I just build & load the application firmware at the address of 0x08002000 without embedding CRC it was working.2)But when I embed CRC into the executable it was not working, I also verify flash contained and that it was loaded properly. (After loading cube-programmer gives a warning: The core is locked up)Am I missing any steps? Please help me here to resolve my issue.

We use Stm32G030C8 for our project, which has only 16bit timers.But we need 32bit timer, therefore we are going to combine two timers.We could combine TIM1 with TIM3 successfully – TIM1 as slave and TIM3 as internal trigger (ITR2).Unfortunately we need TIM3 for other purposes, so are going to use TIM17 OC1 as internal trigger as shown in documentation RM0454 below.But it doesn’t work. Please check our setting for each timers and give us advice to solve this problem.  RM0454 Rev5 : Page 402Table 69. TIM1 internal trigger connectionSlave TIM : TIM1 ITR0 (TS = 00000) : TIM15 ITR1 (TS = 00001) : Not connected ITR2 (TS = 00010) : TIM3ITR3 (TS = 00011) : TIM17 OC1(We have a 64 MHz internal clock.Prescaler for TIM17 is set with 63, because TIM17 should tick every 1 micro second. )For TIM1 we have following setting : LL_TIM_InitTypeDef TIM_InitStruct = {0}; LL_APB2_GRP1_EnableClock(LL_APB2_GRP1_PERIPH_TIM1); TIM_InitStruct.Prescaler = 0; TIM_InitStruct.CounterMode

I am using the SW pins as GPIO outputs for Softpwm generation.(DMA+GPIO)All works great if i do "continue", but when i decide to "migrate" the cubeMx to the last version and i click regenerate code.... the SWDIO and SWCLK pins are not used as GPIO outputs.

Greetings good people of ST communityI have a problem which I didn't manage to solve by myself, so I am hoping to get some help if possibleI have an LPS22HB sensor (https://eu.mouser.com/datasheet/2/389/lps22hb-1849683.pdf), and I want to connect it to STM32L010K8T6 MCU using SPI. The problem is, I get some temperature register readings with STM studio but they are invalid (0, 128, 255). In settings, the MCU CS pin is a pull-up, while pins SCK, MISO, MOSI are no pull-up and no pull-down. All of them are in push-pull mode.These are my SPI setting in the code:hspi1.Instance = SPI1; hspi1.Init.Mode = SPI_MODE_MASTER; hspi1.Init.Direction = SPI_DIRECTION_2LINES; hspi1.Init.DataSize = SPI_DATASIZE_8BIT; hspi1.Init.CLKPolarity = SPI_POLARITY_HIGH; hspi1.Init.CLKPhase = SPI_PHASE_1EDGE; hspi1.Init.NSS = SPI_NSS_SOFT; hspi1.Init.BaudRatePrescaler = SPI_BAUDRATEPRESCALER_256; hspi1.Init.FirstBit = SPI_FIRSTBIT_MSB; hspi1.Init.TIMode = SPI_TIMODE_DISABLE; hspi1.Init.CRCCalculation

ProblemI'm having an issue with my USB peripheral in the STM32F303ZE. Right now I'm capable of receiving the first request from the host after reset, which is a GET_DESCRIPTOR request. I populate the TX buffer and set the EP0R register to VALID for TX. I then get interrupted for an IN request, meaning the host ACKed my TX data (which I assume means the data was transmitted successfully) and then I receive an OUT status to finish the control transfer. And then I receive a reset and do this all over again two more times, resulting in the device failing to enumerate.What confuses me is that, from experience programming USB on a different MCU, I know I should be receiving a reset partway through transferring my device descriptor, yet the entire request goes through and then I receive the reset afterwards. While it may be possible that the host is letting my transfer complete, I still don't receive a SET_ADDRESS setup packet afterwards. As I said above, it just repeats over and over. My hop

I am trying to understand how to configure a custom GPIO pin via the CubeMX/CubeIDE. I am using the STM32H7B3I-EVAL. Through the CubeMX, I am trying to assign PA13 to a GPIO (in output mode). I enabled PA13 via the CubeMX without issue. Now I want to configure the GPIO in the CubeIDE and use it. In the GPIO Example for my STM32H7B3I-EVAl board, they configure it as follows: /* Configure IO in output push-pull mode to drive external LEDs */ gpio_init_structure.Mode = GPIO_MODE_OUTPUT_PP; gpio_init_structure.Pull = GPIO_PULLUP; gpio_init_structure.Speed = GPIO_SPEED_FREQ_VERY_HIGH; gpio_init_structure.Pin = GPIO_PIN_13; HAL_GPIO_Init(GPIOG, &gpio_init_structure);What I don't understand is how they knew that gpio_init_structure.Pin = GPIO_PIN_13. How did the example know to use PIN_13? How do I know which pin PA15 should be?

I am using below code;void HAL_UARTEx_RxEventCallback(UART_HandleTypeDef *huart, uint16_t Size){ if (huart->Instance == USART3) { oldPos = newPos; // Update the last position before copying new data // If the data is large and it is about to exceed the buffer size, we have to route it to the start of the buffer // This is to maintain the circular buffer // The old data in the main buffer will be overlapped if (oldPos+Size > MainBuf_SIZE) // If the current position + new data size is greater than the main buffer { uint16_t datatocopy = MainBuf_SIZE-oldPos; // find out how much space is left in the main buffer memcpy ((uint8_t *)MainBuf+oldPos, RxBuf, datatocopy); // copy data in that remaining space oldPos = 0; // point to the start of the buffer memcpy ((uint8_t *)MainBuf, (uint8_t *)RxBuf+datatocopy, (Size-datatocopy)); // copy the remaining data newPos = (Size-datatocopy); // update the position } // if the current position

Hi good day, could you guys please tell me where i can get the STM32G0B1KBT6 flash module organization Table? i've looked for it on datasheet but found nothing

Do we need to compile CUBEMX dts files before bitbake or we need to convert them into the dtb files with eclipse like in this ST video and what is the best way to go from discovery board to custom board in the means of creating device tree files for peripherals and all. I need some guidance.

Hi,   I at a high level I have designed a program to toggle the user LED on PA5 if a gpio input sees a high signal (shorter than 150ms) on PA0.   The program works well most of the time except in some instances when it will miss an input pulse entirely, seemingly for no reason. I have checked my timer delay function and even switched to a for loop style delay. This allowed me to validate that my timer was not the issue.   The bug only occurs when the output pin is low. (Never when it is high)   Scope Captures of Normal Operation (Input - yellow; Output - blue)   Scope Capture of the Insidious Bug   Here is the main function code and I've attached a copy of the project below also. #include <Input_Capture.h> #include <tim.h> #include "stm32f4xx.h"   int main(void) { /* Set GPIO Pin A0 to Input Capture Mode */ gpio_a_init(); IOPA0_Input_cfg(); IOPA5_Output_cfg(); tim3_150ms_init();   while(1) { ////////// The LED CLAPPER LOGIC

I connected JP1 part to 3.3V pin, Gnd to Gnd pin, Mosı, Mıso, CS and Clk pin to CS,Mosı,mıso, sck pins of the microcontroller in CN7 with the help of jumpers.Bu't I dont know where my DCMI connection(CN4) and shutter, flash connection get interacted with nucle 144 board via using only jumpers. My aim is to get live view from the camera to control my output with buzzer or something else. All connecitons I checked from the internet are done with a display camare done with FFC Cable but ı am trying to connect the module to microcontroller via only using jumper cablesthanks

My test program for my STM32F746VET6 is extremely simple. Other than MX configuring the clock and GPIO, I only have a while loop that flashes some LEDS and then divides by zero. while (1) { /* USER CODE END WHILE */ uint32_t bobbycounter = 0; uint32_t bobbycounter2 = 0; while(1) { if(bobbycounter++ & 0x100000) { STATUS_LED_1_GPIO_Port->ODR &= ~STATUS_LED_1_Pin; STATUS_LED_2_GPIO_Port->ODR |= STATUS_LED_2_Pin; } else { STATUS_LED_1_GPIO_Port->ODR |= STATUS_LED_1_Pin; STATUS_LED_2_GPIO_Port->ODR &= ~STATUS_LED_2_Pin; }   if(bobbycounter > 0x800000) { bobbycounter = bobbycounter / bobbycounter2; } }When I debug in MX, I get the expected behavior where I enter the HardFault_Handler and then flash the LEDS at a faster rate forever:void HardFault_Handler(void) { /* USER CODE BEGIN HardFault_IRQn 0 */   /* USER CODE END HardFault_IRQn 0 */ uint32_t bobbycounter_hf = 0; while (1) { /* USER CODE BEGIN W1_HardFault_IRQn 0 */ if(bobby

My biggest issue currently is on my external app which is connecting to the WB that it cannot get the descriptor.As I debug using BLE using LightBlue there is no descriptor in my characteristic. As I notice recently by reading again the manual there is a command aci_gatt_add_char_desc() which in my opinion add the missing descriptor. By generating the default project with cubeMX, this function is never called. As there are no comments in the code, neither any documentation about this routine, this makes it hard to implement correctly. This would really helpful if the documentation could be extended (@Remy ISSALYS​ ). Thanks in advance!

HiI try to read the WHO_AM_I register using SPI but I get 0xB3 instead of 0xB1. Is this correct?Regards

I am using a STM32H723zg board for a project and I must read analog signals so I am using one 16-bit ADC. Based on the datasheet of this microcontroller serie, the maximum ADC clock frequency is 50 MHz for BOOST = 11.However when I am configuring the ADC clock frequency with the STM32CubeMX, the ADC clock is automatically set with 96 MHz with no error. I would like to know if this ADC clock frequency configuration (96 MHz) affects negatively to the performance of the ADC (noise or erros in measurements) and if this ADC clock frequency is actually used by the microcontroller or if the microcontroller automatically uses another frequency that does not exceed 50 MHz.I didn't find anything very useful in the documentation related to this question.

I am using a Nx_Webserver application example from STM32H735G-DK modified for STM32H743i-Eval. I have moved the Rx, Tx, NetXPool references to RAM_D2 and I find that I get an error when the linker runs if the RxDecripSection and TxDecripSection name matches that which is in main. If the names are different it links fine and the map shows the sections mentioned in 0x240xxxxx. Not what I want.the likker script looks like this:/* Entry Point */ ENTRY(Reset_Handler)   /* Highest address of the user mode stack */ _estack = ORIGIN(RAM_D1) + LENGTH(RAM_D1); /* end of RAM */ /* Generate a link error if heap and stack don't fit into RAM */ _Min_Heap_Size = 0x200; /* required amount of heap */ _Min_Stack_Size = 0x400; /* required amount of stack */   /* Specify the memory areas */ MEMORY { FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 2048K DTCMRAM (xrw) : ORIGIN = 0x20000000, LENGTH = 128K RAM_D1 (xrw) : ORIGIN = 0x24000000, LENGTH = 512K RAM_D2 (xrw) : ORIGIN = 0x30000000, LENGTH =

We've been building a PCB with four STM32F091s on each PCB and we've built about 50 units by now (over about 3 years). I have now seen three PCBs where the ADC readings are 'bad' on two of the four micros. By 'bad' I mean conversion values are 30% ish low. With the design having been stable for quite a while, the chances of uncovering a new bug seem slim, but chip damage seems even more unlikely. The fault also 'went away' on one of the PCBs, so more evidence that it's not damage.The ADC reference is VDD 3.3V on all the chips, and they all run the same code.Anyone got any thoughts?

Hi!Our incoming inspection unit failed to find any information on LSM6DSLTR device marking. We got parts with 2 lines on it.SF2D code106 Could you please confirm it is a LSM6DSLTR device? Is there date code on it?