We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]
Rating:
Author: MIKROE
Last Updated: 2024-10-31
Package Version: 2.1.0.8
mikroSDK Library: 2.0.0.0
Category: RS232
Downloaded: 170 times
Not followed.
License: MIT license
UART to I2C Click is a compact add-on board allowing connections to UART controllers and I2C targets for protocol conversion. This board features the SC18IM704, a bridge between the standard UART host interface and a serial I2C bus from NXP Semiconductors. The SC18IM704 provides a high-speed UART interface with a baud rate of up to 460.8 kbit/s and 256-byte FIFO for the transfer/receive data process, alongside several user-configurable GPIO pins. The host MCU communicates with the SC18IM704 with ASCII messages protocol, allowing it to control all the specific I2C-bus sequences, protocol, arbitration, and timing.
Do you want to subscribe in order to receive notifications regarding "UART to I2C Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "UART to I2C Click" changes.
Do you want to report abuse regarding "UART to I2C Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
5104_uart_to_i2c_clic.zip [475.58KB] | mikroC AI for ARM GCC for ARM Clang for ARM mikroC AI for PIC mikroC AI for PIC32 XC32 GCC for RISC-V Clang for RISC-V mikroC AI for dsPIC XC16 |
|
UART to I2C Click is a compact add-on board allowing connections to UART controllers and I2C targets for protocol conversion. This board features the SC18IM704, a bridge between the standard UART host interface and a serial I2C bus from NXP Semiconductors. The SC18IM704 provides a high-speed UART interface with a baud rate of up to 460.8 kbit/s and 256-byte FIFO for the transfer/receive data process, alongside several user-configurable GPIO pins. The host MCU communicates with the SC18IM704 with ASCII messages protocol, allowing it to control all the specific I2C-bus sequences, protocol, arbitration, and timing.
We provide a library for the UART to I2C Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.
Package can be downloaded/installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.
This library contains API for UART to I2C Click driver.
uarttoi2c_cfg_setup
Config Object Initialization function.
void uarttoi2c_cfg_setup ( uarttoi2c_cfg_t *cfg );
uarttoi2c_init
Initialization function.
err_t uarttoi2c_init ( uarttoi2c_t *ctx, uarttoi2c_cfg_t *cfg );
uarttoi2c_default_cfg
Click Default Configuration function.
err_t uarttoi2c_default_cfg ( uarttoi2c_t *ctx );
uarttoi2c_gpio_write
This function writes a desired data to the gpio port.
void uarttoi2c_gpio_write ( uarttoi2c_t *ctx, uint8_t gpio_data );
uarttoi2c_gpio_read
This function reads data from the gpio port.
err_t uarttoi2c_gpio_read ( uarttoi2c_t *ctx, uint8_t *gpio_data );
uarttoi2c_i2c_write_then_read
This function performs a write then read with a repeated start to the I2C target device.
err_t uarttoi2c_i2c_write_then_read ( uarttoi2c_t *ctx, uint8_t slave_addr, uint8_t *data_in, uint8_t in_len, uint8_t *data_out, uint8_t out_len );
This example demonstrates the use of USB to I2C Click board by reading the device ID of a 3D Hall 11 Click board connected to the I2C port and controlling the GPIO pins.
The demo application is composed of two sections :
Initializes the driver and performs the Click default config which resets the device and sets the GPIO pins 0-3 as push-pull output and others as input. After that, reads and displays the chip firmware version.
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
uarttoi2c_cfg_t uarttoi2c_cfg; /**< Click config object. */
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, " Application Init " );
// Click initialization.
uarttoi2c_cfg_setup( &uarttoi2c_cfg );
UARTTOI2C_MAP_MIKROBUS( uarttoi2c_cfg, MIKROBUS_1 );
if ( UART_ERROR == uarttoi2c_init( &uarttoi2c, &uarttoi2c_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( UARTTOI2C_ERROR == uarttoi2c_default_cfg ( &uarttoi2c ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
uint8_t version[ 16 ] = { 0 };
if ( UARTTOI2C_OK == uarttoi2c_read_version ( &uarttoi2c, version ) )
{
log_printf( &logger, " Firmware version: %s\r\n", version );
}
log_info( &logger, " Application Task " );
}
Reads the device ID of a 3D Hall 11 Click board connected to the I2C port, toggles the output pins and displays the GPIO port state. The results will be displayed on the USB UART approximately once per second.
void application_task ( void )
{
static uint8_t gpio_state = UARTTOI2C_NO_PIN_MASK;
uint8_t slave_address = DEVICE_SLAVE_ADDRESS;
uint8_t reg_addr = DEVICE_REG_ID;
uint8_t device_id;
if ( UARTTOI2C_OK == uarttoi2c_i2c_write_then_read ( &uarttoi2c, slave_address,
®_addr, 1, &device_id, 1 ) )
{
log_printf( &logger, " %s - Device ID read: %s\r\n", ( char * ) DEVICE_NAME,
( char * ) ( ( DEVICE_ID == device_id ) ? "Success" : "Fail" ) );
}
uarttoi2c_gpio_write ( &uarttoi2c, gpio_state );
if ( UARTTOI2C_OK == uarttoi2c_gpio_read ( &uarttoi2c, &gpio_state ) )
{
log_printf( &logger, " GPIO state: 0x%.2X\r\n\n", ( uint16_t ) gpio_state );
gpio_state = ~gpio_state;
}
Delay_ms ( 1000 );
}
The full application code, and ready to use projects can be installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.
Other Mikroe Libraries used in the example:
Additional notes and informations
Depending on the development board you are using, you may need USB UART Click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. UART terminal is available in all MikroElektronika compilers.