On Tue, Apr 28, 2009 at 11:01 PM, Øyvind Harboe oyvind.har...@zylin.com wrote:
On Tue, Apr 28, 2009 at 10:48 PM, Dick Hollenbeck d...@softplc.com wrote:
Michael Bruck wrote:
So my question would be: does anyone know if the drivers produce
different state transitions (except for idling on
I tried that and it seems IS_CYGWIN is not set correctly on cygwin. Any idea ?
Michael
On Tue, Apr 28, 2009 at 10:52 PM, Dick Hollenbeck d...@softplc.com wrote:
Igor Skochinsky wrote:
Hello Dick,
Tuesday, April 28, 2009, 7:29:46 PM, you wrote:
DH Latest.
DH Paaleese commit any time.
Hello All,
Tuesday, April 28, 2009, 7:29:46 PM, Dick wrote:
DH Latest.
DH Paaleese commit any time.
So I decided to try the legendary CMake compatibility and compile
OpenOCD with native Win32 MSVC. The makefile generation went mostly
without a hitch, but the actual compilation ran into a lot of
I thought the logging idea is helpful, but it seems in the end the
arm11 driver needs a general re-write as I would rather not have to
worry about non-deterministic behavior of the JTAG interface driver at
all. And the way to guarantee that is via the pathmove-for-everything
approach.
This
Thank you for help!
Rick Altherr wrote:
Ok. That is a known item. You need to pass --enable-maintainer to
configure.
Rick
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
Hi Dick,
On Wed, Apr 29, 2009 at 16:47, Dick Hollenbeck d...@softplc.com wrote:
Please always state your build environment. What operating system, and what
tool chain is it trying to use?
mingw32?
cygwin?
Just Visual Studio 2005, but I guess the exact version does not matter much.
I
Update. Last night I checked out version 1561 which has the cfi bus/chip
width fixes. I tried it this morning and finally got it to work. My
workspace ram turned out to be my next problem and after I just commented it
out, was able to flash u-boot and recover the board! :)
Yes, my flash parts
Gene Smith wrote:
When I load my program and it burns to flash I see this the first time:
Warn : not enough working area available(requested 16384, free 16336)
This warning is expected, the flash program uses 48 bytes for the flash
algorith.
Then on subsequent loads I see:
Warn : not
As I said, the makefile generation mostly works out of box (I only
had to specifty location of libftd2xx manually). Right now I'm trying
nmake makefiles, not VS projects.
To deal with your issues, and assuming Windows, I would stick with the GNU
compiler as your first attempt, and this
On Wed, Apr 29, 2009 at 5:08 PM, Dick Hollenbeck d...@softplc.com wrote:
How do you build openocd on windows, does it require CYGWIN or is there
another way?
MinGW and cygwin should work, not sure if there are other ways to compile it.
Using CMake on Windows, a reasonable goal would be to
Michael Bruck wrote:
I tried that and it seems IS_CYGWIN is not set correctly on cygwin. Any idea ?
Michael
Michael,
I see a potential solution that is worth a try.
Move these lines:
if(CYGWIN)
set(IS_CYGWIN, true)
else(CYGWIN)
set(IS_CYGWIN, false)
endif(CYGWIN)
if(MINGW)
And I am allergic to Windows, so there will need to be a CMake on Windows
champion to step up and take this bull by the horns.
Good luck finding that one :)
Not my job. I don't use Windows. But I think the folks that do have
found their champion. :)
I found two problems
Øyvind Harboe wrote:
Committed.
Thanks!
I can confirm that at least revision 1570 works again as known from
older versions. This will let me go on with Cortex A8 using recent
svn, now :)
Thanks and best regards
Dirk
___
Openocd-development
Now compare the reported start addresses below with table 5-105 in
OMAP35x TRM, SPRUF98B–September 2008,
and table 2-3 in CoreSight Components, and the management registers in
dap info 1
ap identification register 0x04770002
Type is mem-ap APB
ap debugbase 0x8000
ROM table in legacy
On Wed, 2009-04-29 at 13:24 -0500, Dick Hollenbeck wrote:
[snip]
The C99 stuff is purely arbitrary IMO, there is almost always another
way to code those things. And rather than ifdef-ing them out, I would
simply find that other way and offer those changes as patches, removing
the C99
Ironically, if the project was compilable with C++, there would likely
be *more* compatibility with MS VC++ than what we have now using C. I
say that because Kicad can be compiled by either, using CMake.
Dick
___
Openocd-development mailing list
Can anybody tell me more about the content and organisation
of the STM32 Flash Module Information block. I have searched
but not found :(
This should help
http://www.st.com/stonline/products/literature/pm/13259.pdf
Cheers
Spen
___
Spencer Oliver wrote:
Can anybody tell me more about the content and organisation
of the STM32 Flash Module Information block. I have searched
but not found :(
This should help
http://www.st.com/stonline/products/literature/pm/13259.pdf
I have tried that one, and found The area
I have tried that one, and found The area is reserved for use by
STMicroelectronics . . For further details please refer
to AN2606.
And AN2606 contains how to use instruction but no information
on the actual contents.
Specifically: How do we know that flash size can be found
On Wed, 2009-04-29 at 17:25 -0500, Dick Hollenbeck wrote:
[snip]
This group has talked about using trying to use C++ features; why not
simply start by adopting C99 features?
Yes, minus the designated initializers if not C++ compatible.
I would not consider using the
former language
jim.c fails on cygwin with the new settings.
Please consider the attached patch as it seems to better reflect the
core of the problem, i.e. that environ is declared in unistd.h.
Michael
openocd-jim.c-cygwin.patch
Description: Binary data
___
Dick Hollenbeck wrote:
The new driver is working ok with the calls to
tap_get_tms_path_len(start_state, goal_state);
If I use the old version of the new binary tms_seqs table with the new
driver, I see the exact same behavior on my ARM9 board as with the
ft2232.c in HEAD.
If I use the
This problem was introduced by r1559 in replacements.h
in ft2232.c windows.h (or more precise winsock2.h) must be included
after sys/select.h
Michael
openocd-ft2232.c-cygwin.patch
Description: Binary data
___
Openocd-development mailing list
Hi
This speculation but worth trying.
For targets where the debug interface is entirely memory mapped into the
target, apart from a thin communications layer, we only need low level
memory read and memory write. Everything else can be scripted in Tcl. I
think this is the situation for
Michael Bruck wrote:
This problem was introduced by r1559 in replacements.h
in ft2232.c windows.h (or more precise winsock2.h) must be included
after sys/select.h
Michael
I put this change into my pending patch, so it can be piggy backed there.
That will be on the list by end of the
On Thu, 2009-04-30 at 01:23 +0200, Michael Bruck wrote:
jim.c fails on cygwin with the new settings.
Please consider the attached patch as it seems to better reflect the
core of the problem, i.e. that environ is declared in unistd.h.
Committed as r1572.
--Z
On Wed, 2009-04-29 at 20:02 -0500, Dick Hollenbeck wrote:
Michael Bruck wrote:
This problem was introduced by r1559 in replacements.h
in ft2232.c windows.h (or more precise winsock2.h) must be included
after sys/select.h
Michael
I put this change into my pending patch, so it
On Wed, Apr 29, 2009 at 12:56 PM, Brian Hutchinson b.hutch...@gmail.comwrote:
Update. Last night I checked out version 1561 which has the cfi bus/chip
width fixes. I tried it this morning and finally got it to work. My
workspace ram turned out to be my next problem and after I just
Hello Dick,
Thursday, April 30, 2009, 4:28:54 AM, you wrote:
Due to the lack of prior opposition, I had been debating whether to
simply commit a change that adds -std=c99 and seeing how the community
reacts (since I can now revert it quickly if it poses a real problem).
DH The -std=c99
On Thu, Apr 30, 2009 at 1:16 AM, Zach Welch z...@superlucidity.net wrote:
On Wed, 2009-04-29 at 17:25 -0500, Dick Hollenbeck wrote:
What? It is only several days to get this project to compile with C++,
maybe several weeks to rewrite it. (Do we get to peek at the old
code when we rewrite
Igor Skochinsky wrote:
Hello Dick,
Thursday, April 30, 2009, 4:28:54 AM, you wrote:
Due to the lack of prior opposition, I had been debating whether to
simply commit a change that adds -std=c99 and seeing how the community
reacts (since I can now revert it quickly if it poses a real
On Thu, 2009-04-30 at 05:17 +0200, Michael Bruck wrote:
On Thu, Apr 30, 2009 at 1:16 AM, Zach Welch z...@superlucidity.net wrote:
On Wed, 2009-04-29 at 17:25 -0500, Dick Hollenbeck wrote:
What? It is only several days to get this project to compile with C++,
maybe several weeks to
I have never understood open source projects bending over to compile
with MSVC, when a free compiler is available. What is the impediment to
a programmer, who limits themselves to windows, installing GCC and using
that. Even if they use MSVC for other things?
Is the typical embedded project
On Thu, Apr 30, 2009 at 7:12 AM, Zach Welch z...@superlucidity.net wrote:
On Thu, 2009-04-30 at 05:17 +0200, Michael Bruck wrote:
On Thu, Apr 30, 2009 at 1:16 AM, Zach Welch z...@superlucidity.net wrote:
On Wed, 2009-04-29 at 17:25 -0500, Dick Hollenbeck wrote:
What? It is only several
34 matches
Mail list logo
