Andy, I think this problem is due to ATSC chip and EEPROM sharing same I2C bus. This is like chicken and Egg problem. And initially Cx18 should be initialzed properly to control Cx24227 chip but before that you need to collect EEPROM information to properly initialize Cx18. Also the Cx24227 is mainly controlled through GPIO pins of Cx18. The only way we can solve this problem is isolating EEPROM I2C bus from Cx24227 chip I2C bus. Cx24227 needs certain steps to initialize if not it pulls down I2C bus lines and hence EEPROM cannot be accessed. I believe this is why you do get the EEPROM ERROR.
If any of you can do hardware modifications, Disconnect EEPROM I2C lines from Cx24227 chip lines and connect them to Analog tuner I2C lines and modify the driver to hook up to correct I2C bus. This should solve the problem immediately. Last when I verified the schematics, EEPROM I2C lines are shared with Cx24227 chip I2C lines. I had dealt with similar problems on one of our evaluation boards, this solution immediately fixed the problem. Or if you guys can follow the Cx24227 initialization sequence before accessing EEPROM, then that should work too. But I doubt if that is possible at all or not. The only reason that it is working in Windows might be some timing in my view. There may not be any issue with PCI spec. and probably a not related problem. Or Can you try Raptor Analog board that we sent on same system and see if you can reproduce the problem? Hope this helps. Thanks Sri ________________________________________ From: Andy Walls [EMAIL PROTECTED] Sent: Saturday, August 02, 2008 2:25 PM To: [email protected]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: cx18: Possible causal realtionship for HVR-1600 I2C errors Quite a few HVR-1600 users have reported cx18 driver I2C related problems usually with the following errors present: tveeprom 1-0050: Huh, no eeprom present (err=-121)? tveeprom 1-0050: Encountered bad packet header [ff]. Corrupt or not a Hauppauge eeprom. s5h1409_readreg: readreg error (ret == -121) cx18: frontend initialization failed cx18-0: DVB failed to register and an unusable HVR-1600/CX23418 under linux. On the surface the problem appeared to be related to the devices on the I2C buses of the HVR-1600. Given the data from a number of user reports piling up, I think I can say that it's likely a PCI v2.2 or earlier bus problem with the CX23418 under linux. The I2C bus errors appear to be just a symptom of a larger underlying problem. The CX23418 is a PCI v2.3 device according to Conexant's publicly available product literature. The users who experience the dreaded -121 (-EREMOTEIO) errors under linux, all (I need to double check with Michael) seem to have the HVR-1600 card installed in a machine with a PCI v2.2 or earlier chipset. **So I suspect, under linux at least, the HVR-1600 or CX23418 won't work with a PCI v2.2 or earlier chipset.** Here are my collected reports. Non-working (under linux) setups: Reporter: Scott PCI chipset: Intel 82850 & 82801BA rev 4 PCI version: v2.2 AGP: Yes Video: PCI nVidia NV34 GeForce FX 5500 Symptoms: tveeprom ret=-121 error, card not working Reporter: Ryan Watts PCI chipset: VIA VT8363/8365 & VT82C686 PCI version: v2.2 (VT8363) AGP: Yes Video: AGP nVidia NV18 GeForce4 MX 4000 Symptoms: tveeprom ret=-121 error, card not working Reporter: Michael PCI Chipset: ? PCI Version: ? AGP: ? Video: ? Symptoms: I2C bus intermittently seems to work as intialization completes including tveeprom and dvb demodulator init. Analog tuner init doesn't seem to happen. HVR-1600 cannot be made to do useful work. Reporter: Matt Loomis PCI Chipset: VIA VT8363/8365 & VT82C686 PCI Version: v2.2 (VT8363) AGP: Yes Video: AGP ATI Technologies Inc Radeon RV200 QW [Radeon 7500] PCI Silicon Integrated Systems [SiS] 86C326 5598/6326 Symptoms: cx18 driver fails to init with the tveeprom ret=121 error. Both sets of CX23418 I2C control registers are returning bogus values when read (they don't match what was just written). ***Card works under Windows XP with Hauppauge drivers.**** Reporter: Michael Papet PCI Chipset: Intel 82845G & 82801DB PCI Version: v2.2 (82801DB) AGP: ? Video: 82845 Integrated Graphics Symptoms: cx18 driver fails to init at boot time with I2C ret=-121 errors. If blacklisted for boot and modprobed later, driver appears to initialize. Card seems unable to be tuned. Reporter: Gerhard Wittreich PCI Chipset: Intel 82845 & 82801BA PCI Version: V2.2 (82801) AGP: Yes Video: AGP ATI Technologies Inc Rage 128 Pro Ultra TF Symptoms: cx18 driver fails to init due to apparent I2C bus errors, but one set of CX23418 I2C control registers is acting normally while the other set is returning bogus values when read (identical to the values in Matt Loomis' reports). Working setups: Reporter: Gerhard Wittreich PCI Chipset: nVidia MPC61 PCI Version: Unknown but it's a PCIe chipset, so assuming > v2.2 AGP: no Video: PCIe nVidia Corporation G70 [GeForce 7600 GT] Symptoms: No problems; card works. Reporter: Gerhard Wittreich PCI Chipset: Intel 82915G* & 82801F* PCI Version: v2.3 (82801F*) AGP: no Video: ? Symptoms: No problems; card works. Reporter: Andy Walls PCI Chipset: ATI RS740 & SB700 PCI Version: v2.3 (SB700) AGP: no Video: PCI ATI Technologies Inc Radeon 2100 Symptoms: No problems; card works. I'd be interested in additional reports of: 1. Errors I made in the above collected data. 2. A CX23418 based card working properly or not under Linux (or Windows) in a machine with a PCI v2.2 or earlier chipset. 3. The differences between PCI v2.2 and v2.3 that would cause PC v2.2 host writes to a PCI v2.3 device to fail or for reads to return bogus values (i.e. reading back 0x7 after a value of 0x21c0b was just written.)? 4. If anyone knows what magical tweak Windows or the Hauppauge HVR-1600 Windows driver is making to get the HVR-1600 working with (at least) the VIA VT8363 & VT82C686. Regards, Andy Conexant E-mail Firewall (Conexant.Com) made the following annotations --------------------------------------------------------------------- ********************** Legal Disclaimer **************************** "This email may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message in error, please advise the sender by reply email and delete the message. Thank you." ********************************************************************** --------------------------------------------------------------------- _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
