From: Christian Kapeller <christian.kapeller@gmx.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Debugging u-boot using an EPI Majic JTAG
Date: Thu, 21 Oct 2004 18:10:10 +0200 [thread overview]
Message-ID: <20041021161010.GA18274@localhost> (raw)
Hi!
I'm trying to debug u-boot 1.1.1 using a EPI Majic JTAG probe for arm
processors on an PXA255.
I load the compiled elf-binary down using the JTAG, and try to run it.
I get immediately a "Hardware instruction breakpoint" message. Other
binaries run without problems using the JTAG. Also when i flash u-boot
it works.
Has anyone of you used a EPI Majic to debug u-boot successfully?
Here are the logs:
--snip--
EPI Symbolic Assembly Level Debug Monitor, version V6.9.7 - Linux(x86)
Copyright (c) 1987-2000 by Embedded Performance Inc. - All Rights Reserved.
Processing register file: /home/chrkap/tinylinux/edta21/bin/arm/spaces.rd
Processing register file: /home/chrkap/tinylinux/edta21/bin/arm/pxa250.rd
Processing register file: /home/chrkap/tinylinux/edta21/bin/arm/80200.rd
Processing register file: /home/chrkap/tinylinux/edta21/bin/arm/majic.rd
Reading command history from: '/home/chrkap/tinylinux/edta21/bin/startedb.hst'
Establishing communications with remote target via 192.168.0.2...
Connection verified
Target System: EPI Majic Probe, Version: 3.2.6, S/N 0310H016
Hardware Rev: a0:3:3:10
Target CPU: PXA21x/PXA25x/PXA26x
Ethernet: at address 00:80:CF:00:17:FA
IP address: 192.168.0.2, Subnet mask: 255.255.255.0
Trace Buffer: 0 frames
Profiler: Not Installed
Connected via: Ethernet UDP/IP
Device name: 192.168.0.2
Target Endian: little
Start Address: 00000000:
EPI-OS (HIF): on
Reset Mode: capture
Reading commands from /home/chrkap/tinylinux/edta21/bin/startice.cmd
MON> +q // Enter quiet mode
Reading startice.cmd file
Notification from the target:
Target power detected on VREF
Auto JTAG detection process detected 1 TAP
JTAG connection established
Reading dbpxa250.cmd
Executing One Time Setup Commands
Executing Target Init Commands
48000008: 26F226F2
4800000c: 3FF4A441
48000010: 00007FF0
48000004: 00010018
a0000000: 00000000 00000000 00000000 00000000
a0000010: 00000000 00000000 00000000 00000000
a0000020: 00000000 00000000 00000000 00000000
a0000030: 00000000 00000000 00000000 00000000
a0000040: 00000000 00000000 00000000 00000000
a0000050: 00000000 00000000 00000000 00000000
a0000060: 00000000 00000000 00000000 00000000
a0000070: 00000000 00000000 00000000 00000000
a0000080: 00000000 00000000 00000000 00000000
a0000090: 00000000 00000000 00000000 00000000
a00000a0: 00000000 00000000 00000000 00000000
a00000b0: 00000000 00000000 00000000 00000000
a00000c0: 00000000 00000000 00000000 00000000
a00000d0: 00000000 00000000 00000000 00000000
a00000e0: 00000000 00000000 00000000 00000000
a00000f0: 00000000 00000000 00000000 00000000
Finished reading dbpxa250.cmd
Finished reading startice.cmd
MON> l /home/chrkap/u-boot/u-boot
loading /home/chrkap/u-boot/u-boot
section .text from a3f80000 to a3f93cd7
section .rodata from a3f93cd8 to a3f941cb
section .rodata. from a3f941cc to a3f9840a
section .data from a3f9840c to a3f98d17
section .u_boot_ from a3f98d18 to a3f991c7
section .bss from a3f991c8 to a3f9d70b
Entry address set (pc): a3f80000
$a:
a3f80000: ea000012 B 0xA3F80050 ; $a
MON> g
Hardware instruction breakpoint
0000000c: e59ff014 LDR pc,0x28
MON>
--snap--
reply other threads:[~2004-10-21 16:10 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=20041021161010.GA18274@localhost \
--to=christian.kapeller@gmx.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.