|
I worked with the Ashling tools too. Consider them if you need a good hardware board. But their debugger constantly runs into a "no more hardware resources - free hardware resources" issue when stepping through code without explaining what resource is missing or how to free resources (sigh). This may be related to the single hardware breakpoint problem. This makes debugging a bit annoying. It's easier to do your debugging using Keil's simulator, or Printf style debugging. Another problem with the Ashling tools is the integrated Flash download. it doesen't work well and used to be quite slow, so we resorted to use the Philips provided ISP tool again. |
|
|
Choosing an IDE for the LPC2114
Started by ●March 14, 2004
Reply by ●March 15, 20042004-03-15
Reply by ●March 16, 20042004-03-16
|
--- In , "golssa" <golssa@y...> wrote: > I worked with the Ashling tools too. > > Consider them if you need a good hardware board. > > But their debugger constantly runs into a "no more hardware > resources - free hardware resources" issue when stepping through code > without explaining what resource is missing or how to free resources > (sigh). This may be related to the single hardware breakpoint > problem. This makes debugging a bit annoying. It's easier to do your > debugging using Keil's simulator, or Printf style debugging. > > Another problem with the Ashling tools is the integrated Flash > download. it doesen't work well and used to be quite slow, so we > resorted to use the Philips provided ISP tool again. I'm a sucker for gcc + gdb/insight. I use this on both Winxx(with Cygwin) and Linux and have used these to deliver product. No gripes. This combo is not strickly an IDE... VIDE, which is a true IDE, http://www.objectcentral.com/, works with gcc/gdb All these tools are free to download and run on various hosts... |
Reply by ●March 16, 20042004-03-16
|
Message
Hi
Golssa,
I'm surprised about
your comments re:flash programming/debugging using Ashling tools. What
version of our tools are you using ? We completely rewrote our flash
programming algorithm in v112 (released in January) and now support programming
at > 12KB/s. Also, the EmbeddedICE only has two hardware breakpoints. If you
have a breakpoint set and then attempt to step there may
be certain situations where the debugger needs two breakpoints
(PathFinder attempts to complete the full step as an atomic operation).
PathFinder shows hardware breakpoints in the Source/Disa/Breakpoint dialog
as a small blue icon (software are shown in red); in this situation, you have to
clear the breakpoint you set. Contact me off line if you need details on
upgrading.
Of interest to
Ashling customers is that v113 will be available to all registered users for
download next week. This release adds flash support for all the new LPC
derivatives and support for code protection; in addition, our entry level kit
(for 295 euro) is now code size limited to 32KB (rather than previously been
limited to 60-days).
Hugh @ http://www.ashling.com/support/lpc2100/
|
|
|
Reply by ●March 16, 20042004-03-16
|
Hi Hugh, I used 1.07. Hopefully 1.13 will be improved. Will the upgrade (from 60-days to 32KBytes) be automatic for the entry level kit? --- In , "Hugh O'Keeffe" <hugh.okeeffe@a...> wrote: > Hi Golssa, > I'm surprised about your comments re:flash programming/debugging using > Ashling tools. What version of our tools are you using ? We completely > rewrote our flash programming algorithm in v112 (released in January) and > now support programming at > 12KB/s. Also, the EmbeddedICE only has two > hardware breakpoints. If you have a breakpoint set and then attempt to step > there may be certain situations where the debugger needs two breakpoints > (PathFinder attempts to complete the full step as an atomic operation). > PathFinder shows hardware breakpoints in the Source/Disa/Breakpoint dialog > as a small blue icon (software are shown in red); in this situation, you > have to clear the breakpoint you set. Contact me off line if you need > details on upgrading. > Of interest to Ashling customers is that v113 will be available to all > registered users for download next week. This release adds flash support for > all the new LPC derivatives and support for code protection; in addition, > our entry level kit (for 295 euro) is now code size limited to 32KB (rather > than previously been limited to 60-days). > > > Hugh @ <http://www.ashling.com/support/lpc2100/> > http://www.ashling.com/support/lpc2100/ > > -----Original Message----- > From: golssa [mailto:golssa@y...] > Sent: 15 March 2004 23:17 > To: > Subject: [lpc2000] Re: Choosing an IDE for the LPC2114 > I worked with the Ashling tools too. > > Consider them if you need a good hardware board. > > But their debugger constantly runs into a "no more hardware > resources - free hardware resources" issue when stepping through code > without explaining what resource is missing or how to free resources > (sigh). This may be related to the single hardware breakpoint > problem. This makes debugging a bit annoying. It's easier to do your > debugging using Keil's simulator, or Printf style debugging. > > Another problem with the Ashling tools is the integrated Flash > download. it doesen't work well and used to be quite slow, so we > resorted to use the Philips provided ISP tool again. > > _____ > > > . |
