S
SergeV
Hi group,
Could somebody please help me to start with SMBus.
I plan to access Maxim-Dallas MAX1617 sensor connected to
SMBus (which is part of PCI bus)
and want to try doing something before hardware will come.
I used DevCon to enumerate SMBus drivers. Them are 2 on my machine:
1) Intel SM BIOS drvr (hwid: *ISBB0C01)
2) Microsoft SM BIOS drvr (hwid: root\mssmbios)
I guess (1) is vendor-supplied miniport and (2) is that DDK's class
driver.
Am I correct? Why it's name not an Smbus.sys as documented in the DDK?
I use a oscilloscope to look at SMBus wires.
At power up I see bus diagram, therefore SMBus controller is in there
and firmware BIOS see it.
But at and after WinXP startup nothing happens on the wire (couldn'd
guess why).
In the hope to see on the scope's screed SMBus enumeration diagram
I entered from the console " Devcon rescan", but nothing happened again.
I was unable to find in the DDK docs, nor in h-files any SMBUS_GUID
mentioned/defined
(as is recommended in the doc "SMBus device driver ext. arc. spec." by
smbus.org).
How do I enumerate/open my device?
Do I need to develop my own filter/client and is smbbatt sample (and
%windir%battery.inf)
good as a starting point for it or mssmbios is sufficient to read SMBus
device data from
within client?
How do I know, which SMBus version is supported (1.1 or 2.0)?
If later I add my own SMBus 2.0 device (slave controller) will it be
supported
by standard drivers?
Thank you for any comments.
Serge.
Could somebody please help me to start with SMBus.
I plan to access Maxim-Dallas MAX1617 sensor connected to
SMBus (which is part of PCI bus)
and want to try doing something before hardware will come.
I used DevCon to enumerate SMBus drivers. Them are 2 on my machine:
1) Intel SM BIOS drvr (hwid: *ISBB0C01)
2) Microsoft SM BIOS drvr (hwid: root\mssmbios)
I guess (1) is vendor-supplied miniport and (2) is that DDK's class
driver.
Am I correct? Why it's name not an Smbus.sys as documented in the DDK?
I use a oscilloscope to look at SMBus wires.
At power up I see bus diagram, therefore SMBus controller is in there
and firmware BIOS see it.
But at and after WinXP startup nothing happens on the wire (couldn'd
guess why).
In the hope to see on the scope's screed SMBus enumeration diagram
I entered from the console " Devcon rescan", but nothing happened again.
I was unable to find in the DDK docs, nor in h-files any SMBUS_GUID
mentioned/defined
(as is recommended in the doc "SMBus device driver ext. arc. spec." by
smbus.org).
How do I enumerate/open my device?
Do I need to develop my own filter/client and is smbbatt sample (and
%windir%battery.inf)
good as a starting point for it or mssmbios is sufficient to read SMBus
device data from
within client?
How do I know, which SMBus version is supported (1.1 or 2.0)?
If later I add my own SMBus 2.0 device (slave controller) will it be
supported
by standard drivers?
Thank you for any comments.
Serge.