Is I2c the same as SMBus?
FGFG
Posts: 2
I am interested in using an adm1031, which is a fan controller ic, with my Basic Stamp 2. The adm1031 connects via the SMBus however parallax documentation and examples seem only to describe the I2c interface. I believe they are the same. I2c = Phillips, SMBus = Intel. What's going on? Are they the same?
Also would it be worth upgrading my BS2 to a BS2p with the additional commands for I2c, or maybe the Javelin which seems to have had these features for quite a while.
Thanks - FGFG
Also would it be worth upgrading my BS2 to a BS2p with the additional commands for I2c, or maybe the Javelin which seems to have had these features for quite a while.
Thanks - FGFG
Comments
The Javelin is quite a jump from the BS2 (Does the same stuff, but in Java. You get much better bragging rights using Java than Basic, though)
·· Find out all about SMBus (Defined by Intel) here:
http://www.smbus.org/
http://www.smbus.org/specs/
Apparently, I2C is the backbone of SMBus architecture, used for ACPI in computers.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Chris Savage
Parallax Tech Support
csavage@parallax.com
http://www.maxim-ic.com/appnotes.cfm/appnote_number/356
regards peter
·
That is an interesting app note about the small differences in timing and error recovery. When I first started using I2C on the Stamp, I was concerned about error recovery, as in, what will the Stamp do if it issues an I2C command to a device that is not there or does not respond properly? It should time out, not lock up. And the Stamp does time out after about a second and goes on to the next instruction. At least under the conditions I tried. The app note made me wonder if there is some rare condition with the slave clock being held low that could still make it lock up?
-- Tracy
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Tracy Allen
www.emesystems.com
All slaves must respond to these conditions, no matter what state they are in.
But when a slave holds the clock line low (or data line for that matter), not even the·stamp
can recover the bus.
This however may only happen with·a defective slave (or a badly programmed MCU
acting as I2C slave).
regards peter
·