Re: Persistent stall in the Cypress FX2 FIFO
- From: "A.D." <stevenson@xxxxxxxxxxx>
- Date: Mon, 21 Nov 2005 13:04:41 +0100
"Antti Keskinen" <antti.keskinen@xxxxxxxxx> ha scritto nel messaggio
news:dls3d5$2vrr$1@xxxxxxxxxxxxxxxxx
> Hello !
>
> Are you absolutely certain that the endpoint is STALLed ? STALL condition
> usually means that the endpoint has received an invalid USB request. In
> this case, and looking at the FX2 TRM, it might mean you're not serving
> the IBN and PING requests sent by the host.
[CUT]
Hi Antti,
thank you for your answer!
You're right, it doesn't looks like a real stall condition... Moreover in my
application I use the AUTOIN/AUOTOUT feature, so the CPU does not access the
data (data are directly committed to the FIFOs), and so the CPU doesn't need
to handle the IBN and PING interrupt (Am I right?).
Today I noticed that the condition that triggers this apparent "stall" is
sending 2 bulk packets without empting the FIFO first, it doesn't matter how
long they are (it appends even for 4 byte long packets). If I download a
packet from the FIFO before sending the next one all works fine... But if
the EP receive two packets it doesn't take other packets, even if I empty
the FIFO: I have to reset the FX2!
I'm really puzzled... :-)
Regards,
A.D.
.
- Follow-Ups:
- Re: Persistent stall in the Cypress FX2 FIFO
- From: Antti Keskinen
- Re: Persistent stall in the Cypress FX2 FIFO
- References:
- Persistent stall in the Cypress FX2 FIFO
- From: A.D.
- Re: Persistent stall in the Cypress FX2 FIFO
- From: Antti Keskinen
- Persistent stall in the Cypress FX2 FIFO
- Prev by Date: Re: PIC PSP port bus contention
- Next by Date: Re: Ok, I have to join the windows world ...
- Previous by thread: Re: Persistent stall in the Cypress FX2 FIFO
- Next by thread: Re: Persistent stall in the Cypress FX2 FIFO
- Index(es):
Relevant Pages
|