why does the i2cdetect always gives "UU" on my RTC in embedded Linux
I'd like to communicate read from my RTC in C code rather than the `"hwclock"` shell command.
However, when I use `i2cdetect`, it shows `0x68`(which is my RTC slave address) is having the status `"UU"`, which means "Probing was skipped, because this address is currently in use by a driver". And after I tried the `i2cget`, its givng "could bot set address to `0x68`: Device or resource busy".
So I'm thinking if there are some problem in my Linux kernel that will force to read from my RTC all the time, or some other reason.
Last edited by henryyao; 07-23-2013 at 04:08 PM.