Others: STM32 MCUs related

I've never noticed this problem before. I am using v9.3.0 which has always worked previously, I have not knowingly changed anything. I have tried running as administrator, tried at home and work. Is there anything else I can try?

..

Howdy, I'm ending up in the hard fault handler on any attempt at page erase. Using the function from stm32g0xx_hal_flash_ex.cvoid FLASH_PageErase(uint32_t Banks, uint32_t Page) { volatile uint32_t tmp;   /* Check the parameters */ assert_param(IS_FLASH_BANK(Banks)); assert_param(IS_FLASH_PAGE(Page));   /* Get configuration register, then clear page number */ tmp = (FLASH->CR & ~FLASH_CR_PNB);   #if defined(FLASH_DBANK_SUPPORT) /* Check if page has to be erased in bank 1 or 2 */ if(Banks != FLASH_BANK_1) { tmp |= FLASH_CR_BKER; } else { tmp &= ~FLASH_CR_BKER; } #endif   /* Set page number, Page Erase bit & Start bit */ FLASH->CR = (tmp | (FLASH_CR_STRT | (Page << FLASH_CR_PNB_Pos) | FLASH_CR_PER)); }There on line 25, I crash when writing to FLASH->CR; I've confirmed that just setting the FLASH_CR_PER bit causes the hard fault. I tried using ST's provided eeprom emulation firmware as well, with the same result in the same fu

Greetings,I'm having trouble loading the EEPROM emulation package into STM32CubeIDE.I have downloaded the .zip file from https://www.st.com/en/embedded-software/x-cube-eeprom.html and tried to import it in "Embedded Software Packages Manager" but I get a "Problem during load of selected File" as you can see in the picture.I have tried downloading the file again in another internet browser and loading it but the same problem occurs.Can someone tell me how to import this library or is there an alternative library for EEPROM emulation on STM32H745IIK6?BRDomagoj

IAR version is 9.10.1, the lib version is 1.5.0 for F0 device. The IAR expose a lot of faults about "core_cm0.h". I do not change anything, just open the project file under "EWARM", then compile.

I'm trying to get the STM32H753-EVAL board to work. - The power supply unit is connected, the demo software runs fine - The board is connected to my PC via an USB cable ... an ST-Link Virtual COM port is visible in the device manager. - In STM32CubeMX I selected the STM32H753I-EVAL2 board and generated a project for the Keil environment. - I can compile the generated sources without errors. When I try to upload, I get the following error messages: Load "MPC_EVAL \\ MPC_EVAL.axf" Erase Done. Programming done. Contents mismatch at: 08000300H (Flash = FFH Required = 52H)! Contents mismatch at: 08000301H (Flash = FFH Required = 07H)! Contents mismatch at: 08000302H (Flash = FFH Required = 28H)! ... Flashing doesn't seem to work ... what can I do? I need help urgently! Many greetings recently

Hi everyone,When I try flashing a sample project [en.fp-atr-tomtom1 for STM32L496G-Discovery for BG96] from the STMicro website on to the P-L496G-CELL02 development board, I receive this error. I have attempted to manually add the header file directory for the includes but this does not seem to resolve the problem. Does anyone have any other suggestions as to what I can try?

I want to store my software version and data at a pointed section of STM32's Flash.I have tried to config the stc file in keil mdk,but it seems not working.So could anyone help me to find which step not right,thanks.​1. I set in keil to use user configured stc file;​​2. I set the sct file like this:;Add 0x0x0801B000 start address,2k=0x800 length to define as myram section to store user data​3.I define MYRAM as __attribute__((section("myram"))):​​4.I use MYRAM to define user data const variable:then i rebuild this program and download the hex to STM32G4,but the sct file defined style variable could not be found at MYRAM section at 0x0801B000;​​But when I use the style liking attribute at + address,it is useful;​​So the attribute at + address method is useful,but if I want to define another const variable behind the UserData_BlockValue2, I have to calculate the address because of the length of UserData_BlockValue2, this seems a little tedious.I want to know is it possible to use sct file

Hello!Previously there was a nice write-up on custom Bootloader+App setup on Atollic website:https://info.atollic.com/hubfs/Whitepapers/Atollic_Develop_Debug_BootloaderApps_ARMCortex.pdf​​Now this link redirects to ST website, but document is absent in the Resources category. Can anybody share it for download please?​

..

Previous downloads and verify through JTAG worked great when processor settings were set for 16MHz sysclk. Programming with ARM Keil uVision 5.17.0.0 (ULINK2 ). Verify now fails approximately half way through.

Hello!I'm starting to work on a project and it is built on the IAR IDe (the controller is stm32f103rct6). My task is to change the IDe (to Keil) of this existing project. After reviewing the existing code, I noticed, few configurational structures are getting stored in the Internal-Flash. The base address of these configurational structures is present in the ".icf" file (check the code snippet below). /**ICF file**/ place at address mem: 0x08006400 { readonly section ConfigParSection }; place at address mem: 0x08006800 { readonly section ConstSection1 };In the "main.c" file he was defining the location of these structures using #pragma. /********************struct definition**********************/ #pragma pack(push,1) // for remove padding typedef struct { int a; float f; char c [10]; }TsAFMConfig_StructTypeDef;   #pragma pack(pop) /********************struct variable**********************/ #pragma location = "ConfigParSection" __root const TsAFMConfig_StructTypeDef AFMMCUFl

Hi there,Debugging stops with this error messageError in final launch sequence:Failed to execute MI command:target remote localhost:61234Error message from debugger back end:localhost:61234: The system tried to join a drive to a directory on a joined drive.please suggest how to remove this problem.thanks.

We've got some piece of code that we would like to debug on the MCU. This works fine with the previous hardware version of our product, which uses an STM32L151RET6.On our new hardware version using the STM32L151VE, however, debugging from IAR does not work (full log is attached). Interestingly, flashing the hex file via ST-Link utility and running the code on the new hardware works fine.The attached log file shows many "Verify error at address" errors like shown below. According to my colleagues, the IAR workbench project should be correctly configured for our new hardware.Tue Feb 16, 2021 09:35:29: Warning: Verify error, failed to read memory at address 0x20000000 - 0x2000001F Tue Feb 16, 2021 09:35:29: Warning: Tue Feb 16, 2021 09:35:29: Verify error at address 0x20000000, target byte: 0xAA, byte in file: 0x00 I wasn't able to pin the root cause of this so far and would be happy to find out in which direction I should focus: Is this problem more likely related with the MCU itself,

How can I set in Keil MDK, used to stored some parameters such as soft version,manufacture date and so on at a block of（such as a page） STM32G4‘s Flash memory， thanks.

Hello all,I am working with STM32-Mat/Target and currently facing an issue when placing a receive block with External mode enabled. The error is the multiple definition of 'HAL_UART_RxCpltCallback' and 'HAL_UART_ErrorCallback' which is called in both STM32SerialRtiostream.c and USART.c, where USART.c is the file generated from Simulink using the receive block provided by STM32-Mat/Target. Since the receive block is configured to use interrupt receive mode I guess both files are calling for the same callback functions. Is there a workaround for this bug or can I not use the receive block in interrupt mode while interfacing with External mode in Simulink?Thank you in advance.

Hello everyone,I am currently extending a legacy software, for STM32 ; it is for : "stm32f103cb", with Atollic TrueStudio 9.3 I want to add IWDG (independent watchdog) ; to do so I generated a new project using CubeIDE, latest version, driven by a proper youtube tutorial on IWDG and STM32.Then I manually copied the needed code into my existing project.My question is :is it enough to copy only the C code, into the existing project, to get the IWDG properly working ?Or there is additional setup to be done that cannot be copied this way ?Thank you in advance.

Hello everyone, I would like to know wath's the STM32 equivalent of the serial monitor on Arduino .. Wath's the simpliest way to display integer value like temp or number with a nucleoF401re stuff ? Thank a lot for your responses !

I have Atollic TrueSTUDIO Version: 9.3.0.I bind keys to “Build Selected File(s)�? like this.Ctrl + Shift + L two times for window Preferences.In item Keys, i select "Build Selected File(s)", set Binding = Ctrl + Alt + B and When: In Windows , apply.Maybe does Atollic have any menu with button “Build Selected File(s)�??

I've gone through AN2594 and the associated examples. They're all for the standard peripheral library which is now deprecated.Someone has an example of a port on github that looks reasonably complete https://github.com/lamik/EEPROM-emulation-STM32F1-HAL/blob/master/Src/eeprom.c and at this stage it looks like I will be using thathowever...I'm wondering it ST have (or are planning to have) an official update?

Hi, I am trying to read the contents of the EEPROM on this W25Q128FVIQ. I am using SPI.The data read looked wrong to me, and the Manufacture ID I am getting out of it is wrong. I am getting 0xDC instead of 0xEF.I tried reading and writing data with a 4KB Microchip 25AA040A and that seemed to work fine. I wrote in 0xAB 0xCD and 0xEF and read it out successfully. Test4 is the one for reading the Manufacture ID on the Winbond chip. Also when I send it an address(not required for reading the Manufacture ID), I believe the chip is expecting it in Big Endian, so I believe I have to reverse the byte order of the address correct?But again, test4(marked in the code) is the one I am most concerned with right now.I should be reading 0xEF, but I get 0xDCif(test == 4) { //read jedec id, test4 HAL_GPIO_WritePin(GPIOA, GPIO_PIN_8, GPIO_PIN_SET); HAL_Delay(10); HAL_GPIO_WritePin(GPIOA, GPIO_PIN_8, GPIO_PIN_RESET); HAL_SPI_Transmit(&hspi1, (uint8_t *)&EEPROM_RJEDEC, 1, 100); HAL_SPI_Receiv

In my project I write some bytes to the internal EEPROM of a STM32L152CB. While running a debug session I can verify that the data has been stored correctly. At power up I read the EEPROM data and store it in some variables. As the MCU is configured as USB HID I can read those variables from RAM via a custom USB tool.If I run the program in a debug session, I can read the expected data via the USB tool. But when the device powers up normally (without debugging) I always read 0x00 via USB from those variables. I did not change the EEPROM content nor did I reflash the binary between those 2 tries.I use:BMP as debuggerSTM32L1 HALGNU Arm Embedded Toolchain 7 q4What can cause this issue? Could it be a problem in conjunction with a DFU bootloader?

Posted on May 07, 2018 at 04:00I have been importing CubeMX projects into System Workbench (SW4STM32). It's been working great, a real time saver. I first open System Workbench and select a workspace. Then using CubeMX I configure the project and generate the code. Then when the code generation is done and the dialog window opens, I press the Open Project button. In the past this has nicely imported my CubeMX code into SW. It no longer works. Now after I press the Open Project button, I get a new dialog box with the following error message:Unrecognized option: -d64Error: Could not create the Java Virtual Machine.Error: A fatal exception has occurred. Program will exit.What has gone wrong?Clark#stm32cubemx-eclipse-sw4stm32

I am using an STM32L4 MCU and IAR Embedded Workbench. I noted that when I start a debug session in the register window the "write-only" bits of a certain register are field with the letter "w" (for example in GPIOx_BSRR). I was wondering if this is the behavior just in the IAR debugger or it happens for other debuggers as well and is there a way to watch these bits in particular when they are written or not.

In Keil.STM32L4xx_DFP.2.5.0.pack, which can be downloaded at https://www.keil.com/dd2/pack, the memory information for stm32l452 says that the ram size is 0x00020000 = 128kB, but it actually is 0x00028000 = 160kB (SRAM1 + SRAM2).Using this file for my tooling, gdb is unable to read the values from the stack so I would like to see this fixed. Is this here a good place to report this issue? If not, where should I report it?