STM32CubeProgrammer (MCUs)

Board Name : stm32f7 seriesQUADSPI : N25Q128AI am stored imaged data in nor flash, data stored correctly in memory. After i am reset the controller or power on the controller, data will be resetExample :data : 0xD3005600Data stored first time programming : D3005600after reset the controllerRead the stored data : D3885688Why 0 data replaced as 8 in qspi memory ?data stored programming time : after rest the controller, read the qspi data :

I would like to erase the external flash from terminal using STM32_Programmer_CLI.Using the command STM32_Programmer_CLI -c port=SWD freq=4000 mode=UR -el MX25LM51245G_STM32H735G-DK.stldr --erase alldoes not seem to erase the external flash.Giving the --erase flag indices would not work either because indices for both internal and external flash start at 0.

I tried to program the demo .hex file into a B-U585I-IOT02A by STM32CubeProg, and got this:https://ibb.co/GJ1mHqnIt was prompted, there was flash protection, how to remove it?

I am trying to install STM32CubeProgrammer v2.8.0 on my Windows10 (Home x64) computer. I have updated my Java version to 8.301 (64-bit). However, installation process doesn't go further than Step 7 out of 8. There's no "Next" button or something, but just "Quit" button. Even if I wait for minutes, it doesn't change.What could be the reason for failed installing of STM32CubeProgrammer?Thanks for help in advance.P.S. I have had installed STM32CubeIDE v1.7 without any problem.Ramazan Dermenci

Hi !I'm used to working with F4 and F7 devices, and I've always made '.bin' files to distribute the firmware upgrades, which can be flashed via a custom bootloader, directly on the board, from an SD card.With my current project however, on a STM32H743BI, the generated '.bin' file is almost 700MiB in size!My two questions are:How come this is so big ? Does this have to do with the H7 memory mapping ?What reasonable options do I have ? Can '.hex' files be as easily read and written to FLASH memory ? Should I rather generate several '.bin' files to split sections ?Here's my linkerscript for reference:ENTRY(Reset_Handler) STACK_SIZE = 0x8000;   /* Non cacheable RAM for DMA This can be adjusted as needed */ DMA_RAM_SIZE = 32k; MIN_HEAP_SIZE = 0x2000; /* required amount of heap */ BOOTLOADER_SIZE = 256k; FLASH_ORIGIN = 0x08000000;   /* Specify the memory areas */ MEMORY { bootloader (rx) : ORIGIN = FLASH_ORIGIN, LENGTH = BOOTLOADER_SIZE FLASH (rx) : ORIGIN = FLASH_ORIGIN + BOOTLOA

When I clicked 'Firmware Upgrade' for my STLink, STM32CubeProgrammer complained that 'STLinkUpgrade.jar Not Found'. I found STLinkUpgrade.jar in STSW-LINK007:https://www.st.com/en/development-tools/stsw-link007.htmlBut neither STM32CubeProgrammer nor STSW-LINK007 has any instructions about how install or place STLinkUpgrade.jar so that it can be found by STM32CubeProgrammer.I managed to perform the update by installing a separate Java runtime environment and running the utility separately, but would like to know how to set it up correctly in STM32CubeProgrammer.

I am trying to understand the semantics of the "value" field in the option bytes in Cube Programmer. On my STM32G0 part, the PCROP1A_STRT and PCROP1A_END fields have "value" and "address" fields. What are valid inputs for the "value" field? Thanks!

hello, so i use STM32cubeprogrammer, so i want firmware but i cant use this program coz The program is forcibly terminated by connecting the device and pressing Download to upload the firmware file. I don't know why. Does anyone know why this is happening?

I am trying to program an F4 with an external flash chip in mapped memory mode using the STM32_Programmer_CLI. I use the cli commandSTM32_Programmer_CLI.exe --connect port=SWD mode=UR reset=hwRst -halt --erase all --download <path_to_hex> -el <path>/N25Q128A_STM32469I-DISCO.stldrWhich completes erase on internal flash and external flash, but then sits at parsing file. The file I am trying to write is 12.9MB with some flash existing in internal flash space and some flash existing in the hex position that correlates to the mapped memory modes position.If I try to write all of just the external hex (11.8MB), I still experience the same issue. If I crop the hex file into smaller parts, it will program the correct locations in external flash.I can successfully use the ST-LINK Utility with the same external loader to program the same hex file. I require the CLI however, because I require programming this through a script.Is there a known limitation to the hex size the CLI can acc

I'm working in an environment with multiple targets and ST-Links.In previous versions of CubeProgrammer I had no problem to connect to a target with serial number X while other targets that are connected with other ST-Link are connect to the debugger (CubeIDE)After I start to work with 2.8 I get ST-LINK error (DEV_CONNECT_ERR) when I try to connect to target X while other targets are connected to the debugger.Only if I stop the debugger on all others ST-Links the programmer connect successfully.Any idea?

ST-LINK Utility has checksum calculation for both internal and external memory programming.​But STM32CubeProgrammer has checksum for only external memory programming.​We have used ST-LINK/V2 + ST-LINK Utility until now, but we are considering to update our programmer to ST-LINK/V3 + STM32 Cube Programmer.​Is there any easy way to verify the programming for internal flash(like ST-LINK Utility's checksum function) in STM32CubeProgrammer?Or is there a reason that we don't need checksum calculation for internal memory programming? ​(Using STM's CRC function instead, etc...)Our device is STM32L4.Regards,​

Hi, I'm using STM32f072cbu I'm using ST bootloader (with UART interface).If the firmware upgrade process is interrupted for some reason (power loss for example) , is it possible to recover and load the firmware again ? in my board I don't have access to any boot pins. The only pins that can use are TX e RX. I'm using ST Flash Loader and ST Cube Programmer to load the firmware . Thanks

Tested on : one pieces of NUCLEO-L152RE evm board.I could create one DFU project(NUCLEO-L152-DFU) together with one APP project(NUCLEO-L152-BLINK) in STM32CUBEIDE towards STM32L152. I could upgrade firmware in STM32CUBEPROGRAMMER as well. After upgrading firmware, I pushed the reset button to make the MCU power-cycled. Then the bootloader identified the App firmware (base address = 0x801000) and tried to jump to "0x801093d". However, no expected logging information shown and LD2 didn't blink as wished as well.Try to get button stateButton state: 1Check hex-format data at address: 0x8010000Jump to address: 0x801093dI analyzed the App hex file, the starting-point address shoud be correct.   And the bytes in chip flash coincides with the data in hex file.   So I could confirm that the DFU programming process is unquestionable. There must be somthing wrong with the App firmware.Could somebody help find the root cause why the APP firmware couldn't run as e

I checked STMCubeProgrammer software description PDF. It has description of CLI API. It also says that STMCubeProgrammer has C++ API docs in "doc" folder. But I only see general readme in the folder.

NODE_F411RE. You need an additional 128 KB to copy these files. NODE_F411RE Space free: 8 .00 KB. Total Size: 32.0KB.Can anyone please advise how I can overcome this error message.

I programmed User DFU Boot loader like this,uint16_t MEM_If_Init_FS(void){ /* USER CODE BEGIN 0 */ HAL_FLASH_Unlock(); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_EOP | FLASH_FLAG_OPERR | FLASH_FLAG_WRPERR | FLASH_FLAG_PGAERR | FLASH_FLAG_PGSERR); return (USBD_OK); /* USER CODE END 0 */}/** * @brief De-Initializes Memory * @retval USBD_OK if operation is successful, MAL_FAIL else */uint16_t MEM_If_DeInit_FS(void){ /* USER CODE BEGIN 1 */ HAL_FLASH_Lock(); return (USBD_OK); /* USER CODE END 1 */}/** * @brief Erase sector. * @param Add: Address of sector to be erased. * @retval 0 if operation is successful, MAL_FAIL else. */uint16_t MEM_If_Erase_FS(uint32_t Add){ /* USER CODE BEGIN 2 */ FLASH_EraseInitTypeDef pEraseInit; uint32_t SectorError; pEraseInit.TypeErase = FLASH_TYPEERASE_PAGES; pEraseInit.NbPages = 1; pEraseInit.Page = Add; //pEraseInit.Banks = FLASH_BANK_1;&n

I downloaded latest STM32Flash loader for using the UART boot loaderbut it does not select and see the STM32H743Zi Nucleo boardi searched and found that version 2.8 which i am using does not have MAP file for the H7 Series The flash loader do support STM32 H7, where can i find a version with support for this chip?Thanks!

I can't flash to STM32 MCUs any more. after I accidentally wrote to Option bytes in STM32 CubeProgramming. Now status isPS C:\palm\programe\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin> .\STM32_Programmer_CLI.exe -c port=swd -ob displ     -------------------------------------------------------------------                      STM32CubeProgrammer v2.8.0     -------------------------------------------------------------------ST-LINK SN : 066BFF525649898367213942ST-LINK FW : V2J37M26Board      : NUCLEO-L432KCVoltage    : 3.26VSWD freq   : 4000 KHzConnect mode: NormalReset mode : Software resetDevice ID  : 0x435Revision ID : Rev ZDevice name : STM32L43xxx/STM32L44xxxFlash size : 128 KBytesDevice type : MCUDevice CPU : Cortex

Hello, I'm working on STM32L051 MCU. I just wanted to enter the device to the bootloader for serial flashing via USART peripheral.Here is the simple C code to enter into the bootloader for STM32L0xx family MCU.void JumpToBootloader(void) {  void (*SysMemBootJump)(void);  volatile uint32_t addr = 0x1FF00000;#if defined(USE_FULL_LL_DRIVER)  LL_RCC_DeInit();#endif /* defined(USE_LL_DRIVER) */  /**   * Step: Disable systick timer and reset it to default values   */  SysTick->CTRL = 0;  SysTick->LOAD = 0;  SysTick->VAL = 0;  __disable_irq();#if defined(STM32L051xx)  SYSCFG->CFGR1 = 0x01;#endif  SysMemBootJump = (void (*)(void)) (*((uint32_t *)(addr + 4)));  __set_MSP(*(uint32_t *)addr);  SysMemBootJump();}and after entering into the bootloader, we can see 0x7f and 0x79 value in RDR and TDR registers of USART as shown

hi! i'm using stm32L4r9Ai.​i programmed user dfu boot (from 0x08000000 ~ 0x0800C000).​read, write, and erase operations are also performed normally in cubeprogrammer.​one problem is the speed at which the cube programmer connects to the device in the dfu boot state.​It is fast when connecting to a device in system memory boot state. It takes less than a second.​but, it takes about 6 seconds to connect to a device in the user dfu boot state. its too slow.​usb speed setting is the same in the image below.​ <dfu boot connect> <system memory boot connect> ​Is there a reason why the difference occurs and a way to solve this difference?​ thanks!​

[ The text uses a translation tool. ]Flash size is the default and no more programs can be loaded.environmentWindows10 + STM32CubeMX + ST-Link2************** Console log     -------------------------------------------------------------------                      STM32CubeProgrammer v2.4.0                      -------------------------------------------------------------------ST-LINK SN : 53FF6D064882505226101587ST-LINK FW : V2J36S7Voltage    : 3.23VSWD freq   : 4000 KHzConnect mode: Under ResetReset mode : Hardware resetDevice ID  : 0x436Device name : STM32L15xxD/STM32L162xDFlash size : 128 KBytes (default)Device type : MCUDevice CPU : Cortex-M3Memory Programming ...Opening an

I'm using this command for Tx, and please let me know if I'm using correct clock config as well.uint8_t csend[] = {0x00,0x00,0x27,0x10}; // Tx Buffer  HAL_CAN_AddTxMessage(&hcan,&txHeader,csend,&canMailbox); // Send MessageClock config:RCC_OscInitTypeDef RCC_OscInitStruct = {0}; RCC_ClkInitTypeDef RCC_ClkInitStruct = {0}; /** Initializes the RCC Oscillators according to the specified parameters * in the RCC_OscInitTypeDef structure. */ RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI14|RCC_OSCILLATORTYPE_HSI48; RCC_OscInitStruct.HSI48State = RCC_HSI48_ON; RCC_OscInitStruct.HSI14State = RCC_HSI14_ON; RCC_OscInitStruct.HSI14CalibrationValue = 16; RCC_OscInitStruct.PLL.PLLState = RCC_PLL_NONE; if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK) {  Error_Handler(); } /** Initializes the CPU, AHB and APB buses clocks */ RCC_ClkInitStruct.ClockType = RCC_CLOCKTYPE_HCLK|RCC

..

I want to konw how to unlock the flash,Thanks!

..