From: d_s_klein on
On Mar 24, 4:05 pm, "Nial Stewart"
<nial*REMOVE_TH...(a)nialstewartdevelopments.co.uk> wrote:
>
> I've always had reasonably prompt responses from FTDI support, you might
> want to ping them to get an answer?
>
> Nial.

I too have gotten prompt responses from FTDI support.

However, I'm still waiting to get a *useful* response from them.

RK
From: -jg on
On Mar 25, 9:31 pm, "Peter Dickerson" <first.l...(a)tiscali.invalid>
wrote:
> I'll give it a go, but time is running out.

Do you have a 'Plan B' ?

-jg
From: Peter Dickerson on
"d_s_klein" <d_s_klein(a)yahoo.com> wrote in message
news:7ac7791f-8d29-4002-aa1b-2cad2a4e4de8(a)t32g2000prg.googlegroups.com...
On Mar 24, 4:05 pm, "Nial Stewart"
<nial*REMOVE_TH...(a)nialstewartdevelopments.co.uk> wrote:
>
> I've always had reasonably prompt responses from FTDI support, you might
> want to ping them to get an answer?
>
> Nial.

I too have gotten prompt responses from FTDI support.

However, I'm still waiting to get a *useful* response from them.
----

I have tried again without any response or ack. I've concluded that they're
filtering out the small fry like me (I'm a consultant, so address !=
client ). I have asked an engineer at the client to pass on the support
request to see if that helps.

The problem is that the product being developed is a replacememt for the
current main product range. Consequently parts for the old product are on
order. The new is very late but we're down to a few EMC issues, my firmware
problem with the VNC1L and teething problems. But it won't be long before
the production staff will be idle if the problem is not resolved. FWIW the
MD/CEO has seen the railcrash coming and resigned, knowing that driver
rarely survives such incidents.

As to the actual Vinculum problem, well, I see a notification that a device
has been inserted but when I try to query what it is with Query Port or
Query Device I get nothing, a long string of FFs and EBs, other jibberish or
a prompt. In the case of a mouse I don't even get the device detected
notification. However, if I restrict myself to USB Flash then it works (but
Query commands aren't needed for that).

Peter


From: Peter Dickerson on
"-jg" <jim.granville(a)gmail.com> wrote in message
news:c2ecb7df-ec69-4e4f-ba5f-164449b18491(a)g28g2000prb.googlegroups.com...
On Mar 25, 9:31 pm, "Peter Dickerson" <first.l...(a)tiscali.invalid>
wrote:
> I'll give it a go, but time is running out.

Do you have a 'Plan B' ?
-----

The plan B that I had was abandoned long ago as unable to fit the time
scale. However, the product range includes some with a user interface and
some without. Only the UI versions are affected. My primary task is to get
the non-UI product working well. I'm pretty happy with that. The UI product
includes a touchpanel display and application engine that talks to the
headless part. I'm not responsible for the applications side but have been
involved in device drivers. Oh, and I designed much of the electronics - so
I smell a linching in the air even though the inclusion of the VNC1L was
imposed on me (and have the emails...)

Peter


From: Andrew Jackson on
> As to the actual Vinculum problem, well, I see a notification that a device
> has been inserted but when I try to query what it is with Query Port or
> Query Device I get nothing, a long string of FFs and EBs, other jibberish or
> a prompt. In the case of a mouse I don't even get the device detected
> notification. However, if I restrict myself to USB Flash then it works (but
> Query commands aren't needed for that).

Is the issue associated only with low speed devices? Have you looked at
any sort of USB trace to see what the Vinculum chip is trying to do? (I
realise that this partly negates what it is trying to do.)

Andrew