2022-11-04 03:55 AM
Hey
in a project of us we are using the legacy STMFlashLoader to flash firmware on a STM32F103 via the system bootloader on UART1, but wanted to migrate to STM32CubeProgrammer now. In this application the PC (Win10) which runs STMFlashLoader/STM32CubeProgrammer is not directly connected (via a USB-TTL adapter) to the UART1 of the STM32, but goes through a "tunnel". This works perfectly fine with the legacy STMFlashLoader but does not with STM32CubeProgrammer.
The log generated by STM32CubeProgrammer clearly shows that things break when the first chunk of data to be written is being sent.
The issue is that STM32CubeProgrammer sends a chunk of 256 bytes (0x31CE0800000008FF...), while STMFlashLoader sends only chunks of 128 bytes size (0x31CE08000000087F...), which perfectly explains the issue as the "tunnel" involves a buffer of size 128.
Hence the question: Is it somehow possible to set the chunk size which STM32CubeProgrammer is using for UART uploads?
If not, would it possible that such a feature could be added as option to the next version of STM32FlashProgrammer_CLI.exe?
Many thx, Oliver
(btw, I note that the legacy STMFLashLoader allows to set a timeout, while STM32CubeProgrammer does not, this could also be a useful option)
Solved! Go to Solution.
2022-12-29 05:56 AM
Hello @waldmanns,
For now, it is not possible to set chunk size in STM32CubeProgrammer. I have raised your request to the development team.
Internal ticket number: 142032 (This is an internal tracking number and is not accessible or usable by customers)
Thanks a lot for your contribution!
Aziz
2022-12-29 05:56 AM
Hello @waldmanns,
For now, it is not possible to set chunk size in STM32CubeProgrammer. I have raised your request to the development team.
Internal ticket number: 142032 (This is an internal tracking number and is not accessible or usable by customers)
Thanks a lot for your contribution!
Aziz