From: emre kara <emrekara2002@yahoo.co.uk>
To: linuxppc-embedded@ozlabs.org
Subject: eldk4.0 ppc_85xx-gdb failure while debugging with BDI2000
Date: Tue, 15 Aug 2006 09:41:56 +0100 (BST) [thread overview]
Message-ID: <20060815084156.30290.qmail@web25915.mail.ukl.yahoo.com> (raw)
Dear All;
Is there any one use BDI2000 ppc_85xx-gdb (coming with
ELDK4.0 dist). Please examine the log below.
Target is waiting in start_kernel func.
ppc_85xx-gdb vmlinux
......
......
(gdb) target remote 192.168.101.101:2001
Remote debugging using 192.168.101.101:2001
0x00000000 in ?? ()
(gdb) q
gdb can not display correct addr and debug anything.
but at this state, older version toolchain (eldk3.1)
is working properly.
Second problem, I have check denx web site for an gdb
update and found
gdb-ppc_85xx-6.3.0.0-1.21_3.ppc.rpm,but instalation
fails with the error below.
-----------------------------------------
ppc_85xx-rpm -U gdb-ppc_85xx-6.3.0.0-1.21_3.ppc.rpm
error: Failed dependencies:
info-ppc_85xx is needed by
gdb-ppc_85xx-6.3.0.0-1.21_3.ppc
------------------------------------------
Here is my bdi configuration file:
--------------------------------------------------
;bdiGDB configuration file for MPC8540ADS
;----------------------------------------
[INIT]
WM32 0x000000f0 0x00000000 ;invalidate page table
base
[TARGET]
CPUTYPE 8540 ;the CPU type
JTAGCLOCK 0 ;use 16 MHz JTAG clock
STARTUP STOP 100 ;halt core while HRESET is
asserted
BREAKMODE SOFT ;SOFT or HARD, HARD uses PPC
hardware breakpoint
STEPMODE HWBP ;JTAG or HWBP, HWBP uses a hardware
breakpoint
MMU XLAT; for kernel debug
PTBASE 0xf0;for kernel debug
WAKEUP 500 ;give reset time to complete
POWERUP 5000 ;start delay after power-up detected
in ms
[HOST]
PROMPT 8540_KRNL>
[REGS]
FILE $reg8560.def
How can I solve this problems?
Thanks.
Emre
___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html
reply other threads:[~2006-08-15 8:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060815084156.30290.qmail@web25915.mail.ukl.yahoo.com \
--to=emrekara2002@yahoo.co.uk \
--cc=linuxppc-embedded@ozlabs.org \
/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