Hi list,
I added some SDRAM and clock configuration for the SAM9-L9260 board from
Olimex. Seems to be working pretty well. I followed the AT91SAM9260-EK
board file's example.
This is my first attempt at a git diff, so do tell me if I messed anything
up.
// Dean Glazeski
olimex_sam9_l9260_upd
Forgot a cast on _get_osfhandle(i);
Here's a safer (and hopefully final) version.
patch_long_to_handler_mingw_w64_v3.diff
Description: Binary data
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman
On Friday 16 October 2009, Redirect "Slash" NIL wrote:
> With the previous patches applied, one should now be able to compile on
> MinGW-W64 through:
> ./configure --build=x86_64-w64-mingw32 CFLAGS="-D__USE_MINGW_ANSI_STDIO" ...
Can't that "-D..." be automated? It will always be needed,
if I unde
2009/10/18 Igor Skochinsky
> Actually, in VC9 it returns intptr_t (MSDN is wrong here):
>
> _CRTIMP intptr_t __cdecl _get_osfhandle(_In_ int _FileHandle);
> (from io.h)
>
> So it might be worth it to get mingw people to fix their headers...
>
Actually, the io.h from MinGW-W64 does have the same
On Saturday 17 October 2009, Redirect "Slash" NIL wrote:
> >
> > The "0 +" is mutant...
> >
>
> Yeah. The problem here is that HANDLE is typedef'd as void* (in winnt.h),
> whereas _get_osfhandle() returns a long (
> http://msdn.microsoft.com/en-us/library/ks2530z6.aspx), and gcc insists on
> retur
Hello Redirect,
Sunday, October 18, 2009, 1:14:20 AM, you wrote:
RSN> Yeah. The problem here is that HANDLE is typedef'd as void* (in
RSN> winnt.h), whereas _get_osfhandle() returns a long
RSN> (http://msdn.microsoft.com/en-us/library/ks2530z6.aspx), and gcc
RSN> insists on returning a warning wh
2009/10/17 David Brownell
> On Saturday 17 October 2009, Redirect "Slash" NIL wrote:
>
> > Or we could go with a lighter
> >
> > #ifndef gnu_printf
> > #define gnu_printf printf
> > #endif
> >
> > if you guys prefer.
>
> If it's #defined as a macro in MinGW, that would be the
> way to go ...
>
>
2009/10/17 David Brownell
> ... so I merged the $SUBJECT patch as-is. Though next time
> I'll do something with the quotes, which don't come through safely.
>
Alrighty. Thanks.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
2009/10/17 David Brownell
>
> What's with the strange "(HANDLE)(0 + _get_osfhandle())"?
>
> The "0 +" is mutant...
>
Yeah. The problem here is that HANDLE is typedef'd as void* (in winnt.h),
whereas _get_osfhandle() returns a long (
http://msdn.microsoft.com/en-us/library/ks2530z6.aspx), and gcc
On Saturday 17 October 2009, Øyvind Harboe wrote:
> How do I figure out what version a "git describe" refers to?
git rev-parse $(git describe)
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/lis
On Friday 16 October 2009, Øyvind Harboe wrote:
> > I have a tree that removes those commits plus a few other bits
> > of noise that crept in. Thing is, pushing it would NOT be enough
> > to achieve the full cleanup. The existing clones would need some
> > cleanup/updating...
>
> Do you have a d
On Saturday 17 October 2009, Redirect "Slash" NIL wrote:
> I was trying to avoid a big fat #ifdef IS_MINGW in there, but it looks like
> not every platform knowns gnu_printf as a format.
>
> Or we could go with a lighter
>
> #ifndef gnu_printf
> #define gnu_printf printf
> #endif
>
> if you guys
On Friday 16 October 2009, Redirect "Slash" NIL wrote:
> 2009/10/16 David Brownell
>
> > I meant like something which might appear in any
> > other legal document. Unless your legal name is
> > really "Redirect Slash NIL"?
> >
>
> This is gonna get OT quite fast, but do we really have to go wit
On Saturday 17 October 2009, Øyvind Harboe wrote:
> ./bin2char startup_tcl <
> ../../../zy1000/openocd/src/helper/startup.tcl > startup_tcl.c
> /bin/sh: ./bin2char: No such file or director
Looking at the Makefile I can't see why that would happen.
Did you not reconfigure things from scratch?
What's with the strange "(HANDLE)(0 + _get_osfhandle())"?
The "0 +" is mutant...
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Friday 16 October 2009, Dean Glazeski wrote:
> make[3]: *** No rule to make target
> `../../../openocd/src/helper/bin2char.exe',
> needed by `xscale_debug.h'. Stop.
>
> I believe the issue stems from how I'm doing the build. I made a separate
> build directory instead of building alongside th
How do I add 'dummy' interface to openocd?
$ ./openocd -c "interface dummy"
Open On-Chip Debugger 0.3.0-dev-00355-g9aab763 (2009-10-12-14:15)
$URL$
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Error: The specified JTAG interface was not found (dummy)
The following
mkdir build
cd build
../openocd/configure --enable-maintainer-mode --enable-dummy
=> error
./bin2char startup_tcl <
../../../zy1000/openocd/src/helper/startup.tcl > startup_tcl.c
/bin/sh: ./bin2char: No such file or director
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XSca
Alright - here's v2 of the patch then.
I was trying to avoid a big fat #ifdef IS_MINGW in there, but it looks like
not every platform knowns gnu_printf as a format.
Or we could go with a lighter
#ifndef gnu_printf
#define gnu_printf printf
#endif
if you guys prefer.
2009/10/17 Øyvind Harboe
This fails to build w/Ubuntu 9.04 32 bit gcc version 4.3.3 (Ubuntu
4.3.3-5ubuntu4):
cc1: warnings being treated as errors
In file included from ../../../zy1000/openocd/src/helper/log.h:29,
from ../../../zy1000/openocd/src/helper/binarybuffer.c:27:
../../../zy1000/openocd/src/helpe
On Wed, Oct 14, 2009 at 8:16 PM, Johannes Stezenbach wrote:
> On Wed, Oct 14, 2009 at 04:11:33PM +0200, Ųyvind Harboe wrote:
>> What's the most reasonable way to refer to a git version
>> for human beings?
>>
>> In svn it's a small integer("only" in the thousands).
>>
>> I was thinking about somet
Can you show a test example using the dummy driver?
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://li
22 matches
Mail list logo