• The contents of this document are subject to change without notice.
Customers are advised to consult with FUJITSU sales representatives before ordering.
• The information, such as descriptions of function and application circuit examples, in this document are presented solely
for the purpose of reference to show examples of operations and uses of Fujitsu semiconductor device; Fujitsu does not
warrant proper operation of the device with respect to use based on such information. When you develop equipment
incorporating the device based on such information, you must assume any responsibility arising out of such use of the
information. Fujitsu assumes no liability for any damages whatsoever arising out of the use of the information.
• Any information in this document, including descriptions of function and schematic diagrams, shall not be construed as
license of the use or exercise of any intellectual property right, such as patent right or copyright, or any other right of
Fujitsu or any third party or does Fujitsu warrant non-infringement of any third-party' s intellectual property right or other
right by using such information. Fujitsu assumes no liability for any infringement of the intellectual property rights or other
rights of third parties which would result from the use of information contained herein.
• The products described in this document are designed, developed and manufactured as contemplated for general use,
including without limitation, ordinary industrial use, general office use, personal use, and household use, but are not
designed, developed and manufactured as contemplated (1) for use accompanying fatal risks or dangers that, unless
extremely high safety is secured, could have a serious effect to the public, and could lead directly to death, personal injury,
severe physical damage or other loss (i.e., nuclear reaction control in nuclear facility, aircraft flight control, air traffic
control, mass transport control, medical life support system, missile launch control in weapon system), or (2) for use
requiring extremely high reliability (i.e., submersible repeater and artificial satellite).
Please note that Fujitsu will not be liable against you and/or any third party for any claims or damages arising in connection
with above-mentioned uses of the products.
• Any semiconductor devices have an inherent chance of failure. You must protect against injury, damage or loss from such
failures by incorporating safety design measures into your facility and equipment such as redundancy, fire protection, and
prevention of over-current levels and other abnormal operating conditions.
• If any products described in this document represent goods or technologies subject to certain restrictions on export under
the Foreign Exchange and Foreign Trade Law of Japan, the prior authorization by Japanese government will be required
for export of those products from Japan.
This chapter describes latch-up prevention and pin termination.
● To set latch-up prevention
Latch up may occur on CMOS ICs when the applied voltage for input terminals or output terminals is higher than V
or lower than VSS, or a voltage higher than the maximum rating voltage is applied between VCCand VSS. Make sure
not to apply a voltage higher than the maximum rating voltage since latch up may surge electric current and result in
the thermal destruction of the device.
● Termination of unused pin
An unused pin must be terminated by a pull-up or pull-down resistor externally, or by switching on the internal pull-up
or pull-down resistor before enabling the pin inputs to avoid transverse current.
CC
● Power-supply pin
If multiple VCCand VSSexist, as a matter of device design, they are connected to each other to prevent an error when
their voltage should be identical in the device. In order to reduce unnecessary radiation, prevent an strobe signal error
due to upward ground level, and comply with total output current standard, be sure to externally connect them to power
supply and ground. Give consideration to connect V
Near the device, it is preferable to connect about 0.1uF ceramic capacitor as a bypass capacitor between V
.
V
SS
CC andVSS
of the device from power supply at low impedance.
● Crystal-oscillator circuit
Noise to X0 or X1 pin may cause an error. Make a design for printed board to closely allocate X0, X1, crystal oscillator
(or ceramic oscillator), bypass capacitor towards ground and the device.
It is recommended to make a printed board artwork which surrounds X0 and X1 pins using ground.
The above recommendations also apply to the subclock oscillator pins X0A and X1A.
● NC and OPEN pin termination
Do not terminate NC pin and OPEN pin to use.
● Mode pins (from MD0 to MD2)
Connect pins from MD0 to MOD2 directly to VCCor VSSto use. To avoid entering test mode due to noise, make a short
pattern length between each mode pin on printed board and V
or VSS to connect pins at low impedance.
CC
CC
and
● At the time of power-on
Immediately after power-on operation, be sure to reset INIT pin to initialize the setting (INIT). Immediately after poweron operation, to ensure the oscillation stabilization time required for oscillation circuit, hold “L”-level input to the pin
during the oscillation stabilization time required for oscillation circuit. (INIT operation on the pin initializes the setting for
oscillation stabilization time to minimum value.)
● Source oscillation input at the time of power-on
At the time of power-on, be sure to input the clock until the oscillation stabilization wait is over.
1
Chapter 1 Introduction
1.How to Handle the Device
● Caution: during the PLL clock operation
Even if oscillator is disconnected or input is stopped while selecting PLL clock, self-excited oscillation circuit in the PLL
may continue running at self-running frequency. This self-running operation is not covered by guarantee.
● For more specification about operating voltage, see the latest data sheet.
2
Chapter 1 Introduction
2.Instruction for Users
2. Instruction for Users
■ Clock Controls
By inputting “L” to INIT, ensure clock oscillation stabilization time.
■ Switching of dual-purpose port
Use PFR (Port function register) to switch between PORT and dual-purpose port.
■ Low-power-consumption mode
• For standby mode, enable synchronous standby (TBCR.SYNCS=“1”) and then use the following sequences.
(LDI
(LDI
STB
LDUB
LDUB
NOP
NOP
NOP
NOP
NOP
In addition, after returning from standby, set I flag, ILM and ICR in order to branch to interrupt handler which
triggered the return.
• If you use monitor debugger, you should avoid the following.
• Do not set breakpoints for command sequence above.
• Do not conduct stepwise execution for command sequence above.
#_STCR, R12
R0, @R12
@R12, R0
@R12, R0
value_of_standby is a write data to STCR#value_of_standby, R0
_STCR is the STCR address. (481H)
Write to Standby Control Register (STCR).
STCR read for synchronous standby.
Dammy read STCR again.
NOP x 5 for timing adjustment.
■ Power-on sequence
Power-on and power-off sequence valid for MB91V460 Rev.A. Please review the datasheets of the flash
devices for a valid power-on and power-off sequence on those devices.
The power supply V3 for LCD must not exceed VDD5. The power-on of V3 should be carried out after poweron of VDD5R and VDD5. To power on analogue power supply AVCC and analogue signal, power VDD5R and
VDD5 on before.
■ Power supply operating conditions
Power supply recommendation valid for MB91V460 Rev.A. Please review the datasheets of the flash devices
for a recommendation of the power supply conditions on those devices.
[VDD5 = HVDD5 = AVCC] >= VDD35. This is the recommended condition.
3
Chapter 1 Introduction
2.Instruction for Users
■ Caution: PS register
Because some commands previously proceed PS register, interrupt processing routine may be broken during
the use of debugger or displayed data on PS flag may be updated due to the following excecptional operations
((1) and (2)).
In each case, it is designed to correctly re-proceed operations after the return, the operation before and after
EIT is carried out in accordance with the specification.
• In immediately preceding DIV0U or DIV0S command,
• If interrupted by user,
• If stepwise execution is carried out,
• If data event or emulator menu made a break,
The following operation may be generated.
1. D0 or D1 flag is updated ahead.
2. EIT processing routine (interruption by user or emulator) is carried out.
3. After the return from EIT, it executes DIV0U or DIV0S command and then D0 or D1 flag are updated
to the same value as 1.
• If you execute each command of ORCCR, STILM, MOV Ri or PS to enable interruption with
interruption by user generated, the following operation may be generated.
4. PS register is updated ahead.
5. EIT processing routine (interruption by user) is carried out.
6. After the return from EIT, it executes commands above, and then PS register is updated to the same
value as 1.
■ Watchdog timer function
Watchdog timer function equipped with FR60 monitors the progress to ensure that program executes reset
delay operation within a specified time and resets CPU if reset delay operation was not executed due to
runaway of program. Once you enable watchdog timer function, it continues running until it is reset.
By way of exception, reset delay is automatically conducted under the condition where CPU program
execution is stopped. For this exceptional condition, see “Chapter 20Software Watchdog Timer (Page
No.273)“.
■ Register against read/modify/write command
SMR register within UART cannot use read/modify/write command. To write in SMR register, write by Byte/
Half-word/Word in consideration with write control bit (bit-5, 4, 2, 0) rather than accessing by bit-by-bit.
4
Chapter 1 Introduction
2.Instruction for Users
■ Caution: writing to registers which include a status flag
Writing to a register including a status flag (in particular, interrupt request flag) in order to control the function,
note that you should not clear status flag unintentionally.
That is, take care not to clear the flag for status bit and make control bit to be the expected value during the
writing.
Especially, for control bits consisting of several bits, bit command is not available since single bit access is
only acceptable for bit command, you should write into the both of control bit and status flag at the same time
by Byte/Half-word/Word access. In this case, you should not clear other bits (bits of status flag) unintentionally.
The following shows registers which mostly include both of several bits and status flag.
• TBCR
• OSCR
•TWCR
• TCCS0, TCCS1
• ICS01
• TMCSR0, TMCSR1, TMCSR2, TMCSR3
• PCN00, PCN01, PCN02,...
• ADCSL0, ADCSL1
• CCR0, CCR1
Note: For bit command, you do not have to be careful since this matter has been already considered.
■ Caution: writing to registers which include a status flag
Writing to a register including a status flag (in particular, interrupt request flag) in order to control the function,
note that the actual writing to the registers may be delayed. This is because of using write buffers on the
busses to the resources which accept a write access from CPU immediately but can access the resource
registers delayed.
In this case it can happen that within an ISR the interrupt request flag is cleared by writing to the register and
the ISR is completed with RETI, but the interrupt request flag is still active and the ISR is executed again.
To synchronize the access to the resources on this architecture please follow this recommendation:
Use a read access (byte or halfword) to the RBSYNC address to synchronize the CPU operation (e.g. the
interrupt acceptance of the CPU) to a preceding write access to the resources on R-bus (e.g. to an interrupt
flag) on following addresses (0x0000-0x01FF, 0x0280-0x037F, 0x0400-0x063F and 0x0C00-0x0FFF).
Use a read access (byte or halfword) to the CBSYNC address to synchronize the CPU operation (e.g. the
interrupt acceptance of the CPU) to a preceding write access to the CANs on D-bus (e.g. to an interrupt flag)
on following addresses (0xC000-0xFFFF).
5
Chapter 1 Introduction
3.Caution: debug-related matters
3. Caution: debug-related matters
■ Stepwise execution of RETI command
Under the circumstances where interruption is often generated when carrying out stepwise execution, only
relevant interrupt processing routine is repeatedly executed after the stepwise execution of RETI. Therefore,
main routine or low-level interruption program will not be executed.
To avoid this problem, do not proceed stepwise execution of RETI command.
Or, upon the time when no debug is needed for relevant interrupt routine, proceed the debug by prohibiting
relevant interruptions.
■ Operand break
Do not set the access for area including system stack pointer address as the target for data event break.
6
4.How to Use This Document
4. How to Use This Document
■ Main terminology: This table shows main terminology used for FR60.
TermMeaning
32-bit-wide bus for internal instruction.
I-bus
D-bus
F-bus
R-bus
X-bus32-bit-wide address and data bus. Via bus-converter for external bus, it accesses to external bus.
Main clock
(F
CL-MAIN
Subclock
(F
CL-SUB
Base clock
(Φ)
CPU clock
(CLKB)
Peripheral clock
(CLKP)
External bus clock
(CLKT)
CAN clock
(CLKCAN)
Main clock mode
Subclock mode
Main RUNMain RUN is the status which is in main clock mode and also all circuits are operable.
Sub RUNSub RUN is the status which is in subclock mode and also all circuits are operable.
Oscillation
stabilization time
Main clock
oscillation
stabilization wait
)
)
Since FR60 series employ internal Harvard architecture, instruction and data are independent bus. For I-bus,
Harverd/Prinston-bus-converter is connected.
Internal 32-bit-wide data bus.
For D-bus, bit search module, Harverd/Prinston-bus-converter, R-bus interface (32-bit⇔16-bit Busconverter), and CAN modules are connected.
Internal 32-bit-wide bus.
F-bus is connected to embedded Flash/ROM and embedded RAM.
Internal 16-bit-wide data bus.
R-bus is connected to D-bus via R-bus-converter. For R-bus, peripheral function, I/O, clock generator and
interrupt controller are connected.
This a clock which acts as a benchmark for LSI operation triggered by high-speed-side oscillation.
This is connected to main clock oscillation stabilization timer and clock generator.
This a clock which acts as a benchmark for LSI operation triggered by low-speed-side oscillation.
This is connected to sub oscillation stabilisation timer, real-time clock and clock generator.
At the maximum speed, base clock has the same cycle as source oscillation. In PLL of the clock generator,
base clock has clock multiplied by 1, 2, 3, 4, 5, 6, 7 and 8 or clock divided by 2.
Base clock is basis clock which generates CLKB, CLKP and CKLT in the clock generator.
CPU clock is the clock which is referred by CPU, embedded ROM, embedded RAM, bit search module and
internal bus (I-bus, D-bus, F-bus and X-bus) operations. Generated from the base clock in the clock generator.
Peripheral clock is the clock which is referred by each peripheral function (peripheral functions other than bit
search module and CAN) connected to R-bus and R-bus, clock control, interrupt controller, I/O port and
external interrupt input d operations. Generated from the base clock in the clock generator.
External bus clock is the clock which is referred by external expansion bus interface connected to X-BUS and
external clock output operations. Generated from the base clock in the clock generator.
CAN clock is the clock which is referred by the CAN modules. Generated from the non modulated PLL
output clock to ensure operation within CAN network oscillation tolerances.
Mode which runs based on main clock. This main clock mode has status such as main RUN,main sleep, main
stop, oscillation stabilization wait RUN, oscillation stabilization wait reset and program reset.
Mode which runs based on subclock. This subclock mode has status such as sub RUN, sub sleep, sub stop,
subclock oscillation stabilization wait RUN and program reset.
Upon the reset (INITX, RST), return from stop, return from PLL abnormal operation, generation of watchdog
and during main clock stop, it takes oscillation stabilization time for main clock. Time base timer counts the
time.
Wait time until main clock oscillates after main clock stops in subclock mode.
Main clock oscillation stabilization timer counts the time.
Chapter 1 Introduction
7
Chapter 1 Introduction
4.How to Use This Document
■ Access size and address position
OffsetRegister nameWrite-onlyRead-only
Address
Address offset value/Register name
Read/write
Block
Up/down counter
0, 1
Initial value
Byte access, Half-word access, and Word access are allowed.
There are three kinds of accesses such as Byte access, Half-word access and Word access. However, note
that some registers have restricted access. For more information, see “3.2. I/O Map (Page No.24)” or “Detail
Description of Register” in each chapter.
B,H,W: Byte access, Half-word access, and Wordaccess are allowed.
B: Byte access (Be sure to access by Byte.)
H: Half-word access (Be sure to access by Half-word.)
W: Word access (Be sure to access by Word.)
B, H: Byte access, Half-word access only (Word access is not allowed.)
H,W: Half-word access, Word access only (Byte access is not allowed.)
Reference
The following describes address position to access.
• In Word access, address becomes multiple of 4. (Lowest order 2 bits mandatorily become “00”.)
• In Half-word access, address becomes multiple of 2. (Lowest order 1 bit mandatorily becomes “0”.)
• In Byte access, address will not be changed.
Therefore, for example, make RCR0 register to use Half-word access,
For address 0B0H, RCR1+RCR0 register is accessed.
(When address offset is +1 and +2, (Example: RCR0+UDCR1) Half-word access is not allowed.)
8
■ About access size and bit position
Register markRegister nameTarget peripheral device AddressAccess sizeBit position
(1) Counter control register (Higher byte)
This is the register (higher byte) which controls up/down counter operation.
R: Readable
W: Writable
RM: Reading operation during read/modify/write operation.
“/” (Slash) R/W: Readable and writable. (The read value is the value written.)
“,” (comma) R,W: Values are different between read and write. (The read value is different from
the value written.)
R0: The read value is “0”.
R1: The read value is “1”.
W0: Always write “0”.
W1: Always write “1”.
(RM0): read/modify/write operation reads “0”.
(RM1): read/modify/write operation reads “1”.
RX: The read value is indeterminate. (Reserved bit or undefined bit)
WX: Writing does not affect the operation. (Undefined bit)
• Example of how R/W is used
• R/W: Readable and writable. (The read value is the value written.)
• R,W: Readable and writable. (The read value and written value are different.)
• R,RM/W: Readable and writable. (The read value and written value are different. Read/modify/write
command reads the value written.) Example: port data register
• R(RM1),W: Readable and writable. (The read value and written value are different. Read/modify/write
command reads 1.) Example: interrupt request flag
• R/WX: Read-only (Read-only. Writing does not affect the operation.)
• R1,W: Write-only (Write-only. The read value is 1.)
• R0,W: Write-only (Write-only. The read value is 0.)
• RX,W: Write-only (Write-only. The read value is indeterminate.)
• R/W0: Reserved bit (The written value is 0. The read value is the value written.)
• R0/W0: Reserved bit (The written value is 0. The read value is 0.)
• R1,W0: Reserved bit (The written value is 0. The read value is 1.)
• RX,W0: Reserved bit (The written value is 0. The read value is indeterminate.)
• R/W1: Reserved bit (The written value is 1. The read value is the value written.)
• R1/W1: Reserved bit (The written value is 1. The read value is 1.)
• R0,W1: Reserved bit (The written value is 1. The read value is 0.)
• RX,W1: Reserved bit (The written value is 1. The read value is indeterminate.)
• RX/WX: Undefined bit (The read value is indeterminate. Writing does not affect the operation.)
• R0/WX: Undefined bit (The read value is 0. Writing does not affect the operation.)
10
Chapter 2 MB91460 Rev.A/Rev.B Overview
1.Overview
Chapter 2MB91460 Rev.A/Rev.B Overview
1. Overview
MB91460 is a series of standard microcontrollers containing a range of I/O peripherals and bus control
functions. MB91460 features a 32-bit RISC CPU (FR60 series) core and is suitable for embedded control
applications requiring high-performance and high-speed CPU processing. MB91460 derivatives also contain
up to 16 kByte instruction cache memory and other internal memories to improve the execution speed of the
CPU.
MB91460 Rev.B has the same features as MB91460 Rev.A and adds some additional components in order to
support infotainment applications. Which components and modules will be included in MB91460 Rev.B is not
yet decided finally. So this document gives only a proposal at this stage of development.
MB91460 Rev.B : This series is presently being specified, and not available yet.