HD64F38024DV Renesas Electronics America, HD64F38024DV Datasheet - Page 216

• Manufacturer Part Number: HD64F38024DV
• Description: IC H8/SLP MCU FLASH 80QFP
• Manufacturer: Renesas Electronics America
• Series: H8® H8/300L SLPr

Specifications of HD64F38024DV

• Core Processor: H8/300L
• Core Size: 8-Bit
• Speed: 10MHz
• Connectivity: SCI
• Peripherals: LCD, PWM, WDT
• Number Of I /o: 51
• Program Memory Size: 32KB (32K x 8)
• Program Memory Type: FLASH
• Ram Size: 1K x 8
• Voltage - Supply (vcc/vdd): 1.8 V ~ 5.5 V
• Data Converters: A/D 8x10b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 80-QFP
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Eeprom Size: -

On the other hand, in the group B, the compiler calculates the maximum amount of the
stack area used in the function beforehand, and that amount of stack area is reserved at the
function prolog as shown at [4] of the following example. The SP is unchagened until the
function epilog, and the SP is restored to the original value before the function itself is
called, as shown at [6] of the following example. In this case, a parameter is stored at an
address with 0 or positive offset from the SP without changing the SP, as shown at [5] of
the following example. In group B, the size including the maximum amount of parameter
usage of all the function calls is counted into the Temporary Size of the caller’s stack frame
size as shown at [7] of the following example
As shown at CASE 1 and CASE 4 below, if the groups of the caller and the callee are the
same, the total size of stack consumption for the function g to call the function f is exactly
12 bytes through summing up the Total Frame Size of g and f. As in CASE 2 below, if a
function of the group A calls that of the group B, the total size of stack consumption for the
function g to call the function f is mistakenly 8 bytes through summing up the Total Frame
Size of g and f. This underestimate of the stack consumption came from the fact that the
size for the parameter area in the stack is not summed up. As in CASE 3 below, if a
function of the group B calls that of the group A, the total size of stack consumption for the
function g to call the function f is mistakenly 16 bytes through summing up the Total
Frame Size of g and f. This overestimate of the stack consumption came from the fact that
the size for the parameter area in the stack is summed up twice.
In order to avoid such underestimate or overestimate, do not mix the group A and B, or
correct the estimate of stack consumption finding out the point where a function of the
group A calls that of the group B or the point where a function of the group B calls that of
the group A.
The amount of stack consumption:
CASE 1: the function g of the group A calls the function f of the group B: 8 + 4 = 12
CASE 2: the function g of the group A calls the function f of the group A: 4 + 4 = 8
CASE 3: the function g of the group B calls the function f of the group B: 8 + 8 = 16
CASE 4: the function g of the group B calls the function f of the group A: 8 + 4 = 12
202