Yahoo Groups archive

Lpc2000

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

Thread

Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by compuguru64

Newb - I can't seem to get my wiggler compatible to talk to my olimex 
proto board.  I've tried it on 2 laptops, 800 mhz and 2.8 ghz machines, 
various parallel port speed settings.  I'm using OCD Commander and 
always get an Internal Error 43 message, then "Error Response from 
INITIALIZE: 0x03 initialize_target : cable disconnected  (10 : 03)"  
I'm using OCD Commander 2.4.1 that comes with IAR jumpstart compiler.

I've followed posts warning about system speed, about making sure pins 
8 and 15 are shorted on the wiggler, about making sure the debug jumper 
is installed, about making sure the parallel port is not set to ECP - 
all verified yet nothing seems to work.  Shouldn't I at least be able 
to start OCD Commander with no warning messages and use it to reset the 
board even if the default flash-based program it was shipped with is 
still on it?  The default program appears to work just fine when the 
JTAG cable is disconnected.

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by Joel Winarske

Are you debugging out of RAM or from Flash?

If RAM, under options/debugger do you have a macro file defined?

You might also try:
Enable Hardware reset under Macraigor, define time to 0.

Joel
Show quoted textHide quoted text
> Newb - I can't seem to get my wiggler compatible to talk to my olimex
> proto board.  I've tried it on 2 laptops, 800 mhz and 2.8 ghz machines,
> various parallel port speed settings.  I'm using OCD Commander and
> always get an Internal Error 43 message, then "Error Response from
> INITIALIZE: 0x03 initialize_target : cable disconnected  (10 : 03)"
> I'm using OCD Commander 2.4.1 that comes with IAR jumpstart compiler.
> 
> I've followed posts warning about system speed, about making sure pins
> 8 and 15 are shorted on the wiggler, about making sure the debug jumper
> is installed, about making sure the parallel port is not set to ECP -
> all verified yet nothing seems to work.  Shouldn't I at least be able
> to start OCD Commander with no warning messages and use it to reset the
> board even if the default flash-based program it was shipped with is
> still on it?  The default program appears to work just fine when the
> JTAG cable is disconnected.

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by Karim Virani

I understand that the wiggler will only let you debug in RAM, and in IAR
linker options I do have the RAM xcl file selected.  In debugger options
I don't have any startup macro file defined - I'm not sure what I should
be using.  I did enable hardware reset like you recommended, but that
didn't work either.

Since I'm new to the IAR environment too, I thought I would simplify by
just using OCD Commander directly.  I'd like to know of something that
should always work in OCD Commander regardless of what is in RAM or in
Flash on the board - so I can eliminate the olimex jtag as the problem.
I had assumed that performing a RESET from OCD Commander should always
work - but that's just a guess.

Karim
Show quoted textHide quoted text
-----Original Message-----
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
Of Joel Winarske
Sent: Monday, November 21, 2005 11:05 PM
To: lpc2000@yahoogroups.com
Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board


Are you debugging out of RAM or from Flash?

If RAM, under options/debugger do you have a macro file defined?

You might also try:
Enable Hardware reset under Macraigor, define time to 0.

Joel

> Newb - I can't seem to get my wiggler compatible to talk to my olimex
> proto board.  I've tried it on 2 laptops, 800 mhz and 2.8 ghz
machines,
> various parallel port speed settings.  I'm using OCD Commander and
> always get an Internal Error 43 message, then "Error Response from
> INITIALIZE: 0x03 initialize_target : cable disconnected  (10 : 03)"
> I'm using OCD Commander 2.4.1 that comes with IAR jumpstart compiler.
> 
> I've followed posts warning about system speed, about making sure pins
> 8 and 15 are shorted on the wiggler, about making sure the debug
jumper
> is installed, about making sure the parallel port is not set to ECP -
> all verified yet nothing seems to work.  Shouldn't I at least be able
> to start OCD Commander with no warning messages and use it to reset
the
> board even if the default flash-based program it was shipped with is
> still on it?  The default program appears to work just fine when the
> JTAG cable is disconnected. 





 
Yahoo! Groups Links

Re: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by haare_in_der_dusche

There is reasonable doubt that OCD commander works at all on more 
sophisticated Windows versions.
The wiggler hardware itself works perfectly when used with Rowley 
Crossworks, but OCD commander just doesn't work.
And that happens also with an original "Wiggler" made by Macraigor.

Apparentyl you'll have either to
- replace OCD commander by something better (Rowley Crossworks)
- use a braindead Windows version like Windows 95 or one of it's 
re-brews (98 & Me).

	

	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by Karim Virani

Oh man!  I swear I saw references to OCD Commander working on Win2K and XP, maybe in Jim Lynch's eclipse tutorial?  I thought it was just a system speed issue.  I wanted to follow the Olimex recommendation for Rowley, but this is a hobby for me and Rowley isn't wife-friendly expense-wise.  I'll see if I can dig up a really old system from somewhere.  I hope Olimex comes up with the rumored affordable usb-jtag soon.

Karim
Show quoted textHide quoted text
-----Original Message-----
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
Of haare_in_der_dusche
Sent: Tuesday, November 22, 2005 10:09 AM
To: lpc2000@yahoogroups.com
Subject: Re: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board


There is reasonable doubt that OCD commander works at all on more 
sophisticated Windows versions.
The wiggler hardware itself works perfectly when used with Rowley 
Crossworks, but OCD commander just doesn't work.
And that happens also with an original "Wiggler" made by Macraigor.

Apparentyl you'll have either to
- replace OCD commander by something better (Rowley Crossworks)
- use a braindead Windows version like Windows 95 or one of it's 
re-brews (98 & Me).

	

	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de



 
Yahoo! Groups Links

Re: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by FreeRTOS Info

> Oh man!  I swear I saw references to OCD Commander working on Win2K and
XP, maybe in Jim Lynch's eclipse tutorial?  I thought it was just a system
speed issue.  I wanted to follow the Olimex recommendation for Rowley, but
this is a hobby for me and Rowley isn't wife-friendly expense-wise.  I'll
see if I can dig up a really old system from somewhere.  I hope Olimex comes
up with the rumored affordable usb-jtag soon.


For what its worth - I use wiggler/olimex/OCDLibRemote on Win2k no problem.
Never tried Commander though.

Regards,
Richard.


http://www.FreeRTOS.org

Re: Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by rtstofer

Eclipse -> Insight -> OCDRemote with the ARM-JTAG device from 
Sparkfun does work on Windows XP, more or less.  The less part is 
that it only connects after pounding on it (figuratively) for a 
dozen or more times.  Pretty much what is explained in the tutorial.

However...  What if the LPC didn't have JTAG?  What would you do for 
debugging?  Well, just do that.  I don't have enough pins to leave 
spares for JTAG, the debugger doesn't work often enough to tolerate 
so I just don't bother.  I start by writing basic character IO 
functions, add a string output function and an itoa() function and 
I'm on my way.

It is certainly possible to bring up large embedded systems without 
JTAG.  It is probably easier with it but, sometimes, that't the way 
it goes.

I am using the bootloader at 115.2K baud so programming goes pretty 
quick.

Richard

--- In lpc2000@yahoogroups.com, "FreeRTOS Info" <nospam@F...> wrote:
>
> > Oh man!  I swear I saw references to OCD Commander working on 
Win2K and
> XP, maybe in Jim Lynch's eclipse tutorial?  I thought it was just 
a system
> speed issue.  I wanted to follow the Olimex recommendation for 
Rowley, but
> this is a hobby for me and Rowley isn't wife-friendly expense-
wise.  I'll
> see if I can dig up a really old system from somewhere.  I hope 
Olimex comes
> up with the rumored affordable usb-jtag soon.
> 
> 
> For what its worth - I use wiggler/olimex/OCDLibRemote on Win2k no 
problem.
Show quoted textHide quoted text
> Never tried Commander though.
> 
> Regards,
> Richard.
> 
> 
> http://www.FreeRTOS.org
>

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by Joel Winarske

> I understand that the wiggler will only let you debug in RAM, and in IAR
> linker options I do have the RAM xcl file selected.  In debugger options
> I don't have any startup macro file defined - I'm not sure what I should
> be using.  I did enable hardware reset like you recommended, but that
> didn't work either.

Your IAR debug macro file must have the following in order to debug from
RAM:

execUserPreload()
{
    __writeMemory32(0x00000002, 0xE01FC040, "Memory"); // MEMMAP = 2;
}


Joel

Re: [lpc2000] Re: Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by Bill Knight

Something that has helped me connect to the LPC with OCDRemote is to
put the LPC into Boot Loader mode first.

Regards
-Bill Knight
R O SoftWare &
http://www.theARMPatch.com
Show quoted textHide quoted text
On Tue, 22 Nov 2005 17:19:01 -0000, rtstofer wrote:

>Eclipse -> Insight -> OCDRemote with the ARM-JTAG device from 
>Sparkfun does work on Windows XP, more or less.  The less part is 
>that it only connects after pounding on it (figuratively) for a 
>dozen or more times.  Pretty much what is explained in the tutorial.

>However...  What if the LPC didn't have JTAG?  What would you do for 
>debugging?  Well, just do that.  I don't have enough pins to leave 
>spares for JTAG, the debugger doesn't work often enough to tolerate 
>so I just don't bother.  I start by writing basic character IO 
>functions, add a string output function and an itoa() function and 
>I'm on my way.

>It is certainly possible to bring up large embedded systems without 
>JTAG.  It is probably easier with it but, sometimes, that't the way 
>it goes.

>I am using the bootloader at 115.2K baud so programming goes pretty 
>quick.

>Richard

>--- In lpc2000@yahoogroups.com, "FreeRTOS Info" <nospam@F...> wrote:
>>
>> > Oh man!  I swear I saw references to OCD Commander working on 
>Win2K and
>> XP, maybe in Jim Lynch's eclipse tutorial?  I thought it was just 
>a system
>> speed issue.  I wanted to follow the Olimex recommendation for 
>Rowley, but
>> this is a hobby for me and Rowley isn't wife-friendly expense-
>wise.  I'll
>> see if I can dig up a really old system from somewhere.  I hope 
>Olimex comes
>> up with the rumored affordable usb-jtag soon.
>> 
>> 
>> For what its worth - I use wiggler/olimex/OCDLibRemote on Win2k no 
>problem.
>> Never tried Commander though.
>> 
>> Regards,
>> Richard.
>> 
>> 
>> http://www.FreeRTOS.org
>>








> 
>Yahoo! Groups Links



>

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by Viron Papadopoulos

What is neeeded (hardware & software) to debug in
FLASH?

Viron.


--- Karim Virani <karim@...> wrote:

> I understand that the wiggler will only let you
> debug in RAM, and in IAR
> linker options I do have the RAM xcl file selected. 
> In debugger options
> I don't have any startup macro file defined - I'm
> not sure what I should
> be using.  I did enable hardware reset like you
> recommended, but that
> didn't work either.
> 
> Since I'm new to the IAR environment too, I thought
> I would simplify by
> just using OCD Commander directly.  I'd like to know
> of something that
> should always work in OCD Commander regardless of
> what is in RAM or in
> Flash on the board - so I can eliminate the olimex
> jtag as the problem.
> I had assumed that performing a RESET from OCD
> Commander should always
> work - but that's just a guess.
> 
> Karim
> 
> -----Original Message-----
> From: lpc2000@yahoogroups.com
> [mailto:lpc2000@yahoogroups.com]On Behalf
> Of Joel Winarske
> Sent: Monday, November 21, 2005 11:05 PM
> To: lpc2000@yahoogroups.com
> Subject: RE: [lpc2000] Problems with olimex
> (wiggler) jtag and olimex
> lpc2129 proto board
> 
> 
> Are you debugging out of RAM or from Flash?
> 
> If RAM, under options/debugger do you have a macro
> file defined?
> 
> You might also try:
> Enable Hardware reset under Macraigor, define time
> to 0.
> 
> Joel
> 
> > Newb - I can't seem to get my wiggler compatible
> to talk to my olimex
> > proto board.  I've tried it on 2 laptops, 800 mhz
> and 2.8 ghz
> machines,
> > various parallel port speed settings.  I'm using
> OCD Commander and
> > always get an Internal Error 43 message, then
> "Error Response from
> > INITIALIZE: 0x03 initialize_target : cable
> disconnected  (10 : 03)"
> > I'm using OCD Commander 2.4.1 that comes with IAR
> jumpstart compiler.
> > 
> > I've followed posts warning about system speed,
> about making sure pins
> > 8 and 15 are shorted on the wiggler, about making
> sure the debug
> jumper
> > is installed, about making sure the parallel port
> is not set to ECP -
> > all verified yet nothing seems to work.  Shouldn't
> I at least be able
> > to start OCD Commander with no warning messages
> and use it to reset
> the
> > board even if the default flash-based program it
> was shipped with is
> > still on it?  The default program appears to work
> just fine when the
> > JTAG cable is disconnected. 
> 
> 
> 
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

Re: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by Dominic Rath

If this is a hobby for you and you're willing to spend some time, instead of 
money (not really wife-friendly either...) mail me off-list. I'm looking for 
testers/users for my open-source (GPL) ARM7/ARM9 debugger. Currently, this is 
linux-only software, and I don't plan to port it to windows (could be ported 
quite easly, but I see no reason). It supports wiggler (parport) compatible 
devices and FT2232c (usb 1.1) based interfaces.

Regards, 
Dominic
Show quoted textHide quoted text
On Tuesday 22 November 2005 17:51, Karim Virani wrote:
> Oh man!  I swear I saw references to OCD Commander working on Win2K and XP,
> maybe in Jim Lynch's eclipse tutorial?  I thought it was just a system
> speed issue.  I wanted to follow the Olimex recommendation for Rowley, but
> this is a hobby for me and Rowley isn't wife-friendly expense-wise.  I'll
> see if I can dig up a really old system from somewhere.  I hope Olimex
> comes up with the rumored affordable usb-jtag soon.
>
> Karim
>

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-22 by Joel Winarske

> What is neeeded (hardware & software) to debug in
> FLASH?

Which compiler?  I'll presume IAR as that's what the thread started was
enquiring about:

General Options, Debugger, Download tab:
If ....(default) is not in pane, select edit, new, ok, ok.

This will Flash your part upon entering debug.

Keep in mind the core only supports two hardware breakpoints.  Depending on
your debug settings one may be used by Clib stdio.
 
Joel

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Karim Virani

Since Crossworks is supposed to be bulletproof with wigglers, so I
downloaded a trial copy. It won't connect to the target - I get the
message "Cannot identify target. Check JTAG Connections and that the
target is powered" Same message as when there's nothing connected to the
parallel port.

Is it more likely that my olimex-jtag is DOA or it's the jtag port on
the 2129 board? If the olimex-jtag adapter is fried, can it endanger the
board - I have a 2nd board I can try, but don't want to risk frying it. 

Karim
Show quoted textHide quoted text
-----Original Message-----
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
Of Joel Winarske
Sent: Tuesday, November 22, 2005 11:50 AM
To: lpc2000@yahoogroups.com
Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board


> I understand that the wiggler will only let you debug in RAM, and in
IAR
> linker options I do have the RAM xcl file selected.  In debugger
options
> I don't have any startup macro file defined - I'm not sure what I
should
> be using.  I did enable hardware reset like you recommended, but that
> didn't work either.

Your IAR debug macro file must have the following in order to debug from
RAM:

execUserPreload()
{
    __writeMemory32(0x00000002, 0xE01FC040, "Memory"); // MEMMAP = 2;
}


Joel





 
Yahoo! Groups Links

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Dan Beadle

Are you sure that the jumpers are installed to enable JTAG?  

 

The JTAG port is pretty rugged - so unlikely that you fried it.

 

The ports are pull up to the 3.3V on the jtag port - so not likely that
you would do any damage.  I would try the other board, check the jumpers
first (there is a jumper that tells the chip to use JTAG, otherwise it
is ignored)

 

Dan

 

 

  _____  
Show quoted textHide quoted text
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com] On Behalf
Of Karim Virani
Sent: Wednesday, November 23, 2005 5:21 PM
To: lpc2000@yahoogroups.com
Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board

 

Since Crossworks is supposed to be bulletproof with wigglers, so I
downloaded a trial copy. It won't connect to the target - I get the
message "Cannot identify target. Check JTAG Connections and that the
target is powered" Same message as when there's nothing connected to the
parallel port.

Is it more likely that my olimex-jtag is DOA or it's the jtag port on
the 2129 board? If the olimex-jtag adapter is fried, can it endanger the
board - I have a 2nd board I can try, but don't want to risk frying it. 

Karim

-----Original Message-----
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
Of Joel Winarske
Sent: Tuesday, November 22, 2005 11:50 AM
To: lpc2000@yahoogroups.com
Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board


> I understand that the wiggler will only let you debug in RAM, and in
IAR
> linker options I do have the RAM xcl file selected.  In debugger
options
> I don't have any startup macro file defined - I'm not sure what I
should
> be using.  I did enable hardware reset like you recommended, but that
> didn't work either.

Your IAR debug macro file must have the following in order to debug from
RAM:

execUserPreload()
{
    __writeMemory32(0x00000002, 0xE01FC040, "Memory"); // MEMMAP = 2;
}


Joel






Yahoo! Groups Links










  _____  

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

 

  _____  



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

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Karim Virani

Yes - I have the debug jumper installed, the bsl and jrst jumpers are
open.  I tried the other board - same response.  I think I got a bum
wiggler.

Karim
Show quoted textHide quoted text
-----Original Message-----
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
Of Dan Beadle
Sent: Wednesday, November 23, 2005 7:24 PM
To: lpc2000@yahoogroups.com
Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board


Are you sure that the jumpers are installed to enable JTAG?  

 

The JTAG port is pretty rugged - so unlikely that you fried it.

 

The ports are pull up to the 3.3V on the jtag port - so not likely that
you would do any damage.  I would try the other board, check the jumpers
first (there is a jumper that tells the chip to use JTAG, otherwise it
is ignored)

 

Dan

 

 

  _____  

From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com] On Behalf
Of Karim Virani
Sent: Wednesday, November 23, 2005 5:21 PM
To: lpc2000@yahoogroups.com
Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board

 

Since Crossworks is supposed to be bulletproof with wigglers, so I
downloaded a trial copy. It won't connect to the target - I get the
message "Cannot identify target. Check JTAG Connections and that the
target is powered" Same message as when there's nothing connected to the
parallel port.

Is it more likely that my olimex-jtag is DOA or it's the jtag port on
the 2129 board? If the olimex-jtag adapter is fried, can it endanger the
board - I have a 2nd board I can try, but don't want to risk frying it. 

Karim

-----Original Message-----
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
Of Joel Winarske
Sent: Tuesday, November 22, 2005 11:50 AM
To: lpc2000@yahoogroups.com
Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board


> I understand that the wiggler will only let you debug in RAM, and in
IAR
> linker options I do have the RAM xcl file selected.  In debugger
options
> I don't have any startup macro file defined - I'm not sure what I
should
> be using.  I did enable hardware reset like you recommended, but that
> didn't work either.

Your IAR debug macro file must have the following in order to debug from
RAM:

execUserPreload()
{
    __writeMemory32(0x00000002, 0xE01FC040, "Memory"); // MEMMAP = 2;
}


Joel






Yahoo! Groups Links










  _____  

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

 

  _____  



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




 
Yahoo! Groups Links



 





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

Re: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Michael Johnson

Hi Karim,

Do you have another computer you can try? It could be that your PC 
parallel port isn't working.

Regards
Michael
Show quoted textHide quoted text
>Since Crossworks is supposed to be bulletproof with wigglers, so I
>downloaded a trial copy. It won't connect to the target - I get the
>message "Cannot identify target. Check JTAG Connections and that the
>target is powered" Same message as when there's nothing connected to the
>parallel port.
>
>Is it more likely that my olimex-jtag is DOA or it's the jtag port on
>the 2129 board? If the olimex-jtag adapter is fried, can it endanger the
>board - I have a 2nd board I can try, but don't want to risk frying it. 
>
>Karim
>
>-----Original Message-----
>From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
>Of Joel Winarske
>Sent: Tuesday, November 22, 2005 11:50 AM
>To: lpc2000@yahoogroups.com
>Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
>lpc2129 proto board
>
>
>  
>
>>I understand that the wiggler will only let you debug in RAM, and in
>>    
>>
>IAR
>  
>
>>linker options I do have the RAM xcl file selected.  In debugger
>>    
>>
>options
>  
>
>>I don't have any startup macro file defined - I'm not sure what I
>>    
>>
>should
>  
>
>>be using.  I did enable hardware reset like you recommended, but that
>>didn't work either.
>>    
>>
>
>Your IAR debug macro file must have the following in order to debug from
>RAM:
>
>execUserPreload()
>{
>    __writeMemory32(0x00000002, 0xE01FC040, "Memory"); // MEMMAP = 2;
>}
>
>
>Joel
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>  
>

Re: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Leon Heller

----- Original Message ----- 
Show quoted textHide quoted text
From: "Michael Johnson" <mpj@...>
To: <lpc2000@yahoogroups.com>
Sent: Thursday, November 24, 2005 6:58 AM
Subject: Re: [lpc2000] Problems with olimex (wiggler) jtag and olimex 
lpc2129 proto board


> Hi Karim,
>
> Do you have another computer you can try? It could be that your PC
> parallel port isn't working.

Make sure the port is set for EPC mode.

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] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Karim Virani

Yes - I went back to the original modern laptop and it works with Rowley!  Must've had something off on the parallel port on the older system (though I can use it for other bidirectional, non ecp applications).  Still can't use the newer system with IAR or OCDCommander - it doesn't even recognize the wiggler.  At least I know the jtag hardware works.

So Rowley works like a dream - I can connect via the wiggler, I can download and I can set hardware breakpoints and debug from flash in it.  Goes back to the old price problem for hobbyists.  Maybe they'll sell me an academic licence.  The other problem is that there are many fewer examples.  There's no complete set of header files and examples for the olimex 2129 proto board like there are in IAR.

And is most of the example and free code out there implemented for the gnuarm chain?  I'm entirely new to microconrollers.  Perhaps I should go with Jim Lynch's environment and not worry about flash debugging for now.  I'm under the impression that OCDLibRemote in cygwin doesn't have the same problems that OCDCommander running natively in Windows has.  Is that right?

Thanks,

Karim
Show quoted textHide quoted text
-----Original Message-----
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
Of Michael Johnson
Sent: Thursday, November 24, 2005 12:59 AM
To: lpc2000@yahoogroups.com
Subject: Re: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board


Hi Karim,

Do you have another computer you can try? It could be that your PC 
parallel port isn't working.

Regards
Michael

>Since Crossworks is supposed to be bulletproof with wigglers, so I
>downloaded a trial copy. It won't connect to the target - I get the
>message "Cannot identify target. Check JTAG Connections and that the
>target is powered" Same message as when there's nothing connected to the
>parallel port.
>
>Is it more likely that my olimex-jtag is DOA or it's the jtag port on
>the 2129 board? If the olimex-jtag adapter is fried, can it endanger the
>board - I have a 2nd board I can try, but don't want to risk frying it. 
>
>Karim
>
>-----Original Message-----
>From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
>Of Joel Winarske
>Sent: Tuesday, November 22, 2005 11:50 AM
>To: lpc2000@yahoogroups.com
>Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
>lpc2129 proto board
>
>
>  
>
>>I understand that the wiggler will only let you debug in RAM, and in
>>    
>>
>IAR
>  
>
>>linker options I do have the RAM xcl file selected.  In debugger
>>    
>>
>options
>  
>
>>I don't have any startup macro file defined - I'm not sure what I
>>    
>>
>should
>  
>
>>be using.  I did enable hardware reset like you recommended, but that
>>didn't work either.
>>    
>>
>
>Your IAR debug macro file must have the following in order to debug from
>RAM:
>
>execUserPreload()
>{
>    __writeMemory32(0x00000002, 0xE01FC040, "Memory"); // MEMMAP = 2;
>}
>
>
>Joel
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>  
>




 
Yahoo! Groups Links

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Paul Curtis

Hi, 

> Yes - I went back to the original modern laptop and it works 
> with Rowley!  Must've had something off on the parallel port 
> on the older system (though I can use it for other 
> bidirectional, non ecp applications).  Still can't use the 
> newer system with IAR or OCDCommander - it doesn't even 
> recognize the wiggler.  At least I know the jtag hardware works.
> 
> So Rowley works like a dream - I can connect via the wiggler, 
> I can download and I can set hardware breakpoints and debug 
> from flash in it.  Goes back to the old price problem for 
> hobbyists.  Maybe they'll sell me an academic licence.  

We have considered a low-cost Hobbyist license, but this opens us up to
abuse of our licensing terms.  I also have the very real concern that
this would be perceived as a "Well, they must be in trouble, trying to
squeeze the hobbyist market to make ends meet..."  Introl introduced
hobbyist licenses just before they went south for winter and stayed
there.  I would really need to be persuaded that a hobbyist license is a
viable product.

> The other problem is that there are many fewer examples.

Pardon?  We support a wider range of boards than IAR do with examples
for each one of them.  In the v1.6 release it will be even wider.

> There's 
> no complete set of header files and examples for the olimex 
> 2129 proto board like there are in IAR.

What specific example does IAR provide in the EW package for the
E2124/9?  We supply header files for the LPC2129.  The LPC-E2124/9 has a
port of uIP that I did on our website.

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and now MAXQ processors

Re: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Simon Bosworth

Paul,
could you do a 'reduced speed' version at a lower price? Just a thought.

Cheers,
Simon
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: Paul Curtis 
  To: lpc2000@yahoogroups.com 
  Sent: Thursday, November 24, 2005 2:34 PM
  Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board


  Hi, 

  > Yes - I went back to the original modern laptop and it works 
  > with Rowley!  Must've had something off on the parallel port 
  > on the older system (though I can use it for other 
  > bidirectional, non ecp applications).  Still can't use the 
  > newer system with IAR or OCDCommander - it doesn't even 
  > recognize the wiggler.  At least I know the jtag hardware works.
  > 
  > So Rowley works like a dream - I can connect via the wiggler, 
  > I can download and I can set hardware breakpoints and debug 
  > from flash in it.  Goes back to the old price problem for 
  > hobbyists.  Maybe they'll sell me an academic licence.  

  We have considered a low-cost Hobbyist license, but this opens us up to
  abuse of our licensing terms.  I also have the very real concern that
  this would be perceived as a "Well, they must be in trouble, trying to
  squeeze the hobbyist market to make ends meet..."  Introl introduced
  hobbyist licenses just before they went south for winter and stayed
  there.  I would really need to be persuaded that a hobbyist license is a
  viable product.

  > The other problem is that there are many fewer examples.

  Pardon?  We support a wider range of boards than IAR do with examples
  for each one of them.  In the v1.6 release it will be even wider.

  > There's 
  > no complete set of header files and examples for the olimex 
  > 2129 proto board like there are in IAR.

  What specific example does IAR provide in the EW package for the
  E2124/9?  We supply header files for the LPC2129.  The LPC-E2124/9 has a
  port of uIP that I did on our website.

  --
  Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
  CrossWorks for MSP430, ARM, AVR and now MAXQ processors


  SPONSORED LINKS Microprocessor  Microcontrollers  Pic microcontrollers  
        8051 microprocessor  


------------------------------------------------------------------------------
  YAHOO! GROUPS LINKS 

    a..  Visit your group "lpc2000" on the web.
      
    b..  To unsubscribe from this group, send an email to:
     lpc2000-unsubscribe@yahoogroups.com
      
    c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


------------------------------------------------------------------------------



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

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Joel Winarske

Hi Paul,

> What specific example does IAR provide in the EW package for the
> E2124/9?  We supply header files for the LPC2129.  The LPC-E2124/9 has a
> port of uIP that I did on our website.

LPC2K support in IAR EW-ARM v4.30A Kickstart

Headers:
06/20/2005  08:24 PM            34,751 iolpc210x.h
06/20/2005  08:24 PM            40,067 iolpc210x_old.h
06/20/2005  08:24 PM            38,446 iolpc2114.h
06/20/2005  08:24 PM            49,970 iolpc2119.h
06/20/2005  08:24 PM            38,447 iolpc2124.h
08/29/2005  09:46 AM            49,788 iolpc2129.h
06/20/2005  08:24 PM            44,208 iolpc2130.h
06/20/2005  08:24 PM            37,931 iolpc2131.h
06/20/2005  08:24 PM            41,067 iolpc2132.h
06/20/2005  08:24 PM            41,067 iolpc2134.h
06/20/2005  08:24 PM            41,067 iolpc2136.h
06/20/2005  08:24 PM            41,108 iolpc2138.h
06/20/2005  07:50 AM               475 iolpc2142.h
11/08/2005  03:45 PM            50,903 iolpc2148.h
06/20/2005  08:24 PM            53,066 iolpc2194.h
06/20/2005  08:24 PM            42,699 iolpc2212.h
06/20/2005  08:24 PM            42,699 iolpc2214.h
06/20/2005  08:24 PM            53,497 iolpc2292.h
06/20/2005  08:24 PM            56,598 iolpc2294.h

Examples:
08/14/2005  12:58 PM    <DIR>          LPC210x
10/16/2005  11:57 AM    <DIR>          LPC212x
08/14/2005  12:58 PM    <DIR>          LPC213x
08/14/2005  12:58 PM    <DIR>          LPC214x
08/14/2005  12:58 PM    <DIR>          LPC22xx

Joel

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Paul Curtis

Hi Joel,

That isn't an *example*, that's just a set of header files.

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and now MAXQ processors 
Show quoted textHide quoted text
> -----Original Message-----
> From: Joel Winarske [mailto:joelw@...] 
> Sent: 24 November 2005 21:10
> To: lpc2000@yahoogroups.com
> Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag 
> and olimex lpc2129 proto board
> 
> Hi Paul,
> 
> > What specific example does IAR provide in the EW package for the
> > E2124/9?  We supply header files for the LPC2129.  The 
> LPC-E2124/9 has a
> > port of uIP that I did on our website.
> 
> LPC2K support in IAR EW-ARM v4.30A Kickstart
> 
> Headers:
> 06/20/2005  08:24 PM            34,751 iolpc210x.h
> 06/20/2005  08:24 PM            40,067 iolpc210x_old.h
> 06/20/2005  08:24 PM            38,446 iolpc2114.h
> 06/20/2005  08:24 PM            49,970 iolpc2119.h
> 06/20/2005  08:24 PM            38,447 iolpc2124.h
> 08/29/2005  09:46 AM            49,788 iolpc2129.h
> 06/20/2005  08:24 PM            44,208 iolpc2130.h
> 06/20/2005  08:24 PM            37,931 iolpc2131.h
> 06/20/2005  08:24 PM            41,067 iolpc2132.h
> 06/20/2005  08:24 PM            41,067 iolpc2134.h
> 06/20/2005  08:24 PM            41,067 iolpc2136.h
> 06/20/2005  08:24 PM            41,108 iolpc2138.h
> 06/20/2005  07:50 AM               475 iolpc2142.h
> 11/08/2005  03:45 PM            50,903 iolpc2148.h
> 06/20/2005  08:24 PM            53,066 iolpc2194.h
> 06/20/2005  08:24 PM            42,699 iolpc2212.h
> 06/20/2005  08:24 PM            42,699 iolpc2214.h
> 06/20/2005  08:24 PM            53,497 iolpc2292.h
> 06/20/2005  08:24 PM            56,598 iolpc2294.h
> 
> Examples:
> 08/14/2005  12:58 PM    <DIR>          LPC210x
> 10/16/2005  11:57 AM    <DIR>          LPC212x
> 08/14/2005  12:58 PM    <DIR>          LPC213x
> 08/14/2005  12:58 PM    <DIR>          LPC214x
> 08/14/2005  12:58 PM    <DIR>          LPC22xx
> 
> Joel
> 
> 
> 
> 
> ------------------------ Yahoo! Groups Sponsor 
> --------------------~--> 
> 1.2 million kids a year are victims of human trafficking. 
> Stop slavery.
> http://us.click.yahoo.com/WpTY2A/izNLAA/yQLSAA/dN_tlB/TM
> --------------------------------------------------------------
> ------~-> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 
>

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Paul Curtis

Simon, 

> Paul,
> could you do a 'reduced speed' version at a lower price? Just 
> a thought.

That doesn't really address the root problems of the Hobbyist License.
Our Educational License software is identical to the Commercial License
software, only difference being the use that is made of it.

We have given a number of licenses to worthy users absolutely free of
charge so they can pursue projects that may or may not make money--on
the understanding that if the project starts coining it, then a license
is purchased.  This has worked well for us.  But this is different from
the Hobbyist License which is just a "I want to tinker" license.

I would like to help hobbyists, for sure, as we have done for university
and research work with our very generous educational discounts (they are
just 20% of our commercial prices).  The educational licenses have been
very popular, being taken up by a wide range of universities and
research institutes around the world.

The problems are as I stated, a hobbyist license is open to abuse by
companies masquerading as hobbyists and also the perception of squeezing
the last drop of money out of our customer base by offering hobbyists
licenses to prop up sales.  I can't see how to resolve the hobbyist
license other than by having the hobbyist sign a document (as CadSoft do
for example). And we don't need revenue from hobbyists because
CrossWorks is successful enough on its own.

We have had endless conversations about the hobbyist license here and
although I'd like to be philanthropic and introduce such a license, the
last throes of Introl hoping hobbyists would help prop up the company is
strongly implanted in my mind.

So, tell me how can I be persuaded on this?  My leaning would be to
introduce a hypothetical "hobbyist license" at, say, £99 and require the
user to sign an undertaking of no commercial use.  However, I really do
need to be convinced that this is a good thing...

Regards,

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and now MAXQ processors
Show quoted textHide quoted text
> 
>   Hi, 
> 
>   > Yes - I went back to the original modern laptop and it works 
>   > with Rowley!  Must've had something off on the parallel port 
>   > on the older system (though I can use it for other 
>   > bidirectional, non ecp applications).  Still can't use the 
>   > newer system with IAR or OCDCommander - it doesn't even 
>   > recognize the wiggler.  At least I know the jtag hardware works.
>   > 
>   > So Rowley works like a dream - I can connect via the wiggler, 
>   > I can download and I can set hardware breakpoints and debug 
>   > from flash in it.  Goes back to the old price problem for 
>   > hobbyists.  Maybe they'll sell me an academic licence.  
> 
>   We have considered a low-cost Hobbyist license, but this 
> opens us up to
>   abuse of our licensing terms.  I also have the very real 
> concern that
>   this would be perceived as a "Well, they must be in 
> trouble, trying to
>   squeeze the hobbyist market to make ends meet..."  Introl introduced
>   hobbyist licenses just before they went south for winter and stayed
>   there.  I would really need to be persuaded that a hobbyist 
> license is a
>   viable product.
> 
>   > The other problem is that there are many fewer examples.
> 
>   Pardon?  We support a wider range of boards than IAR do 
> with examples
>   for each one of them.  In the v1.6 release it will be even wider.
> 
>   > There's 
>   > no complete set of header files and examples for the olimex 
>   > 2129 proto board like there are in IAR.
> 
>   What specific example does IAR provide in the EW package for the
>   E2124/9?  We supply header files for the LPC2129.  The 
> LPC-E2124/9 has a
>   port of uIP that I did on our website.
> 
>   --
>   Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
>   CrossWorks for MSP430, ARM, AVR and now MAXQ processors
> 
> 
>   SPONSORED LINKS Microprocessor  Microcontrollers  Pic 
> microcontrollers  
>         8051 microprocessor  
> 
> 
> --------------------------------------------------------------
> ----------------
>   YAHOO! GROUPS LINKS 
> 
>     a..  Visit your group "lpc2000" on the web.
>       
>     b..  To unsubscribe from this group, send an email to:
>      lpc2000-unsubscribe@yahoogroups.com
>       
>     c..  Your use of Yahoo! Groups is subject to the Yahoo! 
> Terms of Service. 
> 
> 
> --------------------------------------------------------------
> ----------------
> 
> 
> 
> [Non-text portions of this message have been removed]
> 
> 
> 
> ------------------------ Yahoo! Groups Sponsor 
> --------------------~--> 
> Get fast access to your favorite Yahoo! Groups. Make Yahoo! 
> your home page
> http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/dN_tlB/TM
> --------------------------------------------------------------
> ------~-> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 
>

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Paul Curtis

Hi Joel, 

> Ah yes.  I'm too quick with the fingers and not quick enough 
> in the head
> sometimes. IAR has no example for the the LPC-E2124.  Your link is
> prominently displayed on olimex.com for the LPC-E2124 product.
> 
> What sort of through put are you able to sustain with your 
> code on this board?

Good question, never bothered to test it.  Note that uIP has some
restrictions and doesn't interoperate well with delayed-ACK
implementations as uIP can only have a single segment in flight at any
one time.  If you don't understand this implication, you'll need to have
a look at a good book on Internet protocols or the RFCs.

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and now MAXQ processors

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Joel Winarske

Hi Paul,

Ah yes.  I'm too quick with the fingers and not quick enough in the head
sometimes. IAR has no example for the the LPC-E2124.  Your link is
prominently displayed on olimex.com for the LPC-E2124 product.

What sort of through put are you able to sustain with your code on this
board?

Joel

Re: Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by rtstofer

> So, tell me how can I be persuaded on this?  My leaning would be to
> introduce a hypothetical "hobbyist license" at, say, £99 and 
require the
> user to sign an undertaking of no commercial use.  However, I 
really do
> need to be convinced that this is a good thing...
> 
> Regards,
> 
> --
> Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
> CrossWorks for MSP430, ARM, AVR and now MAXQ processors

From a business point of view, a larger user base is a good thing; 
any level of user.  Hobbyists probably break down into two 
categories:  those who are working in industry in a different but 
vaguely related field and may someday develop commercial 
applications with the software and those, like me, who are retired 
or working in an unrelated field and will never contribute to your 
profits.

I don't see how it would make sense to provide a hobbyist license to 
those who will never develop commercial applications.  But, if you 
do, sign me up!

Richard

Re: Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-25 by compuguru64

I can only speak for myself.  I'm a professional programmer of 
vertical business applications.  I also consider myself a perpetual 
student.  My hobby is robotics and I take it seriously.  I consider 
the hobby to be preparation for an alternate career path.  If 
personal robotics ever takes off enough and can support more people 
in the field, then I would be happy to make a career move.  At that 
point I would be happy to pay for the professional tools needed.  In 
the meantime I'm always a student, even if I'm only sporadically 
taking courses at community college to refresh atrophied skills like 
linear algebra (for vision processing).

So I guess I'm saying that I don't see much of a neccessary 
difference between intense hobby and more formal student activities 
(regarding learning intent - I'm not talking about business 
models).  Not everyone into hobbies is retired.  I'm a member of the 
Dallas Personal Robotics Group, and only a couple of the guys in 
that group are retired.  The rest are like me - eager to learn, 
possibly in preparation for a career move, or otherwise hoping to 
hit on a commercial angle.  If I got lucky and built something with 
commercial potential I'd be happy to opt into a full commercial 
license for the tools I'm using.


--- In lpc2000@yahoogroups.com, "rtstofer" <rstofer@p...> wrote:
>
> 
> > So, tell me how can I be persuaded on this?  My leaning would be 
to
> > introduce a hypothetical "hobbyist license" at, say, £99 and 
> require the
> > user to sign an undertaking of no commercial use.  However, I 
> really do
> > need to be convinced that this is a good thing...
> > 
> > Regards,
> > 
> > --
> > Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
> > CrossWorks for MSP430, ARM, AVR and now MAXQ processors
> 
> From a business point of view, a larger user base is a good thing; 
> any level of user.  Hobbyists probably break down into two 
> categories:  those who are working in industry in a different but 
> vaguely related field and may someday develop commercial 
> applications with the software and those, like me, who are retired 
> or working in an unrelated field and will never contribute to your 
> profits.
> 
> I don't see how it would make sense to provide a hobbyist license 
to 
Show quoted textHide quoted text
> those who will never develop commercial applications.  But, if you 
> do, sign me up!
> 
> Richard
>

RE: [lpc2000] Re: Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-25 by Paul Curtis

This is the sort of feedback that is useful.  I think we've been very
good in providing free licenses and (in some cases) hardware to many
users for their use--but we don't shout about it.  I may actually put a
page up on the website with the more interesting projects we have
supported, but we have sent more keys to "intense hobbyists" that have
the front to contact us directly.  I'm getting soft... :-)

I *know* that I'd like to do something for hobbyists, but I'm really
unsure as to what the impression would be.  The current company policy
is to offer what *I* would like to see from a company if I used its
tools.  That is, we fix bugs free of charge because we made the mistake,
and we offer e-mail support that isn't limited because if users have
problems then it's a documentation issue or should be covered by a FAQ.

In the three years that we've been selling CrossWorks for MSP430, our
original users have never needed to pay for an upgrade.  However, I can
say now, that when v2 ships, there *will* be a small cost associated
with it because it's a major upgrade in function.

Sorry, I'm rambling.

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and now MAXQ processors
Show quoted textHide quoted text
> -----Original Message-----
> From: compuguru64 [mailto:karim@...] 
> Sent: 25 November 2005 00:24
> To: lpc2000@yahoogroups.com
> Subject: [lpc2000] Re: Problems with olimex (wiggler) jtag 
> and olimex lpc2129 proto board
> 
> I can only speak for myself.  I'm a professional programmer of 
> vertical business applications.  I also consider myself a perpetual 
> student.  My hobby is robotics and I take it seriously.  I consider 
> the hobby to be preparation for an alternate career path.  If 
> personal robotics ever takes off enough and can support more people 
> in the field, then I would be happy to make a career move.  At that 
> point I would be happy to pay for the professional tools needed.  In 
> the meantime I'm always a student, even if I'm only sporadically 
> taking courses at community college to refresh atrophied skills like 
> linear algebra (for vision processing).
> 
> So I guess I'm saying that I don't see much of a neccessary 
> difference between intense hobby and more formal student activities 
> (regarding learning intent - I'm not talking about business 
> models).  Not everyone into hobbies is retired.  I'm a member of the 
> Dallas Personal Robotics Group, and only a couple of the guys in 
> that group are retired.  The rest are like me - eager to learn, 
> possibly in preparation for a career move, or otherwise hoping to 
> hit on a commercial angle.  If I got lucky and built something with 
> commercial potential I'd be happy to opt into a full commercial 
> license for the tools I'm using.

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-25 by Joel Winarske

> > What sort of through put are you able to sustain with your
> > code on this board?
> 
> Good question, never bothered to test it.  Note that uIP has some
> restrictions and doesn't interoperate well with delayed-ACK
> implementations as uIP can only have a single segment in flight at any
> one time.  If you don't understand this implication, you'll need to have
> a look at a good book on Internet protocols or the RFCs.

Yes, yes I'm aware of all the latter.  I'm just looking for a rough unit of
measure; To determine if it might be applicable in a commercial product.
Perhaps it's a better fit for the hobby market?


Joel

RE: [lpc2000] Re: Problems with olimex (wiggler) jtag and olimex lpc2129 proto b

2005-11-25 by Michael Rubitschka

Hi Paul

I think your free licences requests will explode after this email ;-)
I am also thinking to take heart to send one.

Cheers
Michael
Show quoted textHide quoted text
>From: "Paul Curtis" <plc@...>
>Reply-To: lpc2000@yahoogroups.com
>To: <lpc2000@yahoogroups.com>
>Subject: RE: [lpc2000] Re: Problems with olimex (wiggler) jtag and olimex 
>lpc2129 proto board
>Date: Fri, 25 Nov 2005 00:31:52 -0000
>
>This is the sort of feedback that is useful.  I think we've been very
>good in providing free licenses and (in some cases) hardware to many
>users for their use--but we don't shout about it.  I may actually put a
>page up on the website with the more interesting projects we have
>supported, but we have sent more keys to "intense hobbyists" that have
>the front to contact us directly.  I'm getting soft... :-)
>
>I *know* that I'd like to do something for hobbyists, but I'm really
>unsure as to what the impression would be.  The current company policy
>is to offer what *I* would like to see from a company if I used its
>tools.  That is, we fix bugs free of charge because we made the mistake,
>and we offer e-mail support that isn't limited because if users have
>problems then it's a documentation issue or should be covered by a FAQ.
>
>In the three years that we've been selling CrossWorks for MSP430, our
>original users have never needed to pay for an upgrade.  However, I can
>say now, that when v2 ships, there *will* be a small cost associated
>with it because it's a major upgrade in function.
>
>Sorry, I'm rambling.
>
>--
>Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
>CrossWorks for MSP430, ARM, AVR and now MAXQ processors
>
> > -----Original Message-----
> > From: compuguru64 [mailto:karim@...]
> > Sent: 25 November 2005 00:24
> > To: lpc2000@yahoogroups.com
> > Subject: [lpc2000] Re: Problems with olimex (wiggler) jtag
> > and olimex lpc2129 proto board
> >
> > I can only speak for myself.  I'm a professional programmer of
> > vertical business applications.  I also consider myself a perpetual
> > student.  My hobby is robotics and I take it seriously.  I consider
> > the hobby to be preparation for an alternate career path.  If
> > personal robotics ever takes off enough and can support more people
> > in the field, then I would be happy to make a career move.  At that
> > point I would be happy to pay for the professional tools needed.  In
> > the meantime I'm always a student, even if I'm only sporadically
> > taking courses at community college to refresh atrophied skills like
> > linear algebra (for vision processing).
> >
> > So I guess I'm saying that I don't see much of a neccessary
> > difference between intense hobby and more formal student activities
> > (regarding learning intent - I'm not talking about business
> > models).  Not everyone into hobbies is retired.  I'm a member of the
> > Dallas Personal Robotics Group, and only a couple of the guys in
> > that group are retired.  The rest are like me - eager to learn,
> > possibly in preparation for a career move, or otherwise hoping to
> > hit on a commercial angle.  If I got lucky and built something with
> > commercial potential I'd be happy to opt into a full commercial
> > license for the tools I'm using.
>

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-25 by Paul Curtis

Joel, 

> > > What sort of through put are you able to sustain with your
> > > code on this board?
> > 
> > Good question, never bothered to test it.  Note that uIP has some
> > restrictions and doesn't interoperate well with delayed-ACK
> > implementations as uIP can only have a single segment in 
> flight at any
> > one time.  If you don't understand this implication, you'll 
> need to have
> > a look at a good book on Internet protocols or the RFCs.
> 
> Yes, yes I'm aware of all the latter.  I'm just looking for a 
> rough unit of
> measure; To determine if it might be applicable in a 
> commercial product.
> Perhaps it's a better fit for the hobby market?

I believe uIP is now used in a number of commercial products and I'd say
that it isn't just for a hobby market.  I have uIP running on an EDTP
AirDrop-A with a WiFi driver I wrote and integrated into uIP so I can
telnet into the AVR wirelessly and run my NetBASIC interpreter on it.

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and now MAXQ processors

OT: Aidrop

2005-11-25 by Michael Rubitschka

Paul

Is it possible to run Airdrop (after some modifications) on an SD Wlan card?
Adrop has a top priority on my to do list, but I don't like compact flash 
cards.
A SD card is so much easier to work with.

Cheers
Michael
Show quoted textHide quoted text
>From: "Paul Curtis" <plc@...>
>Reply-To: lpc2000@yahoogroups.com
>To: <lpc2000@yahoogroups.com>
>Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex 
>lpc2129 proto board
>Date: Fri, 25 Nov 2005 10:52:13 -0000

>I believe uIP is now used in a number of commercial products and I'd say
>that it isn't just for a hobby market.  I have uIP running on an EDTP
>AirDrop-A with a WiFi driver I wrote and integrated into uIP so I can
>telnet into the AVR wirelessly and run my NetBASIC interpreter on it.
>
>--
>Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
>CrossWorks for MSP430, ARM, AVR and now MAXQ processors

RE: [lpc2000] OT: Aidrop

2005-11-25 by Paul Curtis

Michael, 

> Is it possible to run Airdrop (after some modifications) on 
> an SD Wlan card?

I'm sure it is.  If you are a member of the AirDrop Yahoo! hroup, then
you'll have seen that some people are working on using SDIO.  The
AirDrop itself doesn't have an SD connector, so that hardware platform
is not likely to help you.

> Adrop has a top priority on my to do list, but I don't like 
> compact flash cards. A SD card is so much easier to work with.

The WiFi adapters that are readily available are all SDIO as far as I
can tell.  There was some e-mails on the AirDrop group about
publicly-available information on SD/SDIO.  However, concensus was that
you'd probably need to stump up the cash to become a member of the SDIO
club.  I'm not sure how far that will get you because the SDIO interface
is one thing, the way to access the chipset/firmware is another which
may require vendor support.

The nice thing about the CF cards available is they all use one or other
of the two available chipsets, and a lot of work has been put into the
AirDrop PRISM drivers by quite a number of people, so that does work.

Regards,

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and now MAXQ processors

[lpc2000] Low power RTOS or "normal" program only with interrupts?

2005-11-25 by Marko Pavlin (home)

I am looking for (RT)OS for LPC210x for wireless sensor. Sensor itself 
runs for less than 1% of all time. It should be in powerdown mode during 
the remaining 99% of  time. Is it possible to run RTOS in such way that 
idle process switch the power-down mode after no task is active for some 
time? Wakeup would be via external interrupt or RTC.

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-26 by Karim Virani

Paul,

>However, I really do need to be convinced that this is a good thing...

OK, let me try.  You've expressed a number of concerns:

1. Abuse mitigation
2. Perception management
3. The business case

Regarding abuse mitigation - I think hobbyists would be happy to sign a document promising to upgrade to a commercial license if their use of the product led in a for-profit direction.  I would.  It might, however, be costly to administer.  You could also require proof of membership in an established hobby group.  The Dallas Personal Robotics Group (autonomous, not remote control oriented robots) has a membership page on their website - http://www.dprg.org/members.html.  Most established groups have a similar way to verify membership as it's not new to offer discounts to club members.  This approach would, however, lock out some legitimate but unaffiliated intense hobbyists.  But we can't complain if that's the route you take.

Regarding perception management.  I don't think it's a big issue.  Your own perception of Introl seems mostly due to your knowledge of their failure and that the move was a desperation measure.  It was particularly desperate if they were needing to get real immediate revenue from the hobby market - it just isn't there.  In your case, it's known that crossworks is doing well.  If you decide to support the hobbyist market, it'll be seen as a sign of strength, you can commit to a move that has insignificant immediate benefit, but could have a longer term payoff.  You can afford to invest in good will.

Regarding the business case.  I'd think of it as developing long-term market potential and brand recognition more than direct revenue.  In the robot hobbyist culture, folks can't afford traditional high-end development environments, much as we desire them.  In fact, the availability of a suitable development environment is the most restrictive factor in moving to newer microcontrollers like the ARM family.  I'm certain that 32bit microcontrollers have many advantages over the PICs and AVRs most used for autonomous robots, and I'm eager to lead us in that direction.  If DPRG had a couple of licenses for use in our lab (we have a dedicated warehouse with a number of machines for programming where members meet at least weekly), then more folks would become aware of the possibilities.  But they'd still need access to the discussed hobbyist license so they could take their work home and really commit to the switch.  Some will still go the gnuarm route either for a totally free solution or because of open-source religion, but most of us would be drooling to use a truly professional environment. 

Regarding potential.  Many of these folks will remain hobbyists, but some will move on to become professionals in the field.  It's happened many times at DPRG.  We have about 60 members right now, but hundreds more worldwide participate on our list.  Seattle Robotics is even bigger and there are numerous other significant groups in this one hobby alone.  A very large percentage of us are programmers or electrical engineers.  It wouldn't hurt to develop a reputation among this crowd.  And ultimately it will lead to commercial conversion sales.  Possibly at a similar rate that your educational license does.  It'll also lead to a larger base of shared code examples written for your environment.  It's an investment in momentum.

It's also reasonable to expect that you might limit costs by limiting support (telephone and email - something worth paying for in for-profit settings) for this license.  I'd still hope that you would offer free minor version upgrades and forum-based support.  I'd also suggest targeting $99 US as the price tag - 3 figures throw up a real mental block for most hobbyists.  These individuals are not in the same category as educational institutions.

So that's my spiel. Best wishes,

Karim Virani
Show quoted textHide quoted text
-----Original Message-----
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
Of Paul Curtis
Sent: Thursday, November 24, 2005 3:41 PM
To: lpc2000@yahoogroups.com
Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board


Simon, 

> Paul,
> could you do a 'reduced speed' version at a lower price? Just 
> a thought.

That doesn't really address the root problems of the Hobbyist License.
Our Educational License software is identical to the Commercial License
software, only difference being the use that is made of it.

We have given a number of licenses to worthy users absolutely free of
charge so they can pursue projects that may or may not make money--on
the understanding that if the project starts coining it, then a license
is purchased.  This has worked well for us.  But this is different from
the Hobbyist License which is just a "I want to tinker" license.

I would like to help hobbyists, for sure, as we have done for university
and research work with our very generous educational discounts (they are
just 20% of our commercial prices).  The educational licenses have been
very popular, being taken up by a wide range of universities and
research institutes around the world.

The problems are as I stated, a hobbyist license is open to abuse by
companies masquerading as hobbyists and also the perception of squeezing
the last drop of money out of our customer base by offering hobbyists
licenses to prop up sales.  I can't see how to resolve the hobbyist
license other than by having the hobbyist sign a document (as CadSoft do
for example). And we don't need revenue from hobbyists because
CrossWorks is successful enough on its own.

We have had endless conversations about the hobbyist license here and
although I'd like to be philanthropic and introduce such a license, the
last throes of Introl hoping hobbyists would help prop up the company is
strongly implanted in my mind.

So, tell me how can I be persuaded on this?  My leaning would be to
introduce a hypothetical "hobbyist license" at, say, £99 and require the
user to sign an undertaking of no commercial use.  However, I really do
need to be convinced that this is a good thing...

Regards,

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and now MAXQ processors

> 
>   Hi, 
> 
>   > Yes - I went back to the original modern laptop and it works 
>   > with Rowley!  Must've had something off on the parallel port 
>   > on the older system (though I can use it for other 
>   > bidirectional, non ecp applications).  Still can't use the 
>   > newer system with IAR or OCDCommander - it doesn't even 
>   > recognize the wiggler.  At least I know the jtag hardware works.
>   > 
>   > So Rowley works like a dream - I can connect via the wiggler, 
>   > I can download and I can set hardware breakpoints and debug 
>   > from flash in it.  Goes back to the old price problem for 
>   > hobbyists.  Maybe they'll sell me an academic licence.  
> 
>   We have considered a low-cost Hobbyist license, but this 
> opens us up to
>   abuse of our licensing terms.  I also have the very real 
> concern that
>   this would be perceived as a "Well, they must be in 
> trouble, trying to
>   squeeze the hobbyist market to make ends meet..."  Introl introduced
>   hobbyist licenses just before they went south for winter and stayed
>   there.  I would really need to be persuaded that a hobbyist 
> license is a
>   viable product.
> 
>   > The other problem is that there are many fewer examples.
> 
>   Pardon?  We support a wider range of boards than IAR do 
> with examples
>   for each one of them.  In the v1.6 release it will be even wider.
> 
>   > There's 
>   > no complete set of header files and examples for the olimex 
>   > 2129 proto board like there are in IAR.
> 
>   What specific example does IAR provide in the EW package for the
>   E2124/9?  We supply header files for the LPC2129.  The 
> LPC-E2124/9 has a
>   port of uIP that I did on our website.
> 
>   --
>   Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
>   CrossWorks for MSP430, ARM, AVR and now MAXQ processors
> 
> 
>   SPONSORED LINKS Microprocessor  Microcontrollers  Pic 
> microcontrollers  
>         8051 microprocessor  
> 
> 
> --------------------------------------------------------------
> ----------------
>   YAHOO! GROUPS LINKS 
> 
>     a..  Visit your group "lpc2000" on the web.
>       
>     b..  To unsubscribe from this group, send an email to:
>      lpc2000-unsubscribe@yahoogroups.com
>       
>     c..  Your use of Yahoo! Groups is subject to the Yahoo! 
> Terms of Service. 
> 
> 
> --------------------------------------------------------------
> ----------------
> 
> 
> 
> [Non-text portions of this message have been removed]
> 
> 
> 
> ------------------------ Yahoo! Groups Sponsor 
> --------------------~--> 
> Get fast access to your favorite Yahoo! Groups. Make Yahoo! 
> your home page
> http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/dN_tlB/TM
> --------------------------------------------------------------
> ------~-> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 
> 



 
Yahoo! Groups Links



 




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

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.