I escalated this issue in the internal ticket (ID 165756) for check and analysis.
(PS: ID 165756 is an internal tracking number and is not accessible or usable by customers).
Thanks for your contribution.
Hi @TOMTANG0329 ,
We could not reproduce the issue when tested the firmware update process using STM32CubeProgrammer version 2.14.0 with openBL.
Can you please provide us with your firmware file or the log that shows the error encountered during the update process?