you should look what has claimed GPIO7!I just realized that i was able to solve half of my problem with using 0 chip select overlay for SPI0. Following advice from @aBUGSworstnightmare : "How/why did you enable SPI0? The mcp251xdf overlay will enable the required SPI interface. Leave your fingers from the 'enable SPI' option in raspi-config as this can/will only enable SPI-0. " I have modified my config.txt file to remove all references to SPI 0. However I am still getting this error:Below is the new config.txt file contents:Code:
[ 2.573291] pinctrl-bcm2835 fe200000.gpio: pin gpio7 already requested by fe204000.spi; cannot claim for fe204800.spi[ 2.573347] pinctrl-bcm2835 fe200000.gpio: pin-7 (fe204800.spi) status -22[ 2.573371] pinctrl-bcm2835 fe200000.gpio: could not request pin 7 (gpio7) from group gpio7 on device pinctrl-bcm2711Code:
#For more options and information see# http://rptl.io/configtxt# Some settings may impact device functionality. See link above for details# Uncomment some or all of these to enable the optional hardware interfacesdtoverlay=i2c0,pins_44_45=1dtoverlay=i2c3,pins_2_3dtoverlay=i2c1=off# FAN controller IC is connected to I2C 3 interfacedtoverlay=i2c-fan,emc2301,addr=0x2F,i2c3dtoverlay=i2c-rtc,rv3028,i2c0#dtparam=i2s=on#dtparam=spi=off# SPI0 CS need to be disabled as these conflict with the interrupt pin of DSP# CAN controller IC.#dtoverlay=spi0-0cs,spi_dev=off# Enabling SPI interfaces for battery CAN and DSP CAN controller ICs#dtoverlay=spi1-1cs,cs0_spi_dev=off#dtoverlay=spi4-1cs,cs0_spidev=offdtoverlay=mcp251xfd-spi4,oscillator=20000000,interrupt=24,spimaxfrequency=1000000dtoverlay=mcp251xfd,spi1-0,oscillator=20000000,interrupt=8,spimaxfrequency=1000000#Disable bluetoothdtoverlay=disable-bt# Enable RTC#dtoverlay=i2c-gpio,bus=1,i2c_gpio_sda=15,i2c_gpio_scl=14#dtoverlay=i2c-rtc,rv3028,i2c_bus=1# Enable TPMdtoverlay=tpm-slb9670# Enable audio (loads snd_bcm2835)dtparam=audio=on# Additional overlays and parameters are documented# /boot/firmware/overlays/README# Automatically load overlays for detected camerascamera_auto_detect=1# Automatically load overlays for detected DSI displaysdisplay_auto_detect=1# Automatically load initramfs files, if foundauto_initramfs=1# Enable DRM VC4 V3D driverdtoverlay=vc4-kms-v3dmax_framebuffers=2# Don't have the firmware create an initial video= setting in cmdline.txt.# Use the kernel's default instead.disable_fw_kms_setup=1# Run in 64-bit modearm_64bit=1# Disable compensation for displays with overscandisable_overscan=1# Run as fast as firmware / board allowsarm_boost=1[cm4]# Enable host mode on the 2711 built-in XHCI USB controller.# This line should be removed if the legacy DWC2 controller is required# (e.g. for USB device mode) or if USB support is not required.otg_mode=1[all]enable_uart=0dtoverlay=uart2dtoverlay=uart5
One approach is to invoke one overlay after the other and see when it failed.
Another approach is checking the overlays readme what pins are used by which overlay
Pi5 has some dedicated overlays for UART/SPI/I2C -> check your config. If you want to use that config on CM4 and CM5 make use of the conditional filters for the models (already present i. Config.txt)
no, you haven't https://github.com/raspberrypi/linux/bl ... ay.dts#L14I have modified my config.txt file to remove all references to SPI
Statistics: Posted by aBUGSworstnightmare — Fri Mar 14, 2025 6:12 am