You seem to be mixing a lot of different types of documentation that are not meant to go together.
First of all step 7 and 8 are incorrect. You’re on TorizonCore 5.7.2 so you should use the torizoncore-builder dt checkout command to get your code sources. Manually cloning them as you are, is only for TorizonCore 6, doing this here will get you incorrect versions of the source code.
When using our developer site documentation make sure you’re always referencing the version of the documentation that pertains to the version of software you are using:
So in your case you’d want to be on “5 LTS”.
Next your step 17 and 18. The dtconf tool is an old deprecated tool that should not be used in any versions of TorizonCore anymore. Where did you even see the documentation for this tool?
After you ran torizoncore-builder deploy your overlay should have been deployed to the module already. You can check the overlays.txt file to see, or even the boot logs would show what overlays are being loaded on boot.
We’ve managed to make a little more progress with the updates from Jeremias and looks like we have a overlay applied. At the moment there is nothing showing on the screen so we are making checks.
Looking at your overlays you have your custom overlay which sets timings to panel_dpi, but you also have display-vga_overlay.dtbo enabled which adds it’s own timings. Not sure which of these take precedence but it’s probably for the best you remove this overlay.
So in summary I would recommend:
Enable only colibri-imx6_parallel-rgb-overlay.dtbo and your overlay.
Modify your overlay to only have the panel_dpi section. The colibri-imx6_parallel-rgb-overlay.dtbo already sets the other nodes so doing this in your overlay would be redundant.
If your display still doesn’t work after this, it’s either a hardware related issue or you don’t have the correct display timings in your overlay.
Thanks for the update.
We’ve applied the first & second bullet points, nothing showing up just yet.
We’ll look at display timings next and see if that resolves the issue.
Just a quick follow up query.
Once everything is setup correctly, what would the LCD display?
i.e. would we typically see the boot up sequence?
or would be need to send something to the framebuffer, i.e. /dev/fb0 ?
or something else ?
Once everything is setup correctly, what would the LCD display?
This depends on what you running for containers. If you have the initial set of evaluation containers running then you should see portainer on the display output. Otherwise you can just run a graphical container as a test manually: Debian Containers for Torizon | Toradex Developer Center
would we typically see the boot up sequence?
On boot-up the only thing you would see is a splash screen.
