On Mon, Jun 22, 2009 at 1:59 PM, Anders Montonen wrote:
>> libusb-win32's development branch (libusb1) has the WinUSB backend. It
>> is not working yet. It is also not API compatible with libusb 1.0.
>> That is an unfortunate situation.
>
> Is libusb-win32 still being developed? The SVN repository
On Jun 22, 2009, at 8:40, Xiaofan Chen wrote:
> You may want to use reply to all. This is not as convenient but it
> is the way
> OpenOCD mailing list is running. Thanks.
That was my intention, but I forgot to change the to-address. Sorry
about that.
> libusb-win32's development branch (libu
2009/6/22 Orin Eman :
> All someone need do is produce a DLL that is called FTD2XX and implements
> (or plans to implement) all the interfaces that OpenOCD uses and release it
> under LGPL. The interfaces can all return failure for now. There would be
> no problem whatsoever releasing a binary l
You may want to use reply to all. This is not as convenient but it is the way
OpenOCD mailing list is running. Thanks.
On Mon, Jun 22, 2009 at 1:34 PM, Anders Montonen wrote:
> On Jun 22, 2009, at 6:15, Xiaofan Chen wrote:
>
>> On Mon, Jun 22, 2009 at 4:02 AM, David Brownell
>> wrote:
>>>
>>> * T
2009/6/21 Zach Welch
> On Sun, 2009-06-21 at 13:20 -0700, David Brownell wrote:
> > On Sunday 21 June 2009, Audrius Urmanavičius wrote:
> > > I can also second Xiaofan, who offers distribution of .zip file with
> > > Cygwin building environment set up, probably with shell script that
> > > does `
On Mon, Jun 22, 2009 at 1:21 PM, Freddie Chopin wrote:
> Xiaofan Chen pisze:
>>> Replacing libusb0.sys fixes the problem - OpenOCD works.
>>
>> I am not 100% clear clear. If you just install the master driver
>> (the inf file for the whole device, not individual interface),
>> does OpenOCD work wit
Xiaofan Chen pisze:
>> Replacing libusb0.sys fixes the problem - OpenOCD works.
>
> I am not 100% clear clear. If you just install the master driver
> (the inf file for the whole device, not individual interface),
> does OpenOCD work with the hacked libusb0.sys or
> the latest SVN version of libus
Just a summary for this thread.
On Sun, Jun 21, 2009 at 11:55 PM, Freddie Chopin wrote:
> Now there is a "clean" version of libusb0.sys. I've installed two
> drivers - for channel A and channel B. OpenOCD is not working...
>
> So - I keep my previous statements - you NEED a hacked version of
> lib
On Sunday 21 June 2009, Xiaofan Chen wrote:
> What do you think about this summary?
Ooooh ... *MUCH* better! Thank you!
No comments other than that, for now.
Except for:
> d) Improve libusb-win32, get the driver digital signed to solve the
> 64bit Windows issues. Some HW vendors may be able
On Mon, Jun 22, 2009 at 4:02 AM, David Brownell wrote:
> * The thread about a "Universal" INF file seemed much more
> productive. Sure, more adapters need to be covered, and
> the library binaries that get bundled into the MSI file
> will need to be the right versions (libusb, libftdi).
>
>
On Mon, Jun 22, 2009 at 7:38 AM, Xiaofan Chen wrote:
> On Sun, Jun 21, 2009 at 11:31 PM, Freddie Chopin wrote:
>> Xiaofan Chen pisze:
>>> It seems to me that you are using libusb-win32
>>> with individual interfaces and I am not sure that would work.
>>
>> I'm not sure I understand you correctly, b
On Mon, Jun 22, 2009 at 4:15 AM, David Brownell wrote:
> On Sunday 21 June 2009, Xiaofan Chen wrote:
>> > Michael has a nice tutorial here on building OpenOCD with different
>> > configurations here.
>> > http://forum.sparkfun.com/viewtopic.php?t=11221
>> >
>>
>> Michael Fischer has since updated t
On Sunday 21 June 2009, Duane Ellis wrote:
> I would like to see this exception *documented* so that it does not
> expand, or continue beyond this exact situation.
The way to "document" this is with a change to the license,
signed on to by *everyone* holding any copyright on the code.
Any previo
2009/6/22 Zach Welch :
> On Sun, 2009-06-21 at 13:20 -0700, David Brownell wrote:
>> On Sunday 21 June 2009, Audrius Urmanavičius wrote:
>> > I can also second Xiaofan, who offers distribution of .zip file with
>> > Cygwin building environment set up, probably with shell script that
>> > does `./bo
On Sunday 21 June 2009, Magnus Lundin wrote:
> >
> Yes the licence is GPL, and there are no exceptions stated, unfortunatley.
>
> It is definitly possible to add an exception to allow linking to non GPL
> libraries and still remain GPL, but it is not possible to force derived
> GPL works to
On Sunday 21 June 2009, Freddie Chopin wrote:
> > You are spreading FUD. Please. Stop. Now.
>
> Why?
Because it's an annoying and counterproductive waste-of-time.
And because the developers aren't particularly keen on your
encouragment that folk should violate the licensing on the
software t
On Sun, Jun 21, 2009 at 11:31 PM, Freddie Chopin wrote:
> Xiaofan Chen pisze:
>> It seems to me that you are using libusb-win32
>> with individual interfaces and I am not sure that would work.
>
> I'm not sure I understand you correctly, but if there are no entries for
> individual channels (...&MI
On Mon, Jun 22, 2009 at 12:19 AM, Freddie Chopin wrote:
> Michael Fischer pisze:
>> here is the driver which was build from the SVN r161 (libusb).
>> Please test it, it should work with composite devices too.
>
> Works here.
>
Now it is clear to me. Thanks. The SVN 161 version works. The released
On Sun, 2009-06-21 at 18:33 -0400, Duane Ellis wrote:
> zach> I am afraid that your intent will not matter even one iota, in a
> court of law.
>
> This is not, and was not ever my intent, I am speaking of what I see as
> the original authors "GPL+[undocumented]-exception" intention.
>
> zach> I
Zach Welch wrote:
> On Sun, 2009-06-21 at 17:38 -0400, Duane Ellis wrote:
>
>> zach> Please DO NOT try to cheat the GPL license. You do not understand how
>> zach> far I am willing to take these matters, and I believe any form of
>> binary
>> zach> distribution to be a violation: a DLL wrapper,
zach> I am afraid that your intent will not matter even one iota, in a
court of law.
This is not, and was not ever my intent, I am speaking of what I see as
the original authors "GPL+[undocumented]-exception" intention.
zach> If you want to make exceptions, then they do not apply to the new
co
On Sun, 2009-06-21 at 17:38 -0400, Duane Ellis wrote:
> zach> Please DO NOT try to cheat the GPL license. You do not understand how
> zach> far I am willing to take these matters, and I believe any form of
> binary
> zach> distribution to be a violation: a DLL wrapper, a binary patch,
> anything!
Zach Welch pisze:
> If all of OpenOCD's users chipped in, I bet each
> of you would pay less than any commercial alternative.
You forgot something [; I don't need to pay for anything, nor does
anyone else. I can build my own executable with ftd2xx. If you will drop
that support, I'll just stay w
zach> Please DO NOT try to cheat the GPL license. You do not understand how
zach> far I am willing to take these matters, and I believe any form of
binary
zach> distribution to be a violation: a DLL wrapper, a binary patch,
anything!
Let me ask this another way. I believe the question is some wh
On Sun, 2009-06-21 at 23:15 +0200, Freddie Chopin wrote:
> Zach Welch pisze:
> > Fix the problems with libusb and libfdti. Period.
>
> This is starting to get ridiculous... As I already wrote somewhere - I
> really would like to, but... I cannot. I'm not a PC programmer, in fact
> I'm a newbie
On Sun, 2009-06-21 at 22:05 +0100, John Devereux wrote:
> Zach Welch writes:
>
> > Harald,
> >
> > Thank you for taking the time to participate in this discussion.
> >
> > On Sat, 2009-06-20 at 12:53 +0200, Harald Kipp wrote:
> >> Zach Welch wrote:
> >> > On Fri, 2009-06-19 at 18:26 +0200, Haral
On Sun, 2009-06-21 at 23:07 +0200, Øyvind Harboe wrote:
> > There must be *some* limit to how far this principle can extend.
> >
> > For example, a non-GPLed FTDI "server" communicating via sockets (or
> > via some other messaging).
>
> Also, I have never read the fine print in GPL that stops Wind
On Sunday 21 June 2009, Øyvind Harboe wrote:
> Also, I have never read the fine print in GPL that stops Windows from
> becoming GPL when GPL code is run under Windows.
See the bit about system libraries. If they're part
of the OS, it's OK to link with them.
__
Zach Welch pisze:
> Fix the problems with libusb and libfdti. Period.
This is starting to get ridiculous... As I already wrote somewhere - I
really would like to, but... I cannot. I'm not a PC programmer, in fact
I'm a newbie in embedded world too, so - sorry, I won't fix libftdi and
libusb, b
On Sun, 2009-06-21 at 13:20 -0700, David Brownell wrote:
> On Sunday 21 June 2009, Audrius Urmanavičius wrote:
> > I can also second Xiaofan, who offers distribution of .zip file with
> > Cygwin building environment set up, probably with shell script that
> > does `./bootstrap`, `./configure --with
> There must be *some* limit to how far this principle can extend.
>
> For example, a non-GPLed FTDI "server" communicating via sockets (or
> via some other messaging).
Also, I have never read the fine print in GPL that stops Windows from
becoming GPL when GPL code is run under Windows.
--
Øyvin
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Zach Welch writes:
> Harald,
>
> Thank you for taking the time to participate in this discussion.
>
> On Sat, 2009-06-20 at 12:53 +0200, Harald Kipp wrote:
>> Zach Welch wrote:
>> > On Fri, 2009-06-19 at 18:26 +0200, Harald Kipp wrote:
>>
>> >> Dynamic linking to proprietary libraries by adding
David Brownell wrote:
> On Sunday 21 June 2009, Paulius Zaleckas wrote:
>> +
>> +if { [info exists ENDIAN] } {
>> + set _ENDIAN $ENDIAN
>> +} else {
>> + set _ENDIAN little
>> +}
>> +
>
> Can this chip actually override its endianness?
> If not, I suggest removing that...
Yes,
On Sun, 2009-06-21 at 11:28 +0200, Freddie Chopin wrote:
> As no satisfying solution has been decided I will try to summarise the
> options I think are fine for Windows users. Please - put away your
> "linux >> windows" attitude aside for a moment and do keep in mind three
> things before procee
Harald,
Thank you for taking the time to participate in this discussion.
On Sat, 2009-06-20 at 12:53 +0200, Harald Kipp wrote:
> Zach Welch wrote:
> > On Fri, 2009-06-19 at 18:26 +0200, Harald Kipp wrote:
>
> >> Dynamic linking to proprietary libraries by adding LoadLibrary and
> >> GetProcAddr
On Sunday 21 June 2009, Audrius Urmanavičius wrote:
> I can also second Xiaofan, who offers distribution of .zip file with
> Cygwin building environment set up, probably with shell script that
> does `./bootstrap`, `./configure --with-ftd2xx-blahblah` and `make`
> there, so that Windows users with
On Sunday 21 June 2009, Xiaofan Chen wrote:
> On Sun, Jun 21, 2009 at 5:45 PM, Xiaofan Chen wrote:
> > Michael has a nice tutorial here on building OpenOCD with different
> > configurations here.
> > http://forum.sparkfun.com/viewtopic.php?t=11221
> >
>
> Michael Fischer has since updated the inst
On Sunday 21 June 2009, Paulius Zaleckas wrote:
> +
> +if { [info exists ENDIAN] } {
> + set _ENDIAN $ENDIAN
> +} else {
> + set _ENDIAN little
> +}
> +
Can this chip actually override its endianness?
If not, I suggest removing that...
I think it's counterproductive to support
On Sunday 21 June 2009, Freddie Chopin wrote:
> Should we take silence as an agreement?
Of course not. It was posted maybe twelve hours ago, but
you got impatient after only seven.
Plus, there's not really anything to be said except that
both of your "options" violate the licensing.
At this poi
On Sun, Jun 21, 2009 at 4:00 PM, Michael Fischer wrote:
> Hello List,
>
> No response, no windows user here which need FTD2XX support?
I am Windows user, and I do need FTD2xx support, unless GPL-compatible
alternatives allows dual inteface (I use Olimex ARM-USB-OCD and I
appreciate it having seri
On Sunday 21 June 2009, Xiaofan Chen wrote:
> Maybe you can create a new poll there for the FTD2XX support.
> I think the Windows users will need the FTD2XX support. It is
> not that easy to get OpenOCD+libusb-win32+libftdi working under
> Windows after all.
To repeat: anyone wanting D2XX support
First I want to say that I am very happy with the OpenOCD-software! I
like it very much.
I have a Chameleon POD from Amontec. This dongle can be programmed to
act as a Wiggler-cable, but also as a JTAG Accelerator interface.
I use it in combination with an ARM processor and a FPGA. Both are
sup
On Jun 21, 2009, at 9:30 AM, Freddie Chopin
wrote:
> Should we take silence as an agreement?
>
Of course not.
> That's pretty interesting - so many posts about such insignificant
> cases
> like whitespaces or type-names, so little posts about such significant
> case as ftd2xx...
>
Person
On Sun, Jun 21, 2009 at 6:30 PM, Freddie Chopin wrote:
> Should we take silence as an agreement?
No. (Wasn't this summary posted yesterday?)
This debate is still alive, give the community
time to consider the options and come up with ideas.
I haven't followed this debate terribly closely, I'm ju
Should we take silence as an agreement?
That's pretty interesting - so many posts about such insignificant cases
like whitespaces or type-names, so little posts about such significant
case as ftd2xx...
4\/3!!
___
Openocd-development mailing list
Open
Michael Fischer pisze:
> here is the driver which was build from the SVN r161 (libusb).
> Please test it, it should work with composite devices too.
Works here.
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lis
Michael Fischer pisze:
> what is the md5sum from your libusb0.sys file
> under:
>
> \windows\system32\drivers
>
> The original file from the binary distribution
> libusb-win32-device-bin-0.1.12.1 is:
>
> 34d6730e198a5b0fce0790a6b4769ef2 *libusb0.sys
880e67f337c7940d3a3b9b843300a6a4 *libusb0.sy
Hello Freddie,
what is the md5sum from your libusb0.sys file
under:
\windows\system32\drivers
The original file from the binary distribution
libusb-win32-device-bin-0.1.12.1 is:
34d6730e198a5b0fce0790a6b4769ef2 *libusb0.sys
Regards,
Michael
-Ursprungliche Nachricht-
Von: openocd-dev
Xiaofan Chen pisze:
> It seems to me that you are using libusb-win32
> with individual interfaces and I am not sure that would work.
I'm not sure I understand you correctly, but if there are no entries for
individual channels (...&MI_00 and ...&MI_01) OpenOCD doesn't work. I
think that the "mast
>Did you try the released version of libusb-win32 which
>is 0.1.12.1. I think it should work as well.
This was the version I used at the beginning. And here I need the
hacked version from the page I send the info about the composite
devices.
Regards,
Michael
-Ursprüngliche Nachricht-
Von:
Xiaofan Chen pisze:
> Have you tried this with all of the three JTAG tools?
Nope [; I only have JTAGkey here, but the only difference visible to
drivers is the VID/PID combination [;
> It seems to me that you are using libusb-win32 with individual
> interfaces and I am not sure that would work.
On Sun, Jun 21, 2009 at 11:20 PM, Michael Fischer wrote:
> many thanks for this hint. The 1.0.0.0 was not working here
> with OpenOCD. The libusb build based on 0.1.12.1 is working
> now.
>
> But this is the same version which the user can download from
> sourcefore. Perhaps someone should create a
Hi Xiaofan,
many thanks for this hint. The 1.0.0.0 was not working here
with OpenOCD. The libusb build based on 0.1.12.1 is working
now.
But this is the same version which the user can download from
sourcefore. Perhaps someone should create a 0.1.12.2 for
using with OpenOCD?
Regards,
Michael
--
2009/6/21 Freddie Chopin :
> I attach a patch which adds a universal .inf file for FT2232 based JTAGs to
> the tree in \contrib\libusb-win32_ft2232_driver\. Currently it has 3
> different devices inside:
>
> - normal FT2232
> - Amontec JTAGkey
> - Egnite Turtelizer 2
>
> Of course some more devices
On Sun, Jun 21, 2009 at 5:28 PM, Freddie Chopin wrote:
> So in reality I see only two solutions:
>
> 1. A ftd2xx.dll wrapper library, which would be published under GPL with
> exception for ftd2xx.dll. Such library would dynamically link ftd2xx and
> - as an open-source solution - could be linked w
I attach a patch which adds a universal .inf file for FT2232 based JTAGs
to the tree in \contrib\libusb-win32_ft2232_driver\. Currently it has 3
different devices inside:
- normal FT2232
- Amontec JTAGkey
- Egnite Turtelizer 2
Of course some more devices should be added to make that "truly
un
On Sun, Jun 21, 2009 at 9:00 PM, Michael Fischer wrote:
> Hello List,
>
> No response, no windows user here which need FTD2XX support?
>
I saw you have a poll here. So far 100% users (2 out of 2) are Windows
users. The samples may be too small now. But I believe there are
more Windows users than o
On Sun, Jun 21, 2009 at 7:08 PM, Michael Fischer wrote:
> Hello List,
>
> an hacked version of libusb0.sys is not needed anymore.
> With the hacked version it is still not allowed to distribute
> it because how should the user create the hacked version?
>
> I could build a libusb driver based on SV
On Sun, 2009-06-21 at 15:00 +0200, Michael Fischer wrote:
> Hello List,
>
> No response, no windows user here which need FTD2XX support?
>
> Best regards,
>
> Michael
Well 2 points come to mind...
1 - as pointed out before, most of us windows users are interested in
plug and play
2 - this is a
Hello List,
No response, no windows user here which need FTD2XX support?
Best regards,
Michael
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Sun, Jun 21, 2009 at 5:45 PM, Xiaofan Chen wrote:
> Michael has a nice tutorial here on building OpenOCD with different
> configurations here.
> http://forum.sparkfun.com/viewtopic.php?t=11221
>
> It needs some updates.
>
Michael Fischer has since updated the instruction and
he tested it with O
On Sun, Jun 21, 2009 at 8:02 PM, Michael Fischer wrote:
>>Moreover, I do not have XP 64 or Vista 64 to test it.
>>So I guess it is better not to distribute 64bit
>>libusb-win32 driver.
> We do not want to distribute libusb, we want to distribute
> OpenOCD. And here libftdi is not working under 64 b
>Moreover, I do not have XP 64 or Vista 64 to test it.
>So I guess it is better not to distribute 64bit
>libusb-win32 driver.
We do not want to distribute libusb, we want to distribute
OpenOCD. And here libftdi is not working under 64 bit, is
this correct?
Regards,
Michael
-Ursprüngliche Nac
David Brownell wrote:
> On Friday 19 June 2009, Dirk Behme wrote:
>> Seems to work :) THANKS!!
>
> Good. I look forward to seeing more things start to work
> there ... and the next release after 0.2.0 having some
> support for Cortex-A8! :)
Don't hesitate to send everything you like to get test
On Sun, Jun 21, 2009 at 7:15 PM, Xiaofan Chen wrote:
> On Sun, Jun 21, 2009 at 7:08 PM, Michael Fischer wrote:
>> Hello List,
>>
>> an hacked version of libusb0.sys is not needed anymore.
>> With the hacked version it is still not allowed to distribute
>> it because how should the user create the h
Adds configuration for Cortina Systems CS351x CPUs.
They are based on FA526 core.
Index: tcl/target/cs351x.cfg
===
--- tcl/target/cs351x.cfg (revision 0)
+++ tcl/target/cs351x.cfg (revision 0)
@@ -0,0 +1,30 @@
+if { [info
On Sun, Jun 21, 2009 at 7:08 PM, Michael Fischer wrote:
> Hello List,
>
> an hacked version of libusb0.sys is not needed anymore.
> With the hacked version it is still not allowed to distribute
> it because how should the user create the hacked version?
>
> I could build a libusb driver based on SV
Hello List,
an hacked version of libusb0.sys is not needed anymore.
With the hacked version it is still not allowed to distribute
it because how should the user create the hacked version?
I could build a libusb driver based on SVN trunk version 161,
under MinGW. The drivers version is 1.0.0.0.
Th
On Sun, Jun 21, 2009 at 6:38 PM, Xiaofan Chen wrote:
> On Sun, Jun 21, 2009 at 6:33 PM, Michael Fischer wrote:
>> if the installer support more than FT2232 device, it must install
>> all the driver this way. I think it is not a good idea, and the
>> user should point to the directory where the driv
On Sun, Jun 21, 2009 at 6:33 PM, Michael Fischer wrote:
> Hello Xiaofan,
>
> if the installer support more than FT2232 device, it must install
> all the driver this way. I think it is not a good idea, and the
> user should point to the directory where the driver exist.
> Like the normal way of inst
Hello Xiaofan,
if the installer support more than FT2232 device, it must install
all the driver this way. I think it is not a good idea, and the
user should point to the directory where the driver exist.
Like the normal way of installing driver.
Regards,
Michael
-Ursprüngliche Nachricht-
On Sun, Jun 21, 2009 at 6:23 PM, Michael Fischer wrote:
>>I've checked that now, and normal libusb0.sys seems to work fine, but
>>you can never be sure, maybe after reset I will stop working or sth...
>
> I could not install my ftd2xx device here the normal way. I must
> use a composite version of
>I've checked that now, and normal libusb0.sys seems to work fine, but
>you can never be sure, maybe after reset I will stop working or sth...
I could not install my ftd2xx device here the normal way. I must
use a composite version of the inf file.
Regards,
Michael
-Ursprungliche Nachricht-
On Sun, Jun 21, 2009 at 6:00 PM, Freddie Chopin wrote:
> Xiaofan Chen pisze:
>> Using MinGW/Msys may be complicated. But it is not that difficult to use
>> Cygwin. Installaing Cygwin it can be an issue for average Windows users
>> though.
>
> So it's complicated anyway [;
Yes Windows is complicate
Xiaofan Chen pisze:
> Using MinGW/Msys may be complicated. But it is not that difficult to use
> Cygwin. Installaing Cygwin it can be an issue for average Windows users
> though.
So it's complicated anyway [;
> libusb-win32 device driver has the binary distribution. It is also very easy
> to buil
On Sun, Jun 21, 2009 at 3:58 PM, Freddie Chopin wrote:
> It's not that they (we?) don't want to do something. Building OpenOCD
> from source on Windows using MinGW + MSYS really IS complicated.
> Building libusb and libftdi is even more complicated /; The process
> alone may not be hard (mostly con
As no satisfying solution has been decided I will try to summarise the
options I think are fine for Windows users. Please - put away your
"linux >> windows" attitude aside for a moment and do keep in mind three
things before proceeding:
1. Windows users usually have no knowledgle of linux and l
Thomas A. Moulton pisze:
> In the example above 114k file at 8KB/sec is 14 seconds vs 11KB/sec is
> 10 seconds - a difference of 4 seconds - I for one do not care and my
> flash is smaller than that!
Indeed - flash upload speed is not the most important speed, but the
stepping speed is 100% propo
Michael Bruck wrote:
> Why not just offer a pre-configured linux-VM that cross-compiles for
> mingw or cygwin on the user's PC?
>
Because (a) that promotes linking against a non-GPL library, even if the
binary is not distributed, and (b) because it still won't help on 64-bit
windows.
cu
Michael
On Sun, Jun 21, 2009 at 1:28 AM, Joseph Kuss wrote:
> Also by the way, what do these error messages mean ?:
> Error: SWJ-DP STICKY ERROR
> Error: dcb_dhcsr 0x30003, nvic_shcsr 0x2, nvic_cfsr 0x0, nvic_bfar
> 0xe000edf8
>
>
> On Sat, Jun 20, 2009 at 4:19 PM, Joseph Kuss wrote:
>
>> Dear sir
Michael Schwingen pisze:
> The consensus here seems to be that most windows users do not want to
> build openocd themselves, even if it provides better performance.
It's not that they (we?) don't want to do something. Building OpenOCD
from source on Windows using MinGW + MSYS really IS complicate
On Sat, Jun 20, 2009 at 8:05 PM, Michael
Schwingen wrote:
> Zach Welch wrote:
>>> BTW: one possible solution for 64-bit windows would be to ship an
>>> openocd appliance - ie. a VM image containing a minimal linux system
>>> together with openocd & libraries.
>>>
>>> Users would need to install VMw
Xiaofan Chen wrote:
> Yes this is a possible solution. But then will you use it if you are a
> Vista 64 user and there is a good alternative using private build with
> FTD2XX?
>
> The real fix is to get libusb-win32 working on Vista 64 (with digital
> signing).
>
Sure - I am all in favour of get
84 matches
Mail list logo
