Re: [meta-ti] core-image-sato scarthgap beaglebone x11 startup error

[Denys Dmytriyenko <denis@denix.org>]

On Thu, May 08, 2025 at 01:33:39PM -0500, Randolph Sapp via lists.yoctoproject.org wrote:
> On Wed May 7, 2025 at 12:40 AM CDT, Sebastian via lists.yoctoproject.org wrote:
> > The actual target is to deploy a kiosk system running on chromium with a touch screen.
> >
> > At first I've tried to adopt my patches from kirkstone on scarthgap (device tree and uBoot) to setup the same configuration but it has failed at some missing libglesX.so.2 (haven't got the log at hand) and I was walking back to check when the diverge happens. So I've found out it is not specific related to my introduced chromium but it seems to be related to meta-ti.
> >
> > I'm not bound to X but I've hoped by using the core targets I'll get a window manager running like in kirkstone.
> >
> > I've attached the log from the debug output.
> >
> > Regards,
> >
> > Sebastian
> 
> [    3.524779] tilcdc 4830e000.lcdc: bound 0-0070 (ops 0xc11c332c)
> [    3.532676] [drm] Initialized tilcdc 1.0.0 20121205 for 4830e000.lcdc on minor 0
> [    3.540717] tilcdc 4830e000.lcdc: [drm] Cannot find any crtc or sizes
> [    3.547695] tilcdc 4830e000.lcdc: [drm] Cannot find any crtc or sizes
> 
> These logs in particular are showing that tilcdc is loading and initializing the
> device but it's unable to detect any display. Nothing GFX related will be able
> to work, aside from offscreen rendering, in this case.
> 
> I'd double check overlays or other configurations depending on what connection
> method you are using for your display. You should probably take this to the
> beagleboard forums though as it seems to be more related to your particular
> setup.

I would also suggest trying to run a build for "am335x-evm" MACHINE, which 
is a superset for this SoC that also supports BeagleBone Black (and others). 
As that build uses the latest TI 6.12 BSP, so would be interesting to see if 
the display gets detected properly there.

-- 
Denys