public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
* [U-Boot-Users] BDI2000 with pxa255
@ 2005-01-20 14:50 Hinko Kocevar
  2005-01-20 15:15 ` Matej Kupljen
  0 siblings, 1 reply; 6+ messages in thread
From: Hinko Kocevar @ 2005-01-20 14:50 UTC (permalink / raw)
  To: u-boot

Hi,

I've connected bdi2000 to the host computer and successfully updated 
firmware and managed to telnet to the bdi. I also adapted cfg file for 
my platform (KK trizeps2). When I power up the target device I get this 
error:
...
- TARGET: target will be restarted in 10 sec
- TARGET: processing reset request
- TARGET: BDI asserts RESET and TRST
- TARGET: BDI removed TRST
- TARGET: Bypass check: 0x000000001 => 0x00000000
- TARGET: JTAG exists check failed
# TARGET: resetting target failed
# JTAG: communication with target failed
- TARGET: target will be restarted in 10 sec
...

Can somebody point me to the possible causes for this behaviour?

PS. Is it mandatory to supply ~RESET pin to BDI? Can I just keep it in 
reset with a jumper closed? Trizeps2 is lacking this pin on JTAG connector.

best regards,
hk

-- 
hinko <dot> kocevar <at> iskramedical <dot> si
Hinko Kocevar, embedded systems developer
Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU

	"A? r?n"	|	[Analects XII:22]

^ permalink raw reply	[flat|nested] 6+ messages in thread
* [U-Boot-Users] BDI2000 with pxa255
@ 2005-01-20 15:16 Paugam Luc
  2005-01-24 15:49 ` Hinko Kocevar
  0 siblings, 1 reply; 6+ messages in thread
From: Paugam Luc @ 2005-01-20 15:16 UTC (permalink / raw)
  To: u-boot

Hi,

There is a problem with your JTAG link or chain.
The important line is: 
	- TARGET: Bypass check: 0x000000001 => 0x00000000
It says roughly: (as you know, a JTAG chain is let say "a serial link looped") After setting all JTAG controllers into the JTAG chain to bypass mode, I sent a 1 (only 1 bit) and tried to get back this bit ... but in your case without success!

Regards - Luc

-----Original Message-----
From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin at lists.sourceforge.net] On Behalf Of Hinko Kocevar
Sent: jeudi 20 janvier 2005 15:51
To: u-boot-users at lists.sourceforge.net
Subject: [U-Boot-Users] BDI2000 with pxa255

Hi,

I've connected bdi2000 to the host computer and successfully updated 
firmware and managed to telnet to the bdi. I also adapted cfg file for 
my platform (KK trizeps2). When I power up the target device I get this 
error:
...
- TARGET: target will be restarted in 10 sec
- TARGET: processing reset request
- TARGET: BDI asserts RESET and TRST
- TARGET: BDI removed TRST
- TARGET: Bypass check: 0x000000001 => 0x00000000
- TARGET: JTAG exists check failed
# TARGET: resetting target failed
# JTAG: communication with target failed
- TARGET: target will be restarted in 10 sec
...

Can somebody point me to the possible causes for this behaviour?

PS. Is it mandatory to supply ~RESET pin to BDI? Can I just keep it in 
reset with a jumper closed? Trizeps2 is lacking this pin on JTAG connector.

best regards,
hk

-- 
hinko <dot> kocevar <at> iskramedical <dot> si
Hinko Kocevar, embedded systems developer
Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU

	"A? r?n"	|	[Analects XII:22]


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users

^ permalink raw reply	[flat|nested] 6+ messages in thread
* [U-Boot-Users] BDI2000 with pxa255
@ 2005-01-26  9:49 Paugam Luc
  0 siblings, 0 replies; 6+ messages in thread
From: Paugam Luc @ 2005-01-26  9:49 UTC (permalink / raw)
  To: u-boot

The BDI2000 systematically try to reset the CPU if the JTAG's Bypass check fails. So, there is no issue with the reset line even if it is asserted by the BDI2000.

Many think can introduce issues with your JTAG:
	- If you have several chips in your chain, the chain is broken somewhere.
	- If you have several chips in your chain, the POST or PRE "scan access" to your CPU are wrongs.
	- Your CPU has not properly selected its JTAG port (e.g. there is an errata on the AT91RM9200).
	- Wrong firmware inside the BDI2000.
	- Wrong wiring of the JTAG connector
	- ...etc

Hope that helps.
Regards - Luc

-----Original Message-----
From: Hinko Kocevar [mailto:hinko at iskramedical.si] 
Sent: lundi 24 janvier 2005 16:49
To: Paugam Luc
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] BDI2000 with pxa255

Paugam Luc wrote:
> Hi,
> 
> There is a problem with your JTAG link or chain.
> The important line is: 
> 	- TARGET: Bypass check: 0x000000001 => 0x00000000
> It says roughly: (as you know, a JTAG chain is let say "a serial link looped") After setting all JTAG controllers into the JTAG chain to bypass mode, I sent a 1 (only 1 bit) and tried to get back this bit ... but in your case without success!
> 

So, this could mean that other (TDI,TDO) JTAG lines do not operate 
properly - or is this consequently because target was not reseted properly?

regards,
hk

-- 
hinko <dot> kocevar <at> iskramedical <dot> si
Hinko Kocevar, embedded systems developer
Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU

	"A? r?n"	|	[Analects XII:22]

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2005-01-26  9:49 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-01-20 14:50 [U-Boot-Users] BDI2000 with pxa255 Hinko Kocevar
2005-01-20 15:15 ` Matej Kupljen
2005-01-24 15:46   ` Hinko Kocevar
  -- strict thread matches above, loose matches on Subject: below --
2005-01-20 15:16 Paugam Luc
2005-01-24 15:49 ` Hinko Kocevar
2005-01-26  9:49 Paugam Luc

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox