2020-08-13 03:31 AM
Sorry, posted the wrong device before. Corrected that.
2020-08-14 03:10 PM
I'd be looking for anything interesting/remarkable in the upper address space of the FLASH
ie things looking out of place, large voids in the memory usage
I'd look at the .ELF output, and perhaps the .BIN and .HEX I could generate from that.
Currently assuming the tools have some arbitrary limit/ceiling for the L0, instead of reading the value programmed in by the tester.
2020-08-16 11:31 PM
I think there is something wrong with erase. In the "erase flash memory" tab the "last" start address is 0x801FF80. With that there will be nothing erased above 128k
2020-09-23 06:26 AM
@Mike_ST can you please give an short info about the actual status? Is the ticket available somewhere?
2020-09-23 06:37 AM
Ticket is in our database, and I'm sorry but there is no update so far.
2020-09-24 07:21 AM
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...
2020-09-24 11:49 PM
2020-09-25 12:00 AM
When programming same file with ST-Link it works just fine.
2020-09-25 01:34 AM
STM32L081CZT6
2020-09-25 01:55 AM
Exactly, STM32L081CZT6.
2020-10-06 02:28 AM
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