Which GCC Toolchain & debugging & extmem

Started by deunhido April 15, 2005


I just got an Olimex LPC-H2294 and have a few quesions.

First, which is the best GCC toolchain to use on Windows. So far, I've
found:

GNUARM:
gcc-3.4.3, insight-6.1 + newlib 1.12.0
http://www.gnuarm.com

Macraigor:
gcc 3.4.0, gdb, insight-6.1-macraigor + glibc
+ their own cygwin distro?
http://www.macraigor.com/full_gnu.htm

CodeSourcery:
gcc + newlib (in EABI or Legacy interfaces?)
new distro May 1 to include gdb & insight
http://www.codesourcery.com/gnu_toolchains/arm.html

What are the tradeoffs? I've heard you can't debug in flash with GNU
tools. I only have a USB cable now, do I need a Wiggler to debug? And
if I have to debug in SRAM how can I use external memory? I'd like to
have access to 1MB as 16K seems a bit tight...

Thanks,
Brian



An Engineer's Guide to the LPC2100 Series

At 10:15 AM 4/15/05 +0000, deunhido wrote:
>I just got an Olimex LPC-H2294 and have a few quesions.
>
>First, which is the best GCC toolchain to use on Windows. So far, I've
>found:

There is also WINARM >What are the tradeoffs? I've heard you can't debug in flash with GNU
>tools. I only have a USB cable now, do I need a Wiggler to debug? And
>if I have to debug in SRAM how can I use external memory? I'd like to
>have access to 1MB as 16K seems a bit tight...


You can debug in flash with the wiggler/GDB combination but it's like
stepping back in time a bit. there are only two breakpoints available and
you have to set them from the command line/monitor.

If the breakpoints were integrated (as the commercial products manage to
do) it would be easier.

Robert

" 'Freedom' has no meaning of itself. There are always restrictions, be
they legal, genetic, or physical. If you don't believe me, try to chew a
radio signal. " -- Kelvin Throop, III
http://www.aeolusdevelopment.com/


> if I have to debug in SRAM how can I use external memory? I'd like to
> have access to 1MB as 16K seems a bit tight...

You have to initialize the chipselect and maybe the pll from the debugger
before
downloaing (and also program MEMAP to map the vectors from external RAM).
I do not use gdb so I do not know the excact commands to do so.

--
42Bastian Schick



Robert Adsett wrote:
> At 10:15 AM 4/15/05 +0000, deunhido wrote:
>
>>I just got an Olimex LPC-H2294 and have a few quesions.
>>
>>First, which is the best GCC toolchain to use on Windows. So far, I've
>>found: > There is also WINARM

>>What are the tradeoffs? I've heard you can't debug in flash with GNU
>>tools. I only have a USB cable now, do I need a Wiggler to debug? And
>>if I have to debug in SRAM how can I use external memory? I'd like to
>>have access to 1MB as 16K seems a bit tight...>
>
> You can debug in flash with the wiggler/GDB combination but it's like
> stepping back in time a bit. there are only two breakpoints available and
> you have to set them from the command line/monitor.

Make that stepping back in time "a lot" :)
(Frankly this is worse than an F8 development system I've used ages
ago). I've been using Insight recently on a project and it is very
painful. OK setting the initial breakpoint is not too bad, but once you
get there and want to:
a) look at variables you have to flip back into SOURCE only mode as
MIXED mode (which you used to find the breakpoint hex address) doesn't
do variable observation. On my Insight this flipping is very slow.
b) You can only single step assembler instructions (istep in gdb). If
you want to do a whole C line, or step-over a function (I do this all
the time) it's back to MIXED mode to figure out where the next hex
breakpoint has to go. Very very painful !!

> If the breakpoints were integrated (as the commercial products manage to
> do) it would be easier.

Hoping *hoping* this will be soon. Either by Insight ARM extensions,
Macraigor ocdremote changes or an equivalent.

It'll be interesting to see what CodeSourcery do with Insight (If
anything new ?). --
Cheers,
Bruce
-------------------------------
/\\\/\\\/\\\ / / Bruce Paterson
/ \\\ \\\ \\\ / / Senior Design Engineer
/ /\\\/\\\/\\\/ / 8 Anzed Court, Mulgrave, Vic, 3170
/ / \\\ \\\ \\\ / PO Box 4112, Mulgrave, Vic, 3170, Australia
/ / \\\/\\\ \\\/ Ph: +61 3 8561 4232 Fax: +61 3 9560 9055
Tele-IP Ltd. Email: bruce@bruc... Icq: #32015991
WWW: http://www.tele-ip.com VK3TJN
-------------------------------