Hello,we try to access the I2C4-Bus under barebox, we use:CPU: STM32MP151CAA Rev.ZTF-A: v2.4-r1.0-nofip(release):b5d0088b9-dirtybarebox: barebox 2021.04.0-02204-gaa9b7b34b8e-dirtyIn the TF-A the I2C4 is unlocked by: DECPROT(STM32MP1_ETZPC_I2C4_ID, DE...
We would like to build the TF-A image with a different muxer settingfor i2c4. The usual setting is:i2c4_pins_a: i2c4-0 { pins { pinmux = <STM32_PINMUX('Z', 4, AF6)>, /* I2C4_SCL */ <STM32_PINMUX('Z', 5, AF6)>; /* I2C4_SDA */ bias-dis...
Hello,thanks to your answer we are now able to boot via tf-a 2.5 and barebox the linux kernel.With&rcc { secure-status = "disabled"; ...};we are able to access i2c4.Thank you,greetings Ralf
Hello,under Linux I can access I2C4 without problems.I suppose in TF-A the callDECPROT(STM32MP1_ETZPC_I2C4_ID, DECPROT_NS_RW, DECPROT_UNLOCK)unlocks the access to the nonsecure world and we can use I2C4 under barebox.greetingsRalf
Hello Olivier,after updating the TF-A firmware to version v2.2-r1.4 the problemis solved.I think the reason was the issue:"GPIO clock not enabled in BL32"thank you,Ralf
