[linux-dvb] DVB USB receiver stopped reporting correct USB ID

Alistair Buxton a.j.buxton at gmail.com
Sat Sep 20 20:51:48 CEST 2008


2008/9/20 Michael Sanders <msanders at fenza.com>:

> Thanks for you ideas. I have attached the full dmesg as suggested.
>
> I don't think the problem is a cold/warm state issue. When I used the
> device for the first time, I saw a warning that it (correct name was
> given) was it its cold state and that firmware was not found. Adding
> the firmware fixed the problem and then it worked fine. i.e. in the
> cold state, it did not show the EZ-USB id.

That's odd. However, there is no difference between cold state and the
current state. EZ-USB devices usually have a very small I2C eeprom
which holds nothing except for the device IDs. It looks like that chip
has either been wiped or has blown.

You should still be able to force the firmware loading, after which it
should go into warm state as normal. There are two ways you could do
that. There is a tool called "fxload" which can load the firmware, but
it uses a different format to the kernel drivers for the firmware
file. It needs intel hex format (ihx). You could alternatively add the
EZ-USB development ID to the list of IDs for the kernel driver.

Unfortunately neither of those methods will be a permanent fix. You
will need to reprogram the I2C eeprom with the correct USB IDs in
order to do that. That can be done with fxload and a special firmware
or there is a tool available from Cypress which can do it - although
it is Windows only.

To the list: Does anyone know how to convert the *.fw files into ihx
format for use with fxload?

-- 
Alistair Buxton
a.j.buxton at gmail.com



More information about the linux-dvb mailing list