Jump to content

Component: I2C Master (Comms: Interface): Difference between revisions

From Flowcode Help
XML import
 
m Text replacement - "style="background-color:#EAE1EA;"" to "class="mtx-class-propfolder""
 
(39 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
{| style="width:50%"
 
{| width="50%"
|-
|-
| width="20%" style="color: gray;" | Author
| width="20%" style="color:gray;" | Author
| Matrix Ltd.
| Matrix Ltd.
|-
|-
| width="20%" style="color: gray;" | Version
| width="20%" style="color:gray;" | Version
| 1.4 (Release)
| 1.4
|-
|-
| width="20%" style="color: gray;" | Category
| width="20%" style="color:gray;" | Category
| Comms: Interface
| Comms: Interface
|}
|}




==I2C Master component==
Generic Two Wire I2C Communications Interface


==[[File:Component Icon 24219805_113d_4b12_b6bd_e1b0b0c33981.png|Image]] I2C Master component==
==Component Source Code==
Generic Two Wire I2C Communications Interface
 
Please click here to download the component source project: [https://www.flowcode.co.uk/wiki/componentsource/FC_Comp_Source_I2C_Master.fcfx FC_Comp_Source_I2C_Master.fcfx]


==Examples==
Please click here to view the component source code (Beta): [https://www.flowcode.co.uk/FlowchartView/?wfile=componentsource/FC_Comp_Source_I2C_Master.fcfx FC_Comp_Source_I2C_Master.fcfx]
''<span style="color:red;">No additional examples</span>''


==Detailed description==


==Downloadable macro reference==


===<span style="font-weight: normal;"><u><tt>ReceiveByte</tt></u></span>===
Receives a byte from the I²C bus.


'''Parameters'''


:[[Variable Types|BYTE]] ''Last''
::Used to signify the last byte when streaming incoming data. 0=Not last byte, 1=Last Byte




'''Return value'''


:[[Variable Types|BYTE]]




===<span style="font-weight: normal;"><u><tt>Restart</tt></u></span>===
Outputs a restart condition onto the I²C bus.


'''Parameters'''


:''This macro has no parameters''




'''Return value'''


:''This call does not return a value''




===<span style="font-weight: normal;"><u><tt>Stop</tt></u></span>===
Outputs a stop condition onto the I²C bus.


'''Parameters'''


:''This macro has no parameters''




'''Return value'''


:''This call does not return a value''




===<span style="font-weight: normal;"><u><tt>ReceiveByteTransaction</tt></u></span>===
Function to perform a generic I2C read transaction. The 7-bit device ID is automatically shifted up by one bit to make room for the read/write bit. Returns the data from the location specified.


'''Parameters'''


:[[Variable Types|BYTE]] ''Device_ID''
::7-bit Device Address ID


:[[Variable Types|BYTE]] ''AddrH''
::Internal Address High Byte


:[[Variable Types|BYTE]] ''AddrL''
::Internal Address Low Byte




'''Return value'''


:[[Variable Types|BYTE]]




===<span style="font-weight: normal;"><u><tt>TransmitByte</tt></u></span>===
Sends a byte on the I²C bus. Returns the acknowledge if any.


0 represents that data was acknowledged and 1 represents no acknowledge was detected.
===Overview===


'''Parameters'''
The I2C bus is a medium speed communications bus which is usually best suited for talking between devices situated on the same circuit board. Due to the high frequency digital nature of the bus care should be taken to keep tracks as short as possible and as far away as possible from other sources of noise. A typical I2C bus consists of two signals, data and clock. The I2C bus usually consists of a single master device and then one or more slave devices. The master device initiates all the communications and can only communicate with a single device on the bus at a time by sending a unique device address as the first byte.


:[[Variable Types|BYTE]] ''Data''
Each I2C transaction consists of a start and a stop as well as one or more data bytes made up of 8 clock cycles allowing the 8-bits of each byte to be transferred. Each byte send is followed by an Ack (acknowledged) or a Nak (not acknowledged) from the receiving device.
::Data byte to send on the I²C bus.


[[File:I2C_Bytes.jpg]]


'''Return value'''


:[[Variable Types|BYTE]]
===Pull up resistors===


The I2C bus usually requires pull up resistors in the range of 4.7K to 10K between the two I2C signals and VCC. Some I2C devices have the pull up resistors built in so as to avoid external components.


===<span style="font-weight: normal;"><u><tt>SendByteTransaction</tt></u></span>===
The pull up resistors can be useful when interfacing a 5V microcontroller to a 3V3 sensor as the pull up resistor can be connected to 3V3 to eliminate the need for voltage level shifting.
Function to perform a generic I2C Write transaction. The 7-bit device ID is automatically shifted up by one bit to make room for the read/write bit.


'''Parameters'''


:[[Variable Types|BYTE]] ''Device_ID''
===Start / Restart / Stop===
::7-bit Device Address ID


:[[Variable Types|BYTE]] ''AddrH''
The Start, Restart and Stop operations are each states which the bus can be put into using the I2C specification.
::Internal Address High Byte


:[[Variable Types|BYTE]] ''AddrL''
::Internal Address Low Byte


:[[Variable Types|BYTE]] ''Data''
===Generic Write Transaction===
::Data Byte


A generic write transaction to a memory device might look something like this:


'''Return value'''
Start


:''This call does not return a value''
Send External Device Address Byte (Write mode)


Send Internal Address Byte


===<span style="font-weight: normal;"><u><tt>Start</tt></u></span>===
Send Data Byte
Outputs a start condition onto the I²C bus.


'''Parameters'''
Stop


:''This macro has no parameters''


===Generic Read Transaction===


'''Return value'''
A generic read transaction to a memory device might look something like this:


:''This call does not return a value''
Start


Send External Device Address Byte (Write mode)


===<span style="font-weight: normal;"><u><tt>Initialise</tt></u></span>===
Send Internal Address Byte
Enables the I²C hardware and performs some initialization.


Should be called at the start of the program or at least before any of the other I²C functions are called.
Restart


'''Parameters'''
Send External Device Address Byte (Read mode)


:''This macro has no parameters''
Read Data Byte


Stop


'''Return value'''


:''This call does not return a value''




Referring to the Transaction_Write macro. 
To do a restart without a stop, instead of using just the number of bytes within the Length parameter, use 0x800 + total number of bytes to read.


==Simulation macro reference==
In the I2CEEPROM.fcfx example as 2 bytes require reading with just a restart then instead of the length of 2, a length of 0x8002 is used.


''This component does not contain any simulation macros''
[[File:I2CTransaction_Write_No_Stop.png]]


==Examples==


==Property reference==
<span style="font-weight: normal;"><u>Channel</u></span>


This property is of type ''Fixed list of ints'' and can be referenced with the variable name ''CHANNEL''.


Specifies the I2C peripheral used by the component.


Hardware channels are defined by the number of I2C peripherals available onboard your target microcontroller.


Software channels use standard I/O pins allowing you to connect the I2C bus to pretty much any pin.


<span style="font-weight: normal;"><u>Baud Select</u></span>


This property is of type ''Fixed list of ints'' and can be referenced with the variable name ''BAUD_LIST''.


Sets the rate of the I2C clock which sets the maximum number of bits per second that can be sent or received.


<span style="font-weight: normal;"><u>Slew Rate Control</u></span>


This property is of type ''Fixed list of ints'' and can be referenced with the variable name ''SRC''.


The slew rate control only works with hardware I2C channels but acts to modify the overall baud to ensure
More information on I2C can be found here,


that signals are being transferred correctly based on how fast the control signals are able to rise and fall.
[http://www.matrixtsl.com/blog/simplified-communications-i%c2%b2c-and-spi/ Matrix Flowcode Blog: Simplified communications I2C and SPI]


<span style="font-weight: normal;"><u>SMBus Inputs</u></span>


This property is of type ''Fixed list of ints'' and can be referenced with the variable name ''SMB''.
===Generic I2C EEPROM===


The SMBus Inputs only works with hardware I2C channels but acts to modify the I2C driver to be compatible with SM Bus.
Example file demonstrating how to read and write bytes from a generic I2C EEPROM device.
{{Fcfile|I2CEEPROM.fcfx|I2CEEPROM}}


<span style="font-weight: normal;"><u>Stop Delay</u></span>


This property is of type ''True or false'' and can be referenced with the variable name ''StopDelay''.
===I2C Transaction Mode===


On older microcontroller devices there is a potential for the I2C hardware channel to lock up if there is not
Transaction mode can be used on all target devices.


a 10ms delay between an I2C stop event and the next I2C start event.
If not using transaction mode then your code won't work on ARM or ESP.


With transaction mode, there are fewer component macros required than in Non-transaction read/write mode.


The I2CEEPROM.fcfx Example file demonstrates how I2C transaction component macros can be used to write and read to the memory registers of an I2C external EEPROM


Most modern microcontrollers will not have a problem so this property can be disabled to speed up the  
The I2C Transaction Example file demonstrates how I2C transaction component macros can be used to write and read to the minutes register of DS1307/DS3231 RTC.


I2C communications.
If simulation Mode within properties is set to Yes, then the minutes are read from your PC time via a dll.


<span style="font-weight: normal;"><u>Data (SDA)</u></span>
You can expand using the dll to retrieve the whole date and time.


This property is of type ''Single digital pin'' and can be referenced with the variable name ''SDA''.


I2C data pin commonly referred to as SDA which represents serial data


<span style="font-weight: normal;"><u>Clock (SCL)</u></span>
{{Fcfile|I2C Transaction Example.fcfx|I2C Transaction Example}}


This property is of type ''Single digital pin'' and can be referenced with the variable name ''SCL''.


I2C clock pin commonly referred to as SCL which represents serial clock
===I2C Address Scanner===


<span style="font-weight: normal;"><u>Label</u></span>
An I2C addresses can be determined by using an {{Fcfile|IC2_Address_Scanner.fcfx|IC2 Address Scanner}}


This property is of type ''Line of text'' and can be referenced with the variable name ''label''.
The I2C address to use is the one within the first set of square brackets.


Label shown on the comms flasher on the simulation panel.
For example, with my backpack display, the correct address to use is 0x3F [63]:


<span style="font-weight: normal;"><u>Scope Traces</u></span>
[[File:Sniffer_I2C_backpack_address.png]]


This property is of type ''True or false'' and can be referenced with the variable name ''ScopeTraces''.
The other two Addresses i.e. 0x56 [86] and 0x68 [104] is for other connected devices, 24C32 EEPROM and DS3231 RTC respectively.  


Selects if the scope traces are automatically generated or not
Note The I2c addresses scan will repeat every 5seconds.


<span style="font-weight: normal;"><u>Console Data</u></span>
The sniffer will send data to your PC via UART to USB which can be read using serial terminal software.


This property is of type ''True or false'' and can be referenced with the variable name ''ConsoleData''.


Selects if the console data is automatically generated or not


<span style="font-weight: normal;"><u>Injector</u></span>
==Macro reference==


This property is of type ''Fixed list of ints'' and can be referenced with the variable name ''Injector''.
===GenericReadRegister===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''GenericReadRegister'''
|-
| colspan="2" | Function to perform a generic I2C read.  The 7-bit device ID is automatically shifted up by one bit to make room for the read/write bit. Returns the data from the location specified.&nbsp;
|-
|-
| width="10%" align="center" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" | Device_ID
|-
| colspan="2" | 7-bit Device Address ID&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-u16-icon.png]] - UINT
| width="90%" | Address
|-
| colspan="2" | &nbsp;
|-
| width="10%" align="center" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" | AddressByteCount
|-
| colspan="2" | Specifies the number of address bytes, Range: 1 or 2&nbsp;
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}


Lists all the available injector components on the panel to allow the I2C data to have meaning.


Injectors are available to let you directly type in values, simulate devices and communicate between multiple instances of Flowcode.
===GenericWriteRegister===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''GenericWriteRegister'''
|-
| colspan="2" | Function to perform a generic I2C Write transaction. The 7-bit device ID is automatically shifted up by one bit to make room for the read/write bit.&nbsp;
|-
|-
| width="10%" align="center" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" | Device_ID
|-
| colspan="2" | 7-bit Device Address ID&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-u16-icon.png]] - UINT
| width="90%" | Address
|-
| colspan="2" | &nbsp;
|-
| width="10%" align="center" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" | Data
|-
| colspan="2" | Data Byte&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" | AddressByteCount
|-
| colspan="2" | Specifies the number of address bytes, Range: 1 or 2&nbsp;
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-void-icon.png]] - VOID
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
===Initialise===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''Initialise'''
|-
| colspan="2" | Enables the I²C hardware and performs some initialization. Should be called at the start of the program or at least before any of the other I²C functions are called.&nbsp;
|-
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-void-icon.png]] - VOID
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
===ReceiveByte===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''ReceiveByte'''
|-
| colspan="2" | Receives a byte from the I²C bus. &nbsp;
|-
|-
| width="10%" align="center" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" | Last
|-
| colspan="2" | Used to signify the last byte when streaming incoming data. 0=Not last byte, 1=Last Byte&nbsp;
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
===Restart===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''Restart'''
|-
| colspan="2" | Outputs a restart condition onto the I²C bus.&nbsp;
|-
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-void-icon.png]] - VOID
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
===Start===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''Start'''
|-
| colspan="2" | Outputs a start condition onto the I²C bus.&nbsp;
|-
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-void-icon.png]] - VOID
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
===Stop===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''Stop'''
|-
| colspan="2" | Outputs a stop condition onto the I²C bus.&nbsp;
|-
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-void-icon.png]] - VOID
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
===Transaction_Initialise===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''Transaction_Initialise'''
|-
| colspan="2" | Initialise the I2C interface to communicate with a Slave device at Address Returns 0 on fail, 1 on success&nbsp;
|-
|-
| width="10%" align="center" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" | Address
|-
| colspan="2" | 7-bit I2C Address without the shift for the R/W bit&nbsp;
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
===Transaction_Read===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''Transaction_Read'''
|-
| colspan="2" | Attempt to read Length number of bytes from the I2C slave to the given Buffer. Ensure that the Buffer is large enough.  Returns number of bytes read, caller should check that this matches requested Length&nbsp;
|-
|-
| width="10%" align="center" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" | Buffer
|-
| colspan="2" | Buffer to store the incoming byte data&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-u16-icon.png]] - UINT
| width="90%" | Length
|-
| colspan="2" | Number of bytes to read&nbsp;
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-u16-icon.png]] - UINT
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
===Transaction_Uninit===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''Transaction_Uninit'''
|-
| colspan="2" | Uninitialise the I2C interface&nbsp;
|-
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-void-icon.png]] - VOID
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
===Transaction_Write===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''Transaction_Write'''
|-
| colspan="2" | Attempt to write Length number of bytes to the I2C slave from the given Buffer. Ensure that the Buffer is large enough.  Returns the number of bytes written, the caller should check that this matches requested Length&nbsp;
|-
|-
| width="10%" align="center" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" | Buffer
|-
| colspan="2" | Buffer of bytes to write to the I2C&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-u16-icon.png]] - UINT
| width="90%" | Length
|-
| colspan="2" | Number of bytes to send out, MS bit 0x8000 signifies no Stop if set&nbsp;
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-u16-icon.png]] - UINT
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
===TransmitByte===
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
| width="90%" class="mtx-class-macrohead" | '''TransmitByte'''
|-
| colspan="2" | Sends a byte on the I²C bus. Returns the acknowledge if any.  0 represents that data was acknowledged and 1 represents no acknowledge was detected.&nbsp;
|-
|-
| width="10%" align="center" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" | Data
|-
| colspan="2" | Data byte to send on the I²C bus.&nbsp;
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-u8-icon.png]] - BYTE
| width="90%" style="border-top: 2px solid #000;" | ''Return''
|}
 
 
==Property reference==
 
{| class="mtx-class-macrotable wikitable"
|-
| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-prop-icon.png]]
| width="90%" class="mtx-class-macrohead" | '''Properties'''
|-
|-
| width="10%" align="center" class="mtx-class-propfolder" | [[File:Fc9-conn-icon.png]]
| width="90%" class="mtx-class-propfolder" | Bus Settings
|-
|-
| width="10%" align="center" | [[File:Fc9-type-16-icon.png]]
| width="90%" | Channel
|-
| colspan="2" | Channel selection&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-type-16-icon.png]]
| width="90%" | Baud Select
|-
| colspan="2" | Baud rate option selector&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-type-14-icon.png]]
| width="90%" | Baud Rate
|-
| colspan="2" | Baud rate to be used&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-type-7-icon.png]]
| width="90%" | Stop Delay
|-
| colspan="2" | On older microcontroller devices there is a potential for the I2C hardware channel to lock up if there is not  a 10ms delay between an I2C stop event and the next I2C start event.  Most modern microcontrollers will not have a problem so this property can be disabled to speed up the  I2C communications. &nbsp;
|-
| width="10%" align="center" | [[File:Fc9-type-16-icon.png]]
| width="90%" | Slew Rate Control
|-
| colspan="2" | Slew Rate Control Enabled or Disabled&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-type-16-icon.png]]
| width="90%" | SMBus Inputs
|-
| colspan="2" |  When Enabled input logic thresholds are compliant with SMBus specification&nbsp;
|-
| width="10%" align="center" class="mtx-class-propfolder" | [[File:Fc9-conn-icon.png]]
| width="90%" class="mtx-class-propfolder" | Connections
|-
|-
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
| width="90%" | SDA
|-
| colspan="2" | Pin used for SDA (data signal)&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
| width="90%" | SCL
|-
| colspan="2" | Pin used for SCL (clock signal)&nbsp;
|-
| width="10%" align="center" class="mtx-class-propfolder" | [[File:Fc9-conn-icon.png]]
| width="90%" class="mtx-class-propfolder" | Simulation
|-
|-
| width="10%" align="center" | [[File:Fc9-type-10-icon.png]]
| width="90%" | Label
|-
| colspan="2" | Label shown on the comms flasher on the simulation panel.&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-type-7-icon.png]]
| width="90%" | Scope Traces
|-
| colspan="2" | Selects if the scope traces are automatically generated or not&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-type-7-icon.png]]
| width="90%" | Console Data
|-
| colspan="2" | Selects if the console data is automatically generated or not&nbsp;
|-
| width="10%" align="center" | [[File:Fc9-type-16-icon.png]]
| width="90%" | API
|-
| colspan="2" | &nbsp;
|}

Latest revision as of 14:37, 13 July 2026

Author Matrix Ltd.
Version 1.4
Category Comms: Interface


I2C Master component

Generic Two Wire I2C Communications Interface

Component Source Code

Please click here to download the component source project: FC_Comp_Source_I2C_Master.fcfx

Please click here to view the component source code (Beta): FC_Comp_Source_I2C_Master.fcfx

Detailed description

Overview

The I2C bus is a medium speed communications bus which is usually best suited for talking between devices situated on the same circuit board. Due to the high frequency digital nature of the bus care should be taken to keep tracks as short as possible and as far away as possible from other sources of noise. A typical I2C bus consists of two signals, data and clock. The I2C bus usually consists of a single master device and then one or more slave devices. The master device initiates all the communications and can only communicate with a single device on the bus at a time by sending a unique device address as the first byte.

Each I2C transaction consists of a start and a stop as well as one or more data bytes made up of 8 clock cycles allowing the 8-bits of each byte to be transferred. Each byte send is followed by an Ack (acknowledged) or a Nak (not acknowledged) from the receiving device.


Pull up resistors

The I2C bus usually requires pull up resistors in the range of 4.7K to 10K between the two I2C signals and VCC. Some I2C devices have the pull up resistors built in so as to avoid external components.

The pull up resistors can be useful when interfacing a 5V microcontroller to a 3V3 sensor as the pull up resistor can be connected to 3V3 to eliminate the need for voltage level shifting.


Start / Restart / Stop

The Start, Restart and Stop operations are each states which the bus can be put into using the I2C specification.


Generic Write Transaction

A generic write transaction to a memory device might look something like this:

Start

Send External Device Address Byte (Write mode)

Send Internal Address Byte

Send Data Byte

Stop


Generic Read Transaction

A generic read transaction to a memory device might look something like this:

Start

Send External Device Address Byte (Write mode)

Send Internal Address Byte

Restart

Send External Device Address Byte (Read mode)

Read Data Byte

Stop



Referring to the Transaction_Write macro. To do a restart without a stop, instead of using just the number of bytes within the Length parameter, use 0x800 + total number of bytes to read.

In the I2CEEPROM.fcfx example as 2 bytes require reading with just a restart then instead of the length of 2, a length of 0x8002 is used.

Examples

More information on I2C can be found here,

Matrix Flowcode Blog: Simplified communications I2C and SPI


Generic I2C EEPROM

Example file demonstrating how to read and write bytes from a generic I2C EEPROM device. I2CEEPROM


I2C Transaction Mode

Transaction mode can be used on all target devices.

If not using transaction mode then your code won't work on ARM or ESP.

With transaction mode, there are fewer component macros required than in Non-transaction read/write mode.

The I2CEEPROM.fcfx Example file demonstrates how I2C transaction component macros can be used to write and read to the memory registers of an I2C external EEPROM

The I2C Transaction Example file demonstrates how I2C transaction component macros can be used to write and read to the minutes register of DS1307/DS3231 RTC.

If simulation Mode within properties is set to Yes, then the minutes are read from your PC time via a dll.

You can expand using the dll to retrieve the whole date and time.


I2C Transaction Example


I2C Address Scanner

An I2C addresses can be determined by using an IC2 Address Scanner

The I2C address to use is the one within the first set of square brackets.

For example, with my backpack display, the correct address to use is 0x3F [63]:

The other two Addresses i.e. 0x56 [86] and 0x68 [104] is for other connected devices, 24C32 EEPROM and DS3231 RTC respectively.

Note The I2c addresses scan will repeat every 5seconds.

The sniffer will send data to your PC via UART to USB which can be read using serial terminal software.


Macro reference

GenericReadRegister

GenericReadRegister
Function to perform a generic I2C read. The 7-bit device ID is automatically shifted up by one bit to make room for the read/write bit. Returns the data from the location specified. 
- BYTE Device_ID
7-bit Device Address ID 
- UINT Address
 
- BYTE AddressByteCount
Specifies the number of address bytes, Range: 1 or 2 
- BYTE Return


GenericWriteRegister

GenericWriteRegister
Function to perform a generic I2C Write transaction. The 7-bit device ID is automatically shifted up by one bit to make room for the read/write bit. 
- BYTE Device_ID
7-bit Device Address ID 
- UINT Address
 
- BYTE Data
Data Byte 
- BYTE AddressByteCount
Specifies the number of address bytes, Range: 1 or 2 
- VOID Return


Initialise

Initialise
Enables the I²C hardware and performs some initialization. Should be called at the start of the program or at least before any of the other I²C functions are called. 
- VOID Return


ReceiveByte

ReceiveByte
Receives a byte from the I²C bus.  
- BYTE Last
Used to signify the last byte when streaming incoming data. 0=Not last byte, 1=Last Byte 
- BYTE Return


Restart

Restart
Outputs a restart condition onto the I²C bus. 
- VOID Return


Start

Start
Outputs a start condition onto the I²C bus. 
- VOID Return


Stop

Stop
Outputs a stop condition onto the I²C bus. 
- VOID Return


Transaction_Initialise

Transaction_Initialise
Initialise the I2C interface to communicate with a Slave device at Address Returns 0 on fail, 1 on success 
- BYTE Address
7-bit I2C Address without the shift for the R/W bit 
- BYTE Return


Transaction_Read

Transaction_Read
Attempt to read Length number of bytes from the I2C slave to the given Buffer. Ensure that the Buffer is large enough. Returns number of bytes read, caller should check that this matches requested Length 
- BYTE Buffer
Buffer to store the incoming byte data 
- UINT Length
Number of bytes to read 
- UINT Return


Transaction_Uninit

Transaction_Uninit
Uninitialise the I2C interface 
- VOID Return


Transaction_Write

Transaction_Write
Attempt to write Length number of bytes to the I2C slave from the given Buffer. Ensure that the Buffer is large enough. Returns the number of bytes written, the caller should check that this matches requested Length 
- BYTE Buffer
Buffer of bytes to write to the I2C 
- UINT Length
Number of bytes to send out, MS bit 0x8000 signifies no Stop if set 
- UINT Return


TransmitByte

TransmitByte
Sends a byte on the I²C bus. Returns the acknowledge if any. 0 represents that data was acknowledged and 1 represents no acknowledge was detected. 
- BYTE Data
Data byte to send on the I²C bus. 
- BYTE Return


Property reference

Properties
Bus Settings
Channel
Channel selection 
Baud Select
Baud rate option selector 
Baud Rate
Baud rate to be used 
Stop Delay
On older microcontroller devices there is a potential for the I2C hardware channel to lock up if there is not a 10ms delay between an I2C stop event and the next I2C start event. Most modern microcontrollers will not have a problem so this property can be disabled to speed up the I2C communications.  
Slew Rate Control
Slew Rate Control Enabled or Disabled 
SMBus Inputs
When Enabled input logic thresholds are compliant with SMBus specification 
Connections
SDA
Pin used for SDA (data signal) 
SCL
Pin used for SCL (clock signal) 
Simulation
Label
Label shown on the comms flasher on the simulation panel. 
Scope Traces
Selects if the scope traces are automatically generated or not 
Console Data
Selects if the console data is automatically generated or not 
API