I-Appliance BBS
The Official Source for Internet Appliance Upgrades and Mods

Click Here!
BBS Main List | Sign In | Sign Up | Search | Help | Linux-Hacker.netReply to Thread | Printer |

Home / Other I-Appliances / Philips/AOL-TV
Sound
Sound

New MessageSound (modified 0 times) TempestII
Profile
Still no luck getting the volume to a reasonable level from DOS. I did find some good info on the cyrix chip at http://www.ecn.purdue.edu/~laird/Linux/iDVD3036/cdrom/ Maybe someone w/programming skills can figure out what is needed to enable the onboard amp. This utility does appear to work and allows you to set the volume and DMA http://www.ecn.purdue.edu/~laird/Linux/iDVD3036/cdrom/Drivers/MediaGX-CX5530/UTL/

Chris

10-09-2002 18:31:06

New MessageRE:Sound (modified 0 times) mevanson
Profile
While the Cyrix chip can be used to provide sound, it is the Cyberpro chip in this box that is providing the audio that is tied to the RCA outputs on the back of the box.
10-09-2002 20:22:35

New MessageRE:Sound (modified 0 times) digilexic
Profile
It looks like most of the cyberpro mediaGX chips have the AC97 codec, has anyone tried this? Most sites say the 5005 does NOT support audio, but you have said the audio lines are tied into the chip.

Also, has anyone got the TV functions working under another OS? Perhaps the audio is directly related to the audio portion of the tv tuner? It seems to me that the 5005 controls the TV tuner functions based on what I have read.

10-22-2002 09:36:43

New MessageRE:Sound (modified 0 times) mevanson
Profile
I believe that the cyberpro chip is not labelled properly for some reason. Enumerating devices on the PCI bus reveals that the 5050 is there, and I am able to program the 5050.

Additionally, loading the trident module under Linux works fine. At least the module identifies the chip and loads fine. But it doesn't work.

Additionally, pins 46 (SDATA_OUT), 48 (SDATA_IN), 45 (BIT_CLK), and 52 (SYNC) from CyberPro chip are connected to the appropriate ac97 pins on the AD1819. At least the trace to that vicinity of the board.

The other problem with accessing SB16 sound is that at startup, the 5530 is in SB emulation mode and handling the appropriate legacy ports and interrups (A220 I5 D1). I've sucessfully turned that handling off and I've been able to place the cyberpro chip into a mode that the DOS software will identify it as a sound blaster.

The DOS apps don't work. They end up hanging or giving me an error.

So in my investigation, it seems that the ac97 codec (AD1819) is not responding to my requests via the cyberpro registers. It may be that I've hosed my board in some way or another.

I've created a small executable that tests the ac97 codec and I'd like someone to boot their machine clean, run the command, and post the results here. Do so will help me with my investigation in that I'll know whether something is wrong with my box or if I still don't have everything down just right.

The executable can be downloaded from http://www.twosillies.com/aoltv/aolac97.exe. If someone could do me this favor, perhaps we can get SB16 emulation working under DOS.

Thanks in advance.

--matt

11-03-2002 18:03:37

New MessageRE:Sound (modified 0 times) mevanson
Profile
One other note that I discovered, but have not tested.

While the Cyberpro AC97 codec lines do run to the AD1819 (you can see the traces on the back of the board), it appears that the lines of the MediaGX have been run that way as well, but they do not connect.

However, on the back, there is what looks like pads for 4 jumpers. While I've not traced the lines, I'd bet that if these for jumpers were connected, the codec would be connected to the Media GX. Not sure, just a theory.

11-03-2002 18:21:59

New MessageRE:Sound (modified 0 times) mevanson
Profile
Actually, now that I look at the pads again, I'll bet they're some sort of resistor pads. But the fact that both devices have lines running to that area suggests that there may be a method of having the lines connected to either device.
11-03-2002 18:26:22

New MessageRE:Sound (modified 0 times) pdp1145
Profile | Email
Matt,

Basically a clean boot.
Here's what I got:

PCI BIOS found
Found Cyberpro 5050 (device 14 function 1 on bus 0)
IO access mode specified
IO addr: 0xf800
audio: 0x0
interrupt: 0x9
ac97 not present
couldn't read ac97 register
vendor id1: 0x0000
vendor id2: 0x0000
VOL master: 0x0000
VOL aux : 0x0000
VOL mono : 0x0000
power down: 0x0000
ASR0 : 0x00000000
AINTEN : 0x00000000
MISCINT : 0x00008000
SBCL : 0x00000000
SBCTRL : 0x00000000
GC0 : 0x00000000
GC1 : 0x00000000
ACGPIO : 0x00000000
SCTRL : 0x00014000

11-03-2002 19:59:37

New MessageRE:Sound (modified 0 times) mevanson
Profile
OK, another update.

The ac97 codec is quite definitely attached to the 5530. I can actually pass current through the lines all the way from AD1819 to the where they go under 5530. While I can't tell exactly which 5530 pins they are attached to, they are going under the chip at the location of the ac97 pins.

Looking again at how the cyberpro is attached to the codec, it appears that it is connected to the digital inputs. The pins on the cyberpro 5050 can serve one of two uses: either ac97 or SPDIF. My guess is that output to through the cyberpro actually provides digital input to the codec and can be mixed with other sources of input, but the ac97 codec is actually controlled by the 5530.

With my initial tests, I am unable to get the codec to respond via the 5530, but I will continue to see what I can do that route.

All this said, I no longer need any one to execute my previous request.

--matt

11-03-2002 20:20:05

New MessageRE:Sound (modified 0 times) mevanson
Profile
Thanks pdp1145.

You confirmed what I thought. The code was also unable to connect to the codec on your machine.

11-03-2002 20:21:12

New MessageRE:Sound (modified 0 times) mevanson
Profile
OK. The codec is definitely connected to the 5530. After much pain and agony, I discovered that I'd broken the trace to the reset pin on the AD1819. Apparently, I'd done this very early on because I've never had sound on the machine.

I've repaired the break and audio is now working.

It's quiet for me. I can get it to be a little bit louder via programming the master and PCM out volumes in the codec, but it isn't all the significant an increase. Even connecting the system to my home theater system, I'm not getting much volume until I have the volume turned way up. Not sure what the cause of this is.

The volume exhibits the same behaviour under windows 98.

11-04-2002 15:24:55

New MessageRE:Sound (modified 0 times) pdp1145
Profile | Email
Matt,

"Even connecting the system to my home theater system, I'm not getting much volume until I have the volume turned way up. Not sure what the cause of this is. "

That is exactly what I get. Also I have no sound on the RF signal.

Max

11-05-2002 05:19:21

New MessageRE:Sound (modified 0 times) mevanson
Profile
I don't get the sound either on the RF. I tried that route when I failed to get the volume out of the line-outs.
11-05-2002 08:22:36

New MessageRE:Sound (modified 0 times) pbrandonc00
Profile
is there a line in or mic in??
11-08-2002 03:52:30

New MessageRE:Sound (modified 0 times) mevanson
Profile
pbrandonc00 --

There is a line in.

Everyone --

I am not able to get the sound over the RF signal and it comes at appropriate volume. I did this by unmuting the ac97 codecs mono-out. Unfortunately, this means that the audio sent over RF is done via mono. So that is not the route we want to go.

I know that the output levels between RF and line-out can somehow be matched. I attached both RF and lineout to my TV and I get about the same volume through both mechanisms as I switch between them.

--matt

11-18-2002 10:27:46

New MessageRE:Sound (modified 0 times) mevanson
Profile
Clarification on my last post: I AM able to get audio via the RF out. Also, the matched volume was reproducible with the AOL OS, not with anything else, so it is performing some action that we are not.
11-18-2002 17:52:43

New MessageRE:Sound (modified 0 times) mevanson
Profile
Good news everyone!

I've got the volume working properly over line out. Only in Win98 and DOS for right now, but it shouldn't be too hard to make a Linux initialization routine to do it.

Basically, the BT835 chip has a number of general purpose I/O (GPIO) lines. For those that don't know, systems designers can pretty much use them as they see fit to control or monitor other parts of the system. Well, GPIO6 is tied to the output system. It must be raised in order for the sound to come out at full volume.

I'm not sure what purpose this serves, but I suspect it was designed this way to prevent irregular output to your receiver during system initialization. Perhaps, it even offers a bit of protection. I only wish they tied it to the GPIO pins on either the 5530 or Cyberpro because both are much easier to program. Programming them on the 835 is a little more complex because it is tied to the Cyberpro via an i2c connection and that is how you program it. Fortunately, these tools are already here for us!

First, you'll need to download either i2c.exe (command line, ideal for autoexec.bat) and/or 5ktvio.exe from
http://www.ecn.purdue.edu/~laird/Linux/iDVD3036/cdrom/Document/VGA-Igs5k/Utility/.

To use the command-line version:
C:\> i2c 88 22 0
C:\> i2c 88 21 40

The first command tells the BT835 to use all GPIO pins for output (really only 6 and 7 are tied to anything).
The second line raises GPIO6 (1 shl 6)

To use the Windows version, execute 5ktvio.exe while running Win98. I'd suspect it'd work just fine under Win95.

In the I2C section of the application, do the following:
1) Set addr to 88
2) Set subaddr to 22
3) Set data to 0
4) Click Send. Result should show OK.
5) Set subaddr to 21
6) Set data to 40
7) Click Send. Result should show OK.
8) Run your favorite audio application.

On a side note, the LED labeled Connected on the front of the box is connected to one of the GPIO pins on the 5530. We should be able to make it display disk or network activity.

Enjoy!

11-22-2002 23:09:52

New MessageRE:Sound (modified 0 times) keith721
Profile
Matt:

Great news - - congratulations on your success !!

keith721

11-23-2002 13:30:37

Reply to Thread | Printer |
All times are PSTPowered by UltraBoard v1.62



Copyright © 2000, Netmake Inc. All Rights Reserved.
See Terms and Conditions for more information.




i-opener opener laptop notebook computer help drivers dll free windows dos repair fix linux mac macintosh 2000 95 98 nt pc configure hardware software sound video netscape explorer network networking lan wan software cmos fat bios printer card mouse modem ide scsi cd rom controllers scanner tape hard drive cgi scripts source code mp3