 |
|
 |
MAEC TOOL NEWS:
MAECT-M3T-MR308-020316D
A Note on Real-Time OSes M3T-MR308, and M3T-MR30
|
Please take note of the following problem in using real-time OSes M3T-MR308, and M3T-MR30.
- On the minimum value of the system clock's pulse period
- Products and Versions Concerned
| For the M32C/80 and M16C/80 series MCUs | : All the versions of M3T-MR308 |
| For the M16C/60, M16C/20, and M16C/10 series MCUs | : All the versions of M3T-MR30 |
- Description
The setting of the system clock's pulse period is made in the configuration file, and the minimum value of this period can be calculated using the equation described in the user's manual. However, no value that is less than 0.001 ms is allowed to set even if the calculation gives the minimum value less than 0.001 ms.
Therefore, if you set the value less than 0.001 ms in the configuration file, the configurator will return such an error message as shown below.
[Example of Error Messages]
-----------------------------------------------------------------------
cfgXX Error : illegal clock.unit_time --> <0> near line YY (smp.cfg)
-----------------------------------------------------------------------
When setting the system clock's pulse period in the configuration file, make sure that this period of time is greater than the processing time of the system clock interrupt handler operating in OS. Note that the value of the processing time varies with the type of MCU and the operating condition.
For details of calculating the processing time of the system clock interrupt handler, see the reference manual of each real-time OS.
The latest versions of user's and reference manuals can be downloaded from HERE.
|
 |