From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Hawkins <dwh@ovro.caltech.edu>
Date: Wed, 12 Sep 2007 13:09:36 -0700
Subject: [U-Boot-Users] R: Booting with attached BDI but not
 alone	(onlyICTRL remained in BDI cfg)
In-Reply-To: <F1F6EC0C8B75034F9E3A79FC85122E8E2649BF@aquib01a>
References: <F1F6EC0C8B75034F9E3A79FC85122E8EA642E2@aquib01a>
	<F1F6EC0C8B75034F9E3A79FC85122E8E2649BF@aquib01a>
Message-ID: <46E84780.3080602@ovro.caltech.edu>
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

DI BACCO ANTONIO - technolabs wrote:
>  > Is there any chance that the board is broken? I think I connected a 
> wiggler to the BDM port in the > wrong position for only a while. But 
> why should it boot with attached BDI if is it broken?
> 
> I discovered that when the board is powered on, if I try to connect BDI 
> connector trying to touch only pin 1 and 2 (vfls0 and sreset) the board 
> starts. I suspect that bdi pulls up the sreset in some way.

The JTAG/COP header *should* have the appropriate
pull-ups for HRESET#, and SRESET# *on the board*.
These are open-drain signals.

However, there could be a mistake on your board,
and perhaps the BDI2000 has weak pull-ups on the
BDI 'just in case' the pull-ups are missing on
the target.

Check your board schematic.

Dave