HD64F38024DV Renesas Electronics America, HD64F38024DV Datasheet - Page 962

• 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: -

g. Inter-file Inline Expansion
h. Added Intrinsic Function
i. #pragma address
j. Support for .stack Directive
k. Added Environment Variable
l. Added Implicit Declarations
4. Notes on Optimizing Features of the Compiler Ver. 6.01
a. Access to External Variables or Pointer Variables without volatile Declaration
948
file_inline is used to specify inline expansion for functions that extend across files and
file_inline_path is used to specify the path name of a file for inline expansion.
Intrinsic function set_vbr is used to set the VBR.
#pragma address can be used to allocate variables to specific absolute addresses.
When code=asmcode has been specified, the compiler outputs a .stack directive within the
assembly-source program.
Environment variable CH38SBR can be used to set initial values for the SBR.
Implicit declaration of _ _AE5_ _ and _ _ABS16_ _ have been added.
Notes below about optimization apply in a case where an H8SX and H8S (without the
legacy=v4 option) object program is created with Ver. 6.01 optimization. For the other cases,
optimization is similar to that of Ver. 4.0 or earlier.
Adopting the newest compiler optimization technology allows the optimization processing in
Ver. 6.01 to analyze aliases for pointers or external variables and analyze data live ranges
including the control flow, which were not possible so far (in Ver. 4.0 or ealier). This provides
a wider range of optimization than Ver. 4.0 within the limits of the language specifications.
However, a program that was previously running because it was not optimized enough may not
run because it has become a target of optimization.
Examples of programs that were not optimized so far but will become targets of optimization
in Ver. 6.01 are shown below.
A volatile declaration guarantees that the volatile-qualified variable is accessed whenever it is
used because the variable may be updated outside the program sequence. For example, data
values are changed by interrupt processing or hardware processing.
The compiler assumes that variables without a volatile declaration are changed only by
successive processing of the program sequence or function calls.
In Ver. 4.0 or earlier, external variables without a volatile declaration were optimized as
shown in the example below: