I2C on the TX-C

[vleeuwen]

(For discussion with the 4NetOS specialists)
Keywords: TX-C, use of the I2C bus, near future.

Some moths ago I already publish my general view about the I2C implementaion on the TX-C.
The architecture consists of two levels:
1) A custum function (loadable module) on the TX-C, below TA level.
This fuction controls the on the I2C bus connected I2C slave device;
it takes care for the initialisation and pre prosessing of the raw data.
Like the extended Motor control, this function will use the TA for the communication with the end-user.
So need also be a custom definable parts in the TA-in, TA-out and TA-init
2) Above TA level, the behavior will be the same as the standard functions.
This will makes it possible that the I2C device functionality is available at RoboRpo level

The question is: will it be possible to add a function to the TX-C (4NetOS).
The idea is yes, the OS is able to deal with preemptive tasks. The costom function(s) could run as simple low priority tasks.
>>
The idea to work with some (one or two) custom definable plug ins (modules) is for a technical perspective feasible.
Fischertechnik (Msc) needs to create a loader and a runtime environment with a stub-table (hook-table) for it.
Because this module must fit in into the 4NetOS infrastructure, there exist also the need for a framework (template) for the loadable module itself.
And of couse a good set of I2C library function; these sets are normaly part of the embedded system library for aparticular processor family.
<<

Notes:
For the use of the I2C bus it is almost indispensable to have the ability to run local drivers (loadeble modules); the TA refresh rate (more than 10 ms) is to slow to basic I2C instructions from the PC (Above TA level).
The I2C devices do not need interrupts. It can be done with polling. Maybe the use of an internal timer of the OS.

[vleeuwen]

My notes from last year about I2C