ST32L081 can not be programmed with firmware bigger than 128k with CubeProgrammer and UART-Bootloader.

[VoWa]

Sorry, posted the wrong device before. Corrected that.

[Mike_ST]

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

[Mike_ST]

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...

[VoWa]

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

[VoWa]

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

[Mike_ST]

STM32L081CZT6

[VoWa]

Exactly, STM32L081CZT6.

[Nesrine.JLASSI]

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.

Regards,

Nesrine

[VoWa]

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]

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?

[Nesrine.JLASSI]

No, the problem is not there,

[Nesrine.JLASSI]

Hi @VoWa​ 

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

Best regards,

Nesrine

[VoWa]

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]

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