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.
Howdy, I received a MCB2370 and a ULINK2 recently. I want to try it. After I installed Realview MDK V3.04 to my computer (windows XP), I got a trouble in ULINK2 communication. Here the details. 1. Install Realview MDK V3.04 OK! 2. Plug in USB cable in ULINK2 to computer, computer found this new device and install driver automatically. After that, I can find this Human Interface Devices in windows Device Manager. Open the Properties page for this device. Under General — Location I can find the name Keil ULINK2 which indicates that the ULINK2 adapter is connected properly. 3. Connect 20pin JTAG cable to MCB2370. Jumper is on the J13. 4. Turn on power by connecting USB cable from PC to MCB2370. I can find the program already running in MCB2370 flash. The LCD display " MCB2370 DEMO" and P2.0-P2.7 LED and LCD bar graph display changed when I adjusted POT1. It looks board works fine. 5. Run "Keil uVision3" and load your sample project BLINKY to uVision3. I can build BLINKY without error. Select Project -> Options for Target 'LPC2378 Flash' dialog. Open Debug section, then select the ULINK ARM Debugger as the Flash-programming tool. When clicking the Settings button to open the Flash Download Setup dialog, I can find MCB2370 was resetting. In ARM Target Driver Setup section, I found Error display "JTAG Communication Failure" in JTAG Device Chian section. Also, I can not find "Serial Number", "ULINK Version", "Device Family" information in ULINK USB-JTAG Adapter section. 6. When I select Flash -> Download, an Error block appears with "JTAG Communication Failure". At this time, I can find "COM" blue LED is on in the ULINK2. After clicking "OK' button, blue LED is off. 7. I already checked some topic about ULINK communication Failure in Keil WEB and changed jumper position from "ARM" to "3.3V" in the ULINK2 board. But it is no use.
Would you help me to solve this problem?
Thank you very much.
Roy Zhang
Thank you so much for your reply. At first, I checked JTAG clock rate we used right now. It is 200KHz. I am tried to reduce it to 100 KHz and 50KHz, but the problem still happen. Second, you mentioned "select RTCK with ULINK2". I don't know how to do it. I means taking off jumper from J13? Actually I ever tried to take off J13 jumper to test board, but no use. One thing I got confusing. If I select "Use Reset at Startup" in "Misc Options", software can reset MCB2370 board when I clicking the "Settings" button to open the "Flash Download Setup" dialog. It looks some communication already done. Hope to get your more advices.
Appreciate!
1) Get the latest version of uV and update it. (if you had not done it already)
2) If you had connected com port of PC to UART0 either disable the reset through com0 jumper on the board or remove the UART0 connection.
Suvidh
Also open ULINK2 case and check PCB for solder drops or shorts - mine had solder drop on JTAG connector shorting TCK to ground. Several other users reported similar problems...
- Dejan
I have exactly the same problem as described above... Did you end up with a solution on the issue? The strange thing is that when I have the ULink2 disconnected from the board the uVision reads its serial number and connects to it, but when I connects it to the board via the JTAG cable the serial number and the connection is lost...
Hi, After I got replaced ULINK2 from provider, the problem solved. I really don't know what happened in old ULINK2. Maybe the firmware inside ULINK2 is not correct.
I am having the same problem. Under ARM target Driver Setup it shows my ULINK2 with firmware version 1.10 but the tutorials show V2.1. Is the firmware just out of date?