On Thu, 15 Dec 2005, Arnold Ho wrote:
> On 12/15/05, Patrick Boettcher <patrick.boettcher@xxxxxxx> wrote:
>
>> You can use the dvb-usb-firmware-loader for downloading the firmware to
>> the cypress, you just need to convert the firmware-file into
>> intel-hex-format (in binary) and put the filename in the
>> dvb_usb_properties.
>
> dvb-usb successfully load my firmware yesterday but the
> /dev/dvb/adapter* nodes did not appear. They did when I manually
> loaded the firmware with fxload. I think I converted the hex file
> badly. I had just downloaded hex2bin and will be trying again soon.
> Thanks for letting me know. At least I know I am on the right track.
It could bem that "my" hex-format is different - I used my own script to
generate the binary hex-files.
> I am now looking at the i2c_msg/ctrl_msg and i2c_xfer functions. In
> dibusb-common.c(line 111)
>
> sndbuf[1] = (addr << 1) | (wo ? 0 : 1);
> <snip>
> if (!wo) {
> sndbuf[wlen+2] = (rlen >> 8) & 0xff;
> sndbuf[wlen+3] = rlen & 0xff;
>
> May I know what the bit shifts and bitwise logic are for?
That is for the implementation of the dibusb-i2c-over-usb-protocol. I
assume yours is different. You have to write your own
i2c_master_xfer-callback.
> How did you determine the required structure and thus what to fill
> sndbuf[] with(addr, len) for the various devices? usblog?
No, I used the driver source from DiBcom. But for other boxes I used the
usblogger. You should not need that: You said you have the specifications
from the vendor.
regards,
Patrick.
--
Mail: patrick.boettcher@xxxxxxx
WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/
