u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: early stage debugging on a real product
Date: Mon, 23 Nov 2020 12:08:23 -0700	[thread overview]
Message-ID: <CAPnjgZ0ZyMOadUXWJg8Js2TsM8RBZyui_OXcXK4LgnsFoe1yMQ@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VdPTU-THtHi3eRiD7rd_tC90fC66AiUvzMnoF2Ky0J_HQ@mail.gmail.com>

Hi Andy,

On Mon, 23 Nov 2020 at 07:04, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>
> Hi!
>
> I have been debugging U-Boot on a product (Android-based) device (*)
> which is not yet supported by U-Boot. It's x86 based.
>
> I have stumbled over the couple of things:
> 1/ it required me to enable TIMER_EARLY and by code analysing I can
> tell that DM loop fails by some reason
> 2/ it hangs
>    reserve_uboot,
>    reserve_malloc,
>    reserve_board,
>    ...here...
>
> My suspicion that fastboot does bad things to it (overwritten memory)
> or something I have missed. Any ideas what to try / where to look into
> besides the above which I'm on?

#define DEBUG at the top of board_f.c - you might need DEBUG_UART

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.

>
> (*) Only I can get is just an approximate place where the code is
> stuck / hangs. And it's time consuming...
>

Use a Dediprog SPI emulator and an Intel debugger.

Regards,
Simon

  parent reply	other threads:[~2020-11-23 19:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 14:05 early stage debugging on a real product Andy Shevchenko
2020-11-23 19:00 ` Andy Shevchenko
2020-11-23 19:08 ` Simon Glass [this message]
2020-11-23 19:18   ` Andy Shevchenko
2020-11-23 19:49     ` Andy Shevchenko
2020-11-24 13:58   ` Andy Shevchenko
2020-11-24 16:53     ` Simon Glass
2020-11-24 19:47       ` Andy Shevchenko
2020-11-24 23:41         ` Simon Glass
2020-11-25 11:26           ` Andy Shevchenko
2020-11-25 13:26           ` Andy Shevchenko
2020-11-25 14:49             ` Simon Glass
2020-11-25 15:08               ` Andy Shevchenko
2020-11-25 15:23                 ` Simon Glass
2020-11-25 15:36                   ` Andy Shevchenko
2020-11-25 15:45                     ` Simon Glass
2020-11-25 16:59                       ` Andy Shevchenko
2020-11-25 17:03                         ` Simon Glass
2020-11-25 20:43                           ` Andy Shevchenko
2020-11-25 15:56                     ` Ovidiu Panait
2020-11-25 16:09                       ` Andy Shevchenko
2020-11-25 17:11                     ` Siarhei Siamashka
2020-11-25 17:34                       ` Andy Shevchenko
2020-11-25 18:06                         ` Simon Glass

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPnjgZ0ZyMOadUXWJg8Js2TsM8RBZyui_OXcXK4LgnsFoe1yMQ@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).