h BTW...
Cheers,
--
Liam Redmond.
Rock Software
http://www.rock-software.com
diff --git a/configure.in b/configure.in
index d7f8d47..fa2a498 100644
--- a/configure.in
+++ b/configure.in
@@ -736,12 +736,12 @@ if test $build_ft2232_ftd2xx = yes -o
$build_presto_ftd2xx = yes ; then
# And calculat
> Sadly, that also requires a lot of engineering expertise to write that
Actually the hardware description is not as bad as you might first think, I
have a prototype Xilinx CoolRunnerII CPLD hooked up to a Cypress high speed
FX2, this effectively gives a direct pipe from the OpenOCD USB calls to
ey are currently sampling a device with both
Ethernet and USB.
I'm using the FX2 primarily because it was on my desk from my last project
but also because it's a fully "high speed" device.
Liam.
- Original Message -
From: "David Brownell"
To:
Cc: "Liam R
Hi,
Not from a maintainer but from one following this thread with interest after
I too noticed malloc calls as unchecked function call parameters, something
that made me gasp a little being mainly an embedded programmer.
I would vote for...
> [] Check the result of malloc:
Actually, I would
Hi,
It's been a long time since I built openocd (0.3.0), I used to build with
mingw64 and it worked fine, I've tried today to get the latest and build it
under the same environment I used before and I get some errors. So I have a
couple of questions...
The fist problem I get is in the "Jim"
Probably you want to update your MinGW-w64 installation. Under
Windows, TDM64 is the preferred one to use or you can use Cygwin's
MinGW-w64 cross compiler.
Probably. My GCC is 4.5.0. I suspect this is the issue since you are
reporting "gcc version 4.5.2 (GCC)".
I got past the original issue
It has been a while and I think my msys is quite out of date. Have reverted
to building on Linux.
Thanks.
- Original Message -
From: "Freddie Chopin"
To:
Sent: Monday, June 13, 2011 4:22 PM
Subject: Re: [Openocd-development] Status of building using Mingw64?
OpenOCD versions from
