Hello community
The upgrade process of my device should be handled by the ROM bootloader over UART1 and FDCAN1. Therefore i can unset nBoot0 from the application and reboot to ROM. (If the new app can boot it sets nBoot0)
The reset is triggerd by the HAL_FLASH_OB_Launch().
After this reset i can communicate with the rom bootloader only per UART. To use FDCAN communication a power reset is necessary.
Then it works perfectly fine (go cmd). Trying this i havent connected any UART to my board.
If resetted and once sucessfully queried per fdcan the uart option from STM32_Programmer_CLI.exe says "Error: Activating device: KO." So the protocol detection works after the power reset. (After the OB reset it chooses UART1)
On the NUCLEO board the first thing i get after debugging HAL_Init() is exactly one Frame error in HAL_UART_ErrorCallback() but PA10 is not connected.
I havent seen that behavior on my custom board and can only imagine that by the OB reset the uC sees a uart tx somehow. This vague assumption will be investigated.
Does a timeout exist if a protocol is choosen?
Im happy to receive hints about this and thinking about using a custom bootloader on flash...
(The bootloader version from can cmd(0x1) is 0x10, the get id cmd(0x2): 0x04 0x67)
