dtparam=i2c_arm=on
dtparam=i2c_vc=on
dtparam=i2s=on
disable_splash=1
dtoverlay=disable-bt
dtparam=pcie=off
Do you see some issue above?
Is there a way to get debugging information on device tree parsing? (I understand is the step where the device drivers are probed)
dtparam=i2c_vc=on
dtparam=i2s=on
disable_splash=1
dtoverlay=disable-bt
dtparam=pcie=off
the carrier board has I2C/I2S devices and also some PCIe devices, but I had issues on the PCIe bus so for now I keep it disabled to avoid hanging at boot (will ask for help in a separate post)what do you need that for
I'm implementing the overlay point by point, I'll add it in the near future actuallyWhy didn't you add your backlight to the overlay?
Add below to config.txt, will give you more details on the device tree
Code:
009167.460: dtdebug: Opened overlay file 'overlays/st7703-customlcd.dtbo'009167.984: brfs: File read: /mfs/sd/overlays/st7703-customlcd.dtbo009196.801: Loaded overlay 'st7703-customlcd'009222.037: dtdebug: merge_fragment(/soc/dsi@7e700000,/fragment@0/__overlay__)009222.073: dtdebug: +prop(status)009231.239: dtdebug: merge_fragment(/soc/dsi@7e700000/panel,/fragment@0/__overlay__/panel)009231.274: dtdebug: +prop(compatible)009232.593: dtdebug: +prop(reset-gpios)009234.701: dtdebug: +prop(vcc-supply)009236.807: dtdebug: +prop(iovcc-supply)009238.956: dtdebug: +prop(width-mm)009241.100: dtdebug: +prop(height-mm)009243.235: dtdebug: +prop(rotation)009253.182: dtdebug: merge_fragment(/soc/dsi@7e700000/panel/port,/fragment@0/__overlay__/panel/port)009260.964: dtdebug: merge_fragment(/soc/dsi@7e700000/panel/port/endpoint,/fragment@0/__overlay__/panel/port/endpoint)009261.000: dtdebug: +prop(remote-endpoint)009263.166: dtdebug: +prop(phandle)009264.556: dtdebug: merge_fragment() end009264.589: dtdebug: merge_fragment() end009264.632: dtdebug: merge_fragment() end009264.697: dtdebug: merge_fragment() end009267.580: dtdebug: merge_fragment(/soc/gpio@7e200000,/fragment@1/__overlay__)009279.311: dtdebug: merge_fragment(/soc/gpio@7e200000/panel-reset,/fragment@1/__overlay__/panel-reset)009279.352: dtdebug: +prop(gpio-hog)009281.536: dtdebug: +prop(gpios)009283.631: dtdebug: +prop(output-high)009285.807: dtdebug: +prop(line-name)009288.586: dtdebug: +prop(phandle)009290.632: dtdebug: merge_fragment() end009290.672: dtdebug: merge_fragment() end009310.784: dtdebug: merge_fragment(/soc/dsi@7e700000,/fragment@2/__overlay__)009318.922: dtdebug: merge_fragment(/soc/dsi@7e700000/ports,/fragment@2/__overlay__/ports)009318.959: dtdebug: +prop(#address-cells)009320.291: dtdebug: +prop(#size-cells)009329.670: dtdebug: merge_fragment(/soc/dsi@7e700000/ports/port@0,/fragment@2/__overlay__/ports/port@0)009329.700: dtdebug: +prop(reg)009339.063: dtdebug: merge_fragment(/soc/dsi@7e700000/ports/port@0/endpoint,/fragment@2/__overlay__/ports/port@0/endpoint)009339.099: dtdebug: +prop(remote-endpoint)009341.243: dtdebug: +prop(phandle)009342.641: dtdebug: merge_fragment() end009342.675: dtdebug: merge_fragment() end009342.720: dtdebug: merge_fragment() end009342.780: dtdebug: merge_fragment() end009343.255: brfs: File read: 1665 bytesIs there a way to get debugging information on device tree parsing? (I understand is the step where the device drivers are probed)
Statistics: Posted by platux — Mon Mar 31, 2025 3:14 pm