Lpc2000

Hi all,

I never got my Olimex Wiggler to work correctly even after patching the 
adapter and trying out all suggestions on the net. Last possibilities is 
that my parallel port is bad, the cable I use to the wiggler is bad or 
the wiggler itself is bad.  What cable lengths have others tested with 
success?

Regards
/Ake

-- 
 ---
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

----- Original Message ----- 

From: "Ake Hedman, eurosource" <akhe@...>
To: <lpc2000@yahoogroups.com>
Sent: Wednesday, November 09, 2005 2:40 PM
Subject: [lpc2000] WIGGLER and cable length


> Hi all,
>
> I never got my Olimex Wiggler to work correctly even after patching the
> adapter and trying out all suggestions on the net. Last possibilities is
> that my parallel port is bad, the cable I use to the wiggler is bad or
> the wiggler itself is bad.  What cable lengths have others tested with
> success?

I made my own 'Wiggler-alike". It works fine with a 2m cable on the parallel 
port.

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. ]

Ake Hedman, eurosource wrote:

>Hi all,
>
>I never got my Olimex Wiggler to work correctly even after patching the 
>adapter and trying out all suggestions on the net. Last possibilities is 
>that my parallel port is bad, the cable I use to the wiggler is bad or 
>the wiggler itself is bad.  What cable lengths have others tested with 
>success?
>
>  
>
Cable lengths are a problem with JTAG wigglers (JTAG in general, even 
high end units could have that problem).  When using a wiggler on an 
SA1100 project (also ARM), that anything more than 10inches (25cm) could 
cause problems.

Try a different computer, it may not be the cable length but a slow bit 
on the parallel port?

TomW

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

Leon Heller wrote:

>
> I made my own 'Wiggler-alike". It works fine with a 2m cable on the 
> parallel
> port.
>
OK thanks Leon. I also have a 2 m cable. Good to know that this works 
for at least one person.

Cheers
/Ake

-- 
 ---
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

Tom Walsh wrote:

>
> Cable lengths are a problem with JTAG wigglers (JTAG in general, even
> high end units could have that problem).  When using a wiggler on an
> SA1100 project (also ARM), that anything more than 10inches (25cm) could
> cause problems.
>
> Try a different computer, it may not be the cable length but a slow bit
> on the parallel port?
>
> TomW

Thanks Tom appreciate that. My lab bench could really live without a 
computer also on it ;-)  so I hope it will be possible to have a meter 
of cable at least. Will try some configurations.

Cheers
/Ake

-- 
 ---
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

Ake Hedman, eurosource wrote:

>Tom Walsh wrote:
>
>  
>
>>Cable lengths are a problem with JTAG wigglers (JTAG in general, even
>>high end units could have that problem).  When using a wiggler on an
>>SA1100 project (also ARM), that anything more than 10inches (25cm) could
>>cause problems.
>>
>>Try a different computer, it may not be the cable length but a slow bit
>>on the parallel port?
>>
>>TomW
>>    
>>
>
>Thanks Tom appreciate that. My lab bench could really live without a 
>computer also on it ;-)  so I hope it will be possible to have a meter 
>of cable at least. Will try some configurations.
>
>  
>
IIRC, sometimes you have to put some caps to ground to keep signal ring 
/ overshoot down with longer cables (simple noise filter).  Other times, 
the caps get in the way and the cable works without them.

This was the primary reason I purchased an Abatron BDI2000..


TomW

>Cheers
>/Ake
>
>  
>


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

Hey Tom,

> This was the primary reason I purchased an Abatron BDI2000..

I'll get work to buy me an Abatron one of these days ... the
price of the basic unit from Ultimate Solutions (a US distributor)
is about $2800 (BDI2000 & bdiGBD PPC4x + P/s and cable kit).
Then to add bdiGDB for other PPC models, ARM, Coldfire etc is
$1000 per processor.

I was wondering if this is the route you went to get support
for multiple processors, or whether the BDI2000 allows you
to write your own interface, eg. the tradeoff being your own
time versus $1000 to support a new processor.

Is there anything particularly 'special' about using a BDI
versus a Wiggler, other than the fact that its convenient,
debugged, and supported hardware. eg. does Abitron pay ARM etc to
license an interface to say the trace module that somehow
makes the BDI interface better? I've used a TI JTAG-like
interface before and you could only purchase a unit from TI
or a licensee since the interface was proprietry.

Most of the processors I play with as a hobby, so getting work
to pay the extra money for adding processors is not so easy :)

Cheers
Dave

David Hawkins wrote:

>Hey Tom,
>
>  
>
>>This was the primary reason I purchased an Abatron BDI2000..
>>    
>>
>
>I'll get work to buy me an Abatron one of these days ... the
>price of the basic unit from Ultimate Solutions (a US distributor)
>is about $2800 (BDI2000 & bdiGBD PPC4x + P/s and cable kit).
>Then to add bdiGDB for other PPC models, ARM, Coldfire etc is
>$1000 per processor.
>
>I was wondering if this is the route you went to get support
>for multiple processors, or whether the BDI2000 allows you
>to write your own interface, eg. the tradeoff being your own
>time versus $1000 to support a new processor.
>  
>
This was a big expenditure for me and one that was carefully 
considered.   The primary reason  was not so much the cost as to the 
functionality.  I've used wigglers and they just can be a nasty little 
thing, sometimes you cannot figure out why they won't synchronize.  Then 
you fuss around and wiggle wires, change caps and then it starts working 
again.

The project that I'm doing (consultant) is very large, there is a lot of 
code that needs to be written and the last thing I need is to wonder if 
the dongle is any good.  The other thing is that there isn't a single 
solution to a TCP/remote: use JELIE for the XScale, ARM9 uses 
JTAGGER(?), LPC2000 use this if you change this code...  Or, get this 
guys OC something or other and use that.  Too chaotic for my tastes.

My board setup is two processors: LPC2106 and LPC2138, JTAG is daisy 
chained (TDO from one to the TDI of the other processor).  I can launch 
two instances of Insight and debug either processor.  Send a serial 
string from one processor and breakpoint reception of the string on the 
other processor.  I did not think that a dongle could debug a chain, it 
might, but the time I had to spend on other areas of the project didn't 
leave guesswork to the debug setup.

>Is there anything particularly 'special' about using a BDI
>versus a Wiggler, other than the fact that its convenient,
>debugged, and supported hardware. eg. does Abitron pay ARM etc to
>license an interface to say the trace module that somehow
>makes the BDI interface better? I've used a TI JTAG-like
>interface before and you could only purchase a unit from TI
>or a licensee since the interface was proprietry.
>
>  
>
The other thing is that I don't deal with external software to program 
the Flash of the processors.  I simply telnet into the BDI2000, type 
"s1" or "s2" to select either processor, then type "er" to erase and 
"pr" to program.  The BDI2000 uses tftp to fetch the previously defined 
binary for the respective processor.


>Most of the processors I play with as a hobby, so getting work
>to pay the extra money for adding processors is not so easy :)
>
>  
>
BTDT, I've gotten tired of a two-line LCD or an LED to debug with.  heh.

Regards,

TomW


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

Thanks all for help on this. Switched to a 1 meter cable and got it to 
work on speed == 8 today.

Thnaks a lot!
/Ake

Tom Walsh wrote:

> David Hawkins wrote:
>
> >Hey Tom,
> >
> > 
> >
> >>This was the primary reason I purchased an Abatron BDI2000..
> >>   
> >>
> >
> >I'll get work to buy me an Abatron one of these days ... the
> >price of the basic unit from Ultimate Solutions (a US distributor)
> >is about $2800 (BDI2000 & bdiGBD PPC4x + P/s and cable kit).
> >Then to add bdiGDB for other PPC models, ARM, Coldfire etc is
> >$1000 per processor.
> >
> >I was wondering if this is the route you went to get support
> >for multiple processors, or whether the BDI2000 allows you
> >to write your own interface, eg. the tradeoff being your own
> >time versus $1000 to support a new processor.
> > 
> >
> This was a big expenditure for me and one that was carefully
> considered.   The primary reason  was not so much the cost as to the
> functionality.  I've used wigglers and they just can be a nasty little
> thing, sometimes you cannot figure out why they won't synchronize.  Then
> you fuss around and wiggle wires, change caps and then it starts working
> again.
>
> The project that I'm doing (consultant) is very large, there is a lot of
> code that needs to be written and the last thing I need is to wonder if
> the dongle is any good.  The other thing is that there isn't a single
> solution to a TCP/remote: use JELIE for the XScale, ARM9 uses
> JTAGGER(?), LPC2000 use this if you change this code...  Or, get this
> guys OC something or other and use that.  Too chaotic for my tastes.
>
> My board setup is two processors: LPC2106 and LPC2138, JTAG is daisy
> chained (TDO from one to the TDI of the other processor).  I can launch
> two instances of Insight and debug either processor.  Send a serial
> string from one processor and breakpoint reception of the string on the
> other processor.  I did not think that a dongle could debug a chain, it
> might, but the time I had to spend on other areas of the project didn't
> leave guesswork to the debug setup.
>
> >Is there anything particularly 'special' about using a BDI
> >versus a Wiggler, other than the fact that its convenient,
> >debugged, and supported hardware. eg. does Abitron pay ARM etc to
> >license an interface to say the trace module that somehow
> >makes the BDI interface better? I've used a TI JTAG-like
> >interface before and you could only purchase a unit from TI
> >or a licensee since the interface was proprietry.
> >
> > 
> >
> The other thing is that I don't deal with external software to program
> the Flash of the processors.  I simply telnet into the BDI2000, type
> "s1" or "s2" to select either processor, then type "er" to erase and
> "pr" to program.  The BDI2000 uses tftp to fetch the previously defined
> binary for the respective processor.
>
>
> >Most of the processors I play with as a hobby, so getting work
> >to pay the extra money for adding processors is not so easy :)
> >
> > 
> >
> BTDT, I've gotten tired of a two-line LCD or an LED to debug with.  heh.
>
> Regards,
>
> TomW
>
>
> -- 
> Tom Walsh - WN3L - Embedded Systems Consultant
> http://openhardware.net, http://cyberiansoftware.com
> "Windows? No thanks, I have work to do..."
> ----------------------------------------------------
>
>
>
>
> 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]