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
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
>
Problems with olimex (wiggler) jtag and olimex lpc2129 proto board
Started by ●November 22, 2005
Reply by ●November 22, 20052005-11-22
Reply by ●November 22, 20052005-11-22
> 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
> 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
Reply by ●November 23, 20052005-11-23
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@lpc2... [mailto:lpc2000@lpc2...]On Behalf
Of Joel Winarske
Sent: Tuesday, November 22, 2005 11:50 AM
To: lpc2000@lpc2...
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
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@lpc2... [mailto:lpc2000@lpc2...]On Behalf
Of Joel Winarske
Sent: Tuesday, November 22, 2005 11:50 AM
To: lpc2000@lpc2...
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
Reply by ●November 23, 20052005-11-23
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@lpc2... [mailto:lpc2000@lpc2...] On Behalf
Of Karim Virani
Sent: Wednesday, November 23, 2005 5:21 PM
To: lpc2000@lpc2...
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@lpc2... [mailto:lpc2000@lpc2...]On Behalf
Of Joel Winarske
Sent: Tuesday, November 22, 2005 11:50 AM
To: lpc2000@lpc2...
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
> .
_____
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@lpc2... [mailto:lpc2000@lpc2...] On Behalf
Of Karim Virani
Sent: Wednesday, November 23, 2005 5:21 PM
To: lpc2000@lpc2...
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@lpc2... [mailto:lpc2000@lpc2...]On Behalf
Of Joel Winarske
Sent: Tuesday, November 22, 2005 11:50 AM
To: lpc2000@lpc2...
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
> .
_____
Reply by ●November 23, 20052005-11-23
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
-----Original Message-----
From: lpc2000@lpc2... [mailto:lpc2000@lpc2...]On Behalf
Of Dan Beadle
Sent: Wednesday, November 23, 2005 7:24 PM
To: lpc2000@lpc2...
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@lpc2... [mailto:lpc2000@lpc2...] On Behalf
Of Karim Virani
Sent: Wednesday, November 23, 2005 5:21 PM
To: lpc2000@lpc2...
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@lpc2... [mailto:lpc2000@lpc2...]On Behalf
Of Joel Winarske
Sent: Tuesday, November 22, 2005 11:50 AM
To: lpc2000@lpc2...
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
open. I tried the other board - same response. I think I got a bum
wiggler.
Karim
-----Original Message-----
From: lpc2000@lpc2... [mailto:lpc2000@lpc2...]On Behalf
Of Dan Beadle
Sent: Wednesday, November 23, 2005 7:24 PM
To: lpc2000@lpc2...
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@lpc2... [mailto:lpc2000@lpc2...] On Behalf
Of Karim Virani
Sent: Wednesday, November 23, 2005 5:21 PM
To: lpc2000@lpc2...
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@lpc2... [mailto:lpc2000@lpc2...]On Behalf
Of Joel Winarske
Sent: Tuesday, November 22, 2005 11:50 AM
To: lpc2000@lpc2...
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
Reply by ●November 24, 20052005-11-24
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@lpc2... [mailto:lpc2000@lpc2...]On Behalf
>Of Joel Winarske
>Sent: Tuesday, November 22, 2005 11:50 AM
>To: lpc2000@lpc2...
>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
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@lpc2... [mailto:lpc2000@lpc2...]On Behalf
>Of Joel Winarske
>Sent: Tuesday, November 22, 2005 11:50 AM
>To: lpc2000@lpc2...
>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
Reply by ●November 24, 20052005-11-24
----- Original Message -----
From: "Michael Johnson" <mpj@mpj@...>
To: <lpc2000@lpc2...>
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. ]
From: "Michael Johnson" <mpj@mpj@...>
To: <lpc2000@lpc2...>
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. ]
Reply by ●November 24, 20052005-11-24
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
-----Original Message-----
From: lpc2000@lpc2... [mailto:lpc2000@lpc2...]On Behalf
Of Michael Johnson
Sent: Thursday, November 24, 2005 12:59 AM
To: lpc2000@lpc2...
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@lpc2... [mailto:lpc2000@lpc2...]On Behalf
>Of Joel Winarske
>Sent: Tuesday, November 22, 2005 11:50 AM
>To: lpc2000@lpc2...
>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
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
-----Original Message-----
From: lpc2000@lpc2... [mailto:lpc2000@lpc2...]On Behalf
Of Michael Johnson
Sent: Thursday, November 24, 2005 12:59 AM
To: lpc2000@lpc2...
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@lpc2... [mailto:lpc2000@lpc2...]On Behalf
>Of Joel Winarske
>Sent: Tuesday, November 22, 2005 11:50 AM
>To: lpc2000@lpc2...
>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
Reply by ●November 24, 20052005-11-24
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
> 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
Reply by ●November 24, 20052005-11-24
Paul,
could you do a 'reduced speed' version at a lower price? Just a thought.
Cheers,
Simon
----- Original Message -----
From: Paul Curtis
To: lpc2000@lpc2...
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.. ------
could you do a 'reduced speed' version at a lower price? Just a thought.
Cheers,
Simon
----- Original Message -----
From: Paul Curtis
To: lpc2000@lpc2...
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.. ------