Re: I2C, lack of Windows information
From: Paul Hovnanian P.E. (Paul_at_Hovnanian.com)
Date: 03/28/05
- Next message: Robert Monsen: "Re: I2C, lack of Windows information"
- Previous message: Leif Erickson: ""REWIRE IT" with These SMD Prototyping Breadboards QFP TSSOP SOIC DIP"
- In reply to: Robert Monsen: "Re: I2C, lack of Windows information"
- Next in thread: Robert Monsen: "Re: I2C, lack of Windows information"
- Reply: Robert Monsen: "Re: I2C, lack of Windows information"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 27 Mar 2005 17:29:45 -0800
Robert Monsen wrote:
>
> Paul Hovnanian P.E. wrote:
> > Robert Monsen wrote:
> >
> >>michalk@awpi.com wrote:
> >>
> >>>I am trying to interface an on-motherboard Nvidia NForce2 I2C driver to
> >>>a Cygnal processor via the SMBus.
> >>>
> >>>Now, normally I would do this all Linux, and it would be trivial, but
> >>>my development environment is Windows for the Cygnal (now SiLabs).
> >>>Don't go off trying to tell me to change my IDE. There are other
> >>>issues.
> >>>
> >>>My problem is that I can't find any documentation at all on accessing
> >>>the SMBUS that's built into the motherboard. There's lots of
> >>>information on using adapters, and there's some MSDN stuff from
> >>>Microsoft on the SMBus, but it's not clear at all how I access it.
> >>>
> >>>The SMBus is working. I've installed some temperature monitoring
> >>>software, and my oscilloscope shows activity. I've got all the wires,
> >>>just questions on where the #@$%&#(*%$ API is to talk to it.
> >>>
> >>>After reading this, I want to make it clear that I'm not having
> >>>problems on the 8051 processor side. This is a Windows question.
> >>>
> >>
> >>For premade tools, try here:
> >>
> >>http://www.i2ctools.com/index.html
> >>
> >>Chances are, the temperature sensors on the mainboard are I2C. Thus, if
> >>you can figure out how they get read, you can figure out how to read
> >>your device.
> >>
> >>Try calling or emailing the mainboard mfgr.
> >
> >
> > Unless the MS Windows SMBus drivers have control of the bus and don't
> > provide users with the tools to add new device drivers.
> >
>
> One good way to figure this stuff out would be to examine the I2C
> package from the linux sources. Then, a device driver written for
> windows might be able to play games and take over the hardware. This is
> a guess.
Maybe. But I'm wondering if Windows has an acessible API that one can
use to register a driver for a new device added to their bus. Since
modifying motherboards isn't sometthing th typical user does with their
PC, they might not have given users access (API documentation, header
files, etc.) to their bus drivers.
-- Paul Hovnanian mailto:Paul@Hovnanian.com ------------------------------------------------------------------ Madness takes its toll. Please have exact change.
- Next message: Robert Monsen: "Re: I2C, lack of Windows information"
- Previous message: Leif Erickson: ""REWIRE IT" with These SMD Prototyping Breadboards QFP TSSOP SOIC DIP"
- In reply to: Robert Monsen: "Re: I2C, lack of Windows information"
- Next in thread: Robert Monsen: "Re: I2C, lack of Windows information"
- Reply: Robert Monsen: "Re: I2C, lack of Windows information"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
