--- In lpc2100@yahoogroups.com, "Hugh O'Keeffe" <hugh.okeeffe@a...> wrote: > Ashling have seen problems with the secondary debug port as well. > Sometimes it works, sometimes it doesn't. We have been able to > debug/flash via the secondary port, however, not consistently and > reliably. From a recent batch of twenty of our EVBA7 boards we had five > secondary debug failures. We are confident we are doing the right thing > and that it is not a tool issue (we have reproduced the problem with ARM > MultiICE as well). > > > Hugh @ http://www.ashling.com/support/lpc2100/ > > > -----Original Message----- > From: Jim Beagley [mailto:jim5272@h...] > Sent: 21 January 2004 00:59 > To: lpc2100@yahoogroups.com > Subject: [lpc2100] Re: Secondary JTAG problem. -> succesfull solution > > > > Using the Primary for program, and then switching to secondary for > debug works fine. Attempting to program in Secondary mode fails at > every attempt, and only serves to corrupt the currently flashed > program, after which the primary port is required to aleviate the > problem. The following points out that that the secondary JTAG is *only* intended for debugging: http://www.semiconductors.philips.com/acrobat/applicationnotes/AN10255_1.pdf Leon
Message
Re: Secondary JTAG problem. -> succesfull solution
2004-01-22 by leon_heller
Attachments
- No local attachments were found for this message.