wimbeaumont Project / DevInterfaces

This are general defs and base class interfaces. ( DACInterface, I2CInterface) to be used with I2C devices

Dependents:   MCP23009tst AT30TSE752TST MCP4728setaddrProg mbedSerialInterface_talkback2 ... more

The DevInterfaces class is used for a more general support of a number of I2C devices.

For the moment this is MCP4728 Quad DAC.

The idea is to write a libs for the I2C devices (and perhaps later SPI , ... devices) not restricted to a certain hardware platform.

So there is the I2CInterface. This is a ( not pure) virtual class. A pointer to this class is used for the I2C device lib (like the MCP4728 class https://developer.mbed.org/users/wbeaumont/code/MCP4728/ ) to communicate with the I2C interface. The I2C interface is kept simple as possible. So it has to be applied for "tested environments". I2C Bus timeouts etc. are hard to debug with such a simple interface. This kind of interface is also not suitable for optimal performance. The user has to take care of issues of blocking devices, parallel processes etc. This can be dealt with in the implementation of the I2CInterface class

The aim of this project is to generate code for these devices on different platforms without doing the painstaking work of looking up all the register details.

There is an implementation of the I2CInterface for the MBED , tested with the FRDM-KL05Z platform. https://developer.mbed.org/users/wbeaumont/code/I2Cinterfaces/

A very simple application on a MBED can be found in https://developer.mbed.org/users/wbeaumont/code/MCP4728test/

diff -r 8cbf46e5e3e5 -r b5c9eb2330dc I2CInterface.h
--- a/I2CInterface.h	Fri Jan 13 13:52:58 2017 +0000
+++ b/I2CInterface.h	Wed Mar 15 17:16:59 2017 +0000
@@ -3,7 +3,10 @@
 
 #include "getVersion.h"
 
-#define I2CINTERFACE_HDR_VER "0.33" 
+#define I2CINTERFACE_HDR_VER "0.40"
+/*
+ *  ver  0:40  added wait_for_ms 
+*/ 
 
 class I2CInterface : public virtual getVersion{
 private: 
@@ -26,7 +29,8 @@
             return 0;
         };     //   Start non-blocking I2C transfer.       not yet clear how to deal with the callback
              // proposol here is for the implementation a spefic call back function ,that includes the event type  
-    
+            // wait function that is sometimes needed , not I2C hardware related but different implementation for platforms
+virtual void wait_for_ms(int x) { } ;
 }; 
 
 #endif