 |
|
|
MESC TOOL NEWS:
MESCT-MR32R-990301D
Please take note of the following problem in using real-time OS MR32R for the M32R family of microcomputers.
Products Concerned
The following products are concerned with this problem:
MR32R V.1.00 Release 1 to MR32R V.2.00 Release 2
Problem
Using more than one alarm handler in an MR32R V.1.00 Release 1 or later product will cause its configurator not to generate data correctly. In this case several of the alarm handlers may not be invoked absolutely.
Workaround
The order of defining alarm handlers in the configurator should be in the descending order of time they are invoked. An incorrect and a correct example of definition are shown below:
[Example (Incorrect)]
-------------------------------------------------------------------------
| |Invoking
| | order
| |--------
| alarm_hand[1]{ | 2
| time = 0x0000:0x0000:0x0800; |
| entry_address = alh1(); |
| }; |--------
| alarm_hand[2]{ | 1
| time = 0x0000:0x0000:0x0700; |
| entry_address = alh2(); |
| }; |--------
| alarm_hand[3]{ | 3
| time = 0x0000:0x0000:0x0900; |
| entry_address = alh3(); |
| }; |
-------------------------------------------------------------------------
[Example (Correct)]
-------------------------------------------------------------------------
| |Invoking
| | order
| |--------
| alarm_hand[1]{ | 3
| time = 0x0000:0x0000:0x0900; |
| entry_address = alh3(); |
| }; |--------
| alarm_hand[2]{ | 2
| time = 0x0000:0x0000:0x0800; |
| entry_address = alh1(); |
| }; |--------
| alarm_hand[3]{ | 1
| time = 0x0000:0x0000:0x0700; |
| entry_address = alh2(); |
| }; |
-------------------------------------------------------------------------
|
|
