On Sat, Feb 27, 2010 at 09:00:32AM -0800, David Brownell wrote:
> On Thursday 25 February 2010, Mariano Alvira wrote:
> > ---
>
> Needs a patch comment.
Ok. Do the subject lines not get added as patch comments? I figured
they would since they are generated from the commit messages.
>What's an MC13224V? Maybe:
>
> The MC13224V is a FreeScale ARM7TDMI based IEEE® 802.15.4 platform for
> Zigbee and similar low-power wireless applications. It uses PIP
> (Platform In Package) technology, and boots from ROM which shadows
> code from serial flash into RAM.
Sure. Thanks.
>
>
> > tcl/target/mc13224v.cfg | 60
> > +++++++++++++++++++++++++++++++++++++++++++++++
> > 1 files changed, 60 insertions(+), 0 deletions(-)
> > create mode 100644 tcl/target/mc13224v.cfg
> >
> > diff --git a/tcl/target/mc13224v.cfg b/tcl/target/mc13224v.cfg
> > new file mode 100644
> > index 0000000..6766cf7
> > +
> > +jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x01 -irmask 0x0f
> > -expected-id $_CPUTAPID
>
> THose ircapture and irmask values are the defaults for irlen = 4 so
> you shouldn't specify them. ("ircapture" should only be specified
> if the chip doesn't conform to the JTAG spec in that way.)
Ok.
>
>
> > +
> > +set _TARGETNAME [format "%s.cpu" $_CHIPNAME]
> > +target create $_TARGETNAME arm7tdmi -endian $_ENDIAN -chain-position
> > $_TARGETNAME -variant arm7tdmi
>
> There are no variants of the arm7tdmi, so don't specify that.
Ok.
>
> > +
> > +# Internal sram memory
> > +$_TARGETNAME configure -work-area-virt 0x00408000 -work-area-phys
> > 0x00408000 -work-area-size 0x1000 -work-area-backup 1
>
> Line too long. Also, with no MMU in this chip, "-work-area-virt" is
> inappropriate. (Right, no MMU?)
Right. No MMU. I'll remove work-area-virt and wrap the line.
> > +
> > +proc run {file} {
> > + puts "loading $file into location 0x00400000 and executing..."
> > + soft_reset_halt
> > + load_image $file 0x00400000
> > + reg pc 0x00400000
> > + resume
> > +}
>
> That's specific to your work environment; don't include it
> in a file that's intended to be general purpose.
It's a handy procedure for anyone using the mc13224v to run an
images. Is there anyway to include it or something like it?
Are you worried about "run" interfering with some other name or do you
not like that it always goes to 0x00400000?
Thanks,
-Mar.
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
