Download Processor Expert

Processor Expert User's manual
Application Design
enabled in init., method SetWait), the FinishProcess method has to be called after the end of the operation.
Since the flash device does not support erase verification feature, the EraseVerify method is implemented by
software routine. Thus it gets more time to verify the flash memory than this method is implemented by
hardware module (all parts of the flash memory have to be read).
3.8.2. Version Specific Information for HC(S)08
The ROM, Z_RAM and RAM ranges depend on the target CPU. It is recommended to increase the stack size if
some standard libraries are used.
For the detailed information on debugging HC08 application using MON8 interface please follow to the chapter
3.8.2.2 Debugging on HC08 Using MON8.
Beans' implementation details:
• All the beans:
- Interrupt priority - the value of this property is ignored, since the HC08 has no HW support for setting
interrupt priorities.
- Event priority - the value of this property can be only "0" (interrupts disabled) or "1" (interrupts enabled),
since the HC08 has no HW support for setting interrupt priorities.
• CPU:
- Speed Mode selection (CPU methods SetHighSpeed, SetLowSpeed, SetSlowSpeed ): if CPU
clock-dependent beans are used then signals generated from such internal peripherals may be corrupted at
the moment of the speed mode selection (if function of clocked devices is enabled). Handling of such a
situation may be done via events BeforeNewSpeed and AfterNewSpeed.
- Interrupt vector table in ROM is placed at the default address in the ROM or in the Flash.
If the interrupt vector table in RAM is selected then it is generated the table in RAM and special
redirection code to ROM. This code transfers program control to the selected address according the table
in RAM. You can use CPU methods SetIntVect to set the address of interrupt service routine.
Note: you cannot change the interrupt vector that is allocated by any bean in your project. It is
recommended to select the event OnSWI together with this option to minimize size of generated code.
• PPG : The PPG beans always allocates the whole timer. Although it would be possible to share the selected
timer between 2 PPG beans, it would be impossible to set the PPG period for these two beans separately. (
More information about this bean can be found in chapter Timers)
• PWM : In contrast to the PPG beans, it is possible for PWM beans to share the selected timer, since they do
not have the SetPeriod method. (More information about this bean can be found in chapter Timers)
• EventCntr16 : Since the timer overflow flag is set when the timer reaches a value of 65535, the maximum
number of events that can be counted by this bean is limited to 65534 (value of 65535 is marked as invalid as
the method GetNumEvents returns the ERR_OVERFLOW value as its result.) (More information about this
bean can be found in chapter Timers)
• TimeDate : It is recommended to make a setting close to 10 ms (resolution provided by GetTime/SetTime
methods). Smaller values unnecessarily overload the system.
• WatchDog: When the Watchdog bean is added to the project, it is automatically enabled. The enabling code
is placed in the CPU initialization code.
Note: Watchdog is enabled by a write to the configuration register. This register can be written only once
after CPU reset. Since the register also contains other bits, that are written during the CPU initialization,
the watchdog must be enabled when CPU is initialized. The property "CPU clock/speed selection" has no
- 100 -