We have a custom board based on the STM32MP157 series, and are trying to get the TF-A boot chain working. We have downloaded and compiled the linux kernel, u-boot, and arm-trusted-firmware for the STLinux ecosystem v2. We can boot to u-boot, and the kernel decompresses and begins running, but it appears that none of the peripheral clocks are accessable (I2C, SPI, SDMMC etc).
My question is what part of the boot chain is repsonsible for initilizeing the non-secure rtt clocks? Is it uboot? I don't see any initialization there. I don't think it's the kernel, but please correct me if I am wrong. I see some Cortex M4 code generated by the CubeMX took, is it REQUIRED that the M4 initialize the non-secure rtt clocks?
