We had the same problem when we migrated from kirkstone to scarthgap.In our machine config we set the BOOTSCHEME_LABELS to trusted, which seems to no long be valid. Valid values can be found in the scarthgap release notes:https://wiki.st.com/stm32mpu...
Not really a solution but we found out, that the pin is indeed not set up to FDCAN and is set to analog instead./sys/kernel/debug/pinctrl/soc:pin-controller@50002000# cat pinconf-pins | grep 'PA11\|PD1'
pin 11 (PA11): analog
pin 49 (PD1): analog Thi...
