public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: George G. Davis <gdavis@mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Doubts about usage of BDI2000 !
Date: Thu, 14 Oct 2004 16:16:35 -0400	[thread overview]
Message-ID: <20041014201635.GN8731@mvista.com> (raw)
In-Reply-To: <93AC2F9171509C4C9CFC01009A820FA0117436@blr-ec-msg05.wipro.com>

On Thu, Oct 14, 2004 at 08:46:16PM +0530, ravi.aloor at wipro.com wrote:
> 
> Hi, I am new to u-boot. I have few doubts. A brief explanation about my
> working environment:
> 	- ARM11 based target board, having its own IP address
> 	- PC running on RedHat Linux-8.0, having its own IP address
> 	- BDI2000, having its own IP address
> 	- PC and BDI2000 are connected to the network
> 		(IP address for BDI2000 is 192.168.226.159)
> 	- U-boot is already available on target board in the flash
> memory
> 	- Firmware is already available on BDI2000
> 	- BDI2000 is connected to the target board through
> 	- Using gdb-6.1 configured with --target=arm-linux
> 
> The following are my doubts:
> 1. I want to debug u-boot. So to start debugging u-boot, Do I need to
> use bare target board that does not contain u-boot already ?
> 
> 2. I could not start debugging u-boot. So I started debugging kernel
> with the target board that already contains u-boot. Please check the
> following:
> 
> [ravi at localhost 2.6_kernel]$ /home/ravi/gdb-6.1/temp/gdb/gdb vmlinux
> GNU gdb 6.1
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "--host=i686-pc-linux-gnu
> --target=arm-linux"...
> (gdb)
> (gdb) target remote 192.168.226.159:2001
> 192.168.226.159:2001: Connection refused.
> (gdb) target remote bdi:2001
> bdi:2001: Connection refused.

Based on that response, I would guess that your BDI2000 is not yet
configured and connected to the target yet, i.e. the BDI2000 has
not successfully detected any target CPU on the JTAG chain. Try
using `telnet 192.168.226.159` to see what's going on with the
BDI2000. Also, try referring to the BDI manual for help configuring
the BDI and, of course, talk to your processor/board vendor to
resolve BDI setup/config details. Does the BDI2000 even support ARM11
based processors yet?

--
Regards,
George

> (gdb) quit
> [ravi at localhost 2.6_kernel]$
> 
> Please help me ... Thanks A Lot In Advance,
> Ravi
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users

  parent reply	other threads:[~2004-10-14 20:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 15:16 [U-Boot-Users] Doubts about usage of BDI2000 ! ravi.aloor at wipro.com
2004-10-14 19:55 ` T Michael Turney
2004-10-14 20:16 ` George G. Davis [this message]
2004-10-14 21:06 ` Wolfgang Denk
2004-10-16  6:10   ` George G. Davis
  -- strict thread matches above, loose matches on Subject: below --
2004-10-14 19:28 VanBaren, Gerald
2004-10-14 20:40 Woodruff, Richard
2004-10-16  9:05 ravi.aloor at wipro.com

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=20041014201635.GN8731@mvista.com \
    --to=gdavis@mvista.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