arm jtag interface.

[ongth60]

Posted on August 09, 2005 at 02:00

arm jtag interface.

[ongth60]

Posted on July 08, 2005 at 01:33

Hi,

My fabricated main board that contains the ARM cpu could worked well with the JTAG board from the evaluation board. I soldered some wires from the JTAG port of the evaluation board to my fabricated main board which contains the ARM cpu. The link is robust and I can connect and disconnect at every instance. The reason I'm using this method is that I can't get a robust link with another JTAG board which I have constructed based on the schematics(debug1.jpg and debug2.jpg) posted above. JTAG board constructed based on debug1.jpg schematic can work but the link is not robust enough. It can connect only 3 times out of 10 times), so I've decided to construct the other JTAG board which contains the reset circuitry based on debug2.jpg.(Pls note that I've changed the transistors) By then, it could nt work well and the errors that I've got are stated above. So, now I've tried to test with a workable evaluation board but my emulator refuse to cooperate. rgrds, ongth60

[ongth60]

Posted on July 08, 2005 at 05:24

Hi ibtiss,

Thanks for ur support. 1.I've tried rebooting the PC before running the RVD and the same problem still occurs. 2.The second option is how do i run armcc from command line? Pls advise. Rgrds, ongth60

[ongth60]

Posted on July 08, 2005 at 07:23

Hi,

Ive got the below: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Jim>armcc ARM/Thumb C/C++ Compiler, RVCT2.0.1 [Build 313] for ST [basic for ARM7] Usage: armcc [options] file1 file2 ... filen Main options: --arm Generate ARM code --thumb Generate Thumb code --c90 Switch to C mode (default for .c files) -O0 Minimum optimization -O1 Restricted optimization for debugging -O2 Maximum optimization -Ospace Optimize for codesize -Otime Optimize for maximum performance --cpu Select CPU to generate code for (eg. ARM9E/ARM10E) -o Name the final output file of the compilation -c Compile only, do not link --asm Output assembly code as well as object code -S Output assembly code instead of object code -fs Interleave source with disassembly (use with -asm or -S) -E Preprocess the C source code only -D Define on entry to the compiler -g Generate tables for high-level debugging -I Include on the #include search path For support please contact your tools supplier Software supplied by: ARM Limited License is dongled to RVI-ME C:\Documents and Settings\Jim> Err, what is the command syntax to connect RVI-ME via DOS? rgrds, ongth60

[ongth60]

Posted on July 08, 2005 at 08:07

Hi,

I've tried the autoconfigure scan chain Respond was: Error:Auto configure failed. Check the RVI connection with the target or try using a lower fixed frequency. rgrds, ongth60

[ongth60]

Posted on July 10, 2005 at 04:48

Hi ibtiss,

i dun have an example in the onchip flash memory, therefore I can't confrim with you whether the RVIME is broken or not. However, I have probed the signals of JTAG with J4 jumper not fitted: Signals of JTAG when not connected to emulator: Pin 1 - 3.29V Pin 2 - 3.29V Pin 3 - 3.29V Pin 4 - ground Pin 5 - 3.29V Pin 6 - ground Pin 7 - 3.29V Pin 8 - ground Pin 9 - 3.29V Pin 10 - ground Pin 11 - ground Pin 12 - ground Pin 13 - 1.230V Pin 14 - ground Pin 15 - 2.83V Pin 16 - ground Pin 17 - 0V Pin 18 - ground Pin 19 - 0V Pin 20 - ground Signals of JTAG when connected to emulator: Pin 1 - 3.29V Pin 2 - 3.29V Pin 3 - 0.016V Pin 4 - ground Pin 5 - 0.981V Pin 6 - ground Pin 7 - 0.978V Pin 8 - ground Pin 9 - 0.971V Pin 10 - ground Pin 11 - ground Pin 12 - ground Pin 13 - 0.374V Pin 14 - ground Pin 15 - 0.115V Pin 16 - ground Pin 17 - 0V Pin 18 - ground Pin 19 - 0V Pin 20 - ground Pls advise. Rgrds, ongth60 [ This message was edited by: ongth60 on 10-07-2005 09:40 ]

[ongth60]

Posted on July 14, 2005 at 05:59

Hi,

anyone can help me to troubleshoot the problem cos to get a new emulator will take me 6 weeks. Rgrds, ongth60

[ongth60]

Posted on August 09, 2005 at 02:00

Hi ibtiss,

Ya, got my replacement and indeed the emulator was spoilt. Thanks for looking up into it. Rgrds, ongth60