Is there a incompatibility issue between the STM32F72x UART system bootloader and STM32CubeProgrammer?

[stormrush]

I'm trying to utilize the STM32F72x's UART internal system bootloader with the STM32CubeProgrammer application. I am able to connect to the sys bl via uart, view memory, erase flash, but CANNOT program the target.

Every time I do I get the following console error spew:

12:59:46 : Memory Programming ...
 
12:59:46 : Opening and parsing file: C:\source_code\experiment_and_test_projects\f7_bl_chatter\Debug\f7_bl_chatter.hex
 
12:59:46 : File : C:\source_code\experiment_and_test_projects\f7_bl_chatter\Debug\f7_bl_chatter.hex
 
12:59:46 : Size : 15628 Bytes
 
12:59:46 : Address : 0x08000000 
 
12:59:46 : 
 
12:59:46 : Erasing memory corresponding to segment 0:
 
12:59:46 : Not flash Memory : No erase done
 
12:59:46 : File segment @0x08000000 is not 255-bytes aligned. It will be aligned to @0x07FFFFF8
 
12:59:46 : Download in Progress:
 
12:59:46 : Response received from device: NACK
 
12:59:46 : 
 
12:59:46 : Error: Write address not acknowledged: 0x7FFFFF8
 
12:59:46 : 
 
12:59:46 : Error: failed to download Segment[0]
 
12:59:46 : Error: failed to download the File
 
12:59:46 : Time elapsed during download operation: 00:00:00.029

CubeProgrammer also reports the flash sectors incorrectly in "Erasing & Programming>Internal flash erasing" tab. It reports that there is only one flash sector, at address 0x20000000 and is of size 256k bytes. This is nowhere near accurate since flash starts at 0x08000000 and is of size 512k bytes and has 8 separate sectors.

Any info on how to resolve this issue would be greatly appreciated.

[CRams.1]

Hi!

Any progress on this issue? I'm experiencing the same problem. The STM32CubeProgrammer lists only the RAM in the internal FLASH erasing section and I get 'File segment @0x08000000 is not 255-bytes aligned. It will be aligned to @0x07FFFFF8' when programming from STM32CubeIDE.

This might have happen after I updated my STM32CubeIDE to v1.6 and tried to program my stm32 device.

[Nick van IJzendoorn]

Hi all,

We have the same problem using STM32CubeProgrammer in combination with an STM32L4P5VE using SWD / JTAG. "File segment @0x08000000 is not 255-bytes aligned. It will be aligned to @0x07FFFFF8". And we all know that 0x07FFFFF8 is not a valid flash address. :D

We thought to be smart and switch to ST-Link Utility to circumvent the problem, but there we get "the elf loader file is not accessible"

[CRams.1]

Hi,

I managed to program my device after trying the solution suggested here (https://electronics.stackexchange.com/a/205513). I had to try it several times - probably because it can be hard to the steps timing wise.

I didn't investigate it further - so I don't have the conclusion on what was my problem nor what fixed it.

Hope it helps!

[Nick van IJzendoorn]

Thanks for your response.

We also solved the problem, we updated from STM32CubeProgrammer v2.4.0 to v2.7.0. In the latter programming the STM32L4P5xx was fixed. I wanted to include the version number in my bug report, but than found out there was a newer version. :beaming_face_with_smiling_eyes: