Merged.
Thanks!
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-d
> + it has to do with whether you want to use the
> installed Jim Tcl or not.
Or more typically: if there even *is* one...
More likely to be a "real" Tcl installed, IME.
Maybe someone with time and knowlege can come
up with a wrapper that makes Real Tcl look and
behave like Jim. ;)
_
On Mon, Dec 20, 2010 at 12:20 AM, David Brownell wrote:
>
>
> --- On Sun, 12/19/10, Øyvind Harboe wrote:
> missed.
>
>>
>> I'm thinking that bootstrap could be split in two:
>>
>> - a script that does what it does today and that can be
>> invoked
>> directly.
>
> Two bootstraps might make sense.
--- On Sun, 12/19/10, Øyvind Harboe wrote:
missed.
>
> I'm thinking that bootstrap could be split in two:
>
> - a script that does what it does today and that can be
> invoked
> directly.
Two bootstraps might make sense. That one
might be mostly for GIT-less environments,
as from a source/d
According to ST datasheets the last two characters (usually -T6) stand
for package type (T = LQFP) and temperature range (6 - industrial).
These two are not very informative and not very important, so I'd be for
omitting them every time.
4\/3!!
___
O
From: Tormod Volden
---
With this, all www.st.com URLs have been corrected or verified.
Tormod
tcl/interface/flashlink.cfg |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/tcl/interface/flashlink.cfg b/tcl/interface/flashlink.cfg
index 5c81cf5..22abe7b 100644
--- a/tc
From: Tormod Volden
Make consistent use of hex memory size for flashing.
Delete stm32f10x_128k_eval.cfg. It has no product reference
nor any settings in it.
---
This patch is mostly cosmetic and just makes things that are the
same, look the same.
Anyway I am not sure if the board name uniquely
From: Tormod Volden
ST recently rewamped (screwed up) their web site and broke all links.
Also match the chip names with those on the web site product
descriptions.
---
Hi,
Here is a series of patches for the STM32. This one only makes
documentation changes.
Tormod
tcl/board/stm32100b_eval.cf
Merged.
Thanks!
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-d
On Sun, Dec 19, 2010 at 8:58 PM, David Brownell wrote:
> Example: against a fresh clone of mainline.
>
> I think it ought to support "configure"next ... but instead it seems to
> require more, and
> thus is needlessly error prone... Folk won't often be
> reading script output except to see and f
On Sun, Dec 19, 2010 at 7:56 PM, David Brownell wrote:
>
>
> --- On Sun, 12/19/10, Øyvind Harboe wrote:
>
>> So you don't think there is a disadvantage to
> using variables
>> to pass information around?
>
> I never said that. Are you saying that one
> goal is reducing usage of globals? That's
Example: against a fresh clone of mainline.
I think it ought to support "configure"next ... but instead it seems to
require more, and
thus is needlessly error prone... Folk won't often be
reading script output except to see and fix well-flagged errors, so
the need for two submodule commands is e
--- On Sun, 12/19/10, Øyvind Harboe wrote:
> So you don't think there is a disadvantage to
using variables
> to pass information around?
I never said that. Are you saying that one
goal is reducing usage of globals? That's
generally a good thing ... but since you had
stipulated that the sing
>> What do you think about the new structure?
>
> By structure, if you mean default value handling,
> I didn't like the complex if/then/... stuff, so
> count the subroutine a win, even if it adds a
> potentially confusing OpenOCD-only mechanism.
Note that it's backwards compatible. You can employ
On Sun, Dec 19, 2010 at 6:50 PM, David Brownell wrote:
>
>> Øyvind Harboe wrote:
>> > A board script should export a single procedure
>> without arguments
>> > with a name that's fixed by convention.
>
> Is there an advantage to that approach? After
> all, a script file *is* essentially a single
--- On Sun, 12/19/10, Øyvind Harboe wrote:
>
> > A good simplification would be to remove every
> > non-BIG endianness setting.
> The big/little endian issue is orthogonal to how we
> organize the config files.
But not to $SUBJECT of this specific thread.
>
> What do you think about th
> Øyvind Harboe wrote:
> > A board script should export a single procedure
> without arguments
> > with a name that's fixed by convention.
Is there an advantage to that approach? After
all, a script file *is* essentially a single
procedure etc (nameless, but no never mind).
_
Øyvind Harboe wrote:
> A board script should export a single procedure without arguments
> with a name that's fixed by convention.
This sounds good to me, for starters!
//Peter
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
h
Looks OK to me after a cursory inspection.
Any objections?
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
On Sun, Dec 19, 2010 at 5:22 PM, David Brownell wrote:
>
>
> --- On Sun, 12/19/10, Øyvind Harboe wrote:
>
>
>
>> -if { [info exists ENDIAN] } {
>> - set _ENDIAN $ENDIAN
>> -} else {
>> - set _ENDIAN little
>
>
>
> A good simplification would be to remove every
> non-BIG endianness setting.
--- On Sun, 12/19/10, Øyvind Harboe wrote:
> -if { [info exists ENDIAN] } {
> - set _ENDIAN $ENDIAN
> -} else {
> - set _ENDIAN little
A good simplification would be to remove every
non-BIG endianness setting. When not
specified, the OpenOCD default is "little".
Including "little"
Am 12/18/2010 09:09 PM, schrieb Øyvind Harboe:
> Hi Michael,
>
> you'll have to rebase your patch on top of the master branch and
> update the comments to use ;# at the end of lines as the master
> branch now follows tcl rules for comments.
No problem - I also fixed the working area address.
Is th
On Fri, Dec 17, 2010 at 5:33 PM, Peter Stuge wrote:
> Øyvind Harboe wrote:
>> > In my opinion the if/then version makes it easier for new users
>> > to customize cfg files. And since most users will need to
>> > customize at least one cfg file, I think simplicity trumps short
>> > files.
>>
>> I
Am 12/17/2010 10:38 PM, schrieb Steve Bennett:
>> +# setup expansion bus CS
>> +
>> ##
>> +mww 0xc400 0xbd113842 #CS0 : Flash, write enabled @0x5000
> Tcl only recognises comments at the beginning of a co
Illustration of the new config script handling scheme.
Signed-off-by: Øyvind Harboe
---
tcl/board/at91cap7a-stk-sdram.cfg | 297 ++---
1 files changed, 143 insertions(+), 154 deletions(-)
diff --git a/tcl/board/at91cap7a-stk-sdram.cfg
b/tcl/board/at91cap7a-stk-
this allows configuration scripts to export a init_targets proc
rather than setting up the target directly.
This allows for new conventions in how to set up target vs. board
script and how to transfer default settings between board and
target scripts.
Signed-off-by: Øyvind Harboe
---
src/ecosbo
> How does this work in case we have multiple devices in one scan chain? does
> the last included "setup_target" replace the previous one, or do we need
> unique names?
What target scripts export that board scripts can use would have
to be defined by each individual target script as there is no
si
On 12/18/2010 10:15 PM, Øyvind Harboe wrote:
How about having target scripts export a proc as the default
behavior rather than just executing statements?
This would get rid of using (effectively global)variables as
a way to communicate with these scripts.
A proc also opens up for handling varia
28 matches
Mail list logo
