Re: BF533 / ISP1761 USB Host enumerating problem

On Mar 17, 4:07 pm, "Robson Tovo" <robson.t...@xxxxxxxxx> wrote:
Hello people.

I'm using BlackFin BF533 EZ-Kit with ISP1761 as a USB Host Controller.

I could succesfully enumerate the internal root hub thanks to the
documentation from NXP: AN10037, AN10054.
(BTW, also found out some corrections to AN10037, such as writing HC
Status Buffer Register)

Well, I can send and receive tokens to the root hub, set its address and
power the ports using the SetFeature request.

Then, my program keeps polling the hub via GetPortStatus, waiting for my
Full-Speed device to be physically connected to the port.

Once the hub detects it, I got the following:
wPortChange: 0x0001
wPortStatus: 0x0001

After that, the program issues a PORT_RESET and Gets Port Status again:
wPortChange: 0x0011 <-- Port was reset, right?
wPortStatus: 0x0001

(I also assured the port was reset by viewing the 10ms SE0 on the line)

Then, if I GetPorStatus again (one or more times), I get:
wPortChange: 0x0003
wPortStatus: 0x0001

From the USB 2.0 Spec, I understand this means port was disabled due to an
Port_Error condition.

I have been trying to solve this question for the last week: Why do I get
this Port_Error?

I wonder if any of you have already passed through this kind of problem or
have any clue about it.

(Just for testing, I try to talk to the device issuing an
GetDeviceDescriptor (at address 0), but the Setup token's PTD fields
return the 'H' and 'X' error flags.)

Thanks in advance.

This probably isn't the best group to be asking this on; maybe try
comp.arch.embedded or something. It does sound like you're doing
everything right. From what I understand, Port_Error events are
probably signal-integrity-related, but that's just from my reading of
the USB spec. You should see the port-enabled bit (0x02) set at the
end of the port reset, after which you can start enumeration.

My opinion: avoid USB if at all possible. The stress that I've had
over the years mucking with USB has taken untold years off of my life,
I'm sure. Writing a host driver (as you seem to be for the ISP1761,
which is I will say the nicest USB controller I've used) is about as
enjoyable as having bamboo shoots shoved under your fingernails.

Good luck.

Jason
.

Relevant Pages

  • Re: USB 2.0 crawling / mystification under XP SP2
    ... His laptop's USB is slow. ... It has 3 USB ports in the back. ... USB root hub, whose Device ID says it's 2.0, and driver says its ... that each Root Hub is associated with one of your physical connectors. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: USB 2.0 Problems
    ... downloading some updated VIA drivers all to no avail. ... Root Hub Following the recommendation I disconnected from the ... first port and plugged the device into each and every port all of which ... At this point I plugged the USB cable into ...
    (microsoft.public.windowsxp.hardware)
  • Re: 20-30 sec surfing lag after short idle time?
    ... Modem connects directly to your PC? ... Sounds like your NIC or USB ... Root hub is "Napping" and the delay you note is due to the ... and tons of drive space on 2 drives. ...
    (microsoft.public.windowsxp.general)
  • Re: USB 2 or 1
    ... in response to Ed Cryer's plea for some way to tell which of his USB ... 'power' tab under properties from the 'Device Manager'. ... identified which root hub is the USB2 root hub, ... drive and plugging it into each socket in turn, ...
    (uk.comp.misc)
  • Re: BF533 / ISP1761 USB Host enumerating problem
    ... I'm using BlackFin BF533 EZ-Kit with ISP1761 as a USB Host Controller. ... I could succesfully enumerate the internal root hub thanks to the ... Well, I can send and receive tokens to the root hub, set its address ... the program issues a PORT_RESET and Gets Port Status ...
    (comp.dsp)