TDC 2 Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.
- Author : Stefan Ilic
- Date : Jan 2023.
- Type : SPI type
This library contains API for TDC 2 Click driver. The library initializes and defines the SPI bus drivers to write and read data from registers, as well as the default configuration for a reading time between two STOP signals.
- MikroSDK.Board
- MikroSDK.Log
- Click.TDC2
tdc2_cfg_setup
Config Object Initialization function.
void tdc2_cfg_setup ( tdc2_cfg_t *cfg );
tdc2_init
Initialization function.
err_t tdc2_init ( tdc2_t *ctx, tdc2_cfg_t *cfg );
tdc2_default_cfg
Click Default Configuration function.
err_t tdc2_default_cfg ( tdc2_t *ctx );
tdc2_read_results
TDC 2 results data reading function.
err_t tdc2_read_results( tdc2_t *ctx, uint8_t reg, uint32_t *reference_index, uint32_t *stop_result );
tdc2_start_measuring
TDC 2 start measuring function.
err_t tdc2_start_measuring ( tdc2_t *ctx );
tdc2_set_resolution
TDC 2 set resolution function.
err_t tdc2_set_resolution ( tdc2_t *ctx, uint32_t resolution );
Initializes the driver after that resets the device and performs default configuration and sets the device in read mode.
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
tdc2_cfg_t tdc2_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.
tdc2_cfg_setup( &tdc2_cfg );
TDC2_MAP_MIKROBUS( tdc2_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == tdc2_init( &tdc2, &tdc2_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( TDC2_ERROR == tdc2_default_cfg ( &tdc2 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
tdc2_start_measuring ( &tdc2 );
log_info( &logger, " Application Task " );
}
This example demonstrates the use of the TDC 2 Click board by measuring the time between two STOP signals. This example is set up to generate stop signals until FIFO fil's up which is indicated by interrupt pin going to low state. After that FIFO buffer is completely emptied by reading, and that data is used to calculate the time between STOP signals.
void application_task ( void )
{
uint32_t reference_index [ 18 ] = { 0 };
uint32_t stop_result [ 18 ] = { 0 };
uint8_t cnt = 0;
tdc2_reset_index( &tdc2 );
Delay_ms ( 10 );
while ( tdc2_get_int_state( &tdc2 ) == 1 )
{
dev_generate_stop( &tdc2 );
Delay_ms ( 100 );
}
while ( tdc2_get_int_state( &tdc2 ) == 0 )
{
tdc2_read_results( &tdc2, TDC2_REG_INDEX_CH1_BYTE3, &reference_index[ cnt ], &stop_result[ cnt ] );
log_printf( &logger, "CH1: Reference Index[%d]: %lu, Stop Result[%d]: %lu \r\n", ( uint16_t ) cnt,
reference_index[ cnt ], ( uint16_t ) cnt, stop_result[ cnt ] );
Delay_ms ( 10 );
if ( cnt )
{
uint32_t time = 0;
tdc2_get_time_between_stops ( &tdc2, stop_result[ cnt - 1 ], reference_index[ cnt - 1 ],
stop_result[ cnt ], reference_index[ cnt ], &time );
log_printf( &logger, "Time between STOP %d and STOP %d is %lu ms \r\n",
( uint16_t ) ( cnt - 1 ), ( uint16_t ) cnt, time / TDC2_uS_TO_mS );
Delay_ms ( 10 );
}
cnt++;
}
log_printf( &logger, "---------------------------------------------- \r\n" );
}
In order to test this example, you will need to connect STOP1 with the DIS pin. Disable pin is disabled by software and it isn't going to affect the working state of the TDC 2 Click Bord.
This Click board can be interfaced and monitored in two ways:
- Application Output - Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
- UART Terminal - Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.