Only the official Raspberry Pi touch display is connected to I2C0. All addresses displayed in i2cdetect for i2c-0 / i2c-10 belong to the display. I found an explanation for this in another post:
viewtopic.php?t=303680#p1818308
0x45 is the backlight and regulator, and 0x38 is the touchscreen controller of the raspberry pi display. 0x30 must be also a i2c device from the touchdisplay, because no other device is connected to the i2c0 bus on the custom board. The rtc module is connected to the i2c6 bus. What surprises me, however, is that the touch display devices should only be displayed on i2c-10 and not on i2c-0 in i2cdetect.
In connection with the interrupt error of the display, it was noticed that if you run i2cdetect twice during a freeze, the touch then works again.
However, one problem is still that the RTC does not work even though it is on a completely different I2C channel. It's also not clear to me whether the RTC problem is related to the display or the touch freezes.
This is my complete /boot/config.txt:
viewtopic.php?t=303680#p1818308
0x45 is the backlight and regulator, and 0x38 is the touchscreen controller of the raspberry pi display. 0x30 must be also a i2c device from the touchdisplay, because no other device is connected to the i2c0 bus on the custom board. The rtc module is connected to the i2c6 bus. What surprises me, however, is that the touch display devices should only be displayed on i2c-10 and not on i2c-0 in i2cdetect.
In connection with the interrupt error of the display, it was noticed that if you run i2cdetect twice during a freeze, the touch then works again.
However, one problem is still that the RTC does not work even though it is on a completely different I2C channel. It's also not clear to me whether the RTC problem is related to the display or the touch freezes.
This is my complete /boot/config.txt:
Code:
# For more options and information see# http://rpf.io/configtxt# Some settings may impact device functionality. See link above for details# uncomment if you get no picture on HDMI for a default "safe" mode#hdmi_safe=1# uncomment the following to adjust overscan. Use positive numbers if console# goes off screen, and negative if there is too much border#overscan_left=16#overscan_right=16#overscan_top=16#overscan_bottom=16# uncomment to force a console size. By default it will be display's size minus# overscan.#framebuffer_width=1280#framebuffer_height=720# uncomment if hdmi display is not detected and composite is being output#hdmi_force_hotplug=1# uncomment to force a specific HDMI mode (this will force VGA)#hdmi_group=1#hdmi_mode=1# uncomment to force a HDMI mode rather than DVI. This can make audio work in# DMT (computer monitor) modes#hdmi_drive=2# uncomment to increase signal to HDMI, if you have interference, blanking, or# no display#config_hdmi_boost=4# uncomment for composite PAL#sdtv_mode=2#uncomment to overclock the arm. 700 MHz is the default.#arm_freq=800# Uncomment some or all of these to enable the optional hardware interfacesdtparam=i2c_arm=on#dtparam=i2s=ondtparam=spi=ondtoverlay=mcp251xfd,spi0-0,oscillator=20000000,interrupt=25dtoverlay=mcp251xfd,spi0-1,oscillator=20000000,interrupt=26dtparam=i2c_vc=ondtoverlay=i2c6,pins_22_23dtoverlay=i2c-rtc,pcf85063a,i2c6,addr=0x51# Uncomment this to enable infrared communication.#dtoverlay=gpio-ir,gpio_pin=17#dtoverlay=gpio-ir-tx,gpio_pin=18# Additional overlays and parameters are documented /boot/overlays/README# Enable audio (loads snd_bcm2835)dtparam=audio=on# Automatically load overlays for detected camerascamera_auto_detect=0# Automatically load overlays for detected DSI displaysdisplay_auto_detect=0# Enable DRM VC4 V3D driverdtoverlay=vc4-fkms-v3d# Run in 64-bit modearm_64bit=1# Disable compensation for displays with overscandisable_overscan=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=1dtoverlay=dwc2,dr_mode=host[pi3]framebuffer_width=800framebuffer_height=444max_framebuffers=1[pi4]# Run as fast as firmware / board allowsarm_boost=1framebuffer_width=800framebuffer_height=444max_framebuffers=2framebuffer_aspect=-1[all]disable_splash=1enable_uart=1lcd_rotate=0Statistics: Posted by tonysbk — Fri Jan 26, 2024 9:40 am