yes, now this is possible as a guy from China named TwentyOne made H-JTAG RDI support for Wiggler compatible, thus made possible ARM-JTAG to work flawless with any commercial debugger which suports RDI: this means EW-ARM, uVision, ADS, STD, RealView, GreenHils etc.etc.
For these of you who are not fans of the command line interface and GCC, here is what you have to do:
install your favourite IDE from above (almost all of them give free trials or limited versions), for instance the 32KB limited free kickstart version of EW-ARM from IAR Systems
install H-JTAG package from the link of our ARM-JTAG page, use the version from our web as our ARM-JTAG have some additional signals than the Wiggler clone schematics which circulate on the internet. TwentyOne was kind enough to adjust his code to support our ARM-JTAG and the code on our web is made specially for ARM-JTAG.
In EW-ARM make new project with options as Debugger: RDI support and in RDI browse to H-JTAG.dll
that’s all folks, now you can compile, flash load, debug your application without the annoying speed setups and so on as with OCDeamon.
And VERY interesting fact: although Segger claim that their J-LINK program with 120-250KB/sec we can’t see this happend on LPC microcontrollers and boards we have! The flash load/programming speed with ARM-JTAG ($20) device is about 30% slower than the J-LINK ($250) USB debugger when you load your code in LPC flash.
We don’t have any other commercial debugger to make comparison to.
I followed the same procedure given above but i get the
follwing exception message when ever i try to debug the program (In the EWARM):
Failed to Initialize the RDI Driver (WinRDI openagent)
Check the RDI driver configuration,cables,power etc.
H-Jtag Server not ready.Please make sure that the hardware is properly connected and powered up.
Session Aborted !!
Any help wil be highly appreciated.
HOST OS: WinXP .
rgds
som
Did you start the H-JTAG server first, and see that it actually detected your target?
After you see that H-JTAG has detected your target, you can close it’s window and leave H-JTAG running in the Windows Taskbar. If you do not see H-JTAG detect your hardware then you probably have an H-JTAG configuration problem or a hardware problem. However the way you describe your problem it seems like the H-JTAG server is not actually running when try to start a debug session.
Ya , i had started the HJTAG before using the EWARM Application …
But it never connected it always said unable to detect target.
After i accidentally shorted the erase jumper pins, i am in a desperate state to push some code into the board … the LED OLIMEX logo which was glowing earlier has also gone !!
I tried installed the SAM- BA from Atmel and tried to burn to the flash some code using the JTAG, then Serial cable ,( for some reason i never got the USB option) but in vain …
I am now staring at a black box i donno what to do …
Please help me …
If you have any queries or Logs that you want you can very well ask me to that … i shall try it out …
som1:
Ya , i had started the HJTAG before using the EWARM Application …
But it never connected it always said unable to detect target.
That message indicates a hardware problem.
The PC parallel port may have a problem.
The signal connections from H-JTAG to the target may not be configured correctly for the debugger pod that you are using. If you are using the Olimex Wiggler clone it requires a different H-JTAG signal routing setup than other Wiggler types.
The target’s JTAG port may be disabled somehow.
The target chip may have been accidently destroyed.
In any case, until H-JTAG can detect the target there is nothing that needs to be done concerning your compiler/debugger setup. That comes after you get H-JTAG to communicate with the target.
