I have been trying to hunt down the source of some I2C communications
problems between the verdex pro and robostix for several months now as part
of my work on a school project which I am using them for. I am not the only
one experiencing these problems but I won't go into the details about that
here since the problem has been discussed at length in other threads (
http://www.nabble.com/i2c-problem-td20848539i20.html ). In my
troubleshooting I have narrowed the suspects down to the i2c kernel
drivers/modules. (i2c-core, i2c-dev, and i2c-pxa)
I would like to compile the i2c drivers with development/debugging options
in order to get a better idea of where in the driver code to look for the
I have looked through some of the I2C code already and see places where
certain debugging messages are being sent but I am not sure how to actually
enable them in the context of the OpenEmbedded build environment. My
question is, what is the easiest way to enable these debugging functions
I assume I will need to write a patch file that changes something in one of
the Makefile or Kconfig files and add it to the SRC_URI value in a custom
version of the kernel recipe which would go in the user.collection tree.
If this is the right idea, I still don't know which file(s) need to be
changed or in exactly what way. Do I need to define debugging for the whole
kernel or can I just change it for the i2c drivers. The kernel source tree
is a massive collection of code and I'm a little lost about exactly how to
make the necessary changes to the build.
The code in question is located in:
I am no stranger to programming embedded systems but I am fairly new to the
gumstix community and not very experienced with the Linux kernel and some of
the other lower level pieces of Linux.
Also, if anyone has found a solution to these i2c problems PLEASE let us
know. And if anyone with more direct experience with the I2C driver is
willing to help out with this problem too, I would be very appreciative.
We only have 2 weeks left to get the project working and this problem is
really getting in our way.
View this message in context: http://www.nabble.com/I2C-Driver-Debuging-OE-tp23018877p23018877.html
Sent from the Gumstix mailing list archive at Nabble.com.