Reply by Christian Brauchli June 22, 20032003-06-22
Hi,

at the beginning of my 5680x experience 3 years ago I faced the same problem
that the Parallel/ Jtag Interface was not working with my Notebook. Reason:
The Debugging and Downloading was not working with Windows2000, Win98 but it
was working with Win95. Remember I tried all on the same notebook. Somehow
strange isn't it? But it seams so that Codewarrier running on different
Windows Operating system are different. Finally I had to install a different
partition (Win95) on my Notebook just for Codewarrier and Win2000 for all
the other nice things I have to do througout the day. (Different Bios
Settings or a Parallel-Booster didn't help, if you need a parallel booster I
have an unused one)

kind regards
Christian Brauchli
__________________________________
BRAUCHLI NETSOLUTION BERG
Bahnhofstrasse 7
CH- 8572 Berg
Switzerland
Tel. +41/ 71 / 638 00 45
Fax. +41/ 71 / 638 00 46
Mob. +41/ 78 / 616 22 14
email.
www.brauchli-netsolution.ch
__________________________________ -----Original Message-----
From: Charlie W [mailto:]
Sent: Samstag, 21. Juni 2003 06:33
To: cmafatcontroller;
Subject: Re: [motoroladsp] JTAG Hardware Failure Ian,
We have seen some JTAG failures. The most problems
came from JTAG converter and paralle cable. My
experiences are 1) use as short parallel cable as
possible, 2) go to computer BIOS, try different
parallel port operation mode. 3)If JTAG converter uses
74AC244 or 245 as buffer, try different brand computer
or use different length parallel cable; finally use a
parallel boost. hopefully these tips help.

Charlie. --- cmafatcontroller <> wrote:
> Has anybody had experience with apparent hardware
> failure localised
> to JTAG functions on 5680x's ? We had 3 NewMicros
> boards fail
> yesterday, where symptom of failure is no connection
> to board from
> CodeWarrior, however at least 1 of the boards during
> the attempted
> connection/ download would reset and start
> initialising previously
> loaded code. Have confirmed the problem is with the
> DSP, not the PC
> or cable.
>
> What might cause a failure of this type ?
>
> Thanks,
>
> Ian Duncan >


__________________________________
_____________________________________
Note: If you do a simple "reply" with your email client, only the author of
this message will receive your answer. You need to do a "reply all" if you
want your answer to be distributed to the entire group.

_____________________________________
About this discussion group:

To Join:

To Post:

To Leave:

Archives: http://www.yahoogroups.com/group/motoroladsp

More Groups: http://www.dsprelated.com/groups.php3 ">http://docs.yahoo.com/info/terms/


Reply by Charlie W June 21, 20032003-06-21
Ian,
We have seen some JTAG failures. The most problems
came from JTAG converter and paralle cable. My
experiences are 1) use as short parallel cable as
possible, 2) go to computer BIOS, try different
parallel port operation mode. 3)If JTAG converter uses
74AC244 or 245 as buffer, try different brand computer
or use different length parallel cable; finally use a
parallel boost. hopefully these tips help.

Charlie. --- cmafatcontroller <> wrote:
> Has anybody had experience with apparent hardware
> failure localised
> to JTAG functions on 5680x's ? We had 3 NewMicros
> boards fail
> yesterday, where symptom of failure is no connection
> to board from
> CodeWarrior, however at least 1 of the boards during
> the attempted
> connection/ download would reset and start
> initialising previously
> loaded code. Have confirmed the problem is with the
> DSP, not the PC
> or cable.
>
> What might cause a failure of this type ?
>
> Thanks,
>
> Ian Duncan >


__________________________________



Reply by cmafatcontroller June 21, 20032003-06-21
Has anybody had experience with apparent hardware failure localised
to JTAG functions on 5680x's ? We had 3 NewMicros boards fail
yesterday, where symptom of failure is no connection to board from
CodeWarrior, however at least 1 of the boards during the attempted
connection/ download would reset and start initialising previously
loaded code. Have confirmed the problem is with the DSP, not the PC
or cable.

What might cause a failure of this type ?

Thanks,

Ian Duncan