Dear Maintainer,

I have been using stlink for over 5 years now to regular flash files STM32L152RE and similar chips.
This has always worked quite well.
Specifially, I have a script that contains this line:

st-flash write /tmp/stage1.bin 0x08000000 || exit 10

Normally, the output is something like:
2023-07-14T14:06:30 INFO common.c: Attempting to write 122236 (0x1dd7c) bytes to stm32 address: 134254592 (0x8009000)
2023-07-14T14:06:30 INFO common.c: Flash page at addr: 0x08009000 erased
2023-07-14T14:06:30 INFO common.c: Flash page at addr: 0x08009100 erased
2023-07-14T14:06:30 INFO common.c: Flash page at addr: 0x08009200 erased
2023-07-14T14:06:30 INFO common.c: Flash page at addr: 0x08009300 erased
...
2023-07-14T14:06:42 INFO common.c: Flash written and verified! jolly good!

I recently updated to bookworm and since then it fails to write to the flash.
The key message in the output seems to be "Flash base use default L0 address".

Nothing gets written to the flash, nor does it get erased.

On my bookworm system I downgraded the packages using the following deb files:
libstlink1_1.6.1+ds-3_amd64.deb and stlink-tools_1.6.1+ds-3_amd64.deb
I can confirm that downgrading to the previous package versions reverts to the old (working) behaviour.

I consider this "grave" because the main purpose of the st-link tool is to flash software to the STM chips, and that's what is broken. This makes the package unsuable for many/most users IMHO.

This seems to have been reported (and fixed) upstream already:

https://github.com/stlink-org/stlink/issues/1161

I would very much appreciate an updated package and are happy to do some testing.