early stage debugging on a real product

[Simon Glass]

Hi Andy,

On Tue, 24 Nov 2020 at 12:46, Andy Shevchenko <andy.shevchenko at gmail.com> wrote:
>
> On Tue, Nov 24, 2020 at 6:54 PM Simon Glass <sjg at chromium.org> wrote:
> > On Tue, 24 Nov 2020 at 06:57, Andy Shevchenko <andy.shevchenko at gmail.com> wrote:
> > > On Mon, Nov 23, 2020 at 9:08 PM Simon Glass <sjg at chromium.org> wrote:
> > > > On Mon, 23 Nov 2020 at 07:04, Andy Shevchenko <andy.shevchenko at gmail.com> wrote:
>
> ...
>
> > > > Make sure that start.S puts the top of memory in a sensible place. If
> > > > something has set up RAM already then you probably want it to be the
> > > > top of RAM, below 2GB.
> > >
> > > Now I'm struggling to get *delay() working. In run_main_loop() if I
> > > call mdelay(<whatever>) the code gets stuck (presumably by not getting
> > > timer initialized and returning -EAGAIN).
> > > Any ideas?
> >
> > Do you mean in get_ticks() in lib/time.c ?
> >
> > Some panic() calls were recently added in there to check that the
> > timer is ready.
> >
> > Did you get the console working?
>
> Nope. The PCI (framebuffer) driver is not getting probed.
>
> Nevertheless the above problem is gone when I cleaned up configuration.

I'm amazed how far you can get without a UART. There must be a way to
make it ouput...

Regards,
Simon