The aduc702x code was copied from stm32.c or str9x.c.
The original code counted 16 bit words whereas the
aduc702x counted bytes & 16 bit words willy nilly.
Looking at the original stm32.c and str9x.c code it lacks
a lot of error checking/propagation, but unless we hear
complaints, it's perhaps be
On Wed, 2009-07-08 at 23:08 +0200, Øyvind Harboe wrote:
> On Wed, Jul 8, 2009 at 11:00 PM, Zach Welch wrote:
> > I just saw you did re-post... but you only waited 4 hours. That is not
> > enough time. You need to wait 12-24 hours, preferably 24.
>
> 24h it is until 0.2 is out then.
Let me try t
On Wed, 2009-07-08 at 23:37 +0200, Øyvind Harboe wrote:
> >> I wanted to use a new subdirectory for all these target binaries,
> >> but I don't speak automake well enough to pull it off.
> >
> > Yeah, that's a little trickier. I still think these files need to be in
> > pkglibdir, though. I think
On Thu, 2009-07-09 at 09:56 +0800, Xiaofan Chen wrote:
> On Thu, Jul 9, 2009 at 1:24 AM, David Brownell wrote:
> > On Wednesday 08 July 2009, Zach Welch wrote:
> >> The files in this series are meant for review, so feedback may be
> >> incorporated in them before I commit them.
> >>
> >> 1/5 Add
On Wednesday 08 July 2009, Xiaofan Chen wrote:
> If I were a maintainer (luckily or unluckily I am not), I would be a bit
> scared by the harsh/strict words in the Maintainers document considering
> the fact that all the maintainers and active contributors spend their
> free time to do free develop
Update lm3s3748 support: split EK board support out
from the target CPU support ... other boards with this
chip will likely be set up differently.
Shrink some too-long lines in that target CPU support.
---
tcl/board/ek-lm3s3748.cfg | 17 +
tcl/target/lm3s3748.cfg | 35 +
On 7/8/09 5:05 PM, "Xiaofan Chen" wrote:
> On Thu, Jul 9, 2009 at 5:53 AM, Gary Carlson
> wrote:
>> Zach/Spencer/Xiaofan,
>>
>> I did some more experimentation on the latest subversion (2499) and was able
>> to tweak the jlink.c code slightly to possibly achieve three objectives:
>>
>> 1. Make
On Thu, Jul 9, 2009 at 1:24 AM, David Brownell wrote:
> On Wednesday 08 July 2009, Zach Welch wrote:
>> The files in this series are meant for review, so feedback may be
>> incorporated in them before I commit them.
>>
>> 1/5 Add comments to top-level files to "excuse" their Doxygen markup.
>> 2/
On Thu, Jul 9, 2009 at 5:53 AM, Gary Carlson wrote:
> Zach/Spencer/Xiaofan,
>
> I did some more experimentation on the latest subversion (2499) and was able
> to tweak the jlink.c code slightly to possibly achieve three objectives:
>
> 1. Make jlink dongles work under Windows for Spencer.
> 2. Make
On Thu, Jul 9, 2009 at 12:19 AM, Michael Fischer wrote:
> Hello Xiaofan,
>
> I have updated the Sparkfun page now, please check it.
Thanks. It is quite good now.
> PS: The best is if the OpenOCD project get a wiki page, where
> other one can add information too?
>
I agree.
--
Xiaofan http:/
Zach/Spencer/Xiaofan,
I did some more experimentation on the latest subversion (2499) and was able
to tweak the jlink.c code slightly to possibly achieve three objectives:
1. Make jlink dongles work under Windows for Spencer.
2. Make jlink dongles work under Mac OS X for me.
3. Make jlink dongles
David Brownell escreveu:
> On Wednesday 08 July 2009, Xiaofan Chen wrote:
>> Is this "a la Jim" English? Is it " aka Jim"?
>> or "also know as Jim"? I am not a native speaker
>> of English though.
>
> It's a borrowing from French, where "a la" would be
> kind of odd. Best change to ", as done wi
>> I wanted to use a new subdirectory for all these target binaries,
>> but I don't speak automake well enough to pull it off.
>
> Yeah, that's a little trickier. I still think these files need to be in
> pkglibdir, though. I think moving them to the pkgdatadir will cause
> warnings on some packa
On Wed, 2009-07-08 at 23:09 +0200, Øyvind Harboe wrote:
> On Wed, Jul 8, 2009 at 10:56 PM, Zach Welch wrote:
> > On Wed, 2009-07-08 at 16:25 +0200, Øyvind Harboe wrote:
> >> Testing&comments appreciated!
> >>
> >> I'm thinking that target executables should be placed
> >> into the same folder as sc
On Wed, Jul 8, 2009 at 10:56 PM, Zach Welch wrote:
> On Wed, 2009-07-08 at 16:25 +0200, Øyvind Harboe wrote:
>> Testing&comments appreciated!
>>
>> I'm thinking that target executables should be placed
>> into the same folder as scripts.
>>
>> It's not really executables from the host OS's point of
On Wed, Jul 8, 2009 at 11:00 PM, Zach Welch wrote:
> I just saw you did re-post... but you only waited 4 hours. That is not
> enough time. You need to wait 12-24 hours, preferably 24.
24h it is until 0.2 is out then.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://ww
I just saw you did re-post... but you only waited 4 hours. That is not
enough time. You need to wait 12-24 hours, preferably 24.
On Wed, 2009-07-08 at 13:50 -0700, Zach Welch wrote:
> You need to re-post patches when they change substantially. You added
> new code that was not in the original
On Wed, 2009-07-08 at 16:25 +0200, Øyvind Harboe wrote:
> Testing&comments appreciated!
>
> I'm thinking that target executables should be placed
> into the same folder as scripts.
>
> It's not really executables from the host OS's point of
> view, it's just data that ships w/OpenOCD and that
> O
You need to re-post patches when they change substantially. You added
new code that was not in the original patch.
It still has whitespace problems.
On Wed, 2009-07-08 at 20:29 +0200, ohar...@mail.berlios.de wrote:
> Author: oharboe
> Date: 2009-07-08 20:29:03 +0200 (Wed, 08 Jul 2009)
> New R
Zach Welch wrote:
> On Wed, 2009-07-08 at 12:47 +0200, Øyvind Harboe wrote:
>
>> How is the attached patch?
>>
>
> The NEWS file details the migration of the installed scripts from
> $(pkglibdir) to $(pkgdatadir)/scripts; the former should not be used
> anymore, and custom scripts migrated
On 7/8/09 8:18 AM, "Spencer Oliver" wrote:
>> You asked me what the result of Spencer's patch was under Mac
>> OS X. I tested it against my system this evening and as you
>> will see below, it caused a number of startup faults. It
>> also appears to make the j-link dongle completely
>> unres
Hi Spencer,
I will do some more digging. It sounds like you have a Windows test
platform. Was the intermittent startup issue ever a problem on this
operating system?
Based on Xiaofan's recent digging it sounds like the usb_reset solution is a
temporary fix that is going to cause future problems
On Wed, Jul 8, 2009 at 5:53 PM, Thomas A. Moulton wrote:
> On Wed, 2009-07-08 at 17:31 +0200, Øyvind Harboe wrote:
>> On Wed, Jul 8, 2009 at 5:20 PM, Thomas A. Moulton wrote:
>> > On Wed, 2009-07-08 at 16:10 +0200, Øyvind Harboe wrote:
>> >> This patch fixes the broken flash programming w/workarea
On Wed, Jul 8, 2009 at 7:37 PM, David Brownell wrote:
> On Wednesday 08 July 2009, Michael Schwingen wrote:
>> XScale (IXP42x) is broken
>
> I reported not that long ago that PXA 255 is broken
> too ... it doesn't seem to be able to detect the chip
> in the JTAG chain.
>
> It's not clear to me if t
Small clarification:
Everything is fine when I fun the chip ALONE - OpenOCD is closed, JTAG
can be connected and powered, I cycle the power, everything works fine
When I run OpenOCD and via telnet issue the commands:
> reset
JTAG tap: lpc2103.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, part:
I have a very simple code which just blinks the LED. The code itself is
fine.
When I upload the code and just run it everything is fine. When I try to
debug the same code that I've uploaded before (flash is not modified)
some registers have some funny values which make the code work wrong.
Whe
On Wednesday 08 July 2009, Michael Schwingen wrote:
> XScale (IXP42x) is broken
I reported not that long ago that PXA 255 is broken
too ... it doesn't seem to be able to detect the chip
in the JTAG chain.
It's not clear to me if that was a *regression* since
the 0.1.0 release though. It may have
On Wednesday 08 July 2009, Øyvind Harboe wrote:
> I don't understand why you need or want to distinguish between target
> executables and scripts.
As a rule, a script can be maintained with a text editor
but a binary can't be ...
___
Openocd-development
On Wednesday 08 July 2009, Zach Welch wrote:
> The files in this series are meant for review, so feedback may be
> incorporated in them before I commit them.
>
> 1/5 Add comments to top-level files to "excuse" their Doxygen markup.
> 2/5 Add microscopic style guide at the end of the PATCH prim
On Wednesday 08 July 2009, Xiaofan Chen wrote:
> -# Write a new C implementation a la Jim?
>
> Is this "a la Jim" English? Is it " aka Jim"?
> or "also know as Jim"? I am not a native speaker
> of English though.
It's a borrowing from French, where "a la" would be
kind of odd. Best change to "
Hi Maróy,
I do development work on Mac OS X Leopard and I ran into a lot of issues
like this getting a cross-compiler to work properly in the past. I finally
succeeded, but I had to spend three weeks making and testing a custom script
to build cross gcc.
I don't know if it will help you, but if
On Wed, 2009-07-08 at 17:31 +0200, Øyvind Harboe wrote:
> On Wed, Jul 8, 2009 at 5:20 PM, Thomas A. Moulton wrote:
> > On Wed, 2009-07-08 at 16:10 +0200, Øyvind Harboe wrote:
> >> This patch fixes the broken flash programming w/workarea enabled.
> >>
> >> Please test & report.
> >>
> >> These bugs
On Wed, Jul 8, 2009 at 5:20 PM, Thomas A. Moulton wrote:
> On Wed, 2009-07-08 at 16:10 +0200, Øyvind Harboe wrote:
>> This patch fixes the broken flash programming w/workarea enabled.
>>
>> Please test & report.
>>
>> These bugs explain the intermittent SEGFAULT's reported +
>> that flash programmi
On Wed, 2009-07-08 at 16:10 +0200, Øyvind Harboe wrote:
> This patch fixes the broken flash programming w/workarea enabled.
>
> Please test & report.
>
> These bugs explain the intermittent SEGFAULT's reported +
> that flash programming worked some of the time.
>
Pardon my ignorance, but is the
On Wed, 2009-07-08 at 14:43 +0200, Øyvind Harboe wrote:
> On Wed, Jul 8, 2009 at 2:22 PM, Thomas A. Moulton wrote:
> > On Wed, 2009-07-08 at 09:41 +0200, Øyvind Harboe wrote:
> >> I have an Aduc7024 here that I can test with.
> >>
> >> Could you provide instructions on how to reproduce the crash on
> You asked me what the result of Spencer's patch was under Mac
> OS X. I tested it against my system this evening and as you
> will see below, it caused a number of startup faults. It
> also appears to make the j-link dongle completely
> unresponsive thereafter.
>
> I guess the bigger quest
On Wed, Jul 8, 2009 at 10:53 PM, Xiaofan Chen wrote:
> On Wed, Jul 8, 2009 at 12:43 PM, Xiaofan Chen wrote:
>> I will ask in the libusb mailing list why it still works under Linux
>> and Mac OS X.
>
> Here is the answer from Alan Stern in the libusb mailing list.
>
>>> Apparently the code is not co
On Wed, Jul 8, 2009 at 12:43 PM, Xiaofan Chen wrote:
> I will ask in the libusb mailing list why it still works under Linux
> and Mac OS X.
Here is the answer from Alan Stern in the libusb mailing list.
>> Apparently the code is not correct.
>> After this one, the usb_handle should not be valid a
On Wed, Jul 8, 2009 at 2:11 PM, Gary Carlson wrote:
> You asked me what the result of Spencer's patch was under Mac OS X. I
> tested it against my system this evening and as you will see below, it
> caused a number of startup faults. It also appears to make the j-link
> dongle completely unrespon
On Wed, Jul 8, 2009 at 7:28 AM, Xiaofan Chen wrote:
> http://www.nabble.com/Possibility-to-release-the-current-SVN-version-as-0.1.12.2-td24141073.html
> The author has accepted my suggestion released the latest svn
> of libusb-win32 0.1 branch as 0.1.12.2.
>
> Download:
> http://sourceforge.net/pro
On Wed, Jul 8, 2009 at 7:28 AM, Xiaofan Chen wrote:
> http://www.nabble.com/Possibility-to-release-the-current-SVN-version-as-0.1.12.2-td24141073.html
> The author has accepted my suggestion released the latest svn
> of libusb-win32 0.1 branch as 0.1.12.2.
>
> Download:
> http://sourceforge.net/pro
Testing&comments appreciated!
I'm thinking that target executables should be placed
into the same folder as scripts.
It's not really executables from the host OS's point of
view, it's just data that ships w/OpenOCD and that
OpenOCD uses.
--
Øyvind Harboe
Embedded software and hardware consult
I am now looking at the OpenOCD source codes and find out that
there is one patch file for libftdi 0.12 by Spen.
As the README file stated that Windows support of libftdi is
since version 0.14 and libftdi 0.14 has already the patches
implemented, I think this directory contrib\libftdi is no longer
On Wed, Jul 8, 2009 at 6:05 PM, Zach Welch wrote:
> Add comments to top-level files to "excuse" their Doxygen markup.
> ---
> BUGS | 1 +
> PATCHES | 4 ++--
> TODO | 1 +
> 3 files changed, 4 insertions(+), 2 deletions(-)
>
The TODO file has the following section.
@section thelist
This patch fixes the broken flash programming w/workarea enabled.
Please test & report.
These bugs explain the intermittent SEGFAULT's reported +
that flash programming worked some of the time.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
### Eclips
On Wed, Jul 8, 2009 at 1:11 PM, Michael
Schwingen wrote:
> Øyvind Harboe wrote:
>>
>> How is the attached patch?
>>
>
> Works fine.
The other workaround is to add that path on the command line
to OpenOCD.
Perhaps we should postpone this patch until after 0.2.
--
Øyvind Harboe
Embedded software
On Wed, Jul 8, 2009 at 2:22 PM, Thomas A. Moulton wrote:
> On Wed, 2009-07-08 at 09:41 +0200, Øyvind Harboe wrote:
>> I have an Aduc7024 here that I can test with.
>>
>> Could you provide instructions on how to reproduce the crash on
>> that target?
>>
>>
>
> It works without crashing now!
With or
On Wed, 2009-07-08 at 09:41 +0200, Øyvind Harboe wrote:
> I have an Aduc7024 here that I can test with.
>
> Could you provide instructions on how to reproduce the crash on
> that target?
>
>
It works without crashing now!
The elf file does have a problem.
I will send it to you.
I did not cha
> Let's give this some time to stew. Clearly, I did not manage to
> convince myself entirely, and it's not 0.2.0 material. I still dislike
> the idea of having both pkglibdir and pkgdatadir in the search path.
I would have thought the right spot for target executables was
in the pkgdatadir.
On Wed, 2009-07-08 at 14:03 +0200, Øyvind Harboe wrote:
> On Wed, Jul 8, 2009 at 1:55 PM, Zach Welch wrote:
> > On Wed, 2009-07-08 at 12:47 +0200, Øyvind Harboe wrote:
> >> How is the attached patch?
> >
> > The NEWS file details the migration of the installed scripts from
> > $(pkglibdir) to $(pkg
On Wed, Jul 8, 2009 at 1:55 PM, Zach Welch wrote:
> On Wed, 2009-07-08 at 12:47 +0200, Øyvind Harboe wrote:
>> How is the attached patch?
>
> The NEWS file details the migration of the installed scripts from
> $(pkglibdir) to $(pkgdatadir)/scripts; the former should not be used
> anymore, and custo
On Wed, 2009-07-08 at 12:47 +0200, Øyvind Harboe wrote:
> How is the attached patch?
The NEWS file details the migration of the installed scripts from
$(pkglibdir) to $(pkgdatadir)/scripts; the former should not be used
anymore, and custom scripts migrated into $(pkgdatadir)/site/. This
patch wil
Øyvind Harboe wrote:
> How is the attached patch?
>
Works fine.
cu
Michael
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
If yes, then test with svn head *now* and give feedback ASAP.
We're trying to push out 0.2, but we'll wait until we have fixed
all *serious* regressions since 0.1.
If you have a known regression in svn head vs. 0.1 that is not in the
TODO list, then post a reminder to the list about the problem.
How is the attached patch?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
### Eclipse Workspace Patch 1.0
#P openocd
Index: src/helper/Makefile.am
===
--- src/helper/Makefile.am (revisi
On Wed, 2009-07-08 at 12:06 +0200, Nico Coesel wrote:
> > -Original Message-
> > From: openocd-development-boun...@lists.berlios.de [mailto:openocd-
> > development-boun...@lists.berlios.de] On Behalf Of Zach Welch
> > Sent: woensdag 8 juli 2009 0:35
> > To: Øyvind Harboe
> > Cc: openocd-de
> Don't add blank lines in lists, and use @par at the end of the line to
> get the proper formatting for the link.
>
> The blank lines separates the items and causes Doxygen to generate
> separate lists, whereas my suggestions preserve the integrity of the
> emitted lists. This is particular impor
On Wed, 2009-07-08 at 12:25 +0200, oharboe at BerliOS wrote:
> Author: oharboe
> Date: 2009-07-08 12:25:39 +0200 (Wed, 08 Jul 2009)
> New Revision: 2497
>
> Modified:
>trunk/TODO
> Log:
> Xscale installation regression entered
>
> Modified: trunk/TODO
> ===
> [snip]
>> - retval = ERROR_FLASH_OPERATION_FAILED;
>> + if ((buf_get_u32(reg_params[3].value, 0, 32) & 1) !=
>> 1)
>
> Ditto.
I didn't touch this part of the code, so I'm leaving it alone.
Although desirable, such no-op cleanup's is best left to a separate
co
> If I may be very blunt: I don't think we are very close to a 0.2.0 release.
> It seems (based on bug reports) the recent changes broke some of the
> existing functionality. That needs to be tested & fixed first. IMHO release
> 0.2.0 should have at least the same functionality that 0.1.0 had.
Reg
I'll do this before committing, awaiting comments on the functionality first.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://li
On Wed, 2009-07-08 at 10:04 +0200, Øyvind Harboe wrote:
> ### Eclipse Workspace Patch 1.0
> #P openocd
> Index: src/flash/aduc702x.c
> ===
> --- src/flash/aduc702x.c(revision 2490)
> +++ src/flash/aduc702x.c(working cop
> -Original Message-
> From: openocd-development-boun...@lists.berlios.de [mailto:openocd-
> development-boun...@lists.berlios.de] On Behalf Of Zach Welch
> Sent: woensdag 8 juli 2009 0:35
> To: Øyvind Harboe
> Cc: openocd-development@lists.berlios.de
> Subject: Re: [Openocd-development] 0.
Add style rule to avoid combining assignment and logical tests.
---
style.txt | 14 ++
1 file changed, 14 insertions(+)
Add style rule to avoid combining assignment and logical tests.
---
style.txt | 14 ++
1 file changed, 14 insertions(+)
==
only in patch2:
unchan
Document Maintainers and Testing.
- Extend The Developer Manual to document Maintainer and Testing Processes.
- Update main page with references and overview of these new pages.
---
main.txt| 15
maintainers.txt | 139
testing.txt |
Add section to provide some documentation for cross-compiling.
---
README | 23 +++
1 file changed, 23 insertions(+)
Add section to provide some documentation for cross-compiling.
---
README | 23 +++
1 file changed, 23 insertions(+)
==
only in patc
Add microscopic style guide at the end of the PATCH primer.
---
patches.txt | 13 +
1 file changed, 13 insertions(+)
Add microscopic style guide at the end of the PATCH primer.
---
patches.txt | 13 +
1 file changed, 13 insertions(+)
==
only in patch2:
unchanged:
-
Add comments to top-level files to "excuse" their Doxygen markup.
---
BUGS|1 +
PATCHES |4 ++--
TODO|1 +
3 files changed, 4 insertions(+), 2 deletions(-)
Add comments to top-level files to "excuse" their Doxygen markup.
---
BUGS|1 +
PATCHES |4 ++--
TODO|
The files in this series are meant for review, so feedback may be
incorporated in them before I commit them.
1/5 Add comments to top-level files to "excuse" their Doxygen markup.
2/5 Add microscopic style guide at the end of the PATCH primer.
3/5 Add section to provide some documentati
Hi,
I just did a "svn update" on my work machine (Debian 5.0). It seems
XScale (IXP42x) is broken because OpenOCD can't find the debug handler
in the installed location:
I did:
./bootstrap
./configure --enable-maintainer-mode --prefix=/opt/openocd \
--enable-parport --enable-parport_ppdev \
-
Comments?
Flash programming on adu7024 w/working area does
not work out of the box with the shipping aduc702x.cfg config script.
I strongly suspect that a reset-init script is needed Patches anyone?
Using parport flash programming w/working area does not crash as
Thomas reported, it just doe
I have an Aduc7024 here that I can test with.
Could you provide instructions on how to reproduce the crash on
that target?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Op
Hi Xiaofan,
You asked me what the result of Spencer's patch was under Mac OS X. I
tested it against my system this evening and as you will see below, it
caused a number of startup faults. It also appears to make the j-link
dongle completely unresponsive thereafter.
I guess the bigger question i
73 matches
Mail list logo
