Charlie Flynn wrote:
>
> Georg Acher wrote:
>
> > On Fri, Aug 18, 2000 at 01:26:32AM +0000, Charlie Flynn wrote:
> > > Hi George
> > >
> > > I have just tried using the alternative driver uhci.o without success.
> >
> > That is a very strong indication that your code has some ... problems.
>
> I managed to get it to work (using usb-uhci.o) by retransmitting the first 64-byte
> packet. In otherwords if I have (say) 'X' bytes to send I send the 1st 64 bytes twice
> then I can send the remaining packets as normal.
> I have successfully sent upto 16384 bytes from the iPAQ to the PC using this kludge.
>I
> will take a CATC trace with and without the kludge. It looks like some sort of timing
> problem.
>
It looks like the data toggle bit of the first packet is wrong.
It should start with DATA0 and the next packet should be a DATA1
followed by a DATA0 and so on.
Roman
> >
> > How do you initialize the URBs?
>
> I use the FILL_BULK_URB macro as per the Programmer's Ref Manual.
>
> >
> > > /* at this point the iPAQ receives the 64 bytes and returns a 63 byte packet */
> > > return 0;
> > > }
> > >
> > > /* call back is as simple as this - it is never called if I send <= 64 bytes. If
> > > I send > 64 bytes it reports only pktlen-64*/
> > > my_rx_complete(urb_t *purb)
> > > {
> > > printk("RXComplete Called Packet=%d",pkt_count);
> > > }
> >
> > I assume you mean urb->actual_length?
>
> Yes. The point I was trying to make was the callback function was never being called
>if
> I sent less or equal to 64 bytes.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
