Other Parts Discussed in Thread: CC2640
Tool/software: TI-RTOS
Hi there,
I'm a little confused regarding the use of SYS/BIOS and drivers (I2C, ...) on a C2000 based project and if it's make sense to step over to use SYS/BIOS or TI-RTOS.
In the old project we use one 3-phase motor (up to 1 kW), a standard I2C eeprom and a UART interface for the user. To control the motor an interrupt routine is called approx. 20.000 times per second.
In the new project, which based on the old one it is intended to use 2 motors and additional an I2C pressure- and temperature-sensor. The remaining parts are the same as in the old project which runs currently on a F28069 controller as bare-metal software. With the old project we have sometimes trouble with the I2C communication and until now it's not clear what is the cause, so I'm thinking about to use SYS/BIOS or RTOS and it's drivers but I don't know if this will be a good decision and generally possible.
In short, in the new project two motors are used for a special tool. During the usage the measured current or power shall be saved in the eeprom. The user interface is also active. My experience with TI-RTOS on a wireless measurement project with bluetooth communication (CC2640) is quite positive, so if the we can use drivers as non-blocking functions will be fine. That's the main reason why I think that SYS/BIOS or RTOS would be a good decision but due to the amount of manuals, guides etc. I'm confused. Many of these describing the nonBIOS way, others are good HowTo's but based on another processor like M3-core in place of C2000 if I'm right and so on. So is it possible and makes it sense to use SYS/BIOS and drivers on a F28069 with 2 motors + peripherals?
