Lpc2000

I hope that my introduction post did not demean Ashling in any way. 
That was not my intention. I tried to word it carefully to point out 
that Ashling dev kit wasn't working out for "our project". We ran 
into alot of problems with it. These problems go beyond what I would 
call normal 'new to platform, RTFM issues'. The eval timed out so 
often it actually affected what little time we have to develop with 
it. Instead of spending time learning, we spent hours reinstalling 
from scratch. Your offer for assistance is appreciated but, The last 
eval kit we bought is about to time out on us now. 

 Neither myself, nor my development partner do embedded work for a 
living. Unless I can figure out a way to convience my wife that the $ 
1500.00 I would spend on the full dev kit is justified, we are done 
messing with our eval kits. I am sure my attitude would be different 
if I did this kind of development professionally or the overall 
experience was better than it was.

 I would recommend to anyone interested in professional Arm7 
development to consider Ashling. Their eval kit has everything you 
need to get started and enough time to decide if the LPC2106 is right 
for your application. The Ashling Full dev kit is attractively priced 
for anyone intending to make a profit producing products with the 
Arm7.

 This brings me to the question for the group that I had about 
building our own GNU C toolset. I know I will miss the nice features 
we have enjoyed using both ASIDE (windows IDE) and Pathfinder (visual 
debugger). Still, I can give those features up if it means we can 
continue working on the project. Something is alot better than 
nothing at all. 

 Robert, I appreciate your offer to help me get started building a 
GCC-Arm7 toolset. With your permission, I can contact you by email. 
We have a prototype board layout finished, now I just need to be able 
to flash and debug to continue the project. Loading the code into RAM 
is nice because it is alot faster than flashing. Also, It doesn't 
restrict the number of breakpoints we can set for debugging. (one) 

 If you can point me in the right direction towards getting the GCC-
arm tools working, I would be greatful.

 shinji242 at yahoo dot com


--- In lpc2100@yahoogroups.com, "Hugh O'Keeffe" <hugh.okeeffe@a...> 
wrote:
> Hi Shinji,
>  
> Disappointed to hear of your problems with Ashling tools and that 
you
> are not happy with the support from Ashling. As manager of the
> development tools group in Ashling I want to address this 
immediately.
> Please let me know what your problems are and I will do my utmost to
> help.
>  
> Hugh @ http://www.ashling.com/support/lpc2100/