Solved

Hello,When I plug this board to my computer, appears a removable disk of 1,6 MB capacity.Is this disk accessible from the MCU? For store small data, or make a dataloggerWhere the filesystem is stored? Neither the STM32F446RE nor STM32F103CB of the STlink have enough capacity 

Hello,I want to connect X-NUCLEO-IHM11M1 module with a NUCLEO-G071RB board, but when I select it in the MC Workbench, I get this error:It is not possible to create a motor control project with the FOC algorithm using the selected hardware. No proper path for motor control signals was found for the following mandatory features: - Phase Voltage GenerationFor more details, please, look at the following log file in your home directory: .st_workbench/connectAlgo.logHere is the content of the connectAlgo.log file:INFO - --root assets --control NUCLEO-G071RB --power X-NUCLEO-IHM11M1DEBUG - General: --- Processing start NUCLEO-G071RB X-NUCLEO-IHM11M1DEBUG - SWConnect: SingleShunt_AmplifiedCurrents Global processing startDEBUG - SWConnect: SingleShunt_AmplifiedCurrents Global processing completedDEBUG - SWConnect: SingleErrorTrigger_FixedReference Global processing startDEBUG - SWConnect: SingleErrorTrigger_FixedReference Global processing completedDEBUG - PVConnect: DrivingHighAndLowSides Glob

Need to IAP save two 16(10) bit ADC values to EEROM. Done parm saves before in STM8S105, but want to see it in ICP mode.In NXP MC9S08, I can turn off download, which cleared Its EEROM. That let me run the ADC "learn" of the values, save them to EEROM, then power cycle and see them retained.I'm thinking running debug without download will be the same, but I can't find it.SO, I want to test "stuff" two values to EEROM, power down / up, invoke Debug (ICP) and see them preserved.Trusting IAP to get/save values without verifying doesn't sit well. Like Reagan: Engineers don't Trust - they Verify!Deeply appreciate my "betters", everybody old enough has been on BOTH sides of this!!  Thanks, Kevin

I am working on X-CUBE-AZURE in B-U585I-IOT02A board. My IDE version is 1.18 and i am using Fedora 41. When i enable FDCAN peripheral in CubeMX it places the stm32u5xx_hal_fdcan.c and .h file into the X-CUBE-AZURE/Drivers/STM32U5xx_HAL_Driver/Src. Even though it places the correct .c and .h files the build fails when i enable FDCAN from CubeMX. Here is the build error message./home/erhangok/Documents/GitHub/IOT_Node_Azure_v01fw/Projects/B-U585I-IOT02A/Applications/NetXDuo/Nx_Azure_IoT/Core/Src/main.c:357:(.text.MX_FDCAN1_Init+0x72): undefined reference to `HAL_FDCAN_Init' collect2: error: ld returned 1 exit status make: *** [makefile:104: Nx_Azure_IoT.elf] Error 1 "make -j8 all" terminated with exit code 2. Build might be incomplete. 15:41:47 Build Failed. 2 errors, 478 warnings. (took 19s.801ms)Even though the file exists in Drivers/STM32U5xx_HAL_Driver it still cannot find it. When i look further into this i saw that subdir.mk file does not contain this line: "./Drivers/STM32U5xx_HA

Hello everyoneIt's my first time messing around with STM32 microcontrollersA few days back I got a black pill (STM32F401CCU6 - https://robu.in/product/stm32f401ccu6-minimum-system-board-microcomputer-stm32-arm-core-board/) and an ST-Link V2. The black pill came with 3 buttons, namely (KEY, NRST, BOOT0) and a USB-C Port. Since the ST-Link was arriving later, I connected the black pill to my PC through USB-C. The PWR LED on the black pill turned on. I pressed down the boot0 button, clicked the nrst button and then released the boot0 button to enter the dfu mode (according to the guides I saw online) I fired up the Arduino IDE, wrote a tiny blink program, and it worked.A few days later, I got the ST-Link V2. I connected the SWCLK, SWDIO, GND and 3.3V terminals to the black pill as I found online, and connected the ST-Link to my computer. The LED inside the ST-Link turns on, but the PWR LED on the black pill doesn't turn on. The ST-Link is detected by the STM32CubeIDE, I also did a firmwar

Hi,     The default ADC clock source is PLL2P = 80 Mhz in my Cubemax "Clock Configuration" TAB.      I can use ADC clock Prescaller to lower it below 50 Mhz. 50Mhz is the max vale for ADC clock.      Question: The default setting PLL2P = 80Mhz before applying the ADC Prescaller is allowed or disallowed?                        If it is disallowed, how to lower PLL2P in Cubemax "Clock Configuration" TAB. without changing all other clock's default settings?         Thanks Rong     

Hi,In my next project I would like to use 2 type of displays. One with MIPI DSI interface and the other with parallel RGB.That is why I chose microcontrollers from the STM32U5 series ( vector graphics accelelator ).According to the information on the ST website, the series (100 pin):STM32U5G7VJ and U5F7VJ support RGB interface and STM32U5G9VJ and U5F9VJ support MIPI DSIHowever, inside the datasheet of the series: STM32U5F7xx in the section describing the pin layout there are 2 types of 100 pin packages:"LQFP100 SMPS" - there is no MIPI DSI pins"LQFP100 DSI SMPS" - has pins to support MIPI DSI (7,8,10,11)And now I am completely confused.The question is which STM32U5xxxx (100pin) chip should I order to support RGB and which one to support MIPI DSI ??Tomasz

Hello,I have designed a custom STM32 module using the STM32H7A3RGT6 microcontroller. In my design, PB9 is connected to an LED, and to verify the module's functionality, I attempted to toggle this LED.Here’s where the issue arises: According to the STM32H7A3RGT6 reference manual, GPIOB is connected to the AHB4 bus, meaning its peripheral clock should be enabled using RCC_AHB4ENR. The manual specifies an offset of 0x140 for this register. However, when I use this offset in my code, the LED does not toggle, suggesting that the address is incorrect.Interestingly, when I asked ChatGPT for the correct offset, it provided 0xE0—and when I used this value, the LED toggled successfully!This raises concerns about the correctness of the reference manual or suggests that I may be missing something. Could you clarify why there is a discrepancy in the RCC_AHB4ENR address?Here are my codes:GPIO_DRIVER.H Code#ifndef INC_STM32H7A3XX_GPIO_DRIVER_H_#define INC_STM32H7A3XX_GPIO_DRIVER_H_ #ifndef GPIO_

Hello,I am encountering an issue when converting a TensorFlow Dense layer to .tflite and subsequently using the ST Edge AI tool to convert it to .nb format, following the ST Edge AI Guide for MPU.When using a lower-dimensional input, the conversion succeeds. For example, the following code works as expected: input_features = tf.keras.Input(shape=(1, 384), dtype=tf.float32) output = tf.keras.layers.Dense(1536)(input_features) model = tf.keras.Model(inputs=input_features, outputs=output) However, increasing the input dimension to (1500, 384) results in the following error: ST Edge AI Core v2.0.0-20049 PASS: 0%| | 0/2 [00:00<?, ?it/s]Galcore warning: MMU is disabled! E [main.c:vnn_VerifyGraph:93]CHECK STATUS(-3:The requested set of parameters produce a configuration that cannot be supported.) E [main.c:main:236]CHECK STATUS(-3:The requested set of parameters produce a configuration that cannot be supported.) E 21:37:15 Fatal model generation error: 64768 E010(InvalidMode

I'm using a Nucleo-U575ZI-Q board to test Azure USBx MSC storage protocol strack against an Ubuntu-16.04 LTS host, using STM sample MSC code stripped down with a dummy interface against local storage.A Beagle USB 5000v2 is connected between host and device so that I can capture USB traffic. Enumeration works fine and host starts to talk MSC to device over ep 0x01 and 0x81, probing it for number of LUN, capacity, test-unit-ready and so forth, but no request for media transfer (rd/wr). But with 100% certianty it fails on the 24'th command which is a MSC Test-Unit-Ready.Bus analyser show that Command Transport packet is correct on the bus, and device endpoint has ACK'ed the packet. But when MCU calls HAL_PCD_IRQHandler() and reads out OTG_FS::GRXSTSP::EPNUM, it points to an unconfigured endpoint (usually 15). Also, very often, the PKTSTS field of GRXSTSP contain a value that acc.to speification is Reserved. One odd thing is that BCNT field is always 0x6b6 which is way off for what a FS bu

i generated the code using the workbench for stm32h755ziq and the motor driver ihm07m1 with a 12v bldc motor...and i have called the api's for motor start as well in the main code ...but after downloading it into nucleo..i cant see any pwm signals on the respective pins of nucleo ...?(assume me i'm completely new to this thing)

I want to transfer a buffer and receive a buffer of data using a full duplex SPI port with DMA on a STM32H7S3L8H (on the NUCLEO-H7S3L8). My problem is I am not able to modify the transfer buffer and have the modified version sent. I only need to modify the 1st two bytes. Here's the code:void ade9430_read_it(SPI_HandleTypeDef *hspi, uint16_t reg_addr, uint8_t *reg_data) { //int ret = HAL_OK; //gTxData[0] = reg_addr >> 4; //gTxData[1] = ADE9430_SPI_READ | reg_addr << 4; uint16_t Size; //in bytes if (reg_addr >= 0x800) { static uint8_t gTxDmaData[60] = {0}; //{0x80, 0x18}; Size = 30; //debug test gTxDmaData[0] = reg_addr >> 4; gTxDmaData[1] = ADE9430_SPI_READ | reg_addr << 4; HAL_SPI_TransmitReceive_DMA(hspi, (uint8_t *)gTxDmaData, reg_data, Size); //debug DMA test }Here is the resulting SPI activity:Based on the reg_addr being passed the first two values should of been 0x80, 0x18.Setting a breakpoint on line 14 and looking at the gTxDma

I’m trying to replace a blocking call to HAL_I2C_Master_Transmit() with the interrupt version HAL_I2C_Master_Transmit_IT(). The blocking HAL_I2C_Master_Transmit() call works perfectly. The HAL_I2C_Master_Transmit_IT() call sends completely different data. Specifically:My buffer contains: 00 00 00 00 00 00 00 BF 00 3F 00 00 00 00 00 00 00When I call HAL_I2C_Master_Transmit(&hi2c4, I2C_ADDRESS, buffer, 17, 100), I see this:When I call HAL_I2C_Master_Transmit_IT(&hi2c4, I2C_ADDRESS, buffer, 17), I see unrecognized data:I’m using a STM32H755.

Hello,Does anyone from ST actually monitor these forums, and will some of these reported problems get fixed in upcoming releases? or is there another forum or ticket process that needs to get started?

I just received a NUCLEO-H503RB dev board, and while attempting to use the GPIO_IOToggle example program to test out the board, I could not run the debugger due to the error "ST-Link not detected." I went back to my NUCLEO-H7S3L8 board, it now receives the same error. A few days ago, I was able to program it.I was able to detect the ST-Link with my NUCLEO-F446RE board.Do I need to reinstall ST-Link or is there a way to force a firmware update on my two NUCLEO USBC dev kits? Thank you.

Hello,I would like some advice on understanding a code with an example provided with the STM32L5xx evaluation board. I have this code below : /* Initialize the data buffer */ for(int i=0; i < PLAY_BUFF_SIZE; i+=2) { PlayBuff[i]=*((__IO uint16_t *)(AUDIO_FILE_ADDRESS + PLAY_HEADER + i)); }PLAY_BUFF_SIZE = 4096 uint16_t PlayBuff [PLAY_BUFF_SIZE]; #define AUDIO_FILE_ADDRESS 0x08040000 #define PLAY_HEADER 0x2C I understand a little bit but where does the value 0x2C come from, what does it come from ? What does PLAY_HEADER mean ?Thank you for your helps.

Greetings,I would like to know, in summary, what are the key main differences between RDP (ReadOut Protection) and PcROP (Proprietary Code Readout Protection), which one is safer and use cases.Thank you!

HelloI want to implement some filters on the two audio channels in the BLE_Audio_PBP_Sink example project.Where in the code would you recommend that i implement these filters. Where can i without problems alter the audio streams.Are there any documentation that explains the audio paths through out the system, with references to the code?Kind regards Malte F. Developer

I am using the STMG0B1RET on a custom, battery-powered board. During normal operation pin PC4 is used as UART1 (with an external pull-up resistor). In Standby Mode pin PC4 must be LOW in order to shut down the external device. For this I convert PC4 to GPIO and configure it for pull-down in Standby Mode to achieve the 0V at the output.It is not working. When the HAL function HAL_PWR_EnterSTANDBYMode() is called the output goes HI.I studied several posts and discussions about this issue, but no success yet.The below is the latest code snipped. Wakeup pin 6 is used to exit Standby Mode (that works).This line seems to pull the output to HI.  Why?SCB->SCR |= SCB_SCR_SLEEPDEEP_Msk; What else can we try? Thank you!!/* Convert UART1 IO to a GPIO */ GPIO_InitTypeDef GPIO_InitStruct = {0}; HAL_GPIO_WritePin(UART1_GPIO_Port, UART1_Pin, GPIO_PIN_RESET); /*Configure GPIO pin : UART1_Pin */ GPIO_InitStruct.Pin = UART1_Pin; GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP; GPIO_InitStru

..

Hi, I had to recently work on an application that makes use of the UART, and encountered some issues in the HAL (most recent version provided by CubeMX):1) Hal bug?Drivers/STM32G4xx_HAL_Driver/Src/stm32g4xx_hal_uart.c, Line 3825:3831if (!(IS_LPUART_INSTANCE(huart->Instance))) { /* Check that USART RTOEN bit is set */ if (READ_BIT(huart->Instance->CR2, USART_CR2_RTOEN) != 0U) { /* Enable the UART Receiver Timeout Interrupt */ ATOMIC_CLEAR_BIT(huart->Instance->CR1, USART_CR1_RTOIE); } }   According to the reference manual, USART_CR1_RTOIE must be set in CR1 in order to enable the interrupt, here it's cleared. 2) If one performs a HAL_UART_Transmit() and in case an error interrupt is fired on the peripheral tries to  call HAL_UART_Abort(), a buffer overflow can occur and undesired data is pushed the UART-TX.In the abort function "huart->TxXferCount" is set to 0, whereas in the transmit loop the HAL directly decrements that sha

I'm working with the STM32H757 Eval board and I'm using TouchGFX.Using the designer, I created the Dice Animation demo project and got it running on the board.I then duplicated this project and hooked it into our code ecosystem (we use Visual Studios with VisualGDB instead of CubeIDE and have numerous platform submodules that we incorporate into our system).  All of that is working.  I even have the two environments cross building with each other.  Visual Studios will call the TouchGFX makefile and generate assets and build all the UI elements, and then incorporate those files into our build system on our platform.  I can then program the board from Visual Studios and it will program the external QSPI flash with the UI data and the Dice Animation program will boot up.  I even have it working the other way so that from the TouchGFX Designer when you hit program, it will go out and call the Visual Studios make and build the system that way and then program the bo

Both STM32H730 datasheet and application note AN5050 mentions that a write operation can be performed on external Flash memories through the OctoSPI peripheral.However, the STM32H730 reference manual (RM0468), has the following info on section "25.4.14OCTOSPI Regular-command mode configuration":In Memory-mapped mode, the external device is seen as an internal memory but with some latency during accesses. Read and write operations are allowed to the external device in this mode.It is not recommended to program the Flash memory using memory-mapped writes, as the internal flags for erase or programming status have to be polled.So, write operations are allowed, but not recommended? How is that? Is their behavior not guaranteed?I'd like to use a QSPI / OctoSPI as an external code memory, but this seems like a big drawback. How could I perform writes to a QSPI / OctoSPI memory in memory mapped mode, if write operations aren't recommended?

Hello , i am using STM32h750B-dk . i took compass image (PNG file) as texture mapper and i want to rotate the compass image according to BNO055 sensor which is magnetometer. this is connected through I2C4 (for I2C4 , STmod+ is used). i have share the codes. Thank you!#Model.cpp:#include <gui/model/Model.hpp> #include <gui/model/ModelListener.hpp> #include <cstdint> #include "stm32h7xx_hal.h" #include <math.h> #define BNO055_I2C_ADDR (0x28 << 1) // Shifted for STM32 HAL #define BNO055_MAG_DATA_X_LSB_ADDR 0x0E extern I2C_HandleTypeDef hi2c4; Model::Model() : modelListener(0) { } void Model::tick() { static uint32_t lastUpdateTime = 0; uint32_t currentTime = HAL_GetTick(); if ((currentTime - lastUpdateTime) >= 1000) // Check if 1 second has passed { lastUpdateTime = currentTime; if (modelListener) { int heading = getHeading(); modelListener->updateHeading(heading); } } } int Model::getHeading() { uint8_t buffer[6]; int1

HelloI have found a bug that stops updating the RTC_TR register. There is no problem with the RTC clock itself, it is ticking but the content of RTC_TR might in some specific use cases stop updating.I use the latest STM32CubeH5 Firmware Package v1.5.0 for STM32H5. The problem:When only using the function HAL_RTC_GetTime(const RTC_HandleTypeDef *hrtc, RTC_TimeTypeDef *sTime, uint32_t Format), the time stored in sTime is not updated. I even printed the content of RTC->TR and it is stuck, not updating.However, when I use it together with HAL_RTC_GetDate(), the RTC->TR is changing. When stop calling the HAL_RTC_GetDate(), the RTC->TR is stuck.With following example code, in C, I narrowed it down that it relates to access of RTC_SSR register.void call_this_every_second(void) { static int8_t time = 20; if (time > 0) { volatile uint32_t ssr = RTC->SSR; if (time > 10) { volatile uint32_t dr = RTC->DR; } --time; } else if (time == 0) { --ti