I realize your frustrations - but play nice or get booted.
We try to provide as much support as possible - that’s why this forum is here - for you.
I’ll take your recommendation and update the ARM-JTAG listing on the SFE website. In the future, please ask for help and we’ll try to point you in the right direction.
-Nathan
I’ve tried the ocdremote & the arm-jtag under Linux 2.6.8 (don’t try that), 2.4.22 (insmod -f ravenpp.o work there) and Windows 2K & Cygwwin 2.0 (?, from the Macraigor site) and none of them recognize the arm-jtag (error 43 or the not cabled error). The jtag has the jumper between 8 & 15. Any hints?
Hi,
try to decrease the Speed, OCDemon doesn’t work correctly on faster computers, also ensure that ARM clock is at least 8 times faster than JTAG clock.
Best regards
Tsvetan
With ocdremote (2.09), nothing works under Linux. I use the following command line:
ocdremote -c ARM7TDMI -a 1 -d RAVEN -s 1
-s 1 or 2 gives the following error:
OCDemon InitializeTarget Error : Not in Background
-s 3 through 8 just cause the EB40A to continously reboot.
There is no wiggler option under Linux. Should I set the BIOS to something particular for the parallel port setting?
I had better luck with Windows (I don’t like running 2 systems to get things done) and ocdremote.exe. That I can run as a Wiggler (-d wiggler) at -s 4.
So it looks like the Linux drivers are kaput! I tried to load the Linux drivers under Linux 2.6,8 but that crashes during install (Macraigor’s drivers). Under Linux 2.4 I can’t get it to behave but under Windows 2K I can get it to run as a Wiggler and setting 4. At least I have something working. I guess it’s time to put some work into an open source driver so I can run under Linux. Do you know of any? I’ve googled but I get no clear information. I get a lot of info about various projects but none that are clear that allow gdb to access the driver/daemon.
Thanks
under windows 2000.
ocdremote works only with a speed -s 8 if LPT port is in normal mode,
if LPTport is in normal ECP/EPP, ocdremotre cause a reboot of windows.
ocdremote with speed (ocdremote -c ARM7TDMI-S -a 1 -d wiggler -s 1 ) it is ok fi a LPT port is in EPP mode.
sparky:
I realize your frustrations - but play nice or get booted.We try to provide as much support as possible - that’s why this forum is here - for you.
I’ll take your recommendation and update the ARM-JTAG listing on the SFE website. In the future, please ask for help and we’ll try to point you in the right direction.
-Nathan
In the spirit of “providing as much support as possible” and “asking for help” …
Would it be possible for someone from Spark Fun or Olimex to provide links to the versions of the software utilities that are known to work with the hardware being offered for sale? Failing that, perhaps just a simple table?
Call me picky, but I’m not prepared to spend money on untested or semi-tested hardware. I have no objections to beta testing hardware and software combinations, but I’m certainly not going to pay for this ‘privilege’. I frequently test and research hardware/software products for other companies - they send me the ‘stuff’, I figure out what works, and what doesn’t, I give them the results, I keep the stuff. Everybody wins. A similar scheme might be beneficial for you guys (and no, I’m not looking for work - I’m just making a suggestion which might improve your service).
You guys (Spark Fun and Olimex) sell some great stuff. I think you’d sell a whole lot more if the quality of documentation was taken up a notch.
-Pete.
Hello Peter,
I agree on the documentation issue with our development boards, we are going to change this soon.
But the problems here I see is with the open source software tools quality.
Our ARM-JTAG is 100% Wiggler compatible, where our ARM-JTAG doesn’t work so does the original $150 wiggler. This is not issue of the hardware, but of the software which this hardware is used with.
To everyone who is in doubt if his software/hardware works or not I suggest to download Rowley’s CrossWorks (no I don’t get commissioning from them) they provide 30 days free licensee and user see that our boards work when they are used with the proper tunned software - as CrossWorks is nothing but GCC with well designed IDE and debugger which works without you to know what speed you have to tune it at your computer and so on hidden behind IDE issues.
I don’t want to start here debates for the open source / commercial software issues, but the fact is that if you are not linux guru or have no time to spend in learning how and what to tune in the open source tools, you will have almost no luck to use them sucessfully.
CrossWorks (which is GCC) proves that GNUARM and GCC is working just fine with our hardware.
Best regards
Tsvetan
I just got a ARM-JTAG, and I can’t get it to work with OCDRemote 2.11 I keep getting the error 43 nomatter which speed I try to connect with.
I’ve set my LPT1 to EPP and is using the LPC2138 MCU.
How do I check if my ARM-JTAG has been patched between pin 8 and 15? And is it the LPT pins or the JTAG pins?
Does anyone have an older version of OCDRemote? Maybe 2.06
Best Regards
Søren Thestrup
you can do the check with simple ohm meter when touch with the probes pin 8 and 15
Tsvetan
Have just tested, and there is no connection between the two pins. I bought it from demotech in Denmark.
Should I just connect a wire between the two pins?
/Søren
simple wire between both pins will do just fine
Tsvetan
Now I’ve put a wire between pin 8 and 15, and I’ve succeeded in connecting with OCDRemote, but only at speed 8. When transfering my program it only does so, with 100 bits/sec.
My LPT1 is in EPP mode and I thought that the Wiggler interface could work at speeds higher than the 100 bits/sec I’m getting. Futhermore, I keep getting packet errors in GDB, which results in nothing working.
Anyone who have experience with Wiggler and speeds higher than 8?
ps. when trying to connect with e.g. speed 4 I get the message: OCDemon InitializeTarget Error: Cable Disconnected
Regards
Søren
Thestrup:
Now I’ve put a wire between pin 8 and 15, and I’ve succeeded in connecting with OCDRemote, but only at speed 8. When transfering my program it only does so, with 100 bits/sec.My LPT1 is in EPP mode and I thought that the Wiggler interface could work at speeds higher than the 100 bits/sec I’m getting. Futhermore, I keep getting packet errors in GDB, which results in nothing working.
Anyone who have experience with Wiggler and speeds higher than 8?
ps. when trying to connect with e.g. speed 4 I get the message: OCDemon InitializeTarget Error: Cable Disconnected
Regards
Søren
My JTAG interface using a home-made PCB works reliably at speed 1, faster than a genuine Wiggler. I took a lot of care over the PCB layout, the Wiggler has a rather poorly designed PCB. That is under WinXP, with the Crossworks tools.
Leon
Leon
Rowley use their own driver and even don’t need this patch between 8-15 pins which new OCD checks, so Leon you miss the OP point - he wants to use GNUARM toolchain which he can’t configure to work at high speed.
This seems like doomed circle - peoples want to have low cost software tools for ARM after they got our low cost hardware boards.
Unfortunately GNUARM tools are too complex to be configured correctly and used by beginners, and at other side peoples wants to use freeware tools but nobody from those who already set and use don’t share what they do or share something which is setup for his own platform and say to all others - go figure what you have to do on your own platform yourself 
with so many different computers and platforms to write something like this one what Rowley did is quite a work and apparently no body is interested to do this for free.
One month ago customer reported that GNUARM toolchan start working faster if he first run CrossWorks demo and do few steps of debugging, so it’s definitely something in the configuration or initialization.
Best regards
Tsvetan
I should have added that my interface also works fine at high speed with OCD Commander, with the pin 8-15 connection added.
Leon
so you can help with the OCD configuration these guys, there is nothing to do with the hardware - no matter original Wiggler or clone - they are simple level shifters from 5V LPT to 3V JTAG interface and no matter how implemented the major problem is the PC side software configuration when work with GNUARM tools.
Tsvetan
Hi,
I’m trying to program/debug the LPC-E2294 with the ARM-JTAG Adapter and Gnuarm. I setted up the JTAG tool (available from sourceforge.net) with the parallel port and a WIGGLER cable. When I try to detect the board I get no answer! How should I configure the ARM-JTAG Adapter?
Did someone succed using the ARM-JTAG Debugger with the Gnuarm compiler?
Thanks,
Matthias
LMAlmeida:
There are some post in comp.arch.embededd that refer some connection between pins 8 and 15. I still have to try it to se if it works.Luciano Almeida
Yes, join pins 8 and 15 on the DB-25 connector and it should work.
Leon
:?:
HI All.
This is Senthil from India. I am a newly joined member. Hope this msg finds u fine all.
I am using Eclipse IDE and GNUarm compiler. Target board as RMS100 from Revely product which has ARM7TDMI core.
Here I am having the probleme while Debugging the application. I m using Revely’s DBG-4FT Cable similar to wiggler. While Debuggin two modes can be selected from RMS100.
Parallel port Debug Mode - Emulates Macraigor Wiggler Hardware.
Pass-Through Mode - All JTAG signals are buffered and available for an external debugger.
I am using OCDRemote from Macraigor, to made commn. using Debug Cable. But I am getting the following error “Internal Error 43” “OCDemon InitializeTarget Error : Cable Disconnected”. and I plan to use Insight Debugger. I got vexed with this unreliable connection.
Could anyone please provide me a suggestion where I am going wrong with this. and too give me a solution. Thanks in Advance.
Regards,
Senthil Kumar . S
Hi Senthil.
Here are some suggestions that might help.
Make sure pins 8 and 15 of the parallel port are connected.
Make sure your parallel port is not in ECP mode.
Try to use the second slowest speed for the Wiggler.
Your Wiggler setup should have these settings:
-cARM7TDMI-S specifies the CPU being accessed
-p8888 specifies the pseudo TCP-IP port being used
-dWIGGLER specifies the JTAG hardware being used
-a1 specifies LPT1 for the Wiggler
-s7 specifies next-to-slowest speed
Make sure you haven’t accidentally started multiple copies of the OCDRemote. Use the Windows Task Manager to check this.
Obviously, start the OCDRemote before trying to start Insight.
Cheers,
Jim Lynch