Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Hi Hans, with this configuration it does not work. As I commented it seems
that it does not work if GPIO6 is set to 1. If I change to 0 it works fine.
Just one comment, GPIO0 for sure is the LED output of my card. :P
Albert
2008/2/17, Hans-Frieder Vogt <[EMAIL PROTECTED]>:
>
> Albert,
>
> I am happy to hear that your TV-card finally works.
> However, I am still a bit unsure about these GPIO settings. Initially, I
> just copied the GPIO-settings from another entry and
> then left it because it seemed to work. Now, I have digged a little bit
> into this issue and found, that under Windows my
> STK7700PH-based stick gets the GPIO set in a different way.
> Could you please try the following modified stk7700ph_frontend_attach
> routine (in dib0700_devices.c) and tell me
> whether this works for your card as well?
>
>
> static int stk7700ph_frontend_attach(struct dvb_usb_adapter *adap)
>
> {
>
> dib0700_set_gpio(adap->dev, GPIO6, GPIO_OUT, 1);
>
> msleep(20);
>
> dib0700_set_gpio(adap->dev, GPIO9, GPIO_OUT, 1);
>
> dib0700_set_gpio(adap->dev, GPIO4, GPIO_OUT, 1);
> dib0700_set_gpio(adap->dev, GPIO7, GPIO_OUT, 1);
>
> dib0700_set_gpio(adap->dev, GPIO10, GPIO_OUT, 0);
> msleep(10);
>
> dib0700_set_gpio(adap->dev, GPIO10, GPIO_OUT, 1);
>
> msleep(20);
>
> dib0700_set_gpio(adap->dev, GPIO0, GPIO_OUT, 1);
>
> msleep(10);
>
>
> dib7000p_i2c_enumeration(&adap->dev->i2c_adap, 1, 18,
> &stk7700ph_dib7700_xc3028_config);
>
> adap->fe = dvb_attach(dib7000p_attach, &adap->dev->i2c_adap, 0x80,
> &stk7700ph_dib7700_xc3028_config);
>
> return adap->fe == NULL ? -ENODEV : 0;
> }
>
>
> By the way, I also experience the same problem with the missing SNR info,
> on two different dib0700-based USB cards.
>
> Regards,
> Hans-Frieder
>
> Am Sonntag, 17. Februar 2008 schrieb Albert Comerma:
>
> > I got it I remembered that on PCTV DVB-T 72e they had a similar
> problem,
> > which was solved leaving GPIO6 to 0. Doing this the tuning seems to work
> > fine. SNR is always reported as 0% but I think this is not a problem,
> now I
> > can scan and tune dvb-t channels. Firmware is 1.10 and xc3028-v27 with
> that
> > modification. Thanks a lot for your help. Next step would be analog.
> >
> > Albert
> >
>
>
>
>
> --
>
> --
> Hans-Frieder Vogt e-mail: hfvogt gmx .dot. net
>
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Albert,
I am happy to hear that your TV-card finally works.
However, I am still a bit unsure about these GPIO settings. Initially, I just
copied the GPIO-settings from another entry and
then left it because it seemed to work. Now, I have digged a little bit into
this issue and found, that under Windows my
STK7700PH-based stick gets the GPIO set in a different way.
Could you please try the following modified stk7700ph_frontend_attach routine
(in dib0700_devices.c) and tell me
whether this works for your card as well?
static int stk7700ph_frontend_attach(struct dvb_usb_adapter *adap)
{
dib0700_set_gpio(adap->dev, GPIO6, GPIO_OUT, 1);
msleep(20);
dib0700_set_gpio(adap->dev, GPIO9, GPIO_OUT, 1);
dib0700_set_gpio(adap->dev, GPIO4, GPIO_OUT, 1);
dib0700_set_gpio(adap->dev, GPIO7, GPIO_OUT, 1);
dib0700_set_gpio(adap->dev, GPIO10, GPIO_OUT, 0);
msleep(10);
dib0700_set_gpio(adap->dev, GPIO10, GPIO_OUT, 1);
msleep(20);
dib0700_set_gpio(adap->dev, GPIO0, GPIO_OUT, 1);
msleep(10);
dib7000p_i2c_enumeration(&adap->dev->i2c_adap, 1, 18,
&stk7700ph_dib7700_xc3028_config);
adap->fe = dvb_attach(dib7000p_attach, &adap->dev->i2c_adap, 0x80,
&stk7700ph_dib7700_xc3028_config);
return adap->fe == NULL ? -ENODEV : 0;
}
By the way, I also experience the same problem with the missing SNR info, on
two different dib0700-based USB cards.
Regards,
Hans-Frieder
Am Sonntag, 17. Februar 2008 schrieb Albert Comerma:
> I got it I remembered that on PCTV DVB-T 72e they had a similar problem,
> which was solved leaving GPIO6 to 0. Doing this the tuning seems to work
> fine. SNR is always reported as 0% but I think this is not a problem, now I
> can scan and tune dvb-t channels. Firmware is 1.10 and xc3028-v27 with that
> modification. Thanks a lot for your help. Next step would be analog.
>
> Albert
>
--
--
Hans-Frieder Vogt e-mail: hfvogt gmx .dot. net
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
I got it I remembered that on PCTV DVB-T 72e they had a similar problem, which was solved leaving GPIO6 to 0. Doing this the tuning seems to work fine. SNR is always reported as 0% but I think this is not a problem, now I can scan and tune dvb-t channels. Firmware is 1.10 and xc3028-v27 with that modification. Thanks a lot for your help. Next step would be analog. Albert ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Hi hans, thanks for the idea, but the result is the same. I extracted the
firmware for the windows driver using your tool and when I use it, it seems
to work except for a repeating message of;
dvb-usb: error while querying for an remote control event.
I think they have an other .sys for the remote control management firmware.
But when I try to scan the dmesg is exactly the same as before, everything
seems correct, but there's no signal / SNR. I don't know if this could be a
different GPIO used or different i2c or something like that, because the
rest seems correct.
Albert
2008/2/16, Hans-Frieder Vogt <[EMAIL PROTECTED]>:
>
> Albert,
>
> your dmesg-output looks absolutely fine for me (besides the already
> discussed xc2028 4-0061: Error on line 1063: -5
> message).
> Since you also obvisouly succeeded to patch the xc3028 firmware so that
> the scode can be loaded (which in my
> cinergy did not make any noticeable difference), I still have the
> suspicion that the dib0700-firmware is the main reason
> for your device not working.
> Can you try the firmware from the Windows-driver? Comparing various
> dib0700-based device drivers, I found quite
> different dib0700-firmware in these. I am not sure if there is any single
> "latest" version of the firmware which can be used
> for all devices.
>
> I have written a small tool to extract the dib0700 firmware from the
> Windows driver (there are probably already other/better
> tools around, but I just did not find any). If you use this tool (ignore
> the warnings, I am still trying to understand how the
> firmware is organised) and then copy the resulting firmware to the
> firmware-directory under the name of
> dvb-usb-dib0700-1.10.fw, do you see any difference?
>
> Good luck,
> Hans-Frieder
>
> Here comes the tool:
>
> /*
>dib0700 firmware extraction tool
>extracts firmware for DiBcom0700(c) based devices from .sys driver
> files
>and stores all found firmwares in files dibfw-00.fw, dibfw-01.fw, ...
>
>Copyright (C) 2008 Hans-Frieder Vogt <[EMAIL PROTECTED]>
>
>This program is free software; you can redistribute it and/or modify
>it under the terms of the GNU General Public License as published by
>the Free Software Foundation version 2
>
>This program is distributed in the hope that it will be useful,
>but WITHOUT ANY WARRANTY; without even the implied warranty of
>MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>GNU General Public License for more details.
>
>You should have received a copy of the GNU General Public License
>along with this program; if not, write to the Free Software
>Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
> */
> #include
> #include
> #include/* for O_RDONLY */
> #include /* for open/close, ftruncate */
> #include
> #include
> #include
> #include
>
>
> static const char fwstart[] = "\x02\x00\x00\x00\x04\x70\x00\x00";
>
> #define MAX_FW 10
> static int fwofs[MAX_FW];
>
> int read_firmware(unsigned char *m, int idx) {
> int fd;
> int j, i = 0;
> unsigned char *buf; /* fw is stored in junks of 22 bytes */
> char fname[20];
> unsigned char bytes, hibyte, lobyte, endflag, crcbyte;
> unsigned int crc, datapos;
> int databytes = 0;
>
> sprintf(fname,"dibfw-%02x.fw", idx);
>
> fd = open(fname, O_WRONLY | O_CREAT, S_IRUSR | S_IWUSR);
> if (fd < 0) {
> fprintf(stderr, "ERROR trying to open/create output file
> \"%s\""
> "\n", fname);
> return 1;
> }
> for (i=0;; i=i+22) {
> buf = &m[i];
>
> bytes = buf[0];
> lobyte = buf[2];
> hibyte = buf[3];
> endflag = buf[4];
> crcbyte = buf[21];
>
> /* do the checksum test */
> crc = 0;
> for (j=0; j<22; j++)
> crc += buf[j];
> if ((crc & 0xff) != 0) {
> fprintf(stderr, "ERROR: invalid line 0x%08x:\n",
> i);
> for (j=0; j<22; j++)
> fprintf(stderr, "0x%02x ", buf[j]);
> fprintf(stderr, "\n");
> break;
> }
>
> /* check whether data really fits together */
> if (i > 0) {
> datapos = lobyte | (hibyte << 8);
> if (datapos != databytes) {
> fprintf(stderr, "WARNING data
> inconsistent? at "
> "offset 0x%04x data written is
> 0x%04x, "
> "but line says 0x%04x\n", i,
> databytes,
> datapos);
> }
> }
>
> /* now write the data */
> write(fd, &bytes,
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Albert,
your dmesg-output looks absolutely fine for me (besides the already discussed
xc2028 4-0061: Error on line 1063: -5
message).
Since you also obvisouly succeeded to patch the xc3028 firmware so that the
scode can be loaded (which in my
cinergy did not make any noticeable difference), I still have the suspicion
that the dib0700-firmware is the main reason
for your device not working.
Can you try the firmware from the Windows-driver? Comparing various
dib0700-based device drivers, I found quite
different dib0700-firmware in these. I am not sure if there is any single
"latest" version of the firmware which can be used
for all devices.
I have written a small tool to extract the dib0700 firmware from the Windows
driver (there are probably already other/better
tools around, but I just did not find any). If you use this tool (ignore the
warnings, I am still trying to understand how the
firmware is organised) and then copy the resulting firmware to the
firmware-directory under the name of
dvb-usb-dib0700-1.10.fw, do you see any difference?
Good luck,
Hans-Frieder
Here comes the tool:
/*
dib0700 firmware extraction tool
extracts firmware for DiBcom0700(c) based devices from .sys driver files
and stores all found firmwares in files dibfw-00.fw, dibfw-01.fw, ...
Copyright (C) 2008 Hans-Frieder Vogt <[EMAIL PROTECTED]>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation version 2
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/
#include
#include
#include/* for O_RDONLY */
#include /* for open/close, ftruncate */
#include
#include
#include
#include
static const char fwstart[] = "\x02\x00\x00\x00\x04\x70\x00\x00";
#define MAX_FW 10
static int fwofs[MAX_FW];
int read_firmware(unsigned char *m, int idx) {
int fd;
int j, i = 0;
unsigned char *buf; /* fw is stored in junks of 22 bytes */
char fname[20];
unsigned char bytes, hibyte, lobyte, endflag, crcbyte;
unsigned int crc, datapos;
int databytes = 0;
sprintf(fname,"dibfw-%02x.fw", idx);
fd = open(fname, O_WRONLY | O_CREAT, S_IRUSR | S_IWUSR);
if (fd < 0) {
fprintf(stderr, "ERROR trying to open/create output file \"%s\""
"\n", fname);
return 1;
}
for (i=0;; i=i+22) {
buf = &m[i];
bytes = buf[0];
lobyte = buf[2];
hibyte = buf[3];
endflag = buf[4];
crcbyte = buf[21];
/* do the checksum test */
crc = 0;
for (j=0; j<22; j++)
crc += buf[j];
if ((crc & 0xff) != 0) {
fprintf(stderr, "ERROR: invalid line 0x%08x:\n", i);
for (j=0; j<22; j++)
fprintf(stderr, "0x%02x ", buf[j]);
fprintf(stderr, "\n");
break;
}
/* check whether data really fits together */
if (i > 0) {
datapos = lobyte | (hibyte << 8);
if (datapos != databytes) {
fprintf(stderr, "WARNING data inconsistent? at "
"offset 0x%04x data written is 0x%04x, "
"but line says 0x%04x\n", i, databytes,
datapos);
}
}
/* now write the data */
write(fd, &bytes, 1);
write(fd, &lobyte, 1);
write(fd, &hibyte, 1);
write(fd, &endflag, 1);
write(fd, &buf[5], bytes);
write(fd, &crcbyte, 1);
if (i > 0) {
databytes += bytes;
}
/* endflag seems to indicate the end of the firmware */
if (endflag == 1)
break;
}
close(fd);
}
int main(int argc, char **argv) {
struct stat st;
int fd;
unsigned char *map;
unsigned long map_len;
int err;
int i, j;
int num_fw = 0;
printf("%s - an extraction tool for DiBcom0700(c) firmware from W*
drivers\n",
argv[0]);
if (argc!=2) {
fprintf(stderr, "%s \n", argv[0]);
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
More information... I attach a dmesg of tuner-xc2028 loaded in debug mode
while doing a scan ( scan es-Collserola|tee channels.conf ). I don't see any
problem, but it doesn't work.
Albert
2008/2/16, Albert Comerma <[EMAIL PROTECTED]>:
>
> For what I understand, changing the Firmware 64 to 6200 changes the if
> frequency to 5.2MHz. So this modification on the firmware should make the
> card work. What it's more strange for me is that when trying to scan no
> signal or SNR is reported, so it seems like xc3028 firmware is not working
> properly. Perhaps could be a wrong BASE or DTV firmware loaded?
>
> Albert
>
> 2008/2/16, Albert Comerma <[EMAIL PROTECTED]>:
> >
> > So, If it's not a problem, any of you could send me the current xc3028
> > firmware you are using, because mine does not seem to work... Thanks.
> >
> > Albert
> >
> > 2008/2/15, Patrick Boettcher <[EMAIL PROTECTED]>:
> > >
> > > Aah now I remember that issue, in fact it is no issue. I was seeing
> > > that
> > > problem when send the sleep command or any other firmware command
> > > without
> > > having a firmware running. In was, so far, no problem.
> > >
> > > Patrick.
> > >
> > >
> > >
> > > On Fri, 15 Feb 2008, Holger Dehnhardt wrote:
> > >
> > > > Hi Albert, Hi Mauro,
> > > >
> > > > I have successfulli patched and compiled the driver. Im using the
> > > terratec
> > > > cinergy device and it works fine.
> > > >
> > > >>> [ 2251.856000] xc2028 4-0061: Error on line 1063: -5
> > > >
> > > > This error message looked very familar to me, so i searched my log
> > > and guess
> > > > what I found:
> > > >
> > > > Feb 15 20:42:18 musik kernel: xc2028 3-0061: xc2028_sleep called
> > > > Feb 15 20:42:18 musik kernel: xc2028 3-0061: xc2028_sleep called
> > > > Feb 15 20:42:18 musik kernel: xc2028 3-0061: Error on line 1064: -5
> > > > Feb 15 20:42:18 musik kernel: DiB7000P: setting output mode for
> > > demod df75e800
> > > > to 0
> > > > Feb 15 20:42:18 musik kernel: DiB7000P: setting output mode for
> > > demod df75e800
> > > > to 0
> > > >
> > > > It identifies the marked line (just to be sure because of the
> > > differen line
> > > > numbers)
> > > >
> > > > if (priv->firm_version < 0x0202)
> > > > ->rc = send_seq(priv, {0x00, 0x08, 0x00, 0x00});
> > > > else
> > > > rc = send_seq(priv, {0x80, 0x08, 0x00, 0x00});
> > > >
> > > >> The above error is really weird. It seems to be related to
> > > something that
> > > >> happened before xc2028, since firmware load didn't start on that
> > > point of
> > > >> the code.
> > > >
> > > > The error really is weird, but it does not seem to cause the
> > > troubles - my
> > > > card works despite the error!
> > > >
> > > >>
> > > >>> [ 2289.284000] xc2028 4-0061: Device is Xceive 3028 version 1.0,
> > > firmware
> > > >>> version 2.7
> > > >>
> > > >> This message means that xc3028 firmware were successfully loaded
> > > and it is
> > > >> running ok.
> > > >
> > > > This and the following messages look similar...
> > > >
> > > > Holger
> > > >
> > > > ___
> > > > linux-dvb mailing list
> > > > linux-dvb@linuxtv.org
> > > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> > > >
> > >
> > > ___
> > > linux-dvb mailing list
> > > linux-dvb@linuxtv.org
> > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> > >
> >
> >
>
[ 2197.708000] usb 6-1: new high speed USB device using ehci_hcd and address 4
[ 2197.84] usb 6-1: configuration #1 chosen from 1 choice
[ 2197.84] dvb-usb: found a 'Pinnacle Expresscard 320cx' in cold state,
will try to load a firmware
[ 2197.844000] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw'
[ 2198.048000] dib0700: firmware started successfully.
[ 2198.552000] dvb-usb: found a 'Pinnacle Expresscard 320cx' in warm state.
[ 2198.552000] dvb-usb: will pass the complete MPEG2 transport stream to the
software demuxer.
[ 2198.552000] DVB: registering new adapter (Pinnacle Expresscard 320cx)
[ 2198.92] DVB: registering frontend 0 (DiBcom 7000PC)...
[ 2198.92] xc2028: Xcv2028/3028 init called!
[ 2198.92] xc2028 4-0061: type set to XCeive xc2028/xc3028 tuner
[ 2198.92] xc2028 4-0061: xc2028_set_config called
[ 2198.92] input: IR-receiver inside an USB DVB receiver as
/class/input/input11
[ 2198.92] dvb-usb: schedule remote query interval to 150 msecs.
[ 2198.92] dvb-usb: Pinnacle Expresscard 320cx successfully initialized and
connected.
[ 2223.936000] xc2028 4-0061: xc2028_set_params called
[ 2223.936000] xc2028 4-0061: generic_set_freq called
[ 2223.936000] xc2028 4-0061: should set frequency 514000 kHz
[ 2223.936000] xc2028 4-0061: check_firmware called
[ 2223.936000] xc2028 4-0061: load_all_firmwares called
[ 2223.936000] xc2028 4-0061: Reading firmware xc3028-v27.fw
[ 2223.94] xc2028 4-0061: Loading 80 firmware images from xc3028-v27.fw,
type: xc2028 firmware, ver 2.7
[ 2223.94
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
For what I understand, changing the Firmware 64 to 6200 changes the if
frequency to 5.2MHz. So this modification on the firmware should make the
card work. What it's more strange for me is that when trying to scan no
signal or SNR is reported, so it seems like xc3028 firmware is not working
properly. Perhaps could be a wrong BASE or DTV firmware loaded?
Albert
2008/2/16, Albert Comerma <[EMAIL PROTECTED]>:
>
> So, If it's not a problem, any of you could send me the current xc3028
> firmware you are using, because mine does not seem to work... Thanks.
>
> Albert
>
> 2008/2/15, Patrick Boettcher <[EMAIL PROTECTED]>:
> >
> > Aah now I remember that issue, in fact it is no issue. I was seeing that
> > problem when send the sleep command or any other firmware command
> > without
> > having a firmware running. In was, so far, no problem.
> >
> > Patrick.
> >
> >
> >
> > On Fri, 15 Feb 2008, Holger Dehnhardt wrote:
> >
> > > Hi Albert, Hi Mauro,
> > >
> > > I have successfulli patched and compiled the driver. Im using the
> > terratec
> > > cinergy device and it works fine.
> > >
> > >>> [ 2251.856000] xc2028 4-0061: Error on line 1063: -5
> > >
> > > This error message looked very familar to me, so i searched my log and
> > guess
> > > what I found:
> > >
> > > Feb 15 20:42:18 musik kernel: xc2028 3-0061: xc2028_sleep called
> > > Feb 15 20:42:18 musik kernel: xc2028 3-0061: xc2028_sleep called
> > > Feb 15 20:42:18 musik kernel: xc2028 3-0061: Error on line 1064: -5
> > > Feb 15 20:42:18 musik kernel: DiB7000P: setting output mode for demod
> > df75e800
> > > to 0
> > > Feb 15 20:42:18 musik kernel: DiB7000P: setting output mode for demod
> > df75e800
> > > to 0
> > >
> > > It identifies the marked line (just to be sure because of the differen
> > line
> > > numbers)
> > >
> > > if (priv->firm_version < 0x0202)
> > > ->rc = send_seq(priv, {0x00, 0x08, 0x00, 0x00});
> > > else
> > > rc = send_seq(priv, {0x80, 0x08, 0x00, 0x00});
> > >
> > >> The above error is really weird. It seems to be related to something
> > that
> > >> happened before xc2028, since firmware load didn't start on that
> > point of
> > >> the code.
> > >
> > > The error really is weird, but it does not seem to cause the troubles
> > - my
> > > card works despite the error!
> > >
> > >>
> > >>> [ 2289.284000] xc2028 4-0061: Device is Xceive 3028 version 1.0,
> > firmware
> > >>> version 2.7
> > >>
> > >> This message means that xc3028 firmware were successfully loaded and
> > it is
> > >> running ok.
> > >
> > > This and the following messages look similar...
> > >
> > > Holger
> > >
> > > ___
> > > linux-dvb mailing list
> > > linux-dvb@linuxtv.org
> > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> > >
> >
> > ___
> > linux-dvb mailing list
> > linux-dvb@linuxtv.org
> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> >
>
>
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
So, If it's not a problem, any of you could send me the current xc3028
firmware you are using, because mine does not seem to work... Thanks.
Albert
2008/2/15, Patrick Boettcher <[EMAIL PROTECTED]>:
>
> Aah now I remember that issue, in fact it is no issue. I was seeing that
> problem when send the sleep command or any other firmware command without
> having a firmware running. In was, so far, no problem.
>
> Patrick.
>
>
>
> On Fri, 15 Feb 2008, Holger Dehnhardt wrote:
>
> > Hi Albert, Hi Mauro,
> >
> > I have successfulli patched and compiled the driver. Im using the
> terratec
> > cinergy device and it works fine.
> >
> >>> [ 2251.856000] xc2028 4-0061: Error on line 1063: -5
> >
> > This error message looked very familar to me, so i searched my log and
> guess
> > what I found:
> >
> > Feb 15 20:42:18 musik kernel: xc2028 3-0061: xc2028_sleep called
> > Feb 15 20:42:18 musik kernel: xc2028 3-0061: xc2028_sleep called
> > Feb 15 20:42:18 musik kernel: xc2028 3-0061: Error on line 1064: -5
> > Feb 15 20:42:18 musik kernel: DiB7000P: setting output mode for demod
> df75e800
> > to 0
> > Feb 15 20:42:18 musik kernel: DiB7000P: setting output mode for demod
> df75e800
> > to 0
> >
> > It identifies the marked line (just to be sure because of the differen
> line
> > numbers)
> >
> > if (priv->firm_version < 0x0202)
> > ->rc = send_seq(priv, {0x00, 0x08, 0x00, 0x00});
> > else
> > rc = send_seq(priv, {0x80, 0x08, 0x00, 0x00});
> >
> >> The above error is really weird. It seems to be related to something
> that
> >> happened before xc2028, since firmware load didn't start on that point
> of
> >> the code.
> >
> > The error really is weird, but it does not seem to cause the troubles -
> my
> > card works despite the error!
> >
> >>
> >>> [ 2289.284000] xc2028 4-0061: Device is Xceive 3028 version 1.0,
> firmware
> >>> version 2.7
> >>
> >> This message means that xc3028 firmware were successfully loaded and it
> is
> >> running ok.
> >
> > This and the following messages look similar...
> >
> > Holger
> >
> > ___
> > linux-dvb mailing list
> > linux-dvb@linuxtv.org
> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> >
>
> ___
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Aah now I remember that issue, in fact it is no issue. I was seeing that
problem when send the sleep command or any other firmware command without
having a firmware running. In was, so far, no problem.
Patrick.
On Fri, 15 Feb 2008, Holger Dehnhardt wrote:
> Hi Albert, Hi Mauro,
>
> I have successfulli patched and compiled the driver. Im using the terratec
> cinergy device and it works fine.
>
>>> [ 2251.856000] xc2028 4-0061: Error on line 1063: -5
>
> This error message looked very familar to me, so i searched my log and guess
> what I found:
>
> Feb 15 20:42:18 musik kernel: xc2028 3-0061: xc2028_sleep called
> Feb 15 20:42:18 musik kernel: xc2028 3-0061: xc2028_sleep called
> Feb 15 20:42:18 musik kernel: xc2028 3-0061: Error on line 1064: -5
> Feb 15 20:42:18 musik kernel: DiB7000P: setting output mode for demod df75e800
> to 0
> Feb 15 20:42:18 musik kernel: DiB7000P: setting output mode for demod df75e800
> to 0
>
> It identifies the marked line (just to be sure because of the differen line
> numbers)
>
> if (priv->firm_version < 0x0202)
> ->rc = send_seq(priv, {0x00, 0x08, 0x00, 0x00});
> else
> rc = send_seq(priv, {0x80, 0x08, 0x00, 0x00});
>
>> The above error is really weird. It seems to be related to something that
>> happened before xc2028, since firmware load didn't start on that point of
>> the code.
>
> The error really is weird, but it does not seem to cause the troubles - my
> card works despite the error!
>
>>
>>> [ 2289.284000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware
>>> version 2.7
>>
>> This message means that xc3028 firmware were successfully loaded and it is
>> running ok.
>
> This and the following messages look similar...
>
> Holger
>
> ___
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Hi Albert, Hi Mauro,
I have successfulli patched and compiled the driver. Im using the terratec
cinergy device and it works fine.
> > [ 2251.856000] xc2028 4-0061: Error on line 1063: -5
This error message looked very familar to me, so i searched my log and guess
what I found:
Feb 15 20:42:18 musik kernel: xc2028 3-0061: xc2028_sleep called
Feb 15 20:42:18 musik kernel: xc2028 3-0061: xc2028_sleep called
Feb 15 20:42:18 musik kernel: xc2028 3-0061: Error on line 1064: -5
Feb 15 20:42:18 musik kernel: DiB7000P: setting output mode for demod df75e800
to 0
Feb 15 20:42:18 musik kernel: DiB7000P: setting output mode for demod df75e800
to 0
It identifies the marked line (just to be sure because of the differen line
numbers)
if (priv->firm_version < 0x0202)
-> rc = send_seq(priv, {0x00, 0x08, 0x00, 0x00});
else
rc = send_seq(priv, {0x80, 0x08, 0x00, 0x00});
> The above error is really weird. It seems to be related to something that
> happened before xc2028, since firmware load didn't start on that point of
> the code.
The error really is weird, but it does not seem to cause the troubles - my
card works despite the error!
>
> > [ 2289.284000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware
> > version 2.7
>
> This message means that xc3028 firmware were successfully loaded and it is
> running ok.
This and the following messages look similar...
Holger
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
For the DiB7000 the code I sent is requiring a 5.2 IF firmware. Although it should be possible to recover an offset of 200kHz I would recommend to use this firmware. Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ On Fri, 15 Feb 2008, Mauro Carvalho Chehab wrote: > Hi Albert, > > On Thu, 14 Feb 2008 21:20:32 +0100 > "Albert Comerma" <[EMAIL PROTECTED]> wrote: > >> [ 2251.856000] xc2028 4-0061: Error on line 1063: -5 > > The above error is really weird. It seems to be related to something that > happened before xc2028, since firmware load didn't start on that point of the > code. > > >> [ 2289.284000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware >> version 2.7 > This message means that xc3028 firmware were successfully loaded and it is > running ok. > >> [ 2282.504000] xc2028 4-0061: Loading firmware for type=BASE F8MHZ (3), id >> . >> [ 2289.104000] xc2028 4-0061: Loading firmware for type=D2620 DTV8 (208), id >> . >> [ 2289.224000] xc2028 4-0061: Loading SCODE for type=DTV8 SCODE HAS_IF_5400 >> (6200), id . > > The above messages state what firmware you've loaded. > > xc3028 version 2.7 has 80 different firmwares. If you load a wrong one, your > device won't work. > >> From the above, the driver is assuming that you're on an area with 8MHz video > channels. Also, your demod should be using IF = 5.4 MHz: > > Firmware 64, type: DTV8 CHINA SCODE HAS IF (0x64000200), IF = 5.40 MHz id: > (), size: 192 > > Does the above firmware correspond to your configuration? > > Cheers, > Mauro > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Hi Albert, On Thu, 14 Feb 2008 21:20:32 +0100 "Albert Comerma" <[EMAIL PROTECTED]> wrote: > [ 2251.856000] xc2028 4-0061: Error on line 1063: -5 The above error is really weird. It seems to be related to something that happened before xc2028, since firmware load didn't start on that point of the code. > [ 2289.284000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware > version 2.7 This message means that xc3028 firmware were successfully loaded and it is running ok. > [ 2282.504000] xc2028 4-0061: Loading firmware for type=BASE F8MHZ (3), id > . > [ 2289.104000] xc2028 4-0061: Loading firmware for type=D2620 DTV8 (208), id > . > [ 2289.224000] xc2028 4-0061: Loading SCODE for type=DTV8 SCODE HAS_IF_5400 > (6200), id . The above messages state what firmware you've loaded. xc3028 version 2.7 has 80 different firmwares. If you load a wrong one, your device won't work. >From the above, the driver is assuming that you're on an area with 8MHz video channels. Also, your demod should be using IF = 5.4 MHz: Firmware 64, type: DTV8 CHINA SCODE HAS IF (0x64000200), IF = 5.40 MHz id: (), size: 192 Does the above firmware correspond to your configuration? Cheers, Mauro ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Hi I've been trying to load the tunner-xc2028 module in debug mode. I send the results, there's the same error and also some things when loading the firmware. Hans could you send me your firmware to check that it's not an error of that (I mean, when I scan there's no signal or SNR, perhaps this could be something related to it)? Thanks. Albert [ 2219.804000] usb 6-1: new high speed USB device using ehci_hcd and address 4 [ 2219.94] usb 6-1: configuration #1 chosen from 1 choice [ 2219.94] dvb-usb: found a 'Pinnacle Expresscard 320cx' in cold state, will try to load a firmware [ 2219.956000] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' [ 2220.156000] dib0700: firmware started successfully. [ 2220.66] dvb-usb: found a 'Pinnacle Expresscard 320cx' in warm state. [ 2220.66] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 2220.66] DVB: registering new adapter (Pinnacle Expresscard 320cx) [ 2221.032000] DVB: registering frontend 0 (DiBcom 7000PC)... [ 2221.032000] xc2028: Xcv2028/3028 init called! [ 2221.032000] xc2028 4-0061: type set to XCeive xc2028/xc3028 tuner [ 2221.032000] xc2028 4-0061: xc2028_set_config called [ 2221.032000] input: IR-receiver inside an USB DVB receiver as /class/input/input10 [ 2221.032000] dvb-usb: schedule remote query interval to 150 msecs. [ 2221.032000] dvb-usb: Pinnacle Expresscard 320cx successfully initialized and connected. [ 2251.856000] xc2028 4-0061: xc2028_sleep called [ 2251.856000] xc2028 4-0061: Error on line 1063: -5 [ 2282.436000] xc2028 4-0061: xc2028_set_params called [ 2282.436000] xc2028 4-0061: generic_set_freq called [ 2282.436000] xc2028 4-0061: should set frequency 402000 kHz [ 2282.436000] xc2028 4-0061: check_firmware called [ 2282.436000] xc2028 4-0061: load_all_firmwares called [ 2282.436000] xc2028 4-0061: Reading firmware xc3028-v27.fw [ 2282.48] xc2028 4-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7 [ 2282.48] xc2028 4-0061: Reading firmware type BASE F8MHZ (3), id 0, size=8718. [ 2282.48] xc2028 4-0061: Reading firmware type BASE F8MHZ MTS (7), id 0, size=8712. [ 2282.48] xc2028 4-0061: Reading firmware type BASE FM (401), id 0, size=8562. [ 2282.48] xc2028 4-0061: Reading firmware type BASE FM INPUT1 (c01), id 0, size=8576. [ 2282.48] xc2028 4-0061: Reading firmware type BASE (1), id 0, size=8706. [ 2282.48] xc2028 4-0061: Reading firmware type BASE MTS (5), id 0, size=8682. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 10007, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 10007, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 20007, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 20007, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 40007, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 40007, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 80007, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 80007, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 300e0, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 300e0, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id c00e0, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id c00e0, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 20, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 20, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 400, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 400, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type D2633 DTV6 ATSC (10030), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2620 DTV6 QAM (68), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2633 DTV6 QAM (70), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2620 DTV7 (88), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2633 DTV7 (90), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2620 DTV78 (108), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2633 DTV78 (110), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2620 DTV8 (208), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2633 DTV8 (210), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type FM (400), id 0, size=135. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 10, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 10, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 100040, size=169. [ 2282.48] xc2028 4-0061: Reading fi
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
That's what I supposed... So we must get working the 1.10. Thanks again. 2008/2/13, Patrick Boettcher <[EMAIL PROTECTED]>: > > On Wed, 13 Feb 2008, Albert Comerma wrote: > > > Ok, both give the same error, the only one wich does not report any > error is > > the 0.1. Thanks. > > > Just because it does not report an error, does not mean that there isn't > one. > > I2C errors are only reported from the firwmare since the 03-version. > > Patrick. > > > -- >Mail: [EMAIL PROTECTED] >WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
On Wed, 13 Feb 2008, Albert Comerma wrote: > Ok, both give the same error, the only one wich does not report any error is > the 0.1. Thanks. Just because it does not report an error, does not mean that there isn't one. I2C errors are only reported from the firwmare since the 03-version. Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Ok, both give the same error, the only one wich does not report any error is the 0.1. Thanks. Albert 2008/2/13, Patrick Boettcher <[EMAIL PROTECTED]>: > > The latest dib0700-firwmare is dvb-usb-dib0700-1.10.fw not > dvb-usb-dib0700-03-pre1.fw. > > > Patrick. > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
The latest dib0700-firwmare is dvb-usb-dib0700-1.10.fw not dvb-usb-dib0700-03-pre1.fw. Patrick. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Hi Hans, thanks for your answer, I say what I tryed; your dmesg output looks quite good. In fact, the only line that irritates me is the line with > > xc2028 4-0061: Error on line 1063: -5 > > This line indicates an i2c-communication problem with the tuner. > As it happens BEFORE the XC3028 firmware is loaded, it cannot have > anything to do with the xc3028 firmware. > Therefore, I suspect something either with the general setup of the > Expresscard or a DiB firmware that does not > 100% support your device. Have you tried a later firmware? I was trying latest firmware (I think): dvb-usb-dib0700-03-pre1.fw I also tryed the previous; dvb-usb-dib0700-1.10.fw And an other one; dvb-usb-dib0700-01.fw This last one doesn't give any error, but I also can not see anything on scanning. I send you the dmesg. Feb 13 19:14:50: xc2028 7-0061: Loading firmware for type=D2620 DTV8 (208), > id . > Feb 13 19:14:50: xc2028 7-0061: Device is Xceive 3028 version 1.0, > firmware version 2.7 > Feb 13 19:14:50: dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 This last lines are a little bit different from the ones I have... Perhaps something about the firmware modification. I did not change the extract_firmware.pl file (in fact, it is not useable > for the Mod7700.sys driver, but expects the driver > file hcw85bda.sys), but just used a hex editor to replace the ID > 0x64000200 by 0x6200. I tryed to do the same but I can't find 0x64000200 on the hex... Could you send me your firmware just to try? certainly a good idea to use an amplified antenna. Have you got another > DVB-t device that works with a passive > antenna in the same area where you use your new device? I use the same device on XP and it detects some channels. When I try to scan with kaffeine I don't see any SNR or anything so I guess the comunication with xc3028 is failing. Thanks again for your answer. I also send this mail to pattrick who probably knows better the dibcom firmware stuff. [ 4107.196000] usb 1-1: new high speed USB device using ehci_hcd and address 9 [ 4107.328000] usb 1-1: configuration #1 chosen from 1 choice [ 4107.328000] dvb-usb: found a 'Pinnacle Expresscard 320cx' in cold state, will try to load a firmware [ 4107.332000] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' [ 4107.516000] dib0700: firmware started successfully. [ 4108.02] dvb-usb: found a 'Pinnacle Expresscard 320cx' in warm state. [ 4108.02] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 4108.02] DVB: registering new adapter (Pinnacle Expresscard 320cx) [ 4108.30] DVB: registering frontend 0 (DiBcom 7000PC)... [ 4108.30] xc2028 4-0061: type set to XCeive xc2028/xc3028 tuner [ 4108.30] input: IR-receiver inside an USB DVB receiver as /class/input/input13 [ 4108.30] dvb-usb: schedule remote query interval to 150 msecs. [ 4108.30] dvb-usb: Pinnacle Expresscard 320cx successfully initialized and connected. [ 4136.252000] xc2028 4-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7 [ 4136.256000] dib0700: stk7700ph_xc3028_callback: XC2028_TUNER_RESET 0 [ 4136.256000] [ 4136.272000] xc2028 4-0061: Loading firmware for type=BASE F8MHZ (3), id . [ 4136.272000] dib0700: stk7700ph_xc3028_callback: XC2028_TUNER_RESET 0 [ 4136.272000] [ 4139.272000] xc2028 4-0061: Loading firmware for type=D2620 DTV8 (208), id . [ 4139.324000] xc2028 4-0061: Loading SCODE for type=DTV8 SCODE HAS_IF_5400 (6200), id . [ 4139.368000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 4139.384000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 4139.384000] [ 4141.004000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 4141.02] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 4141.02] [ 4142.532000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 4142.548000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 4142.548000] [ 4144.16] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 4144.176000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 4144.176000] [ 4145.696000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 4145.712000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 4145.712000] [ 4147.324000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 4147.34] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 4147.34] [ 4148.852000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 4148.868000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 4148.868000] [ 4150.484000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 4150.50] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 4150.50] [ 4152.016000] xc2028
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Albert, your dmesg output looks quite good. In fact, the only line that irritates me is the line with xc2028 4-0061: Error on line 1063: -5 This line indicates an i2c-communication problem with the tuner. As it happens BEFORE the XC3028 firmware is loaded, it cannot have anything to do with the xc3028 firmware. Therefore, I suspect something either with the general setup of the Expresscard or a DiB firmware that does not 100% support your device. Have you tried a later firmware? For comparison, I list here what is output in kernel.log for my Cinergy HT USB XE: Feb 13 19:13:31: usb 1-5: new high speed USB device using ehci_hcd and address 6 Feb 13 19:13:31: usb 1-5: configuration #1 chosen from 1 choice Feb 13 19:13:31: dib0700: loaded with support for 7 different device-types Feb 13 19:13:31: dvb-usb: found a 'Terratec Cinergy HT USB XE' in cold state, will try to load a firmware Feb 13 19:13:31: dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' Feb 13 19:13:32: dib0700: firmware started successfully. Feb 13 19:13:32: dvb-usb: found a 'Terratec Cinergy HT USB XE' in warm state. Feb 13 19:13:32: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 13 19:13:32: DVB: registering new adapter (Terratec Cinergy HT USB XE) Feb 13 19:13:33: DVB: registering frontend 1 (DiBcom 7000PC)... Feb 13 19:13:33: xc2028 7-0061: type set to XCeive xc2028/xc3028 tuner Feb 13 19:13:33: input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:02.1/usb1/1-5/input/input6 Feb 13 19:13:33: dvb-usb: schedule remote query interval to 150 msecs. Feb 13 19:13:33: dvb-usb: Terratec Cinergy HT USB XE successfully initialized and connected. Feb 13 19:13:33: usbcore: registered new interface driver dvb_usb_dib0700 Feb 13 19:14:43: xc2028 7-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7 Feb 13 19:14:43: dib0700: stk7700ph_xc3028_callback: XC2028_TUNER_RESET 0 Feb 13 19:14:43: Feb 13 19:14:43: xc2028 7-0061: Loading firmware for type=BASE F8MHZ (3), id . Feb 13 19:14:43: dib0700: stk7700ph_xc3028_callback: XC2028_TUNER_RESET 0 Feb 13 19:14:43: Feb 13 19:14:50: xc2028 7-0061: Loading firmware for type=D2620 DTV8 (208), id . Feb 13 19:14:50: xc2028 7-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 Feb 13 19:14:50: dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 Feb 13 19:14:50: with regards to the firmware modification that I mentioned, see the comment below. Regards, Hans-Frieder > Finally I got what you mean... you changed the extract_firmware.pl, but not > only the comment I guess... also the values below. I tested both and the I did not change the extract_firmware.pl file (in fact, it is not useable for the Mod7700.sys driver, but expects the driver file hcw85bda.sys), but just used a hex editor to replace the ID 0x64000200 by 0x6200. > result is the same as described before, everything seems correct, but I have > some errors on dmesg and nothing is detected on scan (I must try with an > amplified antenna but I think it should detect something). certainly a good idea to use an amplified antenna. Have you got another DVB-t device that works with a passive antenna in the same area where you use your new device? > > Albert > -- -- Hans-Frieder Vogt e-mail: hfvogt gmx .dot. net ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Finally I got what you mean... you changed the extract_firmware.pl, but not only the comment I guess... also the values below. I tested both and the result is the same as described before, everything seems correct, but I have some errors on dmesg and nothing is detected on scan (I must try with an amplified antenna but I think it should detect something). Albert [ 9318.084000] usb 1-1: new high speed USB device using ehci_hcd and address 7 [ 9318.216000] usb 1-1: configuration #1 chosen from 1 choice [ 9318.216000] dvb-usb: found a 'Pinnacle Expresscard 320cx' in cold state, will try to load a firmware [ 9318.244000] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' [ 9318.444000] dib0700: firmware started successfully. [ 9318.948000] dvb-usb: found a 'Pinnacle Expresscard 320cx' in warm state. [ 9318.948000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 9318.948000] DVB: registering new adapter (Pinnacle Expresscard 320cx) [ 9319.316000] DVB: registering frontend 0 (DiBcom 7000PC)... [ 9319.316000] xc2028 4-0061: type set to XCeive xc2028/xc3028 tuner [ 9319.316000] input: IR-receiver inside an USB DVB receiver as /class/input/input13 [ 9319.316000] dvb-usb: schedule remote query interval to 150 msecs. [ 9319.316000] dvb-usb: Pinnacle Expresscard 320cx successfully initialized and connected. [ 9342.272000] xc2028 4-0061: Error on line 1063: -5 [ 9363.912000] xc2028 4-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7 [ 9363.912000] dib0700: stk7700ph_xc3028_callback: XC2028_TUNER_RESET 0 [ 9363.912000] [ 9363.936000] xc2028 4-0061: Loading firmware for type=BASE F8MHZ (3), id . [ 9363.936000] dib0700: stk7700ph_xc3028_callback: XC2028_TUNER_RESET 0 [ 9363.936000] [ 9370.424000] xc2028 4-0061: Loading firmware for type=D2620 DTV8 (208), id . [ 9370.54] xc2028 4-0061: Loading SCODE for type=DTV8 SCODE HAS_IF_5400 (6200), id . [ 9370.60] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9370.624000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9370.624000] [ 9372.296000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9372.316000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9372.316000] [ 9373.888000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9373.908000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9373.908000] [ 9375.564000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9375.584000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9375.584000] [ 9377.14] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9377.16] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9377.16] [ 9378.812000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9378.832000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9378.832000] [ 9380.392000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9380.416000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9380.416000] [ 9382.068000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9382.088000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9382.088000] [ 9383.652000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9383.676000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9383.676000] [ 9385.332000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9385.352000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9385.352000] [ 9386.92] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9386.94] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9386.94] [ 9388.60] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9388.62] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9388.62] [ 9390.18] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9390.20] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9390.20] [ 9391.856000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9391.876000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9391.876000] [ 9393.444000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9393.468000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9393.468000] [ 9395.124000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9395.144000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9395.144000] [ 9396.716000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 9396.74] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 9396.74] [ 9398.392000] xc2028 4-0061: Device is Xceive 30
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Hi Hans, you where faster than me... I don't understand what you did with the firmware. I just extracted the xc3028-v27.fw from the win driver as commented in other threads. Then I added my card (pinnacle 320cx) to your patch with some mid-successfully results, this is the dmesg; [ 8067.028000] usb 1-1: new high speed USB device using ehci_hcd and address 4 [ 8067.16] usb 1-1: configuration #1 chosen from 1 choice [ 8067.16] dvb-usb: found a 'Pinnacle Expresscard 320cx' in cold state, will try to load a firmware [ 8067.164000] dvb-usb: downloading firmware from file ' dvb-usb-dib0700-1.10.fw' [ 8067.36] dib0700: firmware started successfully. [ 8067.864000] dvb-usb: found a 'Pinnacle Expresscard 320cx' in warm state. [ 8067.864000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 8067.864000] DVB: registering new adapter (Pinnacle Expresscard 320cx) [ 8068.236000] DVB: registering frontend 0 (DiBcom 7000PC)... [ 8068.236000] xc2028 4-0061: type set to XCeive xc2028/xc3028 tuner [ 8068.236000] input: IR-receiver inside an USB DVB receiver as /class/input/input13 [ 8068.236000] dvb-usb: schedule remote query interval to 150 msecs. [ 8068.236000] dvb-usb: Pinnacle Expresscard 320cx successfully initialized and connected. But when I start kaffeine i got this error; [ 8144.084000] xc2028 4-0061: Error on line 1063: -5 And when I try to scan I get more errors; [ 8176.032000] xc2028 4-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7 [ 8176.032000] dib0700: stk7700ph_xc3028_callback: XC2028_TUNER_RESET 0 [ 8176.032000] [ 8176.06] xc2028 4-0061: Loading firmware for type=BASE F8MHZ (3), id . [ 8176.06] dib0700: stk7700ph_xc3028_callback: XC2028_TUNER_RESET 0 [ 8176.06] [ 8182.548000] xc2028 4-0061: Loading firmware for type=D2620 DTV8 (208), id . [ 8182.668000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 8182.688000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 [ 8182.688000] [ 8184.364000] xc2028 4-0061: Device is Xceive 3028 version 1.0, firmware version 2.7 [ 8184.384000] dib0700: stk7700ph_xc3028_callback: XC2028_RESET_CLK 1 Any idea? is this related to the firmware?? Albert ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
