Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Thread

JTAG Programmer Confusion - Noob Question

JTAG Programmer Confusion - Noob Question

2005-12-03 by sixtyfivebit

Hi all,

I want to get into the LPC2106 or similar mcu, and i'm moving from the
AVR world. I've read many things about how you need some bootloader or
something working on the mcu to receive data from the jtag, etc.

is there some detailed explanation regarding this issue and how to
solve it? Also, I'm looking for a programmer to build for the LPC2106.
I see several schematics listed in the files, which one would you guys
recommend? The standard wiggler? I found these ones online as well:

http://home.comcast.net/~staskh/projects/tools/
http://www.adilam.com.au/ARM/arm.html

Sorry if these questions are stupid and I missed something very obvious.

sixtyfivebit

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-03 by Tom Walsh

sixtyfivebit wrote:

>Hi all,
>
>I want to get into the LPC2106 or similar mcu, and i'm moving from the
>AVR world. I've read many things about how you need some bootloader or
>something working on the mcu to receive data from the jtag, etc.
>
>  
>
The LPC2000 series have their own builtin bootloaders.  Part of the 
Flash memory is protected and that is where it resides (8K).  A 
bootloader utility can be found on 
http://www.standardics.philips.com/support/techdocs/microcontrollers/  
it is called "LPC2000 Flash ISP Utility".


>is there some detailed explanation regarding this issue and how to
>solve it? Also, I'm looking for a programmer to build for the LPC2106.
>I see several schematics listed in the files, which one would you guys
>recommend? The standard wiggler? I found these ones online as well:
>
>  
>

JTAG is not a "programmer", it is a test interface (Joint Test Action 
Group == JTAG).  Most of the people here use simple wigglers, they can 
give you information as to that, or search the messages for "JTAG" and 
"wiggler".  That should get you a lot of hits.

For myself, I've found wigglers to be slow, unstable, and, at times, 
unpredicatable to get working right.  For my current project (dual CPU 
board: LPC2106 + LPC2138), I chose to spend the money ($2700) and 
purchase an Abatron BDI2000.  I've not been unhappy with it!  It can 
also program the Flash of the controllers as well as give me a stable 
JTAG interface to gdb + Insight.  That being said, you can whip up a 
wiggler in about an hour and a few dollars expendature, then use a 
software TCP server which you can download and compile yourself.

The BDI2000 is fast when programming the Flash memory.  For example, a 
34K file would take about 10 seconds to prgram using the serial utility 
only takes about 3 seconds with the BDI2000, and it does it via the JTAG 
with two commands.  While 10 seconds is not a lot of time, I expect my 
program to get a lot larger than 34K!

TomW

-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-03 by Leon Heller

Leon Heller, G1HSM
leon.heller@...
http://www.geocities.com/leon_heller
Show quoted textHide quoted text
----- Original Message ----- 
From: "sixtyfivebit" <sixtyfivebit@...>
To: <lpc2000@yahoogroups.com>
Sent: Saturday, December 03, 2005 9:29 AM
Subject: [lpc2000] JTAG Programmer Confusion - Noob Question


> Hi all,
> 
> I want to get into the LPC2106 or similar mcu, and i'm moving from the
> AVR world. I've read many things about how you need some bootloader or
> something working on the mcu to receive data from the jtag, etc.
> 
> is there some detailed explanation regarding this issue and how to
> solve it? Also, I'm looking for a programmer to build for the LPC2106.
> I see several schematics listed in the files, which one would you guys
> recommend? The standard wiggler? I found these ones online as well:
> 
> http://home.comcast.net/~staskh/projects/tools/
> http://www.adilam.com.au/ARM/arm.html
> 
> Sorry if these questions are stupid and I missed something very obvious.

My interface is in jtag.zip, it works fine with the Crossworks tools.

Leon
---
[This E-mail has been scanned for viruses but it is your responsibility 
to maintain up to date anti virus software on the device that you are
currently using to read this email. ]

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-03 by Arie de Muynck

From: "Tom Walsh" <tom@...>
> For myself, I've found wigglers to be slow, unstable, and, at times, 
> unpredicatable to get working right.  For my current project (dual CPU 
> board: LPC2106 + LPC2138), I chose to spend the money ($2700) and 
> purchase an Abatron BDI2000.  I've not been unhappy with it!  It can 
> also program the Flash of the controllers as well as give me a stable 
> JTAG interface to gdb + Insight.  That being said, you can whip up a 
> wiggler in about an hour and a few dollars expendature, then use a 
> software TCP server which you can download and compile yourself.

Hi Tom,

Do you have an URL for that software TCP server?

Regards,
Arie de Muijnck

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-03 by Tom Walsh

Arie de Muynck wrote:

>From: "Tom Walsh" <tom@...>
>  
>
>>For myself, I've found wigglers to be slow, unstable, and, at times, 
>>unpredicatable to get working right.  For my current project (dual CPU 
>>board: LPC2106 + LPC2138), I chose to spend the money ($2700) and 
>>purchase an Abatron BDI2000.  I've not been unhappy with it!  It can 
>>also program the Flash of the controllers as well as give me a stable 
>>JTAG interface to gdb + Insight.  That being said, you can whip up a 
>>wiggler in about an hour and a few dollars expendature, then use a 
>>software TCP server which you can download and compile yourself.
>>    
>>
>
>Hi Tom,
>
>Do you have an URL for that software TCP server?
>
>  
>
I haven't used it or checked it out, but it looks pretty good.

http://gdb-jtag-arm.sourceforge.net/

TomW


>Regards,
>Arie de Muijnck
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>  
>


-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-03 by Dominic Rath

Hello,

gdb-jtag-arm doesn't support ARM7 targets, only ARM9TDMI. The ARM9 code has 
bugs, and I wouldn't count on its operation.

Macraigor (the company that sells the original "Wiggler") allows you to 
download their on-chip debug software for free. I used it with an Amontec 
Chameleon in its Wiggler configuration, but only on windows, the wiggler 
isn't supported by their linux version.

Regards,

Dominic
Show quoted textHide quoted text
On Saturday 03 December 2005 17:18, Tom Walsh wrote:
>
> I haven't used it or checked it out, but it looks pretty good.
>
> http://gdb-jtag-arm.sourceforge.net/
>
> TomW

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-03 by Tom Walsh

Leon Heller wrote:

>Leon Heller, G1HSM
>leon.heller@...
>http://www.geocities.com/leon_heller
>----- Original Message ----- 
>From: "sixtyfivebit" <sixtyfivebit@...>
>To: <lpc2000@yahoogroups.com>
>Sent: Saturday, December 03, 2005 9:29 AM
>Subject: [lpc2000] JTAG Programmer Confusion - Noob Question
>
>
>  
>
>>Hi all,
>>
>>I want to get into the LPC2106 or similar mcu, and i'm moving from the
>>AVR world. I've read many things about how you need some bootloader or
>>something working on the mcu to receive data from the jtag, etc.
>>
>>is there some detailed explanation regarding this issue and how to
>>solve it? Also, I'm looking for a programmer to build for the LPC2106.
>>I see several schematics listed in the files, which one would you guys
>>recommend? The standard wiggler? I found these ones online as well:
>>
>>http://home.comcast.net/~staskh/projects/tools/
>>http://www.adilam.com.au/ARM/arm.html
>>
>>Sorry if these questions are stupid and I missed something very obvious.
>>    
>>
>
>My interface is in jtag.zip, it works fine with the Crossworks tools.
>
>  
>
That is a wiggler, we were talking about a JTAG gdb-server.

TomW


>Leon
>---
>[This E-mail has been scanned for viruses but it is your responsibility 
>to maintain up to date anti virus software on the device that you are
>currently using to read this email. ]
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>  
>


-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-04 by Bertrik Sikken

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dominic Rath wrote:
> Hello,
> 
> gdb-jtag-arm doesn't support ARM7 targets, only ARM9TDMI. The ARM9 code has
> bugs, and I wouldn't count on its operation.

How hard would it be to make it work? Something like this:
* fix existing bugs (what bugs do you know of?)
* replace pp.c (linux parallel port io) with a windows equivalent
* add support for LPC specific registers
?

> Macraigor (the company that sells the original "Wiggler") allows you to
> download their on-chip debug software for free. I used it with an Amontec
> Chameleon in its Wiggler configuration, but only on windows, the wiggler
> isn't supported by their linux version.

I got my wiggler clone today (an olimex arm-jtag cable, the "new model"
with pin 8 and 15 connected on the PC side) and here what I found out
so far:

I tried both ocdcommander and ocdremote and as far as I understand now,
the big problem with these is that they cannot set breakpoints in flash.
Besides, these programs and some wiggler clones don't seem to be
completely compatible with each other (my cable only works at the lowest
speed setting, 4 kHz, unless I perform some tricks.)

The debugger from http://www.devlf.com/armdbg.html can actually set
breakpoints/singlestep in flash, but it is a completely stand-alone
program. Also I have not been able to find out if it supports
debugging at the C-source level.

Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDkjTuETD6mlrWxPURApPSAKCjLtFo1gzn1pB8Lj+LWG9N6REUkQCfaPXZ
iz4ahVE/euURkaA0wwsy2Po=
=bEzj
-----END PGP SIGNATURE-----

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-04 by Scott Newell

At 06:14 PM 12/3/2005, Bertrik Sikken wrote:

>I tried both ocdcommander and ocdremote and as far as I understand now,
>the big problem with these is that they cannot set breakpoints in flash.

What?  Under OCD Commander, the HBR command doesn't work for you?  That's 
very odd.

I've used hardware breakpoints before, and if you really want to get 
tricky, you can access the ICE-breaker registers from OCD commander as well.

-- 
newell

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-04 by Leon Heller

----- Original Message ----- 
Show quoted textHide quoted text
From: "Bertrik Sikken" <bertrik@...>
To: <lpc2000@yahoogroups.com>
Sent: Sunday, December 04, 2005 12:14 AM
Subject: Re: [lpc2000] JTAG Programmer Confusion - Noob Question


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dominic Rath wrote:
>> Hello,
>>
>> gdb-jtag-arm doesn't support ARM7 targets, only ARM9TDMI. The ARM9 code 
>> has
>> bugs, and I wouldn't count on its operation.
>
> How hard would it be to make it work? Something like this:
> * fix existing bugs (what bugs do you know of?)
> * replace pp.c (linux parallel port io) with a windows equivalent
> * add support for LPC specific registers
> ?
>
>> Macraigor (the company that sells the original "Wiggler") allows you to
>> download their on-chip debug software for free. I used it with an Amontec
>> Chameleon in its Wiggler configuration, but only on windows, the wiggler
>> isn't supported by their linux version.
>
> I got my wiggler clone today (an olimex arm-jtag cable, the "new model"
> with pin 8 and 15 connected on the PC side) and here what I found out
> so far:
>
> I tried both ocdcommander and ocdremote and as far as I understand now,
> the big problem with these is that they cannot set breakpoints in flash.
> Besides, these programs and some wiggler clones don't seem to be
> completely compatible with each other (my cable only works at the lowest
> speed setting, 4 kHz, unless I perform some tricks.)

My interface works at full speed, perhaps I have a better PCB design. I 
wasn't very impressed by the layout on the genuine Wiggler I have, and mine 
is faster than that.

Leon 

---
[This E-mail has been scanned for viruses but it is your responsibility 
to maintain up to date anti virus software on the device that you are
currently using to read this email. ]

Re: JTAG Programmer Confusion - Noob Question

2005-12-04 by ntfreak2000

--- In lpc2000@yahoogroups.com, Scott Newell <digital.pickle@g...> 
wrote:
>
> At 06:14 PM 12/3/2005, Bertrik Sikken wrote:
> 
> >I tried both ocdcommander and ocdremote and as far as I 
understand now,
> >the big problem with these is that they cannot set breakpoints in 
flash.
> 
> What?  Under OCD Commander, the HBR command doesn't work for you?  
That's 
> very odd.
> 
> I've used hardware breakpoints before, and if you really want to 
get 
> tricky, you can access the ICE-breaker registers from OCD 
commander as well.
> 
> -- 
> newell
>

Newer versions of ocdremote support the hbreak command, they have 
also added another monitor command:
monitor softbkpts off

this means that all breakpoint requests by insight/gdb will be set 
as hardware breakpoints, which means when enabled stepping etc works 
correctly in Flash.

to resume the default behaviour type monitor softbkpts on

Hope this helps.
sjo

Re: JTAG Programmer Confusion - Noob Question

2005-12-04 by lynchzilla

May I add some additional points about the wiggler-jtag isssue.

I wrote a tutorial titled "ARM Cross Development with Eclipse" that 
is referenced in the "links" section of this message board. This 
tutorial shows in excessive detail how to set up a free GNU compiler 
set for the ARM using the Eclipse/CDT IDE and how to use the Eclipse 
debugger with the wiggler. Hopefully, you have had a look at that.

The obvious shortcoming is that it couldn't debug in FLASH memory.

I'm now furiously working on a revision to this tutorial that does 
show how to debug in FLASH. Thanks to the genius of my new co-
author, Norwegian engineer Kjell Eirik Andersen, we now have a 
simple utility program, RSPBreakout.exe, that reads all commands 
intended for the Macraigor OCDRemote and converts all Z0,addr,length 
commands (software breakpoints) into Z1,addr,length commands 
(hardware breakpoints). As long as you limit yourself to setting no 
more than two breakpoints at a time, it will properly break in FLASH 
and all single-stepping, variable inspection, etc works 
magnificently. This requires Macraigor's OCDRemote version 2.14 
which supports -Z2 GDB remote serial protocol commands.

Not the ultimate solution, but a great breakthrough for a completely 
free development system nonetheless.

One last point, I can get the Olimex Wiggler to run at speed 3 (140 
khz) using the latest OCDRemote ver 2.14

However, I found that certain Windows applications, such as my 
beloved SKYPE internet phone system, used so much of my CPU 
resources that the speed that the Wiggler could run was severely 
degraded (to the lowest speed). I suggest that you bring up Windows 
Task Manager and make sure that you don't have any applications like 
that running. Remember that the OCDRemote/wiggler is ssentially "bit-
banging" the parallel port and this LPT1 port probably has a much 
lower priority on the Windows driver pecking order. 

I hope to have the tutorial finished in the next several days. I'm 
also hoping that the Eclipse foundation may accept my tutorial as an 
official Eclipse Corner article.

Cheers,
Jim Lynch

RE: [lpc2000] Re: JTAG Programmer Confusion - Noob Question

2005-12-04 by Michael Rubitschka

Dear Jim

Your Eclipse-Arm tutorial is magnificent.
Thank you verry much for this great
work.

Cheers
Michael
Show quoted textHide quoted text
>From: "lynchzilla" <lynchzilla@...>
>Reply-To: lpc2000@yahoogroups.com
>To: lpc2000@yahoogroups.com
>Subject: [lpc2000] Re: JTAG Programmer Confusion - Noob Question
>Date: Sun, 04 Dec 2005 16:20:59 -0000
>
>May I add some additional points about the wiggler-jtag isssue.
>
>I wrote a tutorial titled "ARM Cross Development with Eclipse" that
>is referenced in the "links" section of this message board. This
>tutorial shows in excessive detail how to set up a free GNU compiler
>set for the ARM using the Eclipse/CDT IDE and how to use the Eclipse
>debugger with the wiggler. Hopefully, you have had a look at that.
>
>The obvious shortcoming is that it couldn't debug in FLASH memory.
>
>I'm now furiously working on a revision to this tutorial that does
>show how to debug in FLASH. Thanks to the genius of my new co-
>author, Norwegian engineer Kjell Eirik Andersen, we now have a
>simple utility program, RSPBreakout.exe, that reads all commands
>intended for the Macraigor OCDRemote and converts all Z0,addr,length
>commands (software breakpoints) into Z1,addr,length commands
>(hardware breakpoints). As long as you limit yourself to setting no
>more than two breakpoints at a time, it will properly break in FLASH
>and all single-stepping, variable inspection, etc works
>magnificently. This requires Macraigor's OCDRemote version 2.14
>which supports -Z2 GDB remote serial protocol commands.
>
>Not the ultimate solution, but a great breakthrough for a completely
>free development system nonetheless.
>
>One last point, I can get the Olimex Wiggler to run at speed 3 (140
>khz) using the latest OCDRemote ver 2.14
>
>However, I found that certain Windows applications, such as my
>beloved SKYPE internet phone system, used so much of my CPU
>resources that the speed that the Wiggler could run was severely
>degraded (to the lowest speed). I suggest that you bring up Windows
>Task Manager and make sure that you don't have any applications like
>that running. Remember that the OCDRemote/wiggler is ssentially "bit-
>banging" the parallel port and this LPT1 port probably has a much
>lower priority on the Windows driver pecking order.
>
>I hope to have the tutorial finished in the next several days. I'm
>also hoping that the Eclipse foundation may accept my tutorial as an
>official Eclipse Corner article.
>
>Cheers,
>Jim Lynch
>
>
>
>
>
>
>
>

Re: [lpc2000] Re: JTAG Programmer Confusion - Noob Question

2005-12-04 by Ake Hedman, eurosource

Michael Rubitschka wrote:

> Dear Jim
>
> Your Eclipse-Arm tutorial is magnificent.
> Thank you verry much for this great
> work.
>
> Cheers
> Michael


I think we all can agree on that. Superb!

/Ake

>
>
> >From: "lynchzilla" <lynchzilla@...>
> >Reply-To: lpc2000@yahoogroups.com
> >To: lpc2000@yahoogroups.com
> >Subject: [lpc2000] Re: JTAG Programmer Confusion - Noob Question
> >Date: Sun, 04 Dec 2005 16:20:59 -0000
> >
> >May I add some additional points about the wiggler-jtag isssue.
> >
> >I wrote a tutorial titled "ARM Cross Development with Eclipse" that
> >is referenced in the "links" section of this message board. This
> >tutorial shows in excessive detail how to set up a free GNU compiler
> >set for the ARM using the Eclipse/CDT IDE and how to use the Eclipse
> >debugger with the wiggler. Hopefully, you have had a look at that.
> >
> >The obvious shortcoming is that it couldn't debug in FLASH memory.
> >
> >I'm now furiously working on a revision to this tutorial that does
> >show how to debug in FLASH. Thanks to the genius of my new co-
> >author, Norwegian engineer Kjell Eirik Andersen, we now have a
> >simple utility program, RSPBreakout.exe, that reads all commands
> >intended for the Macraigor OCDRemote and converts all Z0,addr,length
> >commands (software breakpoints) into Z1,addr,length commands
> >(hardware breakpoints). As long as you limit yourself to setting no
> >more than two breakpoints at a time, it will properly break in FLASH
> >and all single-stepping, variable inspection, etc works
> >magnificently. This requires Macraigor's OCDRemote version 2.14
> >which supports -Z2 GDB remote serial protocol commands.
> >
> >Not the ultimate solution, but a great breakthrough for a completely
> >free development system nonetheless.
> >
> >One last point, I can get the Olimex Wiggler to run at speed 3 (140
> >khz) using the latest OCDRemote ver 2.14
> >
> >However, I found that certain Windows applications, such as my
> >beloved SKYPE internet phone system, used so much of my CPU
> >resources that the speed that the Wiggler could run was severely
> >degraded (to the lowest speed). I suggest that you bring up Windows
> >Task Manager and make sure that you don't have any applications like
> >that running. Remember that the OCDRemote/wiggler is ssentially "bit-
> >banging" the parallel port and this LPT1 port probably has a much
> >lower priority on the Windows driver pecking order.
> >
> >I hope to have the tutorial finished in the next several days. I'm
> >also hoping that the Eclipse foundation may accept my tutorial as an
> >official Eclipse Corner article.
> >
> >Cheers,
> >Jim Lynch
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
> SPONSORED LINKS
> Microprocessor 
> <http://groups.yahoo.com/gads?t=ms&k=Microprocessor&w1=Microprocessor&w2=Microcontrollers&w3=Pic+microcontrollers&w4=8051+microprocessor&c=4&s=93&.sig=tsVC-J9hJ5qyXg0WPR0l6g> 
> 	Microcontrollers 
> <http://groups.yahoo.com/gads?t=ms&k=Microcontrollers&w1=Microprocessor&w2=Microcontrollers&w3=Pic+microcontrollers&w4=8051+microprocessor&c=4&s=93&.sig=DvJVNqC_pqRTm8Xq01nxwg> 
> 	Pic microcontrollers 
> <http://groups.yahoo.com/gads?t=ms&k=Pic+microcontrollers&w1=Microprocessor&w2=Microcontrollers&w3=Pic+microcontrollers&w4=8051+microprocessor&c=4&s=93&.sig=TpkoX4KofDJ7c6LyBvUqVQ> 
>
> 8051 microprocessor 
> <http://groups.yahoo.com/gads?t=ms&k=8051+microprocessor&w1=Microprocessor&w2=Microcontrollers&w3=Pic+microcontrollers&w4=8051+microprocessor&c=4&s=93&.sig=1Ipf1Fjfbd_HVIlekkDP-A> 
>
>
>
> ------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
>     *  Visit your group "lpc2000
>       <http://groups.yahoo.com/group/lpc2000>" on the web.
>        
>     *  To unsubscribe from this group, send an email to:
>        lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     *  Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>
> ------------------------------------------------------------------------
>


-- 
 ---
Ake Hedman (YAP - Yet Another Programmer)
eurosource, Brattbergavägen 17, 820 50 LOS, Sweden
Phone: (46) 657 413430 Cellular: (46) 73 84 84 102
Company home: http://www.eurosource.se      
Kryddor/Te/Kaffe: http://www.brattberg.com
Personal homepage: http://www.eurosource.se/akhe
Automated home: http://www.vscp.org



[Non-text portions of this message have been removed]

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-05 by Bertrik Sikken

Leon Heller wrote:
> ----- Original Message -----
> From: "Bertrik Sikken" <bertrik@...>
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Dominic Rath wrote:
>>> Hello,
>>>
>>> gdb-jtag-arm doesn't support ARM7 targets, only ARM9TDMI. The ARM9 code
>>> has
>>> bugs, and I wouldn't count on its operation.
>>
>> How hard would it be to make it work? Something like this:
>> * fix existing bugs (what bugs do you know of?)
>> * replace pp.c (linux parallel port io) with a windows equivalent
>> * add support for LPC specific registers
>> ?
>>
>>> Macraigor (the company that sells the original "Wiggler") allows you to
>>> download their on-chip debug software for free. I used it with an Amontec
>>> Chameleon in its Wiggler configuration, but only on windows, the wiggler
>>> isn't supported by their linux version.
>>
>> I got my wiggler clone today (an olimex arm-jtag cable, the "new model"
>> with pin 8 and 15 connected on the PC side) and here what I found out
>> so far:
>>
>> I tried both ocdcommander and ocdremote and as far as I understand now,
>> the big problem with these is that they cannot set breakpoints in flash.
>> Besides, these programs and some wiggler clones don't seem to be
>> completely compatible with each other (my cable only works at the lowest
>> speed setting, 4 kHz, unless I perform some tricks.)
> 
> My interface works at full speed, perhaps I have a better PCB design. I
> wasn't very impressed by the layout on the genuine Wiggler I have, and mine
> is faster than that.

The weird thing is, getting ocdremote to recognise the cable is the
hard part, once that works it seems to run fine.
The trick I mentioned is to first tell ocdcommander that a raven cable
is connected, let it fail, then tell it to look for a wiggler. If I do
that, the wiggler is recognised fine, even at the highest speed.

Regards,
Bertrik

Re: [lpc2000] Re: JTAG Programmer Confusion - Noob Question

2005-12-05 by Bertrik Sikken

ntfreak2000 wrote:
> --- In lpc2000@yahoogroups.com, Scott Newell <digital.pickle@g...>
> wrote:
>>
>> At 06:14 PM 12/3/2005, Bertrik Sikken wrote:
>>
>> >I tried both ocdcommander and ocdremote and as far as I
> understand now,
>> >the big problem with these is that they cannot set breakpoints in
> flash.
>>
>> What?  Under OCD Commander, the HBR command doesn't work for you? 
> That's
>> very odd.
>>
>> I've used hardware breakpoints before, and if you really want to
> get
>> tricky, you can access the ICE-breaker registers from OCD
> commander as well.

Thanks for the correction, the HBR command works fine.

> Newer versions of ocdremote support the hbreak command, they have
> also added another monitor command:
> monitor softbkpts off
> 
> this means that all breakpoint requests by insight/gdb will be set
> as hardware breakpoints, which means when enabled stepping etc works
> correctly in Flash.
> 
> to resume the default behaviour type monitor softbkpts on

Ah nice, thanks for the tip.
I tried this in gdb console and indeed it works (have not been
able to also get it to work with insight source level debugging yet).

Kind regards,
Bertrik

Re: JTAG Programmer Confusion - Noob Question

2005-12-06 by ntfreak2000

--- In lpc2000@yahoogroups.com, "lynchzilla" <lynchzilla@a...> wrote:
>
> May I add some additional points about the wiggler-jtag isssue.
> 
> I wrote a tutorial titled "ARM Cross Development with Eclipse" that 
> is referenced in the "links" section of this message board. This 
> tutorial shows in excessive detail how to set up a free GNU 
compiler 
> set for the ARM using the Eclipse/CDT IDE and how to use the 
Eclipse 
> debugger with the wiggler. Hopefully, you have had a look at that.
> 
> The obvious shortcoming is that it couldn't debug in FLASH memory.
> 
> I'm now furiously working on a revision to this tutorial that does 
> show how to debug in FLASH. Thanks to the genius of my new co-
> author, Norwegian engineer Kjell Eirik Andersen, we now have a 
> simple utility program, RSPBreakout.exe, that reads all commands 
> intended for the Macraigor OCDRemote and converts all 
Z0,addr,length 
> commands (software breakpoints) into Z1,addr,length commands 
> (hardware breakpoints). As long as you limit yourself to setting no 
> more than two breakpoints at a time, it will properly break in 
FLASH 
> and all single-stepping, variable inspection, etc works 
> magnificently. This requires Macraigor's OCDRemote version 2.14 
> which supports -Z2 GDB remote serial protocol commands.
> 
> Not the ultimate solution, but a great breakthrough for a 
completely 
> free development system nonetheless.
> 
> One last point, I can get the Olimex Wiggler to run at speed 3 (140 
> khz) using the latest OCDRemote ver 2.14
> 
> However, I found that certain Windows applications, such as my 
> beloved SKYPE internet phone system, used so much of my CPU 
> resources that the speed that the Wiggler could run was severely 
> degraded (to the lowest speed). I suggest that you bring up Windows 
> Task Manager and make sure that you don't have any applications 
like 
> that running. Remember that the OCDRemote/wiggler is 
ssentially "bit-
> banging" the parallel port and this LPT1 port probably has a much 
> lower priority on the Windows driver pecking order. 
> 
> I hope to have the tutorial finished in the next several days. I'm 
> also hoping that the Eclipse foundation may accept my tutorial as 
an 
> official Eclipse Corner article.
> 
> Cheers,
> Jim Lynch
>

You mention a utility RSPBreakout.exe that converts the soft 
breakpoint requests to hardware for the ocdremote, this is what the 
new monitor softbkpts command does.
As single stepping/stepping and breakpoints within insight work 
fantastic with monitor softbkpts off command.

Regards
sjo

Re: JTAG Programmer Confusion - Noob Question

2005-12-06 by lynchzilla

--- In lpc2000@yahoogroups.com, "ntfreak2000" <ntfreak2@h...> wrote:
>
> --- In lpc2000@yahoogroups.com, "lynchzilla" <lynchzilla@a...> 
wrote:
> >
> > May I add some additional points about the wiggler-jtag isssue.
> > 
> > I wrote a tutorial titled "ARM Cross Development with Eclipse" 
that 
> > is referenced in the "links" section of this message board. This 
> > tutorial shows in excessive detail how to set up a free GNU 
> compiler 
> > set for the ARM using the Eclipse/CDT IDE and how to use the 
> Eclipse 
> > debugger with the wiggler. Hopefully, you have had a look at that.
> > 
> > The obvious shortcoming is that it couldn't debug in FLASH memory.
> > 
> > I'm now furiously working on a revision to this tutorial that 
does 
> > show how to debug in FLASH. Thanks to the genius of my new co-
> > author, Norwegian engineer Kjell Eirik Andersen, we now have a 
> > simple utility program, RSPBreakout.exe, that reads all commands 
> > intended for the Macraigor OCDRemote and converts all 
> Z0,addr,length 
> > commands (software breakpoints) into Z1,addr,length commands 
> > (hardware breakpoints). As long as you limit yourself to setting 
no 
> > more than two breakpoints at a time, it will properly break in 
> FLASH 
> > and all single-stepping, variable inspection, etc works 
> > magnificently. This requires Macraigor's OCDRemote version 2.14 
> > which supports -Z2 GDB remote serial protocol commands.
> > 
> > Not the ultimate solution, but a great breakthrough for a 
> completely 
> > free development system nonetheless.
> > 
> > One last point, I can get the Olimex Wiggler to run at speed 3 
(140 
> > khz) using the latest OCDRemote ver 2.14
> > 
> > However, I found that certain Windows applications, such as my 
> > beloved SKYPE internet phone system, used so much of my CPU 
> > resources that the speed that the Wiggler could run was severely 
> > degraded (to the lowest speed). I suggest that you bring up 
Windows 
> > Task Manager and make sure that you don't have any applications 
> like 
> > that running. Remember that the OCDRemote/wiggler is 
> ssentially "bit-
> > banging" the parallel port and this LPT1 port probably has a much 
> > lower priority on the Windows driver pecking order. 
> > 
> > I hope to have the tutorial finished in the next several days. 
I'm 
> > also hoping that the Eclipse foundation may accept my tutorial as 
> an 
> > official Eclipse Corner article.
> > 
> > Cheers,
> > Jim Lynch
> >
> 
> You mention a utility RSPBreakout.exe that converts the soft 
> breakpoint requests to hardware for the ocdremote, this is what the 
> new monitor softbkpts command does.
> As single stepping/stepping and breakpoints within insight work 
> fantastic with monitor softbkpts off command.
> 
> Regards
> sjo
>
Thanks, Sjo.

Is that an OCDRemote command, GDB command or Insight command? Where 
is it documented? It may be just what I've been looking for.

Jim Lynch

Re: JTAG Programmer Confusion - Noob Question

2005-12-06 by ntfreak2000

--- In lpc2000@yahoogroups.com, "lynchzilla" <lynchzilla@a...> wrote:
>
> --- In lpc2000@yahoogroups.com, "ntfreak2000" <ntfreak2@h...> 
wrote:
> >
> > --- In lpc2000@yahoogroups.com, "lynchzilla" <lynchzilla@a...> 
> wrote:
> > >
> > > May I add some additional points about the wiggler-jtag isssue.
> > > 
> > > I wrote a tutorial titled "ARM Cross Development with Eclipse" 
> that 
> > > is referenced in the "links" section of this message board. 
This 
> > > tutorial shows in excessive detail how to set up a free GNU 
> > compiler 
> > > set for the ARM using the Eclipse/CDT IDE and how to use the 
> > Eclipse 
> > > debugger with the wiggler. Hopefully, you have had a look at 
that.
> > > 
> > > The obvious shortcoming is that it couldn't debug in FLASH 
memory.
> > > 
> > > I'm now furiously working on a revision to this tutorial that 
> does 
> > > show how to debug in FLASH. Thanks to the genius of my new co-
> > > author, Norwegian engineer Kjell Eirik Andersen, we now have a 
> > > simple utility program, RSPBreakout.exe, that reads all 
commands 
> > > intended for the Macraigor OCDRemote and converts all 
> > Z0,addr,length 
> > > commands (software breakpoints) into Z1,addr,length commands 
> > > (hardware breakpoints). As long as you limit yourself to 
setting 
> no 
> > > more than two breakpoints at a time, it will properly break in 
> > FLASH 
> > > and all single-stepping, variable inspection, etc works 
> > > magnificently. This requires Macraigor's OCDRemote version 
2.14 
> > > which supports -Z2 GDB remote serial protocol commands.
> > > 
> > > Not the ultimate solution, but a great breakthrough for a 
> > completely 
> > > free development system nonetheless.
> > > 
> > > One last point, I can get the Olimex Wiggler to run at speed 3 
> (140 
> > > khz) using the latest OCDRemote ver 2.14
> > > 
> > > However, I found that certain Windows applications, such as my 
> > > beloved SKYPE internet phone system, used so much of my CPU 
> > > resources that the speed that the Wiggler could run was 
severely 
> > > degraded (to the lowest speed). I suggest that you bring up 
> Windows 
> > > Task Manager and make sure that you don't have any 
applications 
> > like 
> > > that running. Remember that the OCDRemote/wiggler is 
> > ssentially "bit-
> > > banging" the parallel port and this LPT1 port probably has a 
much 
> > > lower priority on the Windows driver pecking order. 
> > > 
> > > I hope to have the tutorial finished in the next several days. 
> I'm 
> > > also hoping that the Eclipse foundation may accept my tutorial 
as 
> > an 
> > > official Eclipse Corner article.
> > > 
> > > Cheers,
> > > Jim Lynch
> > >
> > 
> > You mention a utility RSPBreakout.exe that converts the soft 
> > breakpoint requests to hardware for the ocdremote, this is what 
the 
> > new monitor softbkpts command does.
> > As single stepping/stepping and breakpoints within insight work 
> > fantastic with monitor softbkpts off command.
> > 
> > Regards
> > sjo
> >
> Thanks, Sjo.
> 
> Is that an OCDRemote command, GDB command or Insight command? 
Where 
> is it documented? It may be just what I've been looking for.
> 
> Jim Lynch
>

It is a ocdremote command, added in 2.14 release.
to treat all soft breakpoints requests as hardware use:
monitor softbkpts off
use monitor help to list all other ocdremore commands.
help on individual commands can be seen by typing:
eg, monitor help softbkpts

Hope this helps

Regards
sjo

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-06 by Tom Walsh

Bertrik Sikken wrote:

>>My interface works at full speed, perhaps I have a better PCB design. I
>>wasn't very impressed by the layout on the genuine Wiggler I have, and mine
>>is faster than that.
>>    
>>
>
>The weird thing is, getting ocdremote to recognise the cable is the
>hard part, once that works it seems to run fine.
>The trick I mentioned is to first tell ocdcommander that a raven cable
>is connected, let it fail, then tell it to look for a wiggler. If I do
>that, the wiggler is recognised fine, even at the highest speed.
>  
>

Are you debugging from Windows or Linux with the wiggler?

TomW

-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

RE: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-07 by Bruce Paterson

> Bertrik Sikken wrote:
> 
> >>My interface works at full speed, perhaps I have a better 
> PCB design. 
> >>I wasn't very impressed by the layout on the genuine 
> Wiggler I have, 
> >>and mine is faster than that.
> >>    
> >>
> >
> >The weird thing is, getting ocdremote to recognise the cable is the 
> >hard part, once that works it seems to run fine.
> >The trick I mentioned is to first tell ocdcommander that a 
> raven cable 
> >is connected, let it fail, then tell it to look for a 
> wiggler. If I do 
> >that, the wiggler is recognised fine, even at the highest speed.
> >  
> >
> 
> Are you debugging from Windows or Linux with the wiggler?

I was able to run at full speed 0 with the Chameleon Pod pretending to
be a Macraigor Raven (sexier wiggler)....until I moved to a faster PC
where I had to drop to speed 3. Looks like processor speed is a variable
you need to take into account with the wiggler speed.

Cheers
Bruce

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-07 by Bertrik Sikken

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom Walsh wrote:
> Bertrik Sikken wrote:
> 
>>>My interface works at full speed, perhaps I have a better PCB design. I
>>>wasn't very impressed by the layout on the genuine Wiggler I have, and
> mine
>>>is faster than that.
>>>   
>>>
>>
>>The weird thing is, getting ocdremote to recognise the cable is the
>>hard part, once that works it seems to run fine.
>>The trick I mentioned is to first tell ocdcommander that a raven cable
>>is connected, let it fail, then tell it to look for a wiggler. If I do
>>that, the wiggler is recognised fine, even at the highest speed.
>> 
>>
> 
> Are you debugging from Windows or Linux with the wiggler?

I am trying to debug from Windows (with cygwin).

I also tried the gdb-arm-jtag package you mentioned earlier. I replaced
the pp.c file with an implementation that uses libieee1284 instead
of directly accessing /dev/parport0 and tried to get jtag-arm to
work under both windows and linux, but I'm getting no data back
yet.

Kind regards,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDlpmTETD6mlrWxPURAtULAJ9mpL/l6JoamKBTJ/B5RIk9/A75+gCgs+Mz
1t39Nq2Uaht986PZKiwsN8k=
=404D
-----END PGP SIGNATURE-----

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-07 by Tom Walsh

Bertrik Sikken wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Tom Walsh wrote:
>  
>
>>Bertrik Sikken wrote:
>>
>>    
>>
>>>>My interface works at full speed, perhaps I have a better PCB design. I
>>>>wasn't very impressed by the layout on the genuine Wiggler I have, and
>>>>        
>>>>
>>mine
>>    
>>
>>>>is faster than that.
>>>>  
>>>>
>>>>        
>>>>
>>>The weird thing is, getting ocdremote to recognise the cable is the
>>>hard part, once that works it seems to run fine.
>>>The trick I mentioned is to first tell ocdcommander that a raven cable
>>>is connected, let it fail, then tell it to look for a wiggler. If I do
>>>that, the wiggler is recognised fine, even at the highest speed.
>>>
>>>
>>>      
>>>
>>Are you debugging from Windows or Linux with the wiggler?
>>    
>>
>
>I am trying to debug from Windows (with cygwin).
>
>I also tried the gdb-arm-jtag package you mentioned earlier. I replaced
>the pp.c file with an implementation that uses libieee1284 instead
>of directly accessing /dev/parport0 and tried to get jtag-arm to
>work under both windows and linux, but I'm getting no data back
>yet.
>
>  
>
I dragged out my old wiggler clone and tried the gdb-jtag-arm working.  
It does connect to the ARM7TDMI cpu and identifies it as an ARM7TMDI.  
But the gdb-remote won't work with the ARM7 processor.  No register are 
dumped. I tried with the jtag-arm tool and it comes back with all 
registers as 0xffffffff.

I'm sure it prolly has something to do with the length of the SCANCHAIN 
between an ARM9TDMI vs ARM7TDMI.  It was interesting to tinker with, but 
I went back to my other unit (BDI2000).

TomW


-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-07 by Rob Jansen

Tom Walsh wrote:

>  I dragged out my old wiggler clone and tried the gdb-jtag-arm working.
>  It does connect to the ARM7TDMI cpu and identifies it as an ARM7TMDI.
>  But the gdb-remote won't work with the ARM7 processor.  No register are
>  dumped. I tried with the jtag-arm tool and it comes back with all
>  registers as 0xffffffff.
>
>  I'm sure it prolly has something to do with the length of the SCANCHAIN
>  between an ARM9TDMI vs ARM7TDMI.  It was interesting to tinker with, but
>  I went back to my other unit (BDI2000).

Not only may the length of the scan chain differ, the depth of the
prefetch buffer is different which will result in wrong data returned
(reading at the wrong clock tick on the data bus).

Defenitely a nice starting point for someone who starts writing his/her
own JTAG arm7tdmi-s code.

Please note: the scan chains for the ARM7TDMI and the 7TDMI-S are
different...

Regards,

     Rob

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-07 by Bertrik Sikken

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom Walsh wrote:
> Bertrik Sikken wrote:
>>>>The weird thing is, getting ocdremote to recognise the cable is the
>>>>hard part, once that works it seems to run fine.
>>>>The trick I mentioned is to first tell ocdcommander that a raven cable
>>>>is connected, let it fail, then tell it to look for a wiggler. If I do
>>>>that, the wiggler is recognised fine, even at the highest speed.
>>>>
>>>Are you debugging from Windows or Linux with the wiggler?
>>>
>>
>>I am trying to debug from Windows (with cygwin).
>>
>>I also tried the gdb-arm-jtag package you mentioned earlier. I replaced
>>the pp.c file with an implementation that uses libieee1284 instead
>>of directly accessing /dev/parport0 and tried to get jtag-arm to
>>work under both windows and linux, but I'm getting no data back
>>yet.
>>
> I dragged out my old wiggler clone and tried the gdb-jtag-arm working. 
> It does connect to the ARM7TDMI cpu and identifies it as an ARM7TMDI. 
> But the gdb-remote won't work with the ARM7 processor.  No register are
> dumped. I tried with the jtag-arm tool and it comes back with all
> registers as 0xffffffff.
> 
> I'm sure it prolly has something to do with the length of the SCANCHAIN
> between an ARM9TDMI vs ARM7TDMI.  It was interesting to tinker with, but
> I went back to my other unit (BDI2000).

Hi Tom,

Thanks for going through the trouble of trying out your wiggler clone.

I think I'm making some progress with my (olimex) wiggler clone
and the gdb-arm-jtag sources. It appears I can at least get the
JTAG id code now. I get 4F1F0F0F for an LPC2148, which looks similar
to the 7F1F0F0F default code that I see in the ARM7TDMI-S docs from ARM.
Do you remember which idcode you got?

I needed to do two things to make gdb-arm-jtag work so far:
1) wait a bit after the device is reset before accessing JTAG
2) make sure that parallel port bits DATA4 and DATA7 are set

Regarding 2), I see that these pins are going somewhere in
the olimex wiggler clone, but I can't clearly see where
(could be the output enables or perhaps some kind of power pins)

All the best,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDl1uOETD6mlrWxPURAuV1AJ9Sn4bVE4x3HTEBxJfLx3yrIYO+igCgm1Xz
dJY3PpzOkLPwuj4AnGWCcoc=
=mt+C
-----END PGP SIGNATURE-----

Re: JTAG Programmer Confusion - Noob Question

2005-12-08 by sixtyfivebit

Hi,

I'm glad this thread is helping other people, and after some research
things are a bit more clear...

Since I really don't want to buy a wiggler and would rather build one
my self (for experience, learning, etc.), is there any particular
schematic I should go with?

Leon_Heller, nice site and I saw your prototype page earlier
(bookmarked it), but I couldn't find your jtag.zip. I went through
most of the pages on your site but didn't see it... did I miss something?

lynchzilla, I'm eager to read your guide and I will wait till you post
the revision (so I don't confuse myself)... please do let everyone
know when you post the revision (if you haven't already) (no pressure,
of course :-) ). 

It looks like the combination of Leon_Heller's wiggler and
lynchzilla's guide may be the clear solution for me... everything is
compatible and stuff, right?

Thanks.

Re: [lpc2000] Re: JTAG Programmer Confusion - Noob Question

2005-12-08 by Leon Heller

----- Original Message ----- 
Show quoted textHide quoted text
From: "sixtyfivebit" <sixtyfivebit@...>
To: <lpc2000@yahoogroups.com>
Sent: Thursday, December 08, 2005 7:35 AM
Subject: [lpc2000] Re: JTAG Programmer Confusion - Noob Question


> Hi,
> 
> I'm glad this thread is helping other people, and after some research
> things are a bit more clear...
> 
> Since I really don't want to buy a wiggler and would rather build one
> my self (for experience, learning, etc.), is there any particular
> schematic I should go with?
> 
> Leon_Heller, nice site and I saw your prototype page earlier
> (bookmarked it), but I couldn't find your jtag.zip. I went through
> most of the pages on your site but didn't see it... did I miss something?

It's in this groups Files area.

Leon
---
[This E-mail has been scanned for viruses but it is your responsibility 
to maintain up to date anti virus software on the device that you are
currently using to read this email. ]

Re: [lpc2000] JTAG Programmer Confusion - Noob Question

2005-12-08 by Dominic Rath

Hello,

On Wednesday 07 December 2005 23:00, Bertrik Sikken wrote:
>
> Hi Tom,
>
> Thanks for going through the trouble of trying out your wiggler clone.
>
> I think I'm making some progress with my (olimex) wiggler clone
> and the gdb-arm-jtag sources. It appears I can at least get the
> JTAG id code now. I get 4F1F0F0F for an LPC2148, which looks similar
> to the 7F1F0F0F default code that I see in the ARM7TDMI-S docs from ARM.
> Do you remember which idcode you got?
>
The 0x4f1f0f0f is what I get on my lpc2294, so this should be fine.

>
> I needed to do two things to make gdb-arm-jtag work so far:
> 1) wait a bit after the device is reset before accessing JTAG
That's because of Philips' code protection. The test logic is forced into 
reset state whenever the chip is reset, making it impossible to debug right 
out of reset.

> 2) make sure that parallel port bits DATA4 and DATA7 are set
Data4 should be the system reset. Not sure what Data7 is.

>
> Regarding 2), I see that these pins are going somewhere in
> the olimex wiggler clone, but I can't clearly see where
> (could be the output enables or perhaps some kind of power pins)
>
> All the best,
> Bertrik

You should be aware that debugging an ARM7 is different from an ARM9. The 
debug scan-chain of the arm7 has only 33 bits, 32 bit data/address bus + one 
control bit, while the arm9 has 67 bits, 32 bit data, 32 bit address and 
three control bits. Also, the ARM7 has a different pipeline design than the 
ARM9 (3 stages arm7 vs. 5 stages arm9).

If you're interested in working on this topic mail me off-list, I've been 
working on a debugger with a gdb interface for quite some time now, it just 
needs some finishing touches.

Regards,

Dominic

Re: [lpc2000] Re: JTAG Programmer Confusion - Noob Question

2005-12-08 by Bertrik Sikken

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Leon Heller wrote:
> ----- Original Message -----
> From: "sixtyfivebit" <sixtyfivebit@...>
>> I'm glad this thread is helping other people, and after some research
>> things are a bit more clear...
>>
>> Since I really don't want to buy a wiggler and would rather build one
>> my self (for experience, learning, etc.), is there any particular
>> schematic I should go with?
>>
>> Leon_Heller, nice site and I saw your prototype page earlier
>> (bookmarked it), but I couldn't find your jtag.zip. I went through
>> most of the pages on your site but didn't see it... did I miss something?
> 
> It's in this groups Files area.

Hi Leon,

Sorry if I'm asking a stupid question (I'm not a hardware designer),
but is your circuit safe for the parallel port?

As far as I can see the 74HC244 takes its VCC from the 3.3V from
the target board while the 5V parallel port signals are directly
connected to the inputs of the HC244. In the HC244 datasheet I
notice that there are protection diodes between the inputs and
Vcc / ground.

It looks like there is a current path from the 5V parallel ports pins
through the HC244 protection diodes into the target 3.3V without any
obvious current limit. Doesn't this risk blowing out the parallel port
drivers? Also, wouldn't this lift the 3.3V on the target to a possibly
dangerous voltage?

Regards,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDmJY9ETD6mlrWxPURAhJEAJ4kuW6nwVKRxmHsXdKdG2ejIoooMgCeMv+r
ahAx0FVIvPtuTdOupedxOcA=
=b2cL
-----END PGP SIGNATURE-----

Re: [lpc2000] Re: JTAG Programmer Confusion - Noob Question

2005-12-08 by Leon Heller

----- Original Message ----- 
Show quoted textHide quoted text
From: "Bertrik Sikken" <bertrik@...>
To: <lpc2000@yahoogroups.com>
Sent: Thursday, December 08, 2005 8:23 PM
Subject: Re: [lpc2000] Re: JTAG Programmer Confusion - Noob Question


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Leon Heller wrote:
>> ----- Original Message -----
>> From: "sixtyfivebit" <sixtyfivebit@...>
>>> I'm glad this thread is helping other people, and after some research
>>> things are a bit more clear...
>>>
>>> Since I really don't want to buy a wiggler and would rather build one
>>> my self (for experience, learning, etc.), is there any particular
>>> schematic I should go with?
>>>
>>> Leon_Heller, nice site and I saw your prototype page earlier
>>> (bookmarked it), but I couldn't find your jtag.zip. I went through
>>> most of the pages on your site but didn't see it... did I miss 
>>> something?
>>
>> It's in this groups Files area.
>
> Hi Leon,
>
> Sorry if I'm asking a stupid question (I'm not a hardware designer),
> but is your circuit safe for the parallel port?
>
> As far as I can see the 74HC244 takes its VCC from the 3.3V from
> the target board while the 5V parallel port signals are directly
> connected to the inputs of the HC244. In the HC244 datasheet I
> notice that there are protection diodes between the inputs and
> Vcc / ground.
>
> It looks like there is a current path from the 5V parallel ports pins
> through the HC244 protection diodes into the target 3.3V without any
> obvious current limit. Doesn't this risk blowing out the parallel port
> drivers? Also, wouldn't this lift the 3.3V on the target to a possibly
> dangerous voltage?

It would be better to use a 74AC244, but I don't have any problems with it 
as it is.

Leon 

---
[This E-mail has been scanned for viruses but it is your responsibility 
to maintain up to date anti virus software on the device that you are
currently using to read this email. ]

Re: JTAG Programmer Confusion - Noob Question

2005-12-08 by leon_heller

--- In lpc2000@yahoogroups.com, "Leon Heller" <leon.heller@b...> 
wrote:
>
> 
> ----- Original Message ----- 
> From: "Bertrik Sikken" <bertrik@z...>
> To: <lpc2000@yahoogroups.com>
> Sent: Thursday, December 08, 2005 8:23 PM
> Subject: Re: [lpc2000] Re: JTAG Programmer Confusion - Noob Question
> 
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Leon Heller wrote:
> >> ----- Original Message -----
> >> From: "sixtyfivebit" <sixtyfivebit@y...>
> >>> I'm glad this thread is helping other people, and after some 
research
> >>> things are a bit more clear...
> >>>
> >>> Since I really don't want to buy a wiggler and would rather 
build one
> >>> my self (for experience, learning, etc.), is there any 
particular
> >>> schematic I should go with?
> >>>
> >>> Leon_Heller, nice site and I saw your prototype page earlier
> >>> (bookmarked it), but I couldn't find your jtag.zip. I went 
through
> >>> most of the pages on your site but didn't see it... did I miss 
> >>> something?
> >>
> >> It's in this groups Files area.
> >
> > Hi Leon,
> >
> > Sorry if I'm asking a stupid question (I'm not a hardware 
designer),
> > but is your circuit safe for the parallel port?
> >
> > As far as I can see the 74HC244 takes its VCC from the 3.3V from
> > the target board while the 5V parallel port signals are directly
> > connected to the inputs of the HC244. In the HC244 datasheet I
> > notice that there are protection diodes between the inputs and
> > Vcc / ground.
> >
> > It looks like there is a current path from the 5V parallel ports 
pins
> > through the HC244 protection diodes into the target 3.3V without 
any
> > obvious current limit. Doesn't this risk blowing out the parallel 
port
> > drivers? Also, wouldn't this lift the 3.3V on the target to a 
possibly
> > dangerous voltage?
> 
> It would be better to use a 74AC244, but I don't have any problems 
with it 
> as it is.

I should also have said that parallel port outputs don't generate 5V 
signals (I think they are TTL), and they are protected.

Leon

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.