Skip to main content
This topic has been closed for replies.

25 replies

Mike_ST
ST Technical Moderator
Sep 23, 2020 1:37 PM UTC

Ticket is in our database, and I'm sorry but there is no update so far.

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. 
Mike_ST
ST Technical Moderator
Sep 24, 2020 2:21 PM UTC

As I asked for answer, I got one: No problem, it has been tested with 192kb sample hex.

Only thing I can do now is to give a failing hex file. So if you feel like share it...

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. 
VoWa
VoWaAuthor
Associate
Sep 25, 2020 6:49 AM UTC

I've made a simple sample with dummy data exceeding 128kb and it does not work with bootloader. 0693W000004H4sbQAC.jpg

VoWa
VoWaAuthor
Associate
Sep 25, 2020 7:00 AM UTC

When programming same file with ST-Link it works just fine.

0693W000004H4vLQAS.jpg

Mike_ST
ST Technical Moderator
Sep 25, 2020 8:34 AM UTC

STM32L081CZT6

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. 
VoWa
VoWaAuthor
Associate
Sep 25, 2020 8:55 AM UTC

Exactly, STM32L081CZT6.

Nesrine.JLASSI
Visitor II
Oct 6, 2020 9:28 AM UTC

Hello,

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.

Please specify the ID of the Bootloader version.

0693W000004Im9hQAC.png

Regards,

Nesrine

VoWa
VoWaAuthor
Associate
Oct 6, 2020 9:38 AM UTC

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

VoWa
VoWaAuthor
Associate
Oct 6, 2020 9:46 AM UTC

When comparing to my view there are additional parameters shown in your screenshot (at Automatic Mode>Option bytes commands)

0693W000004ImOhQAK.jpg

Maybe the additional parameters solve the problem?

Nesrine.JLASSI
Visitor II
Oct 6, 2020 9:58 AM UTC

No, the problem is not there,

0693W000004ImWlQAK.png

Nesrine.JLASSI
Visitor II
Oct 21, 2020 9:25 AM UTC

Hi @VoWa​ 

Could you please share your .bin file to check with.

Best regards,

Nesrine

VoWa
VoWaAuthor
Associate
Oct 28, 2020 11:53 AM UTC

Hi @Nesrine.JLASSI​ 

Here is the bin file compressed as zip.

But I think it is nothing with the bin or hex file. The memory erase at the beginning fails.

Best regards,

Volker

Nesrine.JLASSI
Visitor II
Oct 30, 2020 8:52 AM UTC

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