HD64F2676VFC33 Renesas Electronics America, HD64F2676VFC33 Datasheet - Page 850

IC H8S MCU FLASH 256K 144-QFP

HD64F2676VFC33

Manufacturer Part Number
HD64F2676VFC33
Description
IC H8S MCU FLASH 256K 144-QFP
Manufacturer
Renesas Electronics America
Series
H8® H8S/2600r
Datasheets

Specifications of HD64F2676VFC33

Core Processor
H8S/2600
Core Size
16-Bit
Speed
33MHz
Connectivity
IrDA, SCI
Peripherals
DMA, POR, PWM, WDT
Number Of I /o
103
Program Memory Size
256KB (256K x 8)
Program Memory Type
FLASH
Ram Size
8K x 8
Voltage - Supply (vcc/vdd)
3 V ~ 3.6 V
Data Converters
A/D 12x10b; D/A 4x8b
Oscillator Type
Internal
Operating Temperature
-20°C ~ 75°C
Package / Case
144-QFP
Lead Free Status / RoHS Status
Contains lead / RoHS non-compliant
Eeprom Size
-

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
HD64F2676VFC33
Manufacturer:
RENESAS
Quantity:
5 530
Part Number:
HD64F2676VFC33
Quantity:
9 520
Part Number:
HD64F2676VFC33
Manufacturer:
Renesas Electronics America
Quantity:
10 000
Part Number:
HD64F2676VFC33V
Manufacturer:
RENESAS
Quantity:
5 530
Part Number:
HD64F2676VFC33V
Manufacturer:
ROHM
Quantity:
750 000
Part Number:
HD64F2676VFC33V
Manufacturer:
RENESAS
Quantity:
120
Part Number:
HD64F2676VFC33V
Manufacturer:
RENESAS/瑞萨
Quantity:
20 000
Section 19 Flash Memory (F-ZTAT Version)
19.8.2
When erasing flash memory, the erase/erase-verify flowchart shown in figure 19.11 should be
followed.
1. Prewriting (setting erase block data to all 0s) is not necessary.
2. Erasing is performed in block units. Make only a single-bit specification in the erase block
3. The time during which the E bit is set to 1 is the flash memory erase time.
4. The watchdog timer (WDT) is set to prevent overprogramming due to program runaway, etc.
5. For a dummy write to a verify address, write 1-byte data H'FF to an address whose lower two
6. If the read data is unerased, set erase mode again, and repeat the erase/erase-verify sequence as
19.8.3
All interrupts, including NMI input, are disabled when flash memory is being programmed or
erased, and while the boot program is executing in boot mode. There are three reasons for this:
1. Interrupt during programming or erasing might cause a violation of the programming or
2. If the interrupt exception handling is started when the vector address has not been programmed
3. If an interrupt occurred during boot program execution, it would not be possible to execute the
Rev. 3.00 Mar 17, 2006 page 798 of 926
REJ09B0283-0300
registers (EBR1 and EBR2). To erase multiple blocks, each block must be erased in turn.
Set a value greater than (y + z +
bits are B'00. Verify data can be read in longwords from the address to which a dummy write
was performed.
before. The maximum number of repetitions of the erase/erase-verify sequence (N) must not be
exceeded.
erasing algorithm, with the result that normal operation could not be assured.
yet or the flash memory is being programmed or erased, the vector would not be read correctly,
possibly resulting in CPU runaway.
normal boot mode sequence.
Erase/Erase-Verify
Interrupt Handling when Programming/Erasing Flash Memory
+ ) ms as the WDT overflow period.

Related parts for HD64F2676VFC33