We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I am having problems to the 2106 using the secondary JTAG, this is on a prototype board. uVision gives me the message: "Couldn't stop the ARM device. Check the JTAG cable" The particulars: DBGSEL is pulled low. RTCK is pulled low TRST, TDI, TDO, and TMS are pulled high TCK is pulled low 14.7456 MHz Xtal I have used this setup in two ther designs without problems. I configure PINSEL2 to 0x55400000 as I always have. I have slow the JTAG as slow as it will go. I can see all the signals active (except RTCK) on the logic analyser. Ideas? Thanks Rich
More Information: I have tried an existing product, using the LPC2106 and 2nd JTAG, on another uVision installation and it works fine. I used my Ulink. So it appears the problem is with my software setup. I have tried, extensively, all debugger settings, always returning to the default. I can see the target reset when I attempt to connect but then I always get the "Couldn't stop the ARM......" Any ideas would be appreciated. Are there drivers I can replace etc? Rich
Richard, did you really read everything in the knowledgebase article. There is also an option that you need to
disable Use Reset at Startup
I have played with that option as well. Thanks Rich
Reinhard, Your mentioning of that dll file got me thinking. Since I have tried everything that I can think of short of sacrificing a chicken, I took a look at that file. Like I mentioned, my co-workers installation works fine. His UL2ARM.dll version is earlier than mine. Out of desperation I replaced my UL2ARM.dll (V1.14) with an older one (V1.11). It now works great! There is a timing problem introduced by this dll, it only seems to affect the secondary JTAG. Perhaps it is PC dependent, I don't know. An interesting note, version 1.14 DOES work on an IAR kickstart board. This board has 74x244 buffers inline with the JTAG signals. I suspect these buffers "correct" the timing enough so it works. Let me know that you see this, I think it is important. Rich