There is a README in the overlays folder on purpose...
'dtparam=i2c_arm=on'
Will start I2C-1 on GPIO2/3
'dtoverlay=i2c0-pi5' as no parameter is given it claims GPIO0/1.'dtoverlay=i2c1-pi5' last overlay wins -> now GPI2/3 are claimed by this overlay. Does not change anything as it's I2C-1 as well.'dtoverlay=spi0-0cs' claims GPIO9/10/11 for use as an SPI'dtoverlay=uart1-pi5' as GPIO0/1 last overlay wins -> this one will disable your I2C-0 on GPIO0/1 and use it for UART1you should not only check if a driver is loaded or device created. Check your GPIO assignment as well.
what is the intention of this one : 'dtparam=uart0=on'? PI5 has a dedicated BOOT UART on the 3-pin UART connector
'dtparam=i2c_arm=on'
Will start I2C-1 on GPIO2/3
'dtoverlay=i2c0-pi5' as no parameter is given it claims GPIO0/1.
Code:
Name: i2c0-pi5Info: Enable i2c0 (Pi 5 only)Load: dtoverlay=i2c0-pi5,<param>=<val>Params: pins_0_1 Use GPIOs 0 and 1 (default) pins_8_9 Use GPIOs 8 and 9 baudrate Set the baudrate for the interface (default "100000")Code:
Name: i2c1-pi5Info: Enable i2c1 (Pi 5 only)Load: dtoverlay=i2c1-pi5,<param>=<val>Params: pins_2_3 Use GPIOs 2 and 3 (default) pins_10_11 Use GPIOs 10 and 11 baudrate Set the baudrate for the interface (default "100000")Code:
spi0-0csInfo: Don't claim any CS pins for SPI0. Requires a device with its chip select permanently enabled, but frees a GPIO for e.g. a DPI display.Load: dtoverlay=spi0-0cs,<param>=<val>Params: no_miso Don't claim and use the MISO pin (9), freeing it for other uses.Code:
Name: uart1-pi5Info: Enable uart 1 on GPIOs 0-1. Pi 5 only.Load: dtoverlay=uart1-pi5,<param>Params: ctsrts Enable CTS/RTS on GPIOs 2-3 (default off)what is the intention of this one : 'dtparam=uart0=on'? PI5 has a dedicated BOOT UART on the 3-pin UART connector
Statistics: Posted by aBUGSworstnightmare — Sun Feb 23, 2025 8:13 am