Skip to contentSkip to conversation

Kworld 315U help?

DISCUSSION Franklin Meng 2 participants 6 messages Oct 21, 2009 – Oct 22, 2009 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

I was wondering if someone would be able to help me with getting the analog and inputs for the Kworld 315U working. I was able to get the digital part working with help from Douglas Schilling and wanted to get the remaining portions of the device working.

I have traces but have not made much progress. In addition I also have some questions about the information that the parse_em28xx.pl skips and does not decode.

For example here is some of the data that doesn't seem to be decoded..
unknown: 40 03 00 00 a0 00 01 00 >>> 08
unknown: c0 02 00 00 a0 00 01 00 <<< d0
unknown: 40 03 00 00 a0 00 01 00 >>> 08
unknown: c0 02 00 00 a0 00 01 00 <<< d0
unknown: 40 03 00 00 a0 00 01 00 >>> 22
unknown: c0 02 00 00 a0 00 01 00 <<< 01
unknown: 40 03 00 00 a0 00 01 00 >>> 04
unknown: c0 02 00 00 a0 00 02 00 <<< 1a eb
unknown: 40 03 00 00 a0 00 01 00 >>> 20
unknown: c0 02 00 00 a0 00 01 00 <<< 46
unknown: 40 03 00 00 a0 00 01 00 >>> 14
unknown: c0 02 00 00 a0 00 04 00 <<< 4e 07 01 00

Anyways, any help that can be provided is appreciated.

Thanks,
Franklin Meng

#1 lore raw
Quoted 18 lines · Franklin Meng

I was wondering if someone would be able to help me with getting the analog and inputs for the Kworld 315U working.  I was able to get the digital part working with help from Douglas Schilling and wanted to get the remaining portions of the device working.

I have traces but have not made much progress.  In addition I also have some questions about the information that the parse_em28xx.pl skips and does not decode.

For example here is some of the data that doesn't seem to be decoded..
unknown: 40 03 00 00 a0 00 01 00 >>> 08
unknown: c0 02 00 00 a0 00 01 00 <<< d0
unknown: 40 03 00 00 a0 00 01 00 >>> 08
unknown: c0 02 00 00 a0 00 01 00 <<< d0
unknown: 40 03 00 00 a0 00 01 00 >>> 22
unknown: c0 02 00 00 a0 00 01 00 <<< 01
unknown: 40 03 00 00 a0 00 01 00 >>> 04
unknown: c0 02 00 00 a0 00 02 00 <<< 1a eb
unknown: 40 03 00 00 a0 00 01 00 >>> 20
unknown: c0 02 00 00 a0 00 01 00 <<< 46
unknown: 40 03 00 00 a0 00 01 00 >>> 14
unknown: c0 02 00 00 a0 00 04 00 <<< 4e 07 01 00

Quoted 1 line

Anyways, any help that can be provided is appreciated.

Those look like i2c commands to the onboard eeprom, which is at i2c address 0xa0. For example:

unknown: 40 03 00 00 a0 00 01 00 >>> 04 // set eeprom read offset to 0x04
unknown: c0 02 00 00 a0 00 02 00 <<< 1a eb // read two bytes back from eeprom

Cheers,

Devin

Signature · 2 lines
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
#2 lore raw

Devin,

Thanks for the info.. Should the parse_em28xx.pl script be updated to reflect this? I'm assuming other em28xx boards also have the eeprom at address 0xa0.

There are a couple more entries that I am unsure about.. I'll post those when I get home tonight.

Are you interested in looking at some traces? I am pretty sure I have most of the analog and input stuff figured out though I probably don't have the GPIO sequence correct. Anyways, if your interested I can send you what I know.

Thanks
Franklin Meng

Quoted 59 lines · Devin Heitmueller

From: Devin Heitmueller <[email protected]>
Subject: Re: Kworld 315U help?
To: "Franklin Meng" <[email protected]>
Cc: [email protected]
Date: Wednesday, October 21, 2009, 5:55 AM

Quoted 1 line · Franklin Meng

I was wondering if someone would be able to help me

with getting the analog and inputs for the Kworld 315U working.  I was able to get the digital part working with help from Douglas Schilling and wanted to get the remaining portions of the device working.

Quoted 2 lines

I have traces but have not made much progress.  In

addition I also have some questions about the information that the parse_em28xx.pl skips and does not decode.

Quoted 2 lines

For example here is some of the data that doesn't seem

to be decoded..

Quoted 4 lines

unknown: 40 03 00 00 a0 00 01 00 >>> 08
unknown: c0 02 00 00 a0 00 01 00 <<< d0
unknown: 40 03 00 00 a0 00 01 00 >>> 08
unknown: c0 02 00 00 a0 00 01 00 <<< d0

Quoted 8 lines

unknown: 40 03 00 00 a0 00 01 00 >>> 22
unknown: c0 02 00 00 a0 00 01 00 <<< 01
unknown: 40 03 00 00 a0 00 01 00 >>> 04
unknown: c0 02 00 00 a0 00 02 00 <<< 1a eb
unknown: 40 03 00 00 a0 00 01 00 >>> 20
unknown: c0 02 00 00 a0 00 01 00 <<< 46
unknown: 40 03 00 00 a0 00 01 00 >>> 14
unknown: c0 02 00 00 a0 00 04 00 <<< 4e 07 01

00

Quoted 2 lines

Anyways, any help that can be provided is

appreciated.

Those look like i2c commands to the onboard eeprom, which is at i2c
address 0xa0.  For example:

unknown: 40 03 00 00 a0 00 01 00 >>> 04
     // set eeprom read offset to 0x04
unknown: c0 02 00 00 a0 00 02 00 <<< 1a eb
// read two bytes back from eeprom

Cheers,

Devin

Signature · 7 lines
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line "unsubscribe
linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw

Here are some more stuff in the trace that was not decoded by the parse_em28xx script..

So what we know from this list of unknowns...

0xa0 is the eeprom
0x4a is the SAA
0x42 ??.
0xd0 ??
0x20 ??
0xc6 ??
0xc4 ??
0xc2 Thomson tuner.

unknown: c0 02 00 00 42 00 01 00 <<< fd
unknown: c0 02 00 00 4a 00 01 00 <<< 11
unknown: 40 03 00 00 a0 00 01 00 >>> 2d
unknown: c0 02 00 00 a0 00 01 00 <<< 1c
unknown: c0 02 00 00 20 00 01 00 <<< fe
unknown: c0 02 00 00 d0 00 01 00 <<< 10
unknown: 40 03 00 00 a0 00 01 00 >>> 0a
unknown: c0 02 00 00 a0 00 01 00 <<< 5a
unknown: 40 03 00 00 a0 00 01 00 >>> 2e
unknown: c0 02 00 00 a0 00 01 00 <<< 00
unknown: 40 03 00 00 a0 00 01 00 >>> 0a
unknown: c0 02 00 00 a0 00 01 00 <<< 5a
unknown: c0 02 00 00 c6 00 01 00 <<< 00
unknown: c0 02 00 00 c4 00 01 00 <<< 10
unknown: c0 02 00 00 c2 00 01 00 <<< b4

Anyone know what are at the other addresses? I don't know if they are important or not.

Thanks,
Franklin Meng

Quoted 106 lines · Franklin Meng

From: Franklin Meng <[email protected]>
Subject: Re: Kworld 315U help?
To: "Devin Heitmueller" <[email protected]>
Cc: [email protected]
Date: Wednesday, October 21, 2009, 8:06 AM Devin,

Thanks for the info..  Should the parse_em28xx.pl script be updated to reflect this?  I'm assuming other em28xx boards also have the eeprom at address 0xa0.

There are a couple more entries that I am unsure about..  I'll post those when I get home tonight.

Are you interested in looking at some traces?  I am pretty sure I have most of the analog and input stuff figured out though I probably don't have the GPIO sequence correct.  Anyways, if your interested I can send you what I know.

Thanks
Franklin Meng

--- On Wed, 10/21/09, Devin Heitmueller <[email protected]>

Quoted 9 lines · wrote:

From: Devin Heitmueller <[email protected]>
Subject: Re: Kworld 315U help?
To: "Franklin Meng" <[email protected]>
Cc: [email protected]
Date: Wednesday, October 21, 2009, 5:55 AM

Quoted 1 line · Franklin Meng

I was wondering if someone would be able to help

me

Quoted 1 line

with getting the analog and inputs for the Kworld

315U

Quoted 1 line

working.  I was able to get the digital part working

with

Quoted 1 line

help from Douglas Schilling and wanted to get the

remaining

Quoted 3 lines

portions of the device working.

Quoted 2 lines

I have traces but have not made much progress.

 In

Quoted 1 line

addition I also have some questions about the

information

Quoted 3 lines

that the parse_em28xx.pl skips and does not decode.

Quoted 2 lines

For example here is some of the data that doesn't

seem

Quoted 9 lines

to be decoded..

Quoted 8 lines

unknown: 40 03 00 00 a0 00 01 00 >>> 08
unknown: c0 02 00 00 a0 00 01 00 <<< d0
unknown: 40 03 00 00 a0 00 01 00 >>> 08
unknown: c0 02 00 00 a0 00 01 00 <<< d0
unknown: 40 03 00 00 a0 00 01 00 >>> 22
unknown: c0 02 00 00 a0 00 01 00 <<< 01
unknown: 40 03 00 00 a0 00 01 00 >>> 04
unknown: c0 02 00 00 a0 00 02 00 <<< 1a

eb

Quoted 4 lines
Quoted 4 lines

unknown: 40 03 00 00 a0 00 01 00 >>> 20
unknown: c0 02 00 00 a0 00 01 00 <<< 46
unknown: 40 03 00 00 a0 00 01 00 >>> 14
unknown: c0 02 00 00 a0 00 04 00 <<< 4e

07 01

Quoted 6 lines

00

Quoted 2 lines

Anyways, any help that can be provided is

appreciated.

Those look like i2c commands to the onboard eeprom,

which

Quoted 17 lines

is at i2c
address 0xa0.  For example:

unknown: 40 03 00 00 a0 00 01 00 >>> 04
     // set eeprom read offset to 0x04
unknown: c0 02 00 00 a0 00 02 00 <<< 1a eb
// read two bytes back from eeprom

Cheers,

Devin

Signature · 4 lines
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line

"unsubscribe

Quoted 4 lines

linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

#4 lore raw
Quoted 4 lines · Franklin Meng

Here are some more stuff in the trace that was not decoded by the parse_em28xx script..

So what we know from this list of unknowns...

Quoted 8 lines

0xa0 is the eeprom
0x4a is the SAA
0x42 ??.
0xd0 ??
0x20 ??
0xc6 ??
0xc4 ??
0xc2 Thomson tuner.

c4 and c6 are probably also the tuner. I know that K-World makes some products with the same name but different regions. Is your version of the 315U an ATSC hybrid tuner? If so, then one of those addresses is probably the demod.

Also, the trace you sent is just an excerpt, but it's possible that the driver is probing for devices and the requests are failing because the hardware isn't present (the Windows driver supports a variety of different hardware combinations). Usually you can tell by looking for a read from register 0x05 immediately after the i2c read. If register 0x05 is nonzero, then the i2c read operation failed.

Devin

Signature · 2 lines
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
#5 lore raw

Devin,

Quoted 7 lines

c4 and c6 are probably also the tuner.  I know that K-World makes some
products with the same name but different regions.  Is your version of
the 315U an ATSC hybrid tuner?  If so, then one of those addresses is
probably the demod.

I believe the device I have is a hybrid tuner since it does both digital and analog.

Quoted 12 lines

Also, the trace you sent is just an excerpt, but it's possible that
the driver is probing for devices and the requests are failing because
the hardware isn't present (the Windows driver supports a variety of
different hardware combinations).  Usually you can tell by looking for
a read from register 0x05 immediately after the i2c read.  If register
0x05 is nonzero, then the i2c read operation failed.

This is good information to know. Here are the list of components that are on the board along with the address..

1. LG LGDT3303 - 0x1c
2. Lattice ISP2032VE - ?? don't know the address
3. Phillips SAA7113H - 0x4a
4. Empia EMP202
5. Empia EM2882
6. Thomson DTT 7611A - 0xc2

In addition there is a TDA at 0x86 and we also know the eeprom is at 0xa0.
I'm attaching the output that I parsed the using the updated parse1b_sniffusb2.pl script as well as the output from a slightly modified parse_em28xx.pl. I modified the parse_em28xx.pl to output the stuff it did not decode.

In the tar ball are 2 files. emparse1new.out (obtained using parse_em28xx.pl) and newlog.out (obtained using the updated script)

These traces are for the component inputs of the kworld 315U device. I have other traces as well for the TV and Svideo inputs. You can find pictures of the device here.. http://www.linuxtv.org/wiki/index.php/KWorld_ATSC_315U

In the source this I added this information that has been commented out. I believe this is how the the board is configured according to what I decoded out of the traces some time ago.

               /* Analog mode - still not ready */
                /*.input        = { {
                        .type = EM28XX_VMUX_TELEVISION,
                        .vmux = SAA7115_COMPOSITE2,
                        .amux = EM28XX_AMUX_VIDEO,
                        .gpio = em2882_kworld_315u_analog,
                        .aout = EM28XX_AOUT_PCM_IN | EM28XX_AOUT_PCM_STEREO,
                }, {
                        .type = EM28XX_VMUX_COMPOSITE1,
                        .vmux = SAA7115_COMPOSITE0,
                        .amux = EM28XX_AMUX_LINE_IN,
                        .gpio = em2882_kworld_315u_analog1,
                        .aout = EM28XX_AOUT_PCM_IN | EM28XX_AOUT_PCM_STEREO,
                }, {
                        .type = EM28XX_VMUX_SVIDEO,
                        .vmux = SAA7115_SVIDEO3,
                        .amux = EM28XX_AMUX_LINE_IN,
                        .gpio = em2882_kworld_315u_analog1,
                        .aout = EM28XX_AOUT_PCM_IN | EM28XX_AOUT_PCM_STEREO,
                } }, */

can you double check this to see if I got things correct? I think all I need is the correct GPIO sequence but I am not sure.

Thanks,
Franklin Meng