Sounds a bit (pun intended) like maybe you want 0x60 -- 0x61 may be
powering it down.
Michael D. Black
[mailto:gumstix-users-bounces@...] On Behalf Of Neil
Sent: Wednesday, October 24, 2007 11:06 AM
To: gum >> "General mailing list for gumstix users."
Subject: [Gumstix-users] I2c read problem
I have a problem addressing two I2C devices on my gumstix but I believe=20
the "feature" is the same.
The devices are:
1. Maxim MAX1169 16 bit A-D
2. Honeywell HMC6352 compass.
I have other devices already working using the conventional I2C
I am using Dave Hylands C code. Neat bit of code Dave!
normal from is:
i2c DEV_ADDR ReadByte REGISTER
But with the two devices above there isn't a register set, you just=20
simply toggle a bit in the DEV_ADDR to change the devices mode from read
to write. (I think I am right in this understanding!)
Has anyone used either of these devices or modified Dave's code? Or am=20
I doing something wrong or misinterpreting what the data sheet is
NOTES from the data sheet for the MAX1169 follow:
A master initiates communication with a slave device by issuing a START=20
condition followed by a slave address byte. The slave address byte=20
consists of 7 address bits and a R/W bit. When the MAX1169 recognises=20
its slave address, it acquires the analog input signal and prepares for=20
conversion. The first three bits (MSBs) of the slave address have been=20
factory programmed and are always 011. Pins AAD3-ADD0 on the device=20
programs the last 4 bits of the slave address (in my case 0000)
Since the MAX1169 does not require set up or configuration, the LSB of=20
the address byte (R/W) controls power down.
~ the address is 011 0000 1 =3D 0x61
If I run the command
i2c 0x61 ReadByte
Then I don't have a register to read. The i2c program falls over.
Any suggestions/help really appreciated. It is fundamental to my design
and I need to get this working.
This message (and any attachments) is for the recipient only. NERC is
to the Freedom of Information Act 2000 and the contents of this email
reply you make may be disclosed by NERC unless it is exempt from release
the Act. Any material supplied to NERC may be stored in an electronic
records management system.
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
gumstix-users mailing list
This electronic message and any files transmitted with it contain =
information which may be privileged and/or proprietary. The information =
is intended for use solely by the intended recipient(s). If you are not =
the intended recipient, be aware that any disclosure, copying, =
distribution or use of this information is prohibited. If you have =
received this electronic message in error, please advise the sender by =
reply email or by telephone (301-939-7000) and delete the message.