|ARM Technical Support Knowledge Articles|
Applies to: ULINK USB-JTAG Debugger
Information in this article applies to:
I have used the Analog Devices ADuC7020 Development Kit together with Keil µVision3 and the Keil CARM Compiler. Since I have configured the chip to use the ADCBUSY signal on IO Pin P0.3 the ULINK is dead. I know that this pin is shared with the TRST signal that is used by the JTAG interface, but I would like to know if there is an alternative solution to this problem.
You are correct. The problem lies with the fact that P0.3 is used for both TRST and ADCBUSY. You can just re-configure the I/O pins so that the ADCBUSY uses the P0.5 as output. In this way, there is no collision.
Article last edited on: 2007-01-28 19:15:43
Did you find this article helpful? Yes No
How can we improve this article?