*ERROR* failed to attach bridge to encoder DPI-31: -517
stm32-rproc 10000000.m4: wdg irq registered Created slice system-systemd\x2dbacklight.slice. Started Network Manager Script Dispatcher Service. Starting Network Manager Script Dispatcher Service. Started A high performance…er and a reverse proxy server. Starting A high performanc… and a reverse proxy server. Finished Remove Stale Onli…ext4 Metadata Check Snapshots. Loading Device Tree to cffe8000, end cffff920. Retrieving file: /boot/vmlinuz-5.15.65-armv7-lpae-x30Īppend: console=ttySTM0,115200 root=/dev/mmcblk0p4 ro rootfstype=ext4 rootwait
WDT: Started with servicing (32s timeout) Model: STMicroelectronics STM32MP157C eval daughter on eval motherīoard: stm32mp1 in trusted - stm32image mode (st,stm32mp157c-ev1)Ĭore: 285 devices, 43 uclasses, devicetree: board NOTICE: Model: STMicroelectronics STM32MP157C eval daughter on eval mother I have even done the ST-LINK upgrade from CubeIDE. Trying to connect via the st-link is even stranger as it shows me no output at all (even though CubeIDE is able to detect the ST-LINK S/N via the debugger). I tried connecting a keyboard to the board and it still does not seem to receive any input. Meaning that it shows me the login prompt, however i cannot enter anything. The problem is that when I try to boot from the board via the UART4 through minicom, while everything looks to be booting correctly (minus this error: *ERROR* failed to attach bridge to encoder DPI-31: -517). I have also followed the same guide on discovery kit 2 board and it worked without issue. I used this guide from digi-key to install debian on it (ĭebian: Getting Started with the STM32MP157), except in the parts where it says stm32mp157c-dk2 i replaced that with the appropriate '-ev1' suffix.