I dropped FTDI for similar reasons and stuck a MAX3420E onto the target
deice. Then I used WinUSB driver on the PC side and though things are not
perfect (I never did find out how to flush EP2 for example) they are much
quicker and cleaner and more visible.
And, let me be honest, anyone who is using Pascal is a wee bit behind the
times and/or academic.
Bill
"LittleAlex" <alex.louie@email.com> wrote in message
news:13c612df-d63c-41a4-9ade-857cad0fd486@o40g2000prn.googlegroups.com...
On Nov 23, 11:45 pm, "Meindert Sprang"
<m...@NOJUNKcustomORSPAMware.nl> wrote:
> "LittleAlex" <alex.lo...@email.com> wrote in message
>
> news:c7ff73ec-e879-4083-ad15-60d33f36af73@k24g2000pri.googlegroups.com...
>
>
>
>
>
> > On Nov 21, 6:31 am, ashu <ashutosh.ghildi...@gmail.com> wrote:
> > > Hello All,
>
> > > I have two questions. They might be very basic and foolish :)
>
> > > I use In circuit emulators and debuggers regularly. One of the
> > > constant problems I face is when the MS WindowsXP fails to recongise
> > > the device. Sometimes it is the FTDI USB chip driver which goes
> > > haywire or sometimes its something else. It shows the name of the
> > > device in device manage
>
> > > Normally I circumvent this problem by reinstallling the USB drivers
> > > again.
>
> > > Is there any easy way ?
>
> > > Secondly, is there any article or book to understand how does Windows
> > > XP recognize these USB ICD and ICEs, and where does it install these
> > > drivers and how does it manage it for better understanding of the
> > > same.
>
> > > thanks and regs
> > > ashu
>
> > I've been deep in side the FTDI drivers, and they would need to be
> > improved greatly before they were cr@p.
>
> > You're on the right track - because of problems with the FTDI driver
> > (s), Windows winds up installing many different copies of the driver,
> > and on occasion uses the wrong one. (On occasion uses the right one?)
>
> I have developed products with the FTDI chips that run 24/7/365 on ships.
> I
> have never had a report that these drivers ar crappy. Instead, I believe
> that the serial-USB solution form FTDI is one of the best on the market.
>
> I think your problem is Windows itself.
>
> Meindert- Hide quoted text -
>
> - Show quoted text -
Nope, it's their driver. Their bugs start rearing their ugly heads
when you have FTDI-based devices from more than one manufacturer.
Reply by Meindert Sprang●November 27, 20082008-11-27
"LittleAlex" <alex.louie@email.com> wrote in message
news:13c612df-d63c-41a4-9ade-857cad0fd486@o40g2000prn.googlegroups.com...
> Nope, it's their driver. Their bugs start rearing their ugly heads
> when you have FTDI-based devices from more than one manufacturer.
Anymore details? I'd be interested to know.
meindert
Reply by Paul Carpenter●November 26, 20082008-11-26
In article <13c612df-d63c-41a4-9ade-
857cad0fd486@o40g2000prn.googlegroups.com>, alex.louie@email.com says...
> On Nov 23, 11:45=A0pm, "Meindert Sprang"
> <m...@NOJUNKcustomORSPAMware.nl> wrote:
> > "LittleAlex" <alex.lo...@email.com> wrote in message
> >
> > news:c7ff73ec-e879-4083-ad15-60d33f36af73@k24g2000pri.googlegroups.com.=
..
> > > On Nov 21, 6:31 am, ashu <ashutosh.ghildi...@gmail.com> wrote:
> > > > Hello All,
> >
> > > > I have two questions. They might be very basic and foolish :)
> >
> > > > I use In circuit emulators and debuggers regularly. One of the
> > > > constant problems I face is when the MS WindowsXP fails to recongis=
e
> > > > the device. Sometimes it is the FTDI USB chip driver which goes
> > > > haywire or sometimes its something else. It shows the name of the
> > > > device in device manage
> >
> > > > Normally I circumvent this problem by reinstallling the USB drivers
> > > > again.
> >
> > > > Is there any easy way ?
> >
> > > > Secondly, is there any article or book to understand how does Windo=
ws
> > > > XP recognize these USB ICD and ICEs, and where does it install thes=
e
> > > > drivers and how does it manage it for better understanding of the
> > > > same.
> >
> > > > thanks and regs
> > > > ashu
> >
> > > I've been deep in side the FTDI drivers, and they would need to be
> > > improved greatly before they were cr@p.
> >
> > > You're on the right track - because of problems with the FTDI driver
> > > (s), Windows winds up installing many different copies of the driver,
> > > and on occasion uses the wrong one. =A0(On occasion uses the right on=
e?)
> >
> > I have developed products with the FTDI chips that run 24/7/365 on ship=
s. I
> > have never had a report that these drivers ar crappy. Instead, I believ=
e
> > that the serial-USB solution form FTDI is one of the best on the market=
.
> >
> > I think your problem is Windows itself.
> >
> > Meindert- Hide quoted text -
> >
> > - Show quoted text -
>=20
> Nope, it's their driver. Their bugs start rearing their ugly heads
> when you have FTDI-based devices from more than one manufacturer.
Having had to deal with the D2XX API and some of its version control=20
issues, there are issues where you need to know the version of the
driver BEFORE you run any application, as there are ways to get
simple buffer overruns in your application!
Their SPI calls to D2XX are overkill.
Driver assumes only ONE device of ONE type is connected.
Don't even get me on the D2XX/VCP changeover issues.
--=20
Paul Carpenter | paul@pcserviceselectronics.co.uk
<http://www.pcserviceselectronics.co.uk/> PC Services
<http://www.pcserviceselectronics.co.uk/fonts/> Timing Diagram Font
<http://www.gnuh8.org.uk/> GNU H8 - compiler & Renesas H8/H8S/H8 Tiny
<http://www.badweb.org.uk/> For those web sites you hate
Reply by LittleAlex●November 26, 20082008-11-26
On Nov 22, 11:56=A0pm, Chris H <ch...@phaedsys.org> wrote:
> In message <4928A3F3.110A7...@yahoo.com>, CBFalconer
> <cbfalco...@yahoo.com> writes
>
>
>
>
>
> >Chris H wrote:
> >> CBFalconer <cbfalco...@yahoo.com> writes
> >>> ashu wrote:
>
> >... snip ...
>
> >>>> Secondly, is there any article or book to understand how does
> >>>> Windows XP recognize these USB ICD and ICEs, and where does it
> >>>> install these drivers and how does it manage it for better
> >>>> understanding of the same.
>
> >>> Your problems revolve around using the buggy Windows OS. =A0Dump
> >>> it, and install Linux. =A0Totally free, full source, etc.
>
> >> Complete red herring. =A0Linux is also buggy.....
> >> Having the full source does not always help.
>
> >No, but it gives you a fighting chance.
>
> Not really. Some users don't have a clue even with the source.
>
> >And, even if you don't use
> >the source, notice that Linux bugfixes can occur within days of bug
> >reports.
>
> Or months later.
>
> > With windows, about the earliest possible is 1 year, and
> >more often the bug is just ignored.
>
> MS can bring out bug fixes within a few days...... but then they do have
> a proper bug fix control system
>
> You are just making things up or wilfully lying. =A0It is this sort of
> religious bigotry that gets FOSS people such a bad name,
>
> --
> \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
> \/\/\/\/\ Chris Hills =A0Staffs =A0England =A0 =A0 /\/\/\/\/
> \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/- Hide quoted text -
>
> - Show quoted text -
"they do have a proper bug fix control system"
No, no they do not. When was the last time YOU worked there, and saw
their bug-control system at work? They don't even have a proper
version control system; the idea that they have a functional bug
tracking system is laughable.
Another problem is that they off-shore almost the entire software QA
process to the lowest bidder. Then they farm out the auditing of the
QA process, also to the lowest bidder.
Reply by LittleAlex●November 26, 20082008-11-26
On Nov 23, 11:45=A0pm, "Meindert Sprang"
<m...@NOJUNKcustomORSPAMware.nl> wrote:
> "LittleAlex" <alex.lo...@email.com> wrote in message
>
> news:c7ff73ec-e879-4083-ad15-60d33f36af73@k24g2000pri.googlegroups.com...
>
>
>
>
>
> > On Nov 21, 6:31 am, ashu <ashutosh.ghildi...@gmail.com> wrote:
> > > Hello All,
>
> > > I have two questions. They might be very basic and foolish :)
>
> > > I use In circuit emulators and debuggers regularly. One of the
> > > constant problems I face is when the MS WindowsXP fails to recongise
> > > the device. Sometimes it is the FTDI USB chip driver which goes
> > > haywire or sometimes its something else. It shows the name of the
> > > device in device manage
>
> > > Normally I circumvent this problem by reinstallling the USB drivers
> > > again.
>
> > > Is there any easy way ?
>
> > > Secondly, is there any article or book to understand how does Windows
> > > XP recognize these USB ICD and ICEs, and where does it install these
> > > drivers and how does it manage it for better understanding of the
> > > same.
>
> > > thanks and regs
> > > ashu
>
> > I've been deep in side the FTDI drivers, and they would need to be
> > improved greatly before they were cr@p.
>
> > You're on the right track - because of problems with the FTDI driver
> > (s), Windows winds up installing many different copies of the driver,
> > and on occasion uses the wrong one. =A0(On occasion uses the right one?=
)
>
> I have developed products with the FTDI chips that run 24/7/365 on ships.=
I
> have never had a report that these drivers ar crappy. Instead, I believe
> that the serial-USB solution form FTDI is one of the best on the market.
>
> I think your problem is Windows itself.
>
> Meindert- Hide quoted text -
>
> - Show quoted text -
Nope, it's their driver. Their bugs start rearing their ugly heads
when you have FTDI-based devices from more than one manufacturer.
Reply by ●November 24, 20082008-11-24
On 22 Nov, 01:53, CBFalconer <cbfalco...@yahoo.com> wrote:
> ashu wrote:
>
> > I have two questions. They might be very basic and foolish :)
>
> > I use In circuit emulators and debuggers regularly. One of the
> > constant problems I face is when the MS WindowsXP fails to
> > recongise the device. Sometimes it is the FTDI USB chip driver
> > which goes haywire or sometimes its something else. It shows
> > the name of the device in device manage
>
> > Normally I circumvent this problem by reinstallling the USB
> > drivers again.
>
> > Is there any easy way ?
>
> > Secondly, is there any article or book to understand how does
> > Windows XP recognize these USB ICD and ICEs, and where does it
> > install these drivers and how does it manage it for better
> > understanding of the same.
>
> Your problems revolve around using the buggy Windows OS. =A0Dump it,
> and install Linux. =A0Totally free, full source, etc.
>
> --
> =A0[mail]: Chuck F (cbfalconer at maineline dot net)
> =A0[page]: <http://cbfalconer.home.att.net>
> =A0 =A0 =A0 =A0 =A0 =A0 Try the download section.
not a very useful post is it?
WinXP Market share is 89.8% and Vista is 6.3%..... why would you limit
your product to 3.8% of the market?
Reply by Meindert Sprang●November 24, 20082008-11-24
"LittleAlex" <alex.louie@email.com> wrote in message
news:c7ff73ec-e879-4083-ad15-60d33f36af73@k24g2000pri.googlegroups.com...
> On Nov 21, 6:31 am, ashu <ashutosh.ghildi...@gmail.com> wrote:
> > Hello All,
> >
> > I have two questions. They might be very basic and foolish :)
> >
> > I use In circuit emulators and debuggers regularly. One of the
> > constant problems I face is when the MS WindowsXP fails to recongise
> > the device. Sometimes it is the FTDI USB chip driver which goes
> > haywire or sometimes its something else. It shows the name of the
> > device in device manage
> >
> > Normally I circumvent this problem by reinstallling the USB drivers
> > again.
> >
> > Is there any easy way ?
> >
> > Secondly, is there any article or book to understand how does Windows
> > XP recognize these USB ICD and ICEs, and where does it install these
> > drivers and how does it manage it for better understanding of the
> > same.
> >
> > thanks and regs
> > ashu
>
> I've been deep in side the FTDI drivers, and they would need to be
> improved greatly before they were cr@p.
>
> You're on the right track - because of problems with the FTDI driver
> (s), Windows winds up installing many different copies of the driver,
> and on occasion uses the wrong one. (On occasion uses the right one?)
I have developed products with the FTDI chips that run 24/7/365 on ships. I
have never had a report that these drivers ar crappy. Instead, I believe
that the serial-USB solution form FTDI is one of the best on the market.
I think your problem is Windows itself.
Meindert
Reply by CBFalconer●November 23, 20082008-11-23
Chris H wrote:
> CBFalconer <cbfalconer@yahoo.com> writes
>
... snip ...
>
>> With windows, about the earliest possible is 1 year, and
>> more often the bug is just ignored.
>
> MS can bring out bug fixes within a few days...... but then
> they do have a proper bug fix control system
Of course. That is why the Windows bug on an extra backspace over
a tab lasted 10 years or more. Has it ever been fixed?
--
[mail]: Chuck F (cbfalconer at maineline dot net)
[page]: <http://cbfalconer.home.att.net>
Try the download section.
Reply by Chris H●November 23, 20082008-11-23
In message <4928A3F3.110A726A@yahoo.com>, CBFalconer
<cbfalconer@yahoo.com> writes
>Chris H wrote:
>> CBFalconer <cbfalconer@yahoo.com> writes
>>> ashu wrote:
>>>
>... snip ...
>>>
>>>> Secondly, is there any article or book to understand how does
>>>> Windows XP recognize these USB ICD and ICEs, and where does it
>>>> install these drivers and how does it manage it for better
>>>> understanding of the same.
>>>
>>> Your problems revolve around using the buggy Windows OS. Dump
>>> it, and install Linux. Totally free, full source, etc.
>>
>> Complete red herring. Linux is also buggy.....
>> Having the full source does not always help.
>
>No, but it gives you a fighting chance.
Not really. Some users don't have a clue even with the source.
>And, even if you don't use
>the source, notice that Linux bugfixes can occur within days of bug
>reports.
Or months later.
> With windows, about the earliest possible is 1 year, and
>more often the bug is just ignored.
MS can bring out bug fixes within a few days...... but then they do have
a proper bug fix control system
You are just making things up or wilfully lying. It is this sort of
religious bigotry that gets FOSS people such a bad name,
--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
>>
>>> Secondly, is there any article or book to understand how does
>>> Windows XP recognize these USB ICD and ICEs, and where does it
>>> install these drivers and how does it manage it for better
>>> understanding of the same.
>>
>> Your problems revolve around using the buggy Windows OS. Dump
>> it, and install Linux. Totally free, full source, etc.
>
> Complete red herring. Linux is also buggy.....
> Having the full source does not always help.
No, but it gives you a fighting chance. And, even if you don't use
the source, notice that Linux bugfixes can occur within days of bug
reports. With windows, about the earliest possible is 1 year, and
more often the bug is just ignored.
--
[mail]: Chuck F (cbfalconer at maineline dot net)
[page]: <http://cbfalconer.home.att.net>
Try the download section.