Philipp Klaus Krause

This should be correct: ~~~~ int putchar(int c) __reentrant { if (c == '\n') _serial_write('\r'); _serial_write(c); return c; } ~~~~ By the C standard, putchar() takes an int, and returns...

I had to remove it for SDCC 3.9.5.

It probably works with some rather old SDCC out-of-the-box. Using current SDCC, the firmware compiles for me using this patch: ~~~~ diff --git a/Firmware/bootloader/product.mk b/Firmware/bootloader/product.mk index d3b9f5d..9d647ea 100644 --- a/Firmware/bootloader/product.mk...

IMO these are two issues: 1) Emit a diagnostic if the input size is larger than the device (one could consider this a bugfix) 2) Add a command line option...

I tried with current stm8flash, Debian GNU/Linux testing, and an STM8SVLDISCOVERY board. It looks like it works for me. But I have no idea what firmware version is on the...

I'll try to find a bit of time for testing next week or the week after.

I tried with an STM8AF5288: ~~~~ root@notebook6:/tmp/stm8flash# ./stm8flash -c stlinkv2 -a STLink: v2, JTAG: v0, SWIM: v4, VID: 8304, PID: 4837 found SP = 0x17ff, assuming ram size = 6K...

With a STM8S003K3 I get a segfault: ~~~~ root@notebook6:/tmp/stm8flash# gdb --args ./stm8flash -c stlink -a GNU gdb (Debian 10.1-2) 10.1.90.20210103-git […] Reading symbols from ./stm8flash... (gdb) run Starting program: /tmp/stm8flash/stm8flash...

The STM8AF5288 debug output: ~~~~ root@notebook6:/tmp/stm8flash# ./stm8flash -c stlinkv2 -a GET_VERSION STLink: v2, JTAG: v0, SWIM: v4, VID: 8304, PID: 4837 GET_CURRENT_MODE -> 03 00 SWIM READBUFSIZE -> 0x1800 SWIM...

AFAIK, some devices are identical, except for the size of some of the memory, or peripherals, possibly they are using the same die, binned according to what works / what...