Not a surprise, but disappointing, the connectors from the Android board do not use BOOT0 and RESET directly despite the BOOT and RESET naming.
Therefore, they have a proprietary boot-loader and they have written bullshit names here and there like LCD on a GPIO board...
Android board connector
Android side MCU side
5V 5V
GND GND
GPIO STM
ADOHC MTS
LED BOOT
GPIOS GPIO
RST RST
SLP
RX RX
TX TX
The bootloader is a 32Kb chunk and therefore is a big one. As specified in the Marlin port, overwriting the vendor bootloader will erase serial numbers and prohibit further vendor update.
There is a weird PWM signal on the pins, while we can read a serial dialog on the TX, RX pins.
The classic STM32 boot process is on the debug connector with the following pinout:
1 3.3V (square pin)
2 BOOT0
3 PA9 USART1_TX
4 PA10 USART1_RX
5 PA14 JTCK-SWCLK
6 PA13 JTMS-SWDIO
7 VSS/GND
8 RESET
I doubt that the vendor bootloader will upload the Klipper firmware. If anyone wants to intercept his dialog and reverse it, you are welcome.
I will connect to the Debug connector. I do not like that at all because it means soldering, and not a pure software conversion. I could also program my own bootloader and then use the vendor pins, it means no soldering, but making a sort of dual programmer/ linux serial console board.
I will look at what can be done with Katapult.
I do not know what the pins here are really for?
GPIO STM
ADOHC MTS
LED BOOT
GPIOS GPIO
RST RST
SLP -----
RX is PA3 USART2_RX
TX is PA2 USART2_TX
BOOT is PD3 USART2_CTS
RESET is PD4 USART2_RTS
STM is PD2 TIM3_ETR/UART5_RX/SDIO_CMD
MTS is PD1 OSC_OUT/FSMC_D3/CAN_TX
GPIO is PD5 USART2_TX
TX and RX is obviously used to program the board, and because the others are connected to the STM32 pins, they can be used for signaling.
Edit:
STM, MTS, BOOT, GPIO are in fact SPI0 form the android board.
Reset is PF1, nothing special. It could be a keep alive signal.
I have seen them used in what seemed a regular RESET/BOOT0 sequence in a script from the vendor firmware, that's why I am disappointed.