Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001397
--- Comment #35 from Mike Jones <[email protected]> 2013-01-02 07:07:14 GMT --- I read the reference on I2C. I am pretty clear how the standard I2C API works in terms of making transactions using locking, etc. I am making a simple app with no tasks, just to run in main. I assume there is some magic for making a cyg_i2c_bus and then you can make some cyg_i2c_device. Then call freescale_i2c_init(...) I see a macro for creating the bus, but it has to pass some function pointers. I assume there is some code for that, or I have to know all the magic things to put in the macro. Once there is a device, it is not clear if the standard API can use it. And if it can, I am not certain if it would behave any different that the Freescale specific API commands. So I think I mainly need to know how to get things glued together and relationship between the generic vs Freescale API. I don't need to know how to use the API to send and receive data. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
