public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Debugging U-boot with BDI-2000 on MPC8349
Date: Thu, 14 Sep 2006 15:39:24 -0400	[thread overview]
Message-ID: <4509AFEC.6090904@smiths-aerospace.com> (raw)
In-Reply-To: <1158261618.16415.68.camel@saruman.qstreams.net>

Ben Warren wrote:
> Thanks Timur,
> 
> On Thu, 2006-09-14 at 13:57 -0500, Timur Tabi wrote:
>> Ben Warren wrote:
>>> Hello,
>>>
>>> Has anybody been able to successfully single step through U-boot code on
>>> an MPC8349 CPU using a BDI-2000?  
>> I've attached two config files.  One can be used to flash the 9349E-mITX, and the other can be used to debug it.
>>
>> The flash-enabled one programs a bunch of registers that wake up the flash chip.  Unfortunately, when using this config, U-boot hangs somewhere in start.S.  I'm probably programming the board just differently enough to confuse U-Boot.
>>
>> The other config programs nothing, which gives U-Boot a clean slate to program.
>>
> The config I use to debug is much like your second one.  In general,
> less is more.
>> I presume it should be possible to create a "unified" config that works in both situations, but I haven't had the time to try it.
>>
>> I've never used GDB with the BDI.
> 
> I've used it with Linux drivers and it's really very slick.  I imagine
> it would be excellent with U-boot too, if I could get it to work in code
> other than start.S.
> 
> regards,
> Ben

Have you tried the FAQ "10.1.2. Debugging of U-Boot After Relocation"?
<http://www.denx.de/wiki/view/DULG/DebuggingUBoot>

gvb

  reply	other threads:[~2006-09-14 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 18:52 [U-Boot-Users] Debugging U-boot with BDI-2000 on MPC8349 Ben Warren
2006-09-14 18:57 ` Timur Tabi
2006-09-14 19:20   ` Ben Warren
2006-09-14 19:39     ` Jerry Van Baren [this message]
2006-09-14 19:53       ` Ben Warren

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=4509AFEC.6090904@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.com \
    --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