Yahoo Groups archive

Lpc2000

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

Thread

AD problem

AD problem

2005-12-22 by zhengy_yong

the problem is i can only enter the interrupt 
funciton once,then never enter the function again.
are there any problems with my program?
anyone can give me a suggestion?


#include "config.h"
unsigned int  result[20];
unsigned char channelx[20];

void __irq IRQ_ADC(void)
{
   unsigned int  value   = 0x0000;       //result of the ADC converter
   unsigned char channel = 0x00;         //the channel
   unsigned char i	       = 0;	
   value        = ADDR;  //read the result and clear the DONE sign
   channel      = (value>>0x18)&0x07; //get the channel
   value        = (value>>6)&0x03ff;  //convert the ADC result
   if(channel == 0x00)                //switch the channel
       	ADCR = ADCR&0xFFFFFF00|0x02;   
    else if(channel == 0x01)
       	ADCR = ADCR&0xFFFFFF00|0x04;
    else if(channel == 0x02)
      	ADCR = ADCR&0xFFFFFF00|0x08;
    else if(channel == 0x03)
      	ADCR = ADCR&0xFFFFFF00|0x01;
    channelx[i]  = channel;
	result[i]    = value;
	i++;	
	if(i<20)             //whether get 20 result ?
		i++;
	else
		i = 0;
	VICVectAddr0 = 0;    //clear the IRQ function address
}

int main(void)
{
    PINSEL1 	 = 0x01400000;//connect the pin to adc
    ADCR    	 = 0x00201501;//setup the ADCR only use the ain0
    ADCR		 = ADCR|0x00010000;//use burst model
    VICIntSelect = 0x00000000;      //
    VICVectCntl0 = 0x32;
    VICVectAddr0 = (int)IRQ_ADC;    //address of the IRQ function
    VICIntEnable = 0x00040000;      //enamble the ADC interrupt
    while(1)
    {
	;                           //wait for the interrupt
     }
	return(0);
}

Re: [lpc2000] AD problem

2005-12-22 by Richard Duits

The line:
VICVectAddr0 = 0;
in IRQ_ADC should be
VICVectAddr = 0;


Richard.


zhengy_yong wrote:
Show quoted textHide quoted text
> the problem is i can only enter the interrupt
> funciton once,then never enter the function again.
> are there any problems with my program?
> anyone can give me a suggestion?
>
>
> #include "config.h"
> unsigned int  result[20];
> unsigned char channelx[20];
>
> void __irq IRQ_ADC(void)
> {
>    unsigned int  value   = 0x0000;       //result of the ADC converter
>    unsigned char channel = 0x00;         //the channel
>    unsigned char i             = 0;     
>    value        = ADDR;  //read the result and clear the DONE sign
>    channel      = (value>>0x18)&0x07; //get the channel
>    value        = (value>>6)&0x03ff;  //convert the ADC result
>    if(channel == 0x00)                //switch the channel
>              ADCR = ADCR&0xFFFFFF00|0x02;  
>     else if(channel == 0x01)
>              ADCR = ADCR&0xFFFFFF00|0x04;
>     else if(channel == 0x02)
>             ADCR = ADCR&0xFFFFFF00|0x08;
>     else if(channel == 0x03)
>             ADCR = ADCR&0xFFFFFF00|0x01;
>     channelx[i]  = channel;
>       result[i]    = value;
>       i++;     
>       if(i<20)             //whether get 20 result ?
>             i++;
>       else
>             i = 0;
>       VICVectAddr0 = 0;    //clear the IRQ function address
> }
>
> int main(void)
> {
>     PINSEL1       = 0x01400000;//connect the pin to adc
>     ADCR          = 0x00201501;//setup the ADCR only use the ain0
>     ADCR            = ADCR|0x00010000;//use burst model
>     VICIntSelect = 0x00000000;      //
>     VICVectCntl0 = 0x32;
>     VICVectAddr0 = (int)IRQ_ADC;    //address of the IRQ function
>     VICIntEnable = 0x00040000;      //enamble the ADC interrupt
>     while(1)
>     {
>       ;                           //wait for the interrupt
>      }
>       return(0);
> }
>
>
>
>
>
> 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/>.
>
>
> ------------------------------------------------------------------------
>

JTAG debugging options

2006-01-03 by Sean

Hello All,

I have seen a lot of talk around about Wiggler-based JTAG debugger boards, 
which can be built for < $1, and I see several commercial JTAG debugging 
pods that are > $1000.  What is it that these things do that you can't do 
with a simple wiggler interface?  I.e. for most intents and purposes what 
can you not do with a wiggler interface?

Even the original maker of wiggler charges > $150 for this board, which can 
be built for like $1.  What's the deal there?

-- Sean

Re: [lpc2000] JTAG debugging options

2006-01-03 by Peter Jakacki

That's not even a realistic comparison, if I gave you <$100 would 
you/could you supply me with 100 wigglers? Are you even considering that 
the newer ones are USB based and much more complicated than a simple 
parallel port device? If for instance an engineers time is valued at 
$100 an hour, could he produce a one-off "professional finish" wriggler 
for less then $150? That's right, why bother!

Have you ever been involved in marketing? A humble can of beans may only 
contain a few cents worth of beans but I'm sure you pay a lot more than 
that for it quite happily. You could save yourself some money and grow 
them yourself, but isn't there always a cost involved in everything we do?

BTW, I have never needed to use ARM wrigglers myself.

*Peter*

Sean wrote:
Show quoted textHide quoted text
> I have seen a lot of talk around about Wiggler-based JTAG debugger boards, 
> which can be built for < $1, and I see several commercial JTAG debugging 
> pods that are > $1000.  What is it that these things do that you can't do 
> with a simple wiggler interface?  I.e. for most intents and purposes what 
> can you not do with a wiggler interface?
>
> Even the original maker of wiggler charges > $150 for this board, which can 
> be built for like $1.  What's the deal there?

Re: [lpc2000] JTAG debugging options

2006-01-03 by Sean

Easy, Tiger :)   Yes... I understand that time = money.

Perhaps I have misunderstood something.  Is this not a Wiggler-compatible 
interface?

http://www.micronix.ca/sbc213x_main.htm
http://www.micronix.ca/catalog/product_pages/images/JTAG02_SCH_011.jpg


Perhaps I should rephrase my original question:

What JTAG debugging options are there, and what's the difference between 
the ~$150 and > $1000 board options?

-- Sean


At 09:22 PM 1/2/2006, you wrote:
Show quoted textHide quoted text
>That's not even a realistic comparison, if I gave you <$100 would
>you/could you supply me with 100 wigglers? Are you even considering that
>the newer ones are USB based and much more complicated than a simple
>parallel port device? If for instance an engineers time is valued at
>$100 an hour, could he produce a one-off "professional finish" wriggler
>for less then $150? That's right, why bother!
>
>Have you ever been involved in marketing? A humble can of beans may only
>contain a few cents worth of beans but I'm sure you pay a lot more than
>that for it quite happily. You could save yourself some money and grow
>them yourself, but isn't there always a cost involved in everything we do?
>
>BTW, I have never needed to use ARM wrigglers myself.
>
>*Peter*
>
>Sean wrote:
> > I have seen a lot of talk around about Wiggler-based JTAG debugger boards,
> > which can be built for < $1, and I see several commercial JTAG debugging
> > pods that are > $1000.  What is it that these things do that you can't do
> > with a simple wiggler interface?  I.e. for most intents and purposes what
> > can you not do with a wiggler interface?
> >
> > Even the original maker of wiggler charges > $150 for this board, which 
> can
> > be built for like $1.  What's the deal there?
>
>
>----------
>YAHOO! GROUPS LINKS
>
>    *  Visit your group "<http://groups.yahoo.com/group/lpc2000>lpc2000" 
> on the web.
>    *
>    *  To unsubscribe from this group, send an email to:
>    * 
> <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>lpc2000-unsubscribe@yahoogroups.com 
>
>    *
>    *  Your use of Yahoo! Groups is subject to the 
> <http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.
>
>
>----------

Re: JTAG debugging options

2006-01-03 by lynchzilla

Sean pointed out that the Macraigor Wiggler is $150 whilst the 
Olimex clone is $19 and asks "what's the deal here?"

Open up a wiggler and you'll see that it's a cheap level-shifter 
chip and a transistor built into a DB-25 shell. Admittedly, $19 
seems more like a fair price, but Olimex didn't write the OCDRemote 
and OCDCommander software and didn't have to ammortize any software 
development (Macraigor does). Macraigor probably provides more 
telephone support if the customer has trouble getting it to work.

Even the fastest wiggler baud rate is slow in comparison to the 
newer USB and Ethernet JTAG debuggers. This is not obvious in short 
demo programs, but painful if you are downloading a very large 
program.

I worry about myself and others relying on the Macraigor OCDRemote 
JTAG program that interfaces GDB to the JTAG pins. OCDRemote is NOT 
open-source. Macraigor allows free downloads of the OCDRemote 
executable but the source code has always been proprietary. They 
could withdraw this "freebie" at any time.

We need two things. A reasonably priced USB JTAG debugger supported 
by a true "open-source" GDB/JTAG driver. Until then, the debugging 
situation will remain tenuous, at best (for those on limited 
budgets).

Cheers,
James P. Lynch

Re: [lpc2000] JTAG debugging options

2006-01-03 by Peter Jakacki

Sean wrote:
> Easy, Tiger :)   Yes... I understand that time = money.
Since I'm not speaking to you face to face I just cut to the chase :)


> Perhaps I have misunderstood something.  Is this not a Wiggler-compatible 
> interface?
>
> http://www.micronix.ca/sbc213x_main.htm
> http://www.micronix.ca/catalog/product_pages/images/JTAG02_SCH_011.jpg
>
>
> Perhaps I should rephrase my original question:
>
> What JTAG debugging options are there, and what's the difference between 
> the ~$150 and > $1000 board options?

The JTAG-02 is only CAD $35, I'm not sure where you find the $150 
option. The Keil ULINK (USB) is only $199 but I'm not aware of any 
 >$1000 options. As James pointed out, the basic hardware is 
straightforward but the driver software is a different story altogether.

*Peter*

Re: [lpc2000] JTAG debugging options

2006-01-03 by Sean

Ok, the one I saw was

http://www.gwmicros.com/public_html/pages/products/iproducts/BDM_JTAG/Macraigor/BDM-JTAG_Macraigor_usbDemon.htm

or

http://www.gwmicros.com/public_html/pages/products/iproducts/BDM_JTAG/Macraigor/BDM-JTAG_Macraigor_Raven.htm

both 818EUR

And their wiggler is 188 EUR.  Yes, most others I see are in the $150 - 
$300 range.

I'm just trying to understand here.  I can see how originally there were 
few (expensive) options, and there was a lot of design and support and 
software creation necessary, so yes, it was expensive.  However from the 
point of view of anyone who is starting a design, be it a starving student 
or a multinational corporation, what do the expensive emulators do that I 
can't do with a $1 DIY one?  Can I get by with a DIY one, or should I 
actually fork out the cash for the name-brand ones?  Let's assume that I 
need to do non-trivial debugging here.

I too am a fan of alternate methods for debugging, or creating modules on 
the PC and then porting them, or loggers, or serial port dumps, however 
there are times when having an ICE makes it a lot easier to figure out.

Thanks for the advice,

-- Sean


At 10:35 PM 1/2/2006, you wrote:
Show quoted textHide quoted text
>Sean wrote:
> > Easy, Tiger :)   Yes... I understand that time = money.
>Since I'm not speaking to you face to face I just cut to the chase :)
>
>
> > Perhaps I have misunderstood something.  Is this not a Wiggler-compatible
> > interface?
> >
> > 
> <http://www.micronix.ca/sbc213x_main.htm>http://www.micronix.ca/sbc213x_main.htm
> > http://www.micronix.ca/catalog/product_pages/images/JTAG02_SCH_011.jpg
> >
> >
> > Perhaps I should rephrase my original question:
> >
> > What JTAG debugging options are there, and what's the difference between
> > the ~$150 and > $1000 board options?
>
>The JTAG-02 is only CAD $35, I'm not sure where you find the $150
>option. The Keil ULINK (USB) is only $199 but I'm not aware of any
> >$1000 options. As James pointed out, the basic hardware is
>straightforward but the driver software is a different story altogether.
>
>*Peter*
>
>
>
>----------
>YAHOO! GROUPS LINKS
>
>    *  Visit your group "<http://groups.yahoo.com/group/lpc2000>lpc2000" 
> on the web.
>    *
>    *  To unsubscribe from this group, send an email to:
>    * 
> <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>lpc2000-unsubscribe@yahoogroups.com 
>
>    *
>    *  Your use of Yahoo! Groups is subject to the 
> <http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.
>
>
>----------

Re: [lpc2000] Re: JTAG debugging options

2006-01-03 by Sean

This is a very good point:  why are they offering their software for free, 
knowing full well that other people are using it on competitor's hardware?

Yes, baud rates are slower over parallel, although you can get > 1mbit/sec 
on the parallel port itself, perhaps only 25KB/sec when using wiggler, but 
even there, even with a rather large code size of 512KB, this is only 20 
seconds to download...  For most debugging scenarios you won't need to 
download the full size anyway, and if you split your program into modules 
you can get by with only debugging a module at a time, which means you only 
need to load a few dozen KB at a time?

-- Sean

At 10:21 PM 1/2/2006, you wrote:
Show quoted textHide quoted text
>Sean pointed out that the Macraigor Wiggler is $150 whilst the
>Olimex clone is $19 and asks "what's the deal here?"
>
>Open up a wiggler and you'll see that it's a cheap level-shifter
>chip and a transistor built into a DB-25 shell. Admittedly, $19
>seems more like a fair price, but Olimex didn't write the OCDRemote
>and OCDCommander software and didn't have to ammortize any software
>development (Macraigor does). Macraigor probably provides more
>telephone support if the customer has trouble getting it to work.
>
>Even the fastest wiggler baud rate is slow in comparison to the
>newer USB and Ethernet JTAG debuggers. This is not obvious in short
>demo programs, but painful if you are downloading a very large
>program.
>
>I worry about myself and others relying on the Macraigor OCDRemote
>JTAG program that interfaces GDB to the JTAG pins. OCDRemote is NOT
>open-source. Macraigor allows free downloads of the OCDRemote
>executable but the source code has always been proprietary. They
>could withdraw this "freebie" at any time.
>
>We need two things. A reasonably priced USB JTAG debugger supported
>by a true "open-source" GDB/JTAG driver. Until then, the debugging
>situation will remain tenuous, at best (for those on limited
>budgets).
>
>Cheers,
>James P. Lynch
>
>
>
>
>
>
>----------
>YAHOO! GROUPS LINKS
>
>    *  Visit your group "<http://groups.yahoo.com/group/lpc2000>lpc2000" 
> on the web.
>    *
>    *  To unsubscribe from this group, send an email to:
>    * 
> <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>lpc2000-unsubscribe@yahoogroups.com 
>
>    *
>    *  Your use of Yahoo! Groups is subject to the 
> <http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.
>
>
>----------

Re: JTAG debugging options

2006-01-03 by rtstofer

--- In lpc2000@yahoogroups.com, Sean <embeddedrelated@w...> wrote:
>
> 
> Ok, the one I saw was
> 
> 
http://www.gwmicros.com/public_html/pages/products/iproducts/BDM_JTAG
/Macraigor/BDM-JTAG_Macraigor_usbDemon.htm
> 
> or
> 
> 
http://www.gwmicros.com/public_html/pages/products/iproducts/BDM_JTAG
/Macraigor/BDM-JTAG_Macraigor_Raven.htm
> 
> both 818EUR
> 
> And their wiggler is 188 EUR.  Yes, most others I see are in the 
$150 - 
> $300 range.
> 
> I'm just trying to understand here.  I can see how originally 
there were 
> few (expensive) options, and there was a lot of design and support 
and 
> software creation necessary, so yes, it was expensive.  However 
from the 
> point of view of anyone who is starting a design, be it a starving 
student 
> or a multinational corporation, what do the expensive emulators do 
that I 
> can't do with a $1 DIY one?  Can I get by with a DIY one, or 
should I 
> actually fork out the cash for the name-brand ones?  Let's assume 
that I 
> need to do non-trivial debugging here.

Well then, if you want to do non-trivial debugging, you'll certainly 
hate Insight->OCD Remote->Wiggler clone.  As James Lynch points out 
in his excellent tutorial, there are days when it just won't work.  
To be blunt, it sucks.  It isn't worth the aggravation to get it 
working; printf works better.

Now, Tom Walsh is more than happy with his high dollar solution 
(Abatron BDI2000) and if I were doing this for money, I would buy 
the same interface he has.  If I could find a distributor in the 
US...

And, if the US$ wasn't complete worthless when converted to British 
Pounds, I might consider the Rowley CrossConnect package.

Richard



> 
> I too am a fan of alternate methods for debugging, or creating 
modules on 
> the PC and then porting them, or loggers, or serial port dumps, 
however 
> there are times when having an ICE makes it a lot easier to figure 
out.
> 
> Thanks for the advice,
> 
> -- Sean
> 
> 
> At 10:35 PM 1/2/2006, you wrote:
> >Sean wrote:
> > > Easy, Tiger :)   Yes... I understand that time = money.
> >Since I'm not speaking to you face to face I just cut to the 
chase :)
> >
> >
> > > Perhaps I have misunderstood something.  Is this not a Wiggler-
compatible
> > > interface?
> > >
> > > 
> > 
<http://www.micronix.ca/sbc213x_main.htm>http://www.micronix.ca/sbc21
3x_main.htm
> > > 
http://www.micronix.ca/catalog/product_pages/images/JTAG02_SCH_011.jp
g
> > >
> > >
> > > Perhaps I should rephrase my original question:
> > >
> > > What JTAG debugging options are there, and what's the 
difference between
> > > the ~$150 and > $1000 board options?
> >
> >The JTAG-02 is only CAD $35, I'm not sure where you find the $150
> >option. The Keil ULINK (USB) is only $199 but I'm not aware of any
> > >$1000 options. As James pointed out, the basic hardware is
> >straightforward but the driver software is a different story 
altogether.
> >
> >*Peter*
> >
> >
> >
> >----------
> >YAHOO! GROUPS LINKS
> >
> >    *  Visit your 
group "<http://groups.yahoo.com/group/lpc2000>lpc2000" 
> > on the web.
> >    *
> >    *  To unsubscribe from this group, send an email to:
> >    * 
> > <mailto:lpc2000-unsubscribe@yahoogroups.com?
subject=Unsubscribe>lpc2000-unsubscribe@yahoogroups.com 
Show quoted textHide quoted text
> >
> >    *
> >    *  Your use of Yahoo! Groups is subject to the 
> > <http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.
> >
> >
> >----------
>

Re: [lpc2000] JTAG debugging options

2006-01-03 by Leon Heller

----- Original Message ----- 
Show quoted textHide quoted text
From: "Sean" <embeddedrelated@...>
To: <lpc2000@yahoogroups.com>
Sent: Tuesday, January 03, 2006 4:21 AM
Subject: Re: [lpc2000] JTAG debugging options


>
> Ok, the one I saw was
>
> http://www.gwmicros.com/public_html/pages/products/iproducts/BDM_JTAG/Macraigor/BDM-JTAG_Macraigor_usbDemon.htm
>
> or
>
> http://www.gwmicros.com/public_html/pages/products/iproducts/BDM_JTAG/Macraigor/BDM-JTAG_Macraigor_Raven.htm
>
> both 818EUR
>
> And their wiggler is 188 EUR.  Yes, most others I see are in the $150 -
> $300 range.
>
> I'm just trying to understand here.  I can see how originally there were
> few (expensive) options, and there was a lot of design and support and
> software creation necessary, so yes, it was expensive.  However from the
> point of view of anyone who is starting a design, be it a starving student
> or a multinational corporation, what do the expensive emulators do that I
> can't do with a $1 DIY one?  Can I get by with a DIY one, or should I
> actually fork out the cash for the name-brand ones?  Let's assume that I
> need to do non-trivial debugging here.
>
> I too am a fan of alternate methods for debugging, or creating modules on
> the PC and then porting them, or loggers, or serial port dumps, however
> there are times when having an ICE makes it a lot easier to figure out.

A DIY one will be fine. I designed a PCB for one that may easily be made at
home with rudimentary facilities (artwork in jtag.zip in the Files area).
It'll probably take a couple of hours to make the PCB and get it working.

I already had a genuine Macraigor Wiggler and mine works at higher speeds
than the real thing; my PCB layout is better. I've also got a Rowley
CrossConnect (99 GBP) with a USB connection to the PCB, and that works very
well. USB is more convenient than a parallel port connection, and faster.

Amontec sells their Chameleon interface, which is based on a reconfigurable 
CPLD. It can emulate a Wiggler or Raven, as well as lots of other 
interfaces, including JTAGs for Xilinx and Altera parts. I've got one of 
those, as well. Worth getting if you want to play with FPGAs and other JTAG 
MCUs.

Leon

Re: [lpc2000] Re: JTAG debugging options

2006-01-03 by Anton Erasmus

On 2 Jan 2006 at 23:25, Sean wrote:

> 
> This is a very good point:  why are they offering their software for
> free, knowing full well that other people are using it on competitor's
> hardware?

The advertising value they get is immense. Anybody who has used a
wiggler or wiggler clone would at least give their more sophisticated
models a look if they are considering getting something a bit better
than a wiggler.

> Yes, baud rates are slower over parallel, although you can get >
> 1mbit/sec on the parallel port itself, perhaps only 25KB/sec when
> using wiggler, but even there, even with a rather large code size of
> 512KB, this is only 20 seconds to download...  For most debugging
> scenarios you won't need to download the full size anyway, and if you
> split your program into modules you can get by with only debugging a
> module at a time, which means you only need to load a few dozen KB at
> a time?

The biggest issue with using the wiggler, is that it is temperamental. It works
quite nicely when it works, but there are days when it just refuses to work - normally 
when you actually need it. Any JTAG interface where the JTAG signal timing is 
independant of the PC hardware/software used are going to be more stable.

An open hardware / open source JTAG interface with USB / ethernet interface 
would be great. Designing and building the hardware is not such a big problem.
Writing the software is the biggest issue for such a project.

Regards
  Anton Erasmus


> -- Sean
> 
> At 10:21 PM 1/2/2006, you wrote:
> >Sean pointed out that the Macraigor Wiggler is $150 whilst the
> >Olimex clone is $19 and asks "what's the deal here?"
> >
> >Open up a wiggler and you'll see that it's a cheap level-shifter chip
> >and a transistor built into a DB-25 shell. Admittedly, $19 seems more
> >like a fair price, but Olimex didn't write the OCDRemote and
> >OCDCommander software and didn't have to ammortize any software
> >development (Macraigor does). Macraigor probably provides more
> >telephone support if the customer has trouble getting it to work.
> >
> >Even the fastest wiggler baud rate is slow in comparison to the
> >newer USB and Ethernet JTAG debuggers. This is not obvious in short
> >demo programs, but painful if you are downloading a very large
> >program.
> >
> >I worry about myself and others relying on the Macraigor OCDRemote
> >JTAG program that interfaces GDB to the JTAG pins. OCDRemote is NOT
> >open-source. Macraigor allows free downloads of the OCDRemote
> >executable but the source code has always been proprietary. They
> >could withdraw this "freebie" at any time.
> >
> >We need two things. A reasonably priced USB JTAG debugger supported
> >by a true "open-source" GDB/JTAG driver. Until then, the debugging
> >situation will remain tenuous, at best (for those on limited
> >budgets).
> >
> >Cheers,
> >James P. Lynch
> >
> >
> >
> >
> >
> >
> >----------
> >YAHOO! GROUPS LINKS
> >
> >    *  Visit your group
> >    "<http://groups.yahoo.com/group/lpc2000>lpc2000" 
> > on the web.
> >    *
> >    *  To unsubscribe from this group, send an email to:
> >    * 
> > <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>lpc2
> > 000-unsubscribe@yahoogroups.com 
> >
> >    *
> >    *  Your use of Yahoo! Groups is subject to the 
> > <http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.
> >
> >
> >----------
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 
> 

-- 
A J Erasmus

JTAG debugging options

2006-01-03 by Stephen Pelc

> Date: Mon, 02 Jan 2006 21:01:04 -0500
> From: Sean <embeddedrelated@...>

> I have seen a lot of talk around about Wiggler-based JTAG
> debugger boards, which can be built for < $1, and I see several
> commercial JTAG debugging pods that are > $1000.  What is it that
> these things do that you can't do with a simple wiggler
> interface?

Warning: Response from JTAG vendor: See
  http://www.mpeforth.com/jtagwidget.htm
which is designed for hardwaare bring-up as well as software 
debugging.

There are three aspects to consider:
  connection to PC host
  connection to ARM target
  software

Host Connection
===============
The host connection in rough order of performance and cost is
  PC parallel port
  USB
  dedicated PCI card
Some parallel port interfaces are powered from the parallel 
port. Without great care in component selection and PC layout 
these can be unreliable. We have several, some work well, some 
don't.

USB interfaces can draw power from the USB port. In general, 
these are the most convenient for site use. But the hardware is 
more expensive and software is required, probably both on the PC 
and on the JTAG adaptor. Software costs.

PCI interfaces will give the highest performance, but are 
usually only found on dedicated testers.

ARM target connection
=====================
As the JTAG speed increases, you need to be more careful with 
drive levels, cable length and cable impedances. We do not use a 
cheap HC244, we use a real level shifter on the JTAG side. It's 
rated to below 1.8 volts. Similarly, the lifetime and cost of a 
good quality 3M connector is much higher than that of a generic 
20 pin connector.

Software
========
Once you move away from the parallel port connection, you'll 
most likely have to write software for the adaptor as well as 
for the PC.

Conclusion
==========
Better (performance, reliability ...) JTAG debuggers require 
more work, which has to be paid for somehow or other. Technical 
support costs time/money too. There's a lot more to ARM JTAG 
debuggers than at first meets the eye.

Stephen

--
Stephen Pelc, stephen@...
MicroProcessor Engineering Ltd - More Real, Less Time
133 Hill Lane, Southampton SO15 5AF, England
tel: +44 23 80 631441, fax: +44 23 80 339691
web: http://www.mpeforth.com - free VFX Forth downloads

Re: JTAG debugging options

2006-01-03 by derbaier

--- In lpc2000@yahoogroups.com, "Stephen Pelc" <stephen@m...> wrote:
>
> 
> Warning: Response from JTAG vendor: See
>   http://www.mpeforth.com/jtagwidget.htm
> which is designed for hardwaare bring-up as well as software 
> debugging.
> 
> There are three aspects to consider:
>   connection to PC host
>   connection to ARM target
>   software
> 
> Host Connection
> ===============
> The host connection in rough order of performance and cost is
>   PC parallel port
>   USB
>   dedicated PCI card
> Some parallel port interfaces are powered from the parallel 
> port. Without great care in component selection and PC layout 
> these can be unreliable. We have several, some work well, some 
> don't.
> 
> USB interfaces can draw power from the USB port. In general, 
> these are the most convenient for site use. But the hardware is 
> more expensive and software is required, probably both on the PC 
> and on the JTAG adaptor. Software costs.
> 
> PCI interfaces will give the highest performance, but are 
> usually only found on dedicated testers.
> 
> ARM target connection
> =====================
> As the JTAG speed increases, you need to be more careful with 
> drive levels, cable length and cable impedances. We do not use a 
> cheap HC244, we use a real level shifter on the JTAG side. It's 
> rated to below 1.8 volts. Similarly, the lifetime and cost of a 
> good quality 3M connector is much higher than that of a generic 
> 20 pin connector.
> 
> Software
> ========
> Once you move away from the parallel port connection, you'll 
> most likely have to write software for the adaptor as well as 
> for the PC.
> 
> Conclusion
> ==========
> Better (performance, reliability ...) JTAG debuggers require 
> more work, which has to be paid for somehow or other. Technical 
> support costs time/money too. There's a lot more to ARM JTAG 
> debuggers than at first meets the eye.
> 
> Stephen
> 
> --
> Stephen Pelc, stephen@m...
> MicroProcessor Engineering Ltd - More Real, Less Time
> 133 Hill Lane, Southampton SO15 5AF, England
> tel: +44 23 80 631441, fax: +44 23 80 339691
> web: http://www.mpeforth.com - free VFX Forth downloads
>

Nice analysis, Stephen.

I just wanted to note that you left out my favorite as the most
powerful of the JTAG to workstation connection methods.

 Ethernet!!!!

The Lauterbach Trace32 Ethernet is the fastest and most powerful of
all the JTAG setups that I have used, and extremely expensive.  :-(

One big advantage of Ethernet, is that the workstation and the debug
target do not have to be in the same location. Of course, it is not as
fast over the Internet as it is with a direct local connection.  :-)

Care to give them some competition in that arena?  :-)

-- Dave

Re: JTAG debugging options

2006-01-03 by rtstofer

> We need two things. A reasonably priced USB JTAG debugger supported 
> by a true "open-source" GDB/JTAG driver. Until then, the debugging 
> situation will remain tenuous, at best (for those on limited 
> budgets).
> 
> Cheers,
> James P. Lynch
>

I posted a question re: using Insight under Linux on the Sparkfun 
Forum.  I received this site as a reply: http://openocd.berlios.de/web/

This may be a HUGE step in the right direction.

Richard

Re: [lpc2000] Re: JTAG debugging options

2006-01-03 by David Hawkins

> 
> Well then, if you want to do non-trivial debugging, you'll certainly 
> hate Insight->OCD Remote->Wiggler clone.  As James Lynch points out 
> in his excellent tutorial, there are days when it just won't work.  
> To be blunt, it sucks.  It isn't worth the aggravation to get it 
> working; printf works better.
> 
> Now, Tom Walsh is more than happy with his high dollar solution 
> (Abatron BDI2000) and if I were doing this for money, I would buy 
> the same interface he has.  If I could find a distributor in the 
> US...
> 
> And, if the US$ wasn't complete worthless when converted to British 
> Pounds, I might consider the Rowley CrossConnect package.

 > If I could find a distributor in the US...

Try Ultimate Solutions ...

http://www.ultsol.com

I requested a quote for PowerPC 4xx and ARM development ...

BDI2000+bdiGDB PPC4xx $2570
bdiGDB for ARM7/9/9E  $1000

I just have to figure out how to get that passed the guys with
the money ...

Dave

Re: [lpc2000] Re: JTAG debugging options

2006-01-03 by Tom Walsh

David Hawkins wrote:

>  
>
>>Well then, if you want to do non-trivial debugging, you'll certainly 
>>hate Insight->OCD Remote->Wiggler clone.  As James Lynch points out 
>>in his excellent tutorial, there are days when it just won't work.  
>>To be blunt, it sucks.  It isn't worth the aggravation to get it 
>>working; printf works better.
>>
>>Now, Tom Walsh is more than happy with his high dollar solution 
>>(Abatron BDI2000) and if I were doing this for money, I would buy 
>>the same interface he has.  If I could find a distributor in the 
>>US...
>>
>>And, if the US$ wasn't complete worthless when converted to British 
>>Pounds, I might consider the Rowley CrossConnect package.
>>    
>>
>
> > If I could find a distributor in the US...
>
>Try Ultimate Solutions ...
>
>http://www.ultsol.com
>
>I requested a quote for PowerPC 4xx and ARM development ...
>
>BDI2000+bdiGDB PPC4xx $2570
>bdiGDB for ARM7/9/9E  $1000
>
>  
>
Interesting.  I got the BDI2000+bdiGDB option for the ARM7/9/9E for the 
same price.  I suspect that the config files are all that is different 
between the models.  I'm still not sure what that "bdiGDB" is all about...

TomW



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

Re: [lpc2000] Re: JTAG debugging options

2006-01-03 by Bertrik Sikken

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

rtstofer wrote:
>> We need two things. A reasonably priced USB JTAG debugger supported
>> by a true "open-source" GDB/JTAG driver. Until then, the debugging
>> situation will remain tenuous, at best (for those on limited
>> budgets).
>>
>> Cheers,
>> James P. Lynch
>>
> 
> I posted a question re: using Insight under Linux on the Sparkfun
> Forum.  I received this site as a reply: http://openocd.berlios.de/web/
> 
> This may be a HUGE step in the right direction.

I played around with this in the past week and I think this is the
most promising open-source ARM7 JTAG project.

The source code looks well organised and extensible.

The latest version (download with subversion) is now able to run
under windows (with cygwin), it supports the ARM7TDMI-S micro and
works with various type of JTAG cables (parallel port and USB).
It successfully stepped through some simple programs in both
gdb and insight.

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

iD8DBQFDuu3NETD6mlrWxPURAtgWAKC6T0KPR1s7J4o0ZEXhPM19zhI1LACeMM6c
hlCeE8YOe76AeQHEubaZsow=
=JTW+
-----END PGP SIGNATURE-----

JTAG debugging options

2006-01-04 by Stephen Pelc

From: "derbaier" <dershu@...>
> I just wanted to note that you left out my favorite as the most
> powerful of the JTAG to workstation connection methods.
> 
>  Ethernet!!!!
> 
> The Lauterbach Trace32 Ethernet is the fastest and most powerful
> of all the JTAG setups that I have used, and extremely expensive.
>  :-(
> 
> One big advantage of Ethernet, is that the workstation and the
> debug target do not have to be in the same location. Of course,
> it is not as fast over the Internet as it is with a direct local
> connection.  :-)
> 
> Care to give them some competition in that arena?  :-)

How many would you like?

We did consider Ethernet, but USB is much more convenient for 
site work. It may become an option ...

Stephen

--
Stephen Pelc, stephen@...
MicroProcessor Engineering Ltd - More Real, Less Time
133 Hill Lane, Southampton SO15 5AF, England
tel: +44 23 80 631441, fax: +44 23 80 339691
web: http://www.mpeforth.com - free VFX Forth downloads

Re: JTAG debugging options

2006-01-04 by derbaier

--- In lpc2000@yahoogroups.com, "Stephen Pelc" <stephen@m...> wrote:
>
> 
> How many would you like?
> 
> We did consider Ethernet, but USB is much more convenient for 
> site work. It may become an option ...
> 
> Stephen
> 
> --
> Stephen Pelc, stephen@m...
> MicroProcessor Engineering Ltd - More Real, Less Time
> 133 Hill Lane, Southampton SO15 5AF, England
> tel: +44 23 80 631441, fax: +44 23 80 339691
> web: http://www.mpeforth.com - free VFX Forth downloads
>

I get your point!  :-)

Unfortunately I am no longer in a position to influence the purchase
of debug hardware, since I am recently retired. My former employer
bought large numbers of the Ethernet debuggers that I was refering to,
and we found the Ethernet connection to be very very handy.  The
ability to debug from a distance was a highly used feature in that
work environment.

I don't think that it would all that difficult to enable remote
debugging using USB as long as a local workstation was available to
act as the local USB connection to the target?

Thanks for the reply!

-- Dave

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.