I added the following contents,There is no dt_blob.bin for the Pi 5 family - you should use Device Tree. For some scenarios you may find that the gpio= config.txt setting is sufficient.
I suggest you don't rely on internal pull-ups for I2C - they are a bit weak, and can lead to unpredictable behaviour.
gpio=38=a3
gpio=39=a3
but from the vclog , it shows,
003622.800: Invalid gpio command '38=a3'
003622.813: Invalid gpio command '39=a3'
at last I use the following contents works,
gpio=38=pu
gpio=39=pu
it also does not work on my issue as there is a delay of a few seconds between power being applied and the changes taking effect.
I use one MCU to connect another I2C LCD bridge, which also connect to the I2C of CM5 by using I2C1(GPIO38/GPIO39 on RP1), the CM5/RP1 will influence MCU to communication with the LCD bridge. If there is another solution to setting gpio38/gpio39 as I2C function quickly after power on?
Statistics: Posted by ayrd — Wed Dec 25, 2024 2:15 am