Okay, so starting from the beginning then. I have some initial questions/suggestions to make sure I understand everything.
First of all I assume you’re trying to load this custom edid binary because the default edid from your HDMI display doesn’t work or something similiar, correct?
Did you create this edid binary yourself or did you get it from somewhere? I assume you then manually wrote the binary to /lib/firmware/edid/ correct?
As for a suggestion, we admittedly haven’t tested this edid loading functionality too much in TorizonCore. If it’s not too much trouble could you flash our reference image instead and try the edid loading functionality there.
It would help us to narrow down whether the issue is with the lower-level BSP or with the upper-level TorizonCore.
Hi @ed-bear , you have to put ZL034.bin into the weston container instead of /lib/firmware/edid/ on TorizonCore. For example, ZL034.bin is placed at /home/torizon/firmware and /home/torizon/firmware will be mounted to /home/torizon/firmware in a weston container e.g. torizon/weston-vivante:2. This is a docker-compose example. Meanwhile, add parameter to kernel command line. fw_setenv tdxargs drm.edid_firmware=ZL034.bin