[pvrusb2] PVRUSB2 on NSLU2 with 2.6.21 dies after loading firmware

[Mike Isely]

On Mon, 28 May 2007, Phil Endecott wrote:

> Dear All,
> 
> About a year ago I had my PVRUSB2 working with my Linksys NSLU2.
> 
> Since then the PVRUSB2 has laid idle, though the NSLU2 has been 
> upgraded a number of times.  The NSLU2 is now fully supported by the 
> mainline kernel and by Debian; I'm using the Debian-packaged 2.6.21 
> kernel.  When I plugged in my PVRUSB2 last week I was hoping that it 
> would just work, since the PVRUSB2 drivers are also now in the 
> mainline.  Unfortunately, I see this in syslog:
> 
> May 23 23:37:17 chad kernel: usb 3-1.4.2: new high speed USB device 
> using ehci_hcd and address 19
> May 23 23:37:17 chad kernel: usb 3-1.4.2: configuration #1 chosen from 
> 1 choice
> May 23 23:37:18 chad kernel: pvrusb2: Device microcontroller firmware 
> (re)loaded; it should now reset and reconnect.
> 
> ..and no further activity.
> 
> I'm using the same firmware files that worked last year.
> 
> Can anyone suggest what could be causing this, or what I should do next 
> to debug it?
> 
> Many thanks,
> 
> Phil.
> 

There was a change to the firmware loader; previously it required the 
firmware image size to be a multiple of 8192 bytes.  Now the requirement 
is relaxed to 4 bytes (and the loader implementation reworked 
accordingly).

However unless the new loader has a bug which manifests itself only on 
the NSLU2's architecture (that's ARM, right?) then I don't think this 
could be it.

Do you even see a USB disconnect message after the firmware is loaded?

If you then unplug and replug the device do you see any sign of life 
anywhere?

My first guess is that the FX2 firmware was incorrectly loaded and this 
cause the FX2 to crash rather than reinitialize after it was reset.  
However in that case I'd at least expect to see the USB disconnect 
message resulting from the FX2 reset that the hardware causes after its 
firmware has been loaded.

Are you sure the firmware image is OK?  (Probably it is if you haven't 
changed anything there.)  I'd try to make sure you are using the correct 
firmware image since the 29xxx and 24xxx firmware images are not 
cross-compatible.  If you have an x86 Linux PC laying around somewhere, 
try the same thing there with the same firmware image and see if it 
works.  If it doesn't work then we know the problem is not likely 
having to do with the NSLU2 setup.  If it does work then we know that 
some kind of processor architecture incompatibility may have crept into 
the driver.  (And if that is the case I'd recommend trying various 
standalone drivers versions in order to find the spot where it broke.)

  -Mike


-- 
                        |         Mike Isely          |     PGP fingerprint
     Spammers Die!!     |                             | 03 54 43 4D 75 E5 CC 92
                        |   isely @ pobox (dot) com   | 71 16 01 E2 B5 F5 C1 E8
                        |                             |