Solved

I'm learning the makefile that generated by cubeMX, but there are some parameters I can't understand.In the part that called "build the application", I saw:$(BUILD_DIR)/%.o: %.c Makefile | $(BUILD_DIR) $(CC) -c $(CFLAGS) -Wa,-a,-ad,-alms=$(BUILD_DIR)/$(notdir $(<:.c=.lst)) $< -o $@I don't know what the parameters `-Wa` , `-a` , `-ad` and `-alms` mean. I checked the GCC manual, but only found the description of -Wa:-Wa,optionPass option as an option to the assembler. If option contains commas, it is split into multiple options at the commas.These cant help of my question.I realy want to know what do these four parameters mean.

I'm trying to generate periodic interrupts with an LPTIM on an STM32H723. I'm using HAL_LPTIM_Counter_Start_IT() from the STM32H7xx_HAL_Driver. My interrupt handler is never being called. I've confirmed that my interrupt handler is in the vector table and at the offset specified in the STM32H723 reference manual. Here's my code for starting up LPTIM1.void lptim1_start(void) { uint32_t period = 500;   hlptim1.Instance = LPTIM1; hlptim1.Init.Clock.Source = LPTIM_CLOCKSOURCE_APBCLOCK_LPOSC; hlptim1.Init.Clock.Prescaler = LPTIM_PRESCALER_DIV1; hlptim1.Init.Trigger.Source = LPTIM_TRIGSOURCE_SOFTWARE; hlptim1.Init.OutputPolarity = LPTIM_OUTPUTPOLARITY_HIGH; hlptim1.Init.UpdateMode = LPTIM_UPDATE_IMMEDIATE; hlptim1.Init.CounterSource = LPTIM_COUNTERSOURCE_INTERNAL; hlptim1.Init.Input1Source = LPTIM_INPUT1SOURCE_GPIO; hlptim1.Init.Input2Source = LPTIM_INPUT2SOURCE_GPIO;   HAL_LPTIM_Init(&hlptim1);   HAL_LPTIM_RegisterCallback(&hlptim1, HAL_LPTIM_AUTORELOAD_MA

Hello,I would like to know how to prevent the execution of the on chip bootloader after a RDP regression from level 1 to level 0. After the necessary option byte load (OBL) a mass erase is done and the chip is reset and after the reset the bootloader is executed.Since I am programming all option bytes, I have played with different values for option bits nBOOT0, nBOOT1 and nBOOT_SEL but no combination will do the trick...Thank you!

How can I find the source code of ST BLE Toolbox?Is there any experience with Flutter or React and which Libraries are useful. Is there someone who has already implemented this successfully or should it be better to use other development environments? What can I look for what are the key points. Thanks very much Best Regards Hainer

I am attempting to use the LPF2 chain on the LSM6 accelerometers. The cut-off frequency is described as something like ODR_XL/100. I assume that means if you are running at 12.5 Hz the cutoff frequency is then .125 Hz. I am assuming that this is the 3 dB cutoff of the filter? I am still getting mechanical noise to make its way into the accelerometer response, so I am wondering what the actual design of the filter is. Is it just a single pole filter? Basically just a moving average of a 100 samples. Or is it a multi pole filter? and if so how many poles?Thanks!

I am writing a driver to retrieve data from the I3G4250D gyroscope embedded in the STM32F411VE discovery board (MB1115D). When the sensor starts up, the first 1 second of data contains an invalid temperature value (typically showing -7). After one second this value changes and is accurate from then on. I noticed from the datasheet that there is a 1 Hz refresh rate for the temperature, which makes sense given what I'm seeing. I'm wondering if there's a way I can retrieve valid temperature data earlier than 1 second, i.e. if I can delay when this refresh rate begins. This temperature data is critical for our calibration calculations, so having bad data is messing up our algorithms.

Hi!I try to understand debug information after hard fault. RTOS dump DFSR register (and some other) after fault to UART. This register is not present in PM0253 programming manual, but there is definition in source code (core_cm7.h address is 0xE000ED30), also this register is described on correspond ARM web page doucmentation.So, is there description of the DFSR register in manuals by ST? Is there this register in MCU?

Hi! We have been evaluating a few accelerometers from ST. So far we have seen reasonable results from H3LIS100 and H3LIS200 devices.However, H3LIS331DLTR is behaving contrary to our expectations.We have the H3LIS331DLTR device on a PCB, interfaced via SPI with a microcontroller.The H3LIS331DLTR device is mounted on the PCB such that the Z-axis of the H3LIS331DLTR device is perpendicular to the ground. The X and Y axes are in the plane of the PCB.We have configured the H3LIS331 device with the following settings:High-pass filter disabled (this is intentional)Output data rate: 400HzReference mode: normalBlock Data Update bit is set, so that both high and low byte of measurement can be readFull-Scale bits are set to 00 (hence +/-100G full scale measurements)Acquisition mode: polling by checking XYZ data ready flag in status registerHowever, we are reading +30G on the Z-axis measurement. When we flip the PCB over, we are reading +15G on the Z-axis measurement.The delta between the two meas

I am trying to configure the TIM2_CH4 to capture mode on EV1 board so I can sense a fan speed from a PWM fan but I keep getting cat: read error: Connection timed outI have configured the timer as follows: &timers2{ pinctrl-names = "default", "sleep"; pinctrl-0 = <&tim2_pins_mx>; pinctrl-1 = <&tim2_sleep_pins_mx>; status = "okay";   /* USER CODE BEGIN timers2 */ dma-names = "ch3"; pwm { /* enable PWM on TIM2 */ status = "okay"; }; /* USER CODE END timers2 */ }; tim2_pins_mx: tim2_mx-0 { pins { pinmux = <STM32_PINMUX('A', 3, AF1)>; /* TIM2_CH4 */ bias-disable; drive-push-pull; slew-rate = <0>; }; };   tim2_sleep_pins_mx: tim2_sleep_mx-0 { pins { pinmux = <STM32_PINMUX('A', 3, ANALOG)>; /* TIM2_CH4 */ }; };I am using TIM12_CH1 to generate a pulse and I have shorted the two pins on the board.What am I doing wrong? Is there a better way to detect the sense on a PWM fan?

External memory, connected to a STM32MP1, is written with the STM32CubeProgrammer via USB. Here the chip to be written is written with "usb1" (STM32_Programmer.sh -c port=usb1 -d some.tsv").Here we could notice the following behavior: If more than one STM32MP1 is connected to the host system via USB, another label (usb2) is assigned. If a higher serial number is connected later, it will be assigned to usb1, and the already connected device will be assigned the new label usb2. The connected devices are displayed in the device manager as DFU Devices. There is no COM port assignment.This raises the question of how several devices can be connected to a host at the same time and assigned uniquely to enable several devices to be flashed in parallel.What is the best practice to guarantee consistent addressing of the boards.

In all the STM32s that have I2S / SAIs and ethernet that I've checked, there is this fixed oversampling ratio of 256 between master clock and sampling rate.When using the internal PLL to get the sampling clocks, no problem (amazing how good and stable these clocks are, even with the 8 MHz from the STLink, checked it with generating 24bit/192k SPDIF signals).But in my case I must use the extra "Audio Clock Input (I2S_CKIN)", which does not have the benefit of getting modified by a PLL.So my problem now: how do I get 3 different sampling rates (e.g. 48k / 96k / 192k) without dividing the clock (done that, but no space available) outside of the STM32 ?And without any downsampling by the CPU.Any ideas? Something I have overseen?

Hi,I am using touchGFX4.16.I copied the project folder for backup.When I tried to use touchGFX in the backed up project folder, an attached image warning appeared.1) What does it mean?2) What should I do to get rid of the warning? Best regards,

Per the title, I'm using USART2 with DMA transfer but for some reason the line stays LOW (active) before/after transmision.Init code is pure HAL generated, I added a "DeInit" just to make sure the UART enable wasn't persisting between resets/debug sessions but it's made no difference.No matter what I do with the control registers (UART_ADVFEATURE_TXINV / UART_ADVFEATURE_DATAINV), the data output & idle state don't seem to change.EDIT: DATAINV and/or TXINV do seem to invert the data bits but the idle line is *always* LOW when there's no data no matter what.Is this some edge case where using DMA transfer keeps the UART "active" all the time rather than releasing it to "idle" once transfer is complete?EDIT #3: It appears HAL_HalfDuplex_Init means the UART behaves this way, using HAL_UART_Init seems to allow the TX line to idle high, although now the data appears to be wrong whichever way up I invert it. Ghaaa,void MX_USART2_UART_Init(void) {   /* USER CODE BEGIN USART2_Init 0 */

I wonder whether I can connect two quad spi ap memory to the same octospi interface on stm32h730 to double the bandwidth. Or such a configuration can only be used with nor flash, not psram. Thanks.

..

Hello, is there any way to use EXTI simultaneously in different ports with the same pin number?Examples for MCU STM32L071CB:Using PA4 and PB4, orUsing PA10 and PB10, orUsing PA6 and PB6, and so on

Hi, We are trying to measure distance from our sensor through an IR Translucent plastic to a curved metal surface, using a VL53L1X. We are getting reasonable results by they are rather noisy (~10% deviation at times)What sort of changes should we be experimenting with to reduce noise in our signal?

I am working with the STM32L4S9AII6 MCU on a project where I am being asked to replace an FPGA implementation with this CPU. We are maxing out all 14 DMA streams via SPIs, I2Cs, & UART. As you can imagine, I am working with some serious hard real-time deadlines. I am using FreeRTOS.I think this is a confusing topic to discuss over a forum, so let me use an example to pose my question. Lets say I have 2 SPI peripherals configured. We'll call them SPI1 & SPI2. Both transmit at say 10MHz or whatever. Both are configured to transmit in 8 bits (1 byte) at a time. Both NSS lines are controlled through software to allow this enable line to be pulled low for the entire duration of a block transfer (multiple bytes per DMA request). Now lets say SPI1 attempts to transmit a block of 8 bytes. Immediately after, SPI2 also attempts to transmit a block of 8 bytes. Question: Does the DMA engine block on SPI1 until SPI1 has finished transmitting all 8 bytes and then allow SPI2 to begin transmit

Hi,I am currently working on a bluetooth application developing it on STM32WB55 Nucleo (FW version V1.13.1, BLE Stack Full)Since the device will have to be connected to a battery, I was researching the use of Low Power modes.Unfortunately, I'm not clear on the correct procedure to send in STOP2 mode the whole system, keeping the bluetooth active, I've already read questions on the forum and examples provided by ST but I'm not very clear on the whole procedure.Reading on the forum, I understood that the second core is self-managing with regard to low power, and the first core can not control it otherwise it would break the power management.Hence, there would be my questions:- The correct procedure to follow on the first core, to send it into STOP 2, what would it be?- Would there be any initialization or procedure to take into account to do also for the second core at the beginning?- Since the system will go in that mode only when both cores are in the same state, how can I control the

HAL_PWR_EnterSTANDBYMode() will still wait properly, but HAL_PWREx_EnterSHUTDOWNMode() will immediately return to RUN mode.What do you think is the cause of immediate wakeup?​As shown below, the only code difference is whether to enable HAL_PWREx_EnterSHUTDOWNMode () or HAL_PWR_EnterSTANDBYMode (). __HAL_PWR_CLEAR_FLAG(PWR_FLAG_WU); __HAL_PWR_CLEAR_FLAG(PWR_FLAG_SB); __HAL_RTC_WAKEUPTIMER_CLEAR_FLAG(&hrtc, RTC_FLAG_WUTF); while(1) { HAL_PWREx_EnterSHUTDOWNMode(); // HAL_PWR_EnterSTANDBYMode(); }Best regards,​

I've been trying to develop a C++ application which uses the C based MC SDK (would really be nice if STM would provide a supported wrapper). I'm getting:arm-none-eabi-g++ -o "nucleo_demo_y4.elf" @"objects.list" -mcpu=cortex-m4 -T"C:\Users\dustin\repos\wheel\nucleo_demo_y4\STM32CubeIDE\STM32F302R8TX_FLASH.ld" --specs=nosys.specs -Wl,-Map="nucleo_demo_y4.map" -Wl,--cref -Wl,--gc-sections -static --specs=nano.specs -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mthumb -Wl,--start-group -lc -lm -lstdc++ -lsupc++ -Wl,--end-group c:\st\stm32cubeide_1.8.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_2.0.0.202105311346\tools\arm-none-eabi\bin\ld.exe: ./Application/User/wheel_ctrl.o: in function `Wheel::WheelCtrl::GetParam(Driver::CANDataPacket*)': C:/Users/dustin/repos/wheel/nucleo_demo_y4/STM32CubeIDE/Debug/../Application/User/wheel_ctrl.cpp:62: undefined reference to `RI_GetRegCommandParser(MCP_Handle_t*, unsigned short)' collect2.exe: error: ld

Have a file and I am trying to transfer it to SAI2. For some reason ???? I am not getting into the DMA Callback. DMA is in normal mode. Can anyone shed any light on this? /* USER CODE BEGIN 2 */ HAL_DMA_RegisterCallback(&hdma_sai2_a, HAL_DMA_XFER_CPLT_CB_ID, &DMA_XferCmplt_Callback); /* USER CODE END 2 */   /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) { if (ISR.DMA_TxCmplt) { ISR.DMA_TxCmplt = F; /* * after each DMA check if high current * if NOT then disable SAI dma */ if (adcValue[1] < (HIGH_CURRENT)) hsai_BlockA2.Instance->CR1 &= ~SAI_xCR1_DMAEN; }   if (ISR.A_ConversionComplete) { ISR.A_ConversionComplete = F; /* * checks to see if actuator has * bottomed out due to high current */ if (adcValue[1] > (HIGH_CURRENT)) { hsai_BlockA2.Instance->CR1 |= SAI_xCR1_DMAEN;   /* * if we are engaging and high current * shut off motor drive and alarm */ if (ISR.

Hi,1- How do I let CubeMX know the SD pin detect, I've set pin PC13 as card_detect, GPIO input, pull-up, but then what?2- Should I use the open source FATFS "https://elm-chan.org/fsw/ff/00index_e.html"? How?Thank you

I thought HANDLE was part of the stm32 hal library so I tried including stm32h7xx_hal.h however it did not resolve the issue

In our application, we don't necessarily need to know the true distance, we only need to know when it's in a certain range, and it doesn't matter if that range is represented as 30-40mm or 50-60mm, only that is consistent. Can we get away with not needing calibration if this is the case?We are using a VL53L1X aimed through a IR transparent plastic.