public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ilan Finci <list@finci.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] help starting
Date: Wed, 01 Dec 2004 08:44:11 +0200	[thread overview]
Message-ID: <41AD683B.9080105@finci.org> (raw)

Hi,
I'm totally new to the world of porting U-Boot (or other boot loaders) 
to new hardware.

I have an older version of U-Boot (0.4.5) that was ported to 2 custom 
made boards we have, based on the MPC5200 CPU, and the IceCube 
evaluation board. Both has the same U-Boot up and running.

We now have a new board, base on the same design, but with some 
modification.

I have BDI2000 up and running, and I can access the board's memory, 
flash, cpu registers etc.

When I try to run the same U-boot, it, as can be expected, fails to run, 
and stop very soon after startup (no message comes out on the serial 
console).

I've tried to connect with GDB to debug, and I manage to do it, then 
step few commands, and I get SIGSTOP. To make sure that this is not a 
problem of the new board, I've tried the same with a working board, and 
the U-Boot fails at the same place (right after the starting point). On 
the other hand, if I don't try to do a step by step debugging, but give 
a "cont" command, the U-boot (on the older board) does work.

So I guess I have a basic problem in understanding how to debug the 
U-Boot with GDB.

Any help (either specific, or pointers to guides), will be great.

Thanks,
Ilan

             reply	other threads:[~2004-12-01  6:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01  6:44 Ilan Finci [this message]
2004-12-01  7:22 ` [U-Boot-Users] help starting Wolfgang Denk
2004-12-01  9:06   ` Ilan Finci
2004-12-01 11:13     ` Wolfgang Denk
2004-12-01 11:20       ` Ilan Finci
  -- strict thread matches above, loose matches on Subject: below --
2004-12-02  8:48 Sam Song
2004-12-02  9:47 ` Wolfgang Denk
2004-12-02 13:02   ` Sam Song

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=41AD683B.9080105@finci.org \
    --to=list@finci.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