Skip to content

Latest commit

 

History

History
68 lines (47 loc) · 5.83 KB

README.md

File metadata and controls

68 lines (47 loc) · 5.83 KB
Raw

TMC5062

How to use

To access the TMC5062's registers, the TMC-API offers two functions: tmc5062_readRegister and tmc5062_writeRegister. Each of these functions takes in an icID, which is used to identify the IC when multiple ICs are connected. This identifier is passed down to the callback functions (see How to Integrate).

How to integrate: overview

  1. Include all the files of the TMC-API/ic/tmc/TMC5062 folder into the custom project.
  2. Include the TMC5062.h file in the custom source code.
  3. Implement the necessary callback functions (see below).
  4. (optional): Take a look at the Examples subfolder for ready-made examples of the TMC-API usage.

Accessing the TMC5062 via UART

The following diagram depicts how to access the TMC5062 via UART using the TMC-API.

screenshot

The description of the functions, in the above flowchart, are as follows:

  • The functions tmc5062_readRegister and tmc5062_writeRegister are used to read and write the registers respectively. These functions check the current active bus and calls the bus-specific function i.e readRegisterUART or writeRegisterUART.
  • These bus specific functions constructs the datagram and further calls the bus specific callback 'tmcXXXX_readWriteUART.
  • This callback function further calls the hardware specific read/write function for UART and needs to be implemented externally.

How to integrate: Callback functions

To communicate with TMC5062 IC, the TMC-API library needs to know which bus (UART, SPI) it shall use. For that, the callback function 'tmc5062_getBusType()' needs to be implemented. Additionally, implement the following callback functions to access the chip via UART:

  1. tmc5062_readWriteUART(), which is a HAL wrapper function that provides the necessary hardware access.

Sharing the CRC table with other TMC-API chips

The TMC5062 UART protocol uses an 8 bit CRC. For calculating this, a table-based algorithm is used. This table (tmcCRCTable_Poly7Reflected[256]) is 256 bytes big and identical across multiple different Trinamic chips (i.e. TMC2209). If multiple Trinamic chips are being used in the same project, avoiding redundant copies of this table could save memory. It is possible to substitute this CRC table with another CRC table.

Necessary hardware modification to use UART

To use UART with the Eval-Kit: pin 39 (DIO17) and 40 (DIO18) should be connected with a 1k ohm resistor. Bend pin 39 (DIO17) on the EVAl Board side of the Eselsbrücke out. Optional: Bend pin 41 (DIO19) out and connect it to 3.3V / 2= 1.65V. You can reach this by making a volage-divider with two 1k ohm resistors. One to 3.3V and one to GND. This can improve the signal quality.

Accessing the TMC5062 via SPI

The following diagram depicts how to access the TMC5062 via SPI using the TMC-API.

screenshot

The description of the functions, in the above flowchart, are as follows:

  • The functions tmc5062_readRegister and tmc5062_writeRegister are used to read and write the registers respectively. These functions check the current active bus and calls the bus-specific function i.e readRegisterSPI or writeRegisterSPI.
  • These bus specific functions constructs the datagram and further calls the bus specific callback 'tmcXXXX_readWriteSPI.
  • This callback function further calls the hardware specific read/write function for SPI and needs to be implemented externally.

How to integrate: Callback functions

To communicate with TMC5062 IC, the TMC-API library needs to know which bus (UART, SPI) it shall use. For that, the callback function 'tmc5062_getBusType()' needs to be implemented. Additionally, implement the following callback functions to access the chip via SPI:

  1. tmc5062_readWriteSPI(), which is a HAL wrapper function that provides the necessary hardware access. This function should also set the chip select pin CSN to low before starting the data transfer and set to high upon completion. Please refer to the datasheet of the IC for further details.

Option to use the cache logic for Write-Only registers

The chip features write-only registers that are unable to be read, necessitating the creation of a shadow copy to cache their contents. This copy is automatically updated whenever data is written to these registers. This cache logic could be enabled by setting the macro TMC5062_CACHE to '1' or disabled by setting to '0' respectively. If this feature is enabled then there comes another option to use tmc5062_cache function, which is already implemeted in the API, by defining TMC5062_ENABLE_TMC_CACHE macro to '1' or one can implement their own function. The function tmc5062_cache works for both reading from and writing to the shadow array. It first checks whether the register has write-only access and data needs to be read from the hadow copy. On the basis of that, it returns true or false. The shadowRegisters on the premade cache implementation need to be one per chip. TMC5062_IC_CACHE_COUNT is set to '1' by default and is user-overwritable. If multiple chips are being used in the same project, increment its value to the number of chips connected.

Further info

Dependency graph for the ICs with new register R/W mechanism

This graph illustrates the relationships between files within the TMC-API library, highlighting dependencies and identifying the files that are essential for integrating the library into the custom projects. screenshot

Example usage: TMC-Evalsystem

For a reference usage of the TMC-API, visit the TMC-Evalsystem

Migration status

The TMC5062 has been reworked to the access system described above. For more infos on the status of this and other ICs, check out the migration page.