2020-08-13 03:31 AM
Sorry, posted the wrong device before. Corrected that.
2020-10-06 02:38 AM
Here is the log-output when connecting to the bootloader:
11:35:50 : Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1.0, flow-control = off
11:35:50 : Activating device: OK
11:35:50 : Chip ID: 0x447
11:35:50 : BootLoader protocol version: 3.1
11:35:52 : UPLOADING OPTION BYTES DATA ...
11:35:52 : Bank : 0x00
11:35:52 : Address : 0x1ff80000
11:35:52 : Size : 20 Bytes
11:35:53 : UPLOADING ...
11:35:53 : Size : 1024 Bytes
11:35:53 : Address : 0x8000000
11:35:53 : Read progress:
11:35:55 : Data read successfully
11:35:55 : Time elapsed during the read operation is: 00:00:01.404
So I think it is version 3.1
2020-10-06 02:46 AM
When comparing to my view there are additional parameters shown in your screenshot (at Automatic Mode>Option bytes commands)
Maybe the additional parameters solve the problem?
2020-10-06 02:58 AM
No, the problem is not there,
2020-10-21 02:25 AM
Hi @VoWa
Could you please share your .bin file to check with.
Best regards,
Nesrine
2020-10-28 04:53 AM
2020-10-30 01:52 AM
Hi @VoWa
Thanks for your post. Tested with 192KB samples with CubeProg 2.5.0 and no issue found.
We are able to program with exactly the same file size as the customer with both ST-LINK and UART interfaces.
I have raised your feedback internally to be reviewed by our bootloader team.
We will give you an update as soon as possible.
Best regards,
Nesrine