From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dmytro Bablinyuk <dmytro.bablinyuk@rftechnology.com.au>
Date: Thu, 06 Oct 2005 08:36:08 +1000
Subject: [U-Boot-Users] Re: Bdi and u-boot
In-Reply-To: <3B58B875DBDE504F94D2A1A1C9DF6F1F02BE161B@bglnt005.asia.ad.flextronics.com>
References: <3B58B875DBDE504F94D2A1A1C9DF6F1F02BE161B@bglnt005.asia.ad.flextronics.com>
Message-ID: <43445558.7080304@rftechnology.com.au>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

>     Check whether you have commneted the memory initialization part in 
> your BDI configuration file. 

Thank you! Yes, now I can just do (gdb)c.
The only thing remains is when I do

(gdb) c
Continuing.

Breakpoint 1, <signal handler called>
(gdb) n
<never comes back>

GDB never comes back on 'n' command and BDI shows
- TARGET: stepped
- TARGET: stepped
- TARGET: stepped
- TARGET: stepped
- TARGET: stepped
- TARGET: stepped
- TARGET: stepped
- TARGET: stepped
...

Does anybody knows what that mean. In BDI config in init part I have 
left only one line uncommented
WM32    0x0F010004      0xFFFFFFC3      ;SYPCR: disable watchdog
IMMR and everything else in init part is commented.

Thank you