[U-Boot-Users] Doubts about usage of BDI2000 !
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@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. (gdb) quit [ravi@localhost 2.6_kernel]$
Please help me ... Thanks A Lot In Advance, Ravi
Please provide IP addresses for all three devices on your development network. RHL8 host? BDI2000 JTAG pod? ARM 11 target?
Did you run bdisetup on RHL8 host to initialize BDI2000?
If U-boot is already in flash why do you want to debug it?
You should be able to use BDI2000 to download new version of U-Boot to debug. You should also be able to use BDI2000 to debug kernel as you are trying to do.
Make sure tftp server is running on RHL8 host.
Cheers, T.mike
-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of ravi.aloor@wipro.com Sent: Thursday, October 14, 2004 8:16 AM To: u-boot-users@lists.sourceforge.net Subject: [U-Boot-Users] Doubts about usage of BDI2000 !
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:
- 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 ?
- 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@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. (gdb) quit [ravi@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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
On Thu, Oct 14, 2004 at 08:46:16PM +0530, ravi.aloor@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:
- 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 ?
- 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@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@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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
In message 93AC2F9171509C4C9CFC01009A820FA0117436@blr-ec-msg05.wipro.com you wrote:
- 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 ?
No. You do the same as always: load (i. e. program to flash) the code and then start it under control of the debugger.
- 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:
This makes no sense. It's like in real life: If the first (simpler) step fails, you should not even think about doing the next step, because usually this will just get you a bloody nose.
(gdb) target remote 192.168.226.159:2001 192.168.226.159:2001: Connection refused. (gdb) target remote bdi:2001 bdi:2001: Connection refused.
Seems you BDI2000 is configured for a different IP address or network, or not powered on, or not connected to the network.
Best regards,
Wolfgang Denk
On Thu, Oct 14, 2004 at 11:06:10PM +0200, Wolfgang Denk wrote:
(gdb) target remote 192.168.226.159:2001 192.168.226.159:2001: Connection refused. (gdb) target remote bdi:2001 bdi:2001: Connection refused.
Seems you BDI2000 is configured for a different IP address or network, or not powered on, or not connected to the network.
FWIW, the BDI2000 responds this way when it is either improperly configured or did not detect a device on the scan chain. I verified this by attempting to do `target remote bdi:2001` to my BDI2000 when it was not connected to a target, it refuses the connection. OTOH, it accepted a telnet session and showed that no target was detected as per usual. Please verify that you've properly configured your BDI2000, i.e. read fancy the manual. : P
-- Regards, George
participants (4)
-
George G. Davis -
ravi.aloor＠wipro.com -
T Michael Turney -
Wolfgang Denk