public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vlad Lungu <vlad@comsys.ro>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Au1550 U-boot debugging - a newbie question
Date: Tue, 19 Feb 2008 11:52:26 +0200	[thread overview]
Message-ID: <47BAA6DA.1030400@comsys.ro> (raw)
In-Reply-To: <15559852.post@talk.nabble.com>

RadekFisera wrote:
> I'm using U-boot 1.3.0. The hardware breakpoint option is set in BDI2000
> configuration file in target part (initial memory controller registers
> settings is also in this file)
> [TARGET]
> JTAGCLOCK   0      		;use 16 MHz JTAG clock
> CPUTYPE     AU1000	        ;AU1000  ;the used target CPU type
> ENDIAN      LITTLE              ;target is little endian
> STARTUP     RESET
> RESET       JTAG		;the reset type (NONE, JTAG, HARD)
> BDIMODE     AGENT   	        ;the BDI working mode (LOADONLY | AGENT)
> BREAKMODE   HARD          	;SOFT or HARD, HARD uses PPC hardware breakpoints
> STEPMODE    JTAG                ;JTAG, HWBP or SWBP
> VECTOR      CATCH               ;catch unhandled exceptions
>
> I know that during debugging program in flash only HW breakpoints are
> enabled. I tried to set breakpoint in gdb via command "break" and "hbreak"
> also. In both case I have observeeed the same behaviour (SIGABRT after stepi
> and "*** TARGET: all hardware breakpoints in use " in the telnet session
> window). I've tried HWBP option instead of JTAG when chosing the stepmode
> for BDI 2000.
>   
Are you sure you have hardware breakpoints  on that target? And if you 
do, isn't that breakpoint (it's probably only one available)
already used maybe? Check the BDI and Au1000 docs.

Also, maybe you should try commenting VECTOR CATCH. That signal looks 
funny to me.


Vlad

  reply	other threads:[~2008-02-19  9:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 14:37 [U-Boot-Users] Au1550 U-boot debugging - a newbie question RadekFisera
2008-02-18 15:21 ` Shinya Kuribayashi
2008-02-19  7:25   ` RadekFisera
2008-02-19  9:52     ` Vlad Lungu [this message]
2008-02-20 10:05       ` RadekFisera

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=47BAA6DA.1030400@comsys.ro \
    --to=vlad@comsys.ro \
    --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