[coldfire-gnu-discuss] Getting started when firmware is located in ColdFire internal FLASH.
David Brown
david at westcontrol.com
Wed Feb 14 16:58:53 UTC 2007
Claude Sylvain wrote:
> Hello Nathan,
>
>
> >
> > nathan wrote:
> >
> >
> > The current sprite is unable to program flash. flash programming will
> > be in our next release, scheduled for the end of March. Debugging a
> > program from flash already works -- the debugger will use hardware
> > breakpoints rather than patched breakpoints.
> >
>
> Great! So, I have only to find out a tool to program the internal
> Flash of the M52235 MCU, and all will be up and running.
> As a programing tool, I have already tryed CFFLASHER. Sadly, this
> tool seems to not work at all on some Windows XP machine !?
> So, I will use the "Flash Programmer" tool included inside the CodeWarrior
> IDE :-/ It is more complex to use, but work on all machines (I know),
> and it can be configured to match custom emmbedded system.
>
>
> I have 1 question...
>
> In the past, I have been able to use Insight (for Windows) with mspgcc
> (GCC for the TI MSP430 MCUs). I had just to configure Insight to
> communicate with the "gdbproxy" utility, and all was working fine.
>
> Is it possible to do the same with Sourcery G++ ?
>
Insight is a little different from other gdb frontends, in that it is
combined with the gdb backend. Thus (I think) you'd need to build gdb
for the ColdFire with Insight support. It should be possible, but it
might be a little scary if you haven't done it before.
There are other front ends available for gdb that can work easily with
any backend. I've used gvd with a number of gdb's for different
targets, and ddd works too (although it's a bit alien on windows) -
Eclipse works basically in this way, although Code Sourcery have added a
bit more integration.
More information about the coldfire-gnu-discuss
mailing list