STM32 MCUs Products

Hi @Tesla DeLorean ,I use the IS25LX064 OctoSPI Flash memory with the STM32H573 and i can write and read from memory using direct mode. In memory mapped mode i can read the flash correctly for 0x90000000 but writing at 0x90000000 using memory mapped mode causes a hard fault with precise error at 0x90000000.Does that mean it's not possible to write to the flash in memory mapped mode? RM0481 says: Line 44 fails. Line 34 and 35 are working fine. And if i write using line 34 and then enable the memory mapped mode the read sequence from li

(Spotted by sx107.)I know the subject is not very descriptive, but a figure is worth 1000 words:It's also in other 'H7 RMs; I leave it to ST to check them all :)(Btw. this is a carryover from the 'F7 RM, where both OTG's SOF indeed feed into TIM2 ITR1, through a mux controlled by a bitfield in TIM2_OR.)JW

TLDR: application tried to write to a FLASH address without accessing FLASH peripheral, so the Flash bit CFGBSY in the SR register got set and further accesses to FLASH CR register leads to a Bus Error (not documented). Of course, the main action is to correct the application behavior, but also tried to reset the bit (which from the documentation can only be reset by hardware) but didn't work.​Long story.​The application tried something as the follows.​static const uint32_t var = 0;​uint32_t * const p_var = (uint32_t * const)&var;*p_var = 12;​the p_var contents assignment didn't generate a Bus Error, rather it set the CFGBSY bit in FLASH SR register.​From the documentation:​

Hello,I am using the Nucleo-H767ZI board. On this board, I am working with both a version that uses an external oscillator and one that does not. My question is whether it is normal for the firmware to work regardless of the following settings: RCC_OscInitStruct.HSEState = RCC_HSE_ON; // Version with external oscillatorRCC_OscInitStruct.HSEState = RCC_HSE_BYPASS; // Version without external oscillator As far as I know, the system should not work if these settings differ depending on whether the external oscillator is present or not. However, in my current situation, the system works regardless of these settings. I've seen cases where it doesn't work, but most of the time it functions without issues, even with different settings.I would like to know if it is acceptable to use these settings when they differ.Thank you.

Posted on October 22, 2016 at 04:27 I am not sure if this is a bug fix or an enhancement. I am developing on a proprietary board using the STM32F7 series processor. I have a device connected via USB using the USB Host Library. This particular device has more than just a CDC interface and the CDC is NOT the first one in the descriptor list. The USB Library source file usbh_core.c has code which should be looking through all of the interfaces, but only looks at the first. To fix this, I changed this: case HOST_CHECK_CLASS: if (phost->ClassNumber == 0) { USBH_UsrLog(''No Class has been registered.''); } else { phost->pActiveClass = NULL; for (idx = 0; idx < USBH_MAX_NUM_SUPPORTED_CLASS ; idx++) { if ((phost->pClass [ idx ]->ClassCode == phost->device.CfgDesc.Itf_Desc [ 0 ].bInterfaceClass)) { phost->pActiveClass = phost->pClass [ idx ]; } } to this: case HOST_CHECK_CLASS: if (phost->

I am a beginner using the Nucleo-F334R8 with Keil and STM32CubeMX.I want to read ADC data with DAC. The ADC is from a potentiometer, and I will read the DAC using an oscilloscope. I am using the program below so that when I run it, it will generate the frequency I need. I am using mapping to create the frequency range I want, with the frequency limits being from 10 Hz to 350 Hz, and I have achieved this according to the potentiometer setting I adjust. The biggest problem in my program is that when I run it and observe the CNT value, it counts up to the ARR value, and the oscilloscope displays a sinusoidal signal. However, when I adjust the signal back and forth, the signal disappears and only shows a straight line, with the CNT value becoming "VERY LARGE, EVEN INTO MILLIONS." I have to press the reset button on the Nucleo to display it again, but SOMETIMES IT DOESN'T WORK, and this is not a time/div issue since I have changed it, but rather a problem with CNT and ARR that I c

HiI use STM32U575I-EV.I want to periodically read data from an external SPI device without CPU.The SPI device will emit a data ready signal(active low gpio), so I want to use that as a trigger to read the data.Ideally, I would like to perform multiple SPI receptions while keeping the CPU in Stop mode.To read data from a SPI device, just do something like HAL_SPI_Receive_DMA(). Are there any good example projects ?Or how can I do this ?I read this articles, but it didn't solve my problem.Solved: STM32U5 SPI Continuous Communication - STMicroelectronics CommunityBest regards.

Hi,i'm using a STM32L031. In my code i first initialize the MCU (FLASH, CLOCK, INTERRUPTs, GPIOs), start the LPTIM (running on LSI), then slow down the MSI clock, start the timer22 for PWM and go into low-power sleep mode.  When i let the program run i experience an hard-fault after exiting the ISR (count = ccr) from the LPTIM because at the moment when r7 and PC gets popped from the stack PC gets a wrong value and suddenly points to RAM instead of FLASH. The strange thing for me is also, that when i don't use the LPTIM for waking up the MCU, but use a GPIO (EXTI) ist works fine. It also works fine when i don't go into low-power sleep mode but into stop-mode and then let the LPTIM wake up the MCU. In this case of course the PWM doesn't work while in stop-mode.So can someone help me out an tell me why the pc gets a wrong value?Here my example code:#######################################################int main

I'm currently testing low-power applications on the NUCLEO-U545RE-Q board, which involves using an SSD1306 OLED display and a BME280 MEMS atmospheric sensor, both interfaced via I2C1 and I2C3 at 1 MHz. The FCLK is configured to 160MHz. Clock source is internal resonators, HSI and LSI (RTC disabled). Internal SMPS is enabled. Additionally, I'm utilizing an integrated user button and LED on the Nucleo board.The process starts by acquiring temperature, humidity, and pressure readings upon power-up. After 5 seconds, the system transitions to standby mode. To restart the process and view the necessary information while conserving battery life, the user can press the reset button. However, I've encountered an issue where the MCU, when in standby mode, consumes 25 mA—a significantly high draw for a small lithium battery. This current draw was measured by placing an ammeter in series with JP4, as specified in the UM3062 for MB1841.Despite several attempts to reduce this consum

I have a NUCLEO-F103RB and I am trying to communicate with my AHT10 sensor. I understand the basics of I2C but i'm a newbie to stm32. For some reason when i do HAL_I2C_MASTER_TRANSMIT it seems to return a failure but HAL_I2C_MASTER_RECIEVE doesn't return any error at all. The null_a_char function basically just puts '/0' into the array so i can reuse it next time.My code is below. while (1) { null_a_char(buf); buf[0]= 172; //0xAC ret = HAL_I2C_Master_Transmit(&hi2c1, 112, buf, 8, 10000); //Returns HAL_ERROR null_a_char(buf); // Just puts /0 in the buff buf[0]= 172; //0xAC ret = HAL_I2C_Master_Receive(&hi2c1, 112, buf, 2, 1000); // Returns HAL_OK null_a_char(buf); ret = HAL_I2C_Master_Receive(&hi2c1, 113, buf, 6, 1000); // Returns HAL_OK // this returns buff[0]=24, buff[1]=220, buff[2]=105, buff[3]=0, buff[4]=0 // buff[5]=0, buff[6]=0 }From my

Hi,I'm using the software EEPROM to save a variable to flash that is being updated during run time, that I would like to read in case the system resets. Whenever the system resets, for stability, it writes a line of "dummy" 0's to the next available location, and sets the virtual address to the address after that. Is it possible to retrieve this value from before the dummy 0's easily? I've seen people suggest parsing through the page to find the correct value on different forums, with slightly different use cases, but it seems to me that this should already be available somewhere in the EE_Init() function, as already seems to find the next location, but I'm struggling to understand what is driving it. I was hoping EE_ReadVariable would take -1 as a virtual Address, but it doesn't seem to give me the correct result. 

Hi,I have been working on NUCLEO-U5A5ZJ-Q EVK to setup as a USB VCP device with the support of STM32CubeIDE. I got an example from the ST repository. Its using the Azure RTOS USBX stack instead of STM32 USB Device stack. I am not very much familiar with this RTOS framework.System details:NUCLEO-U5A5ZJ-QExample: Ux_Device_CDC_ACMI am trying to have a throughput test from data sending from device to Host PC via VCP. So I have edited the thread function usbx_cdc_acm_write_thread_entry() function to remove the UART-USB bridge setup of the example project and just send a bulk data to the HOST. Here is the code,   #define MAX_PKT_SIZE 128 /* 200 */ /* 512 */ /* 1024 */ VOID usbx_cdc_acm_write_thread_entry(ULONG thread_input) { ULONG actual_length; uint32_t i = 0; uint32_t total_bytes_to_send = APP_T

I am trying to implement an IAP function on stm32h563 with Keil. I have a bootloader and image A and B, all running on flash. Image A and image B are running on bank 1 and 2. When i was running image A and updating image B, new image B is successfully programmed in flash and passed software CRC-16 check.Then I jumped to image B and image B get stuck at the software CRC-16 check. Because I need to read data from flash and flash is somehow locked, and PC goes to a wrong place (like calling an uninitialized pointer).  The flash keeps locked even if I download my firmware again. I can only unlock the flash by erasing the whole flash via Keil IDE and reprogram the bootloader. I use the ST sample API to erase and write flash. Below is my code of flash operation. Could anyone help me? /** * @brief Gets the bank of a given address *

I am using stm32f779I eval kit. I am using example UART_HyperTerminal_DMA by en.stm32cubef7.I am trying to implement UART in DMA mode to transmit a simple string.So I have used CubeMX to generate the code and I have configured UART1 TX DMA in normal mode.Whenever I run the code in debugging mode, I see the first time I attemp to send the string, it works ok and sends the string.But I couldn't send a second transmission.Can any one please suggest the correct way to use Uart Tx in DMA mode? How can I send successive strings one after another?E.g. :i used  if(HAL_UART_Transmit_DMA(&UartHandle, (uint8_t*)aTxStartMessage, TXSTARTMESSAGESIZE-10)!= HAL_OK) {  /* Transfer error in transmission process */  Error_Handler(); } if(HAL_UART_Transmit_DMA(&UartHandle, (uint8_t*)aTxStartMessage, TXSTARTMESSAGESIZE-10)!= HAL_OK) {

Hi Folks,I'm having an issue with just reading and writing new values to the RTC. I'm using a custom board that contains a 32.786Khz crystal and in CubeIDE the LSE is setup properly. I also have a battery connected to Vbatt,I'm using the following to read the RTC values:  if (HAL_RTC_GetTime(&hrtc, &rtcTime, RTC_FORMAT_BCD) != HAL_OK) { Error_Handler(); } if (HAL_RTC_GetDate(&hrtc, &rtcDate, RTC_FORMAT_BCD) != HAL_OK) { Error_Handler(); }  And to write the RTC values:  if (HAL_RTC_SetTime(&hrtc, &rtcTime, RTC_FORMAT_BCD) != HAL_OK) { Error_Handler(); } if (HAL_RTC_SetDate(&hrtc, &rtcDate, RTC_FORMAT_BCD) != HAL_OK) { Error_Handler(); } This code seems to work

As per the title: I am using Timer 2 for a PWM. Channel 1 and 2 work just fine, but Channel 3 and 4 won't output anything. Created the project with CubeMX. Tried enabling all 4 channels with all the same values except pulse (CCR) and probed the output-pins. The only user code is enabling the PWM with HAL_TIM_PWM_Stop(&htim2, TIM_CHANNEL_1), ..._2), ..._3) and ..._4).In the created code the Config-Struct is created, Channel 1 is initialized, only the pulse variable is changed, Channel 2 is initialized, etc.The only difference between Channel 1 and 2 and Channel 3 and 4 I found is the CCMR1 / CCRM2 register.Has anyone an idea where this error might stem from?

I have an Arduino Giga (STM32H7) and I'm using the timers to generate PWM's. Everything's working fine, programming is no problem, but I cannot come up with a way to implement what I want. I included a simple visual to describe what I want the output to look like. TIM1 is the master timer, it generates a PWM, set as active high (for CNT<CCR). I have a slave TIM8, which should do the following: when TIM1 starts over again/goes high, TIM8 should generate N pulses. The time it takes for N pulses to complete is shorter than the period of TIM1, I want them to retrigger each time TIM1 goes high again. Here's the catch: The pulses should immediately s

I have a couple dozen of custom boards with STM32G4s on them. These boards are all 'identical' and the software being loaded on them is the same. BOOT0 pin is currently floating so on my initial load I held it to ground and changed the option bytes via HAL functions to choose the software boot bits to use flash memory.All boards initially passed functional testing, but recently some boards get stuck at memory address 0x1fff`5064 on the chip. The assembly command at this address is B . W 0x1fff'5064 which I think holds the chip at this instruction forever.That is the latest bit of information I've gotten. I'm trying to stop short of easter egging this and am hoping for some good tests I can perform to figure out exactly what's happening here. I've included more detail below.Background: Using CubeMx, I'm generating a project with HAL libraries and then adding code around them but leaving generated files untouched. Initial indication of an issu

Hi everyone,I use the IS25LX064 OctoSPI Flash memory with the STM32H573 and after configuring the OctoSPI flash i can read the device Id of the flash successfully. But when i change the configuration of the Volatile configuration register by setting the dummy cycles (see function OSPI_DummyCycles in the code below) there is no change in the register. When i read the register after setting the dummy cycle i get 0xFF and so the change has no effect.Does anyone know what could be the problem did i omit something in the configuration?The gpio config is fine because i can read the device id . Also if i try to write to a reserved address of the volatile configuration register and then read the flag status register, i see that the error bit in the status register is set which is exepected. But writing to the dummy cycle address of the volatile config register has no effect and no error is reported in flag status register.

Using an STM32F373, I setup a USB DEVICE virtual port class.  The connection does work but it takes disconnecting/reconnecting the USB cable once or twice before it gets detected successfully as a serial port/usb device on my linux box.  I use lsusb to see which USB devices are found, and when the connection intialy fails, I get the following message in 'dmesg':"new full-speed USB device number 48 using xhci_hcdusb 3-1: config index 0 descriptor too short (expected 67, got 9)usb 3-1: config 1 has 0 interfaces, different from the descriptor's value: 2usb 3-1: New USB device found, idVendor=0000, idProduct=0001, bcdDevice= 2.00usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3usb 3-1: Product: my Moduleusb 3-1: Manufacturer: STMicroelectronicsusb 3-1: SerialNumber: 2077345D5646 If I disconnect the USB cable and reconnect it it usually works.Any ideas on what I should look at to fix this

Hi AllI'm having a problem with FDCAN transmissions and would appreciate any insights.  I have a pair of H563ZI Nucleo boards, and am transmitting FDCAN messages, but the 20th of the 29 bits in the FDCAN extended identifier is always received as 1, regardless of whether it is 1 or 0 when it is sent.The identifier is set correctly into the Tx FIFO RAM in the HAL layer, but is corrupted in the Rx FIFO RAM when it is received.There are no reported error states.This happens not just between the two boards, but also within one board with internal loopback enabled.Attaching a CAN bus analyser, I can see the corruped identifier on the CAN bus.  So the problem is with the transmit/Tx side, not the receive side.I've attached the ioc file, but the full source project is under development and wouldn't be very easy to follow; I will try and isolate the problem into a simpler test program, but in the meantime if anyone has seen similar problems

I want to port a STM32F103C8T to a STM32F1 series. I go on my .ioc file, click the pinout compatibility and then find the board but i can't seem to see the import option anywhere. Image is attached  

Hello, SDIO 4 bit  R/W with 32 bit HC works. When 64 GB XC is used getting error at:SD_PowerON() > HAL_SD_ERROR_CMD_RSP_TIMEOUTMore questions: when to enable HardwareFlowControl (at times R/W is success when enabled) and why set BusWide as 1 initially Please check above 3 queries

Quick question concerning L0 internal EEPROM...From RM0377, page 79:Write to data EEPROM...DescriptionThis operation aims at writing a word or a part of a word in the data EEPROM. The usermust write the right value at the right address and with the right size. The memoryinterface automatically executes an erase operation when necessary (if all bits arecurrently set to 0, there is no need to delete the old content before writing). Similarly, ifthe data to write is at 0, only the erase operation is executed. So no erasing necessary, simply over-writing eeprom is okay?This is so unusually comfortable (compared to internal flash workings), that I better ask...

Is it safe to use memcpy() in an ISR when another memcpy() was already running on main thread or another ISR?I am getting conflicting info on web about using memcpy() in an ISR to copy data between two uint32_t buffers.MCU: STM32H723CubeIDE V: 1.16.0