[linux-dvb] Re: TDA10046 firmware upload problems

["Antonio V." <tonecho@vinas.org>]

Hi Christian.

> Is everything working fine now for you?
> What about switching channels with vdr? Does it work all the time and do
>   they switch quickly?

I am reading some manual to form vdr. But I have at the moment not been able 
to make work it (it is the first time that I will use it, and not very well 
still as it works).

Therefore, I can comment to you what it happens to me to tzap, and with xine, 
that is the two applications that I have used until the moment.

I receive the channels solely in two frequencies, one for national channels, 
and another one for regional channels. The signals are transmitted by 
different emitting centers.

With tzap I believe that they pass things somewhat strange in the used 
frequency to receive the national channels.:

-----
debian:/usr/src/dvb-apps/util/szap# ./tzap "tve 1" -r
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/root/.tzap/channels.conf'
tuning to 778000000 Hz
video pid 0x0065, audio pid 0x0067
status 00 | signal 8e8e | snr 5656 | ber 0001fffe | unc 00000000 |
status 1f | signal 0000 | snr fefe | ber 00000482 | unc ffffffff | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000422 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000420 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 00000402 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 000003b6 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 000003ca | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 000003d2 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 0000038a | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 00000384 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 0000039e | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 0000037c | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 0000037c | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 0000046a | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000480 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 000003e8 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 000003d6 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 00000450 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 0000040a | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 00000422 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 00000450 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000440 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000442 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000444 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 000004b6 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000424 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 0000041c | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 00000432 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000410 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 000003ea | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 0000040c | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000392 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 000003a4 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 000003c8 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 00000414 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 000003c4 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 0000044c | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000482 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 000003d6 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr 0000 | ber 000003d8 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 000003f0 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fefe | ber 00000424 | unc 00000000 | FE_HAS_LOCK

-----

The value snr oscillates much, nevertheless, if I execute xine stdin://mpeg2 
< /dev/dvb/adapter0/dvr0, the signal is seen perfectly. It happens to me the 
same with all the channels of this frequency.

And in the frequency used for regional channels, it passes the following thing 
to me:

-----
debian:/usr/src/dvb-apps/util/szap# ./tzap tvg -r
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/root/.tzap/channels.conf'
tuning to 810000000 Hz
video pid 0x00a0, audio pid 0x00a1
status 00 | signal 9191 | snr 9393 | ber 0001fffe | unc 00000000 |
status 1f | signal 0000 | snr fdfd | ber 000022ae | unc ffffffff | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 0000211a | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00002230 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 000022ac | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 000022a8 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00002260 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 000022de | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 0000220c | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 000021f0 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 0000224e | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 000020d8 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00002182 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 0000218c | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00002262 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 000020b6 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00002182 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 000020f6 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00002048 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 000020f0 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00002154 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00002106 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 000020fa | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00002012 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00001fa0 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr fdfd | ber 00001fea | unc 00000000 | FE_HAS_LOCK
-----

In this case, as you can verify, the value snr is constant. Of course if I 
execute xine, the signal is seen perfectly.

With tzap, as you can see, the channel is practically tuned at the moment. 

Later I copy the channels.conf to the xine configuration directory, and I 
execute it, with the dvb interface, and the change of channels works to me 
well with all the channels that I receive. Approximately the change of 
channels does in 1-2 seconds (counting on the load of buffers that does 
xine).

You have tested with xine?. It does to you just like vdr?

> Even with the latest CVS I still have problems that the frontend seems
> to have lock but I do not get a picture with vdr in transfer mode.
> On the mailing list Robert Schlabbach wrote something about two
> different modes for the TS interface. Can this be a solution?

Moan not to be able to respond, since I am not developer and I do not 
understand it O:-). Even so if you want that I makes some change in the 
source code, you do not have but that to say it to me and I comment to you 
what happens.

> But if it works fine for you(Antonio), so I assume that the mode does
> not have to be changed then.
>
> The antenna signal must be ok(strong enough). The transmitter is only
> 1km away from my machine. I tried it with amplifier and without. No
> effect. I tried the card in my desktop machine with Windows XP and it
> worked fine.
>
> Which mainboard/chipset do you use?

My mainboard is a P4S5A/DX+, with SIS645DX/SIS962L chipset. And I also have 
all PCI slots equipped.

> May it is really a hardware problem?

> I am using a K7SOM+ with SIS Chipset. All PCI slots are equipped.
> Maybe I should try to swap the PCI slot?!

I don't believe it since you comment that under Windows XP it works to you 
well, so I understand that this would have to discard a hardware problem, and 
that you must change of pci.

Best regards,
Antonio.