 |
|
|
MESC TOOL NEWS:
MESCT-MR32R-990416D
Please take note of the following problem in using real-time OS MR32R for the M32R family of microcomputers.
Problem on Interrupt Disable Time at Processing System Clocks
- Versions Concerned
All of the versions of MR32R V.1.00 Release 1 to MR32R V.3.00 Release 1
- Description
When processing system clocks, the alarm handler and the cyclic handler of MR32R are invoked in their interrupt disabled state, so that interrupt disable time may be extended in proportion to the user-specified processing time of these handlers.
- Workaround
MR32R invokes the alarm and the cyclic handler in their interrupt disabled state. However, even if interrupts are enabled in these handlers, MR32R will work normally as far as the interrupts are disabled at the end of the handlers. Therefore, in the case that the user's system is sensitive to interrupt disable time, the time will be reduced by enabling an interrupt at the beginning of these handlers and disabling it at the end of them.We plan to shorten interrupt disable time by handling the above processing inside the OS in our next release.
[Example]
--------------------------------------------------------------------
|
| void cyc1(void)
| {
| asm(" mvfc R0,PSW");
| asm(" or3 R0,R0,#0x0040");
| asm(" mvtc R0,PSW");
| E
| E
| Processing by cyclic handler
| E
| E
| asm(" mvfc R0,PSW");
| asm(" and3 R0,R0,#0xFFBF");
| asm(" mvtc R0,PSW");
| }
|
--------------------------------------------------------------------
Problem in Using the trcv_msg System Call
- Versions Concerned
MR32R V.2.00 Release 1 and MR32R V.2.00 Release 2
- Description
When a trcv_msg system call is issued to receive a message, the decremented message count is written to an incorrect area, so that improper operation may be effected, or an incorrect value be stored in the message received with the trcv_msg system call.
- Workaround
Since this problem has already been fixed in MR32R V.3.00 Release 1, please use this release when issuing the trcv_msg system call.
|
|
