Fujitsu FR Series Installation and operating instructions

Fujitsu Microelectronics Europe
Application Note MCU-AN-300021-E-V10
FR FAMILY
32-BIT MICROCONTROLLER
MB91460 SERIES
START91460.ASM
APPLICATION NOTE

Start91460.asm
Revision History
Revision History
Date Issue
2007-03-30 UMa
First draft
This document contains 29 pages.
MCU-AN-300021-E-V10 - 2 - © Fujitsu Microelectronics Europe GmbH

Start91460.asm
Warranty and Disclaimer
Warranty and Disclaimer
To the maximum extent permitted by applicable law, Fujitsu Microelectronics Europe GmbH restricts
its warranties and its liability for all products delivered free of charge (eg. software include or
header files, application examples, target boards, evaluation boards, engineering samples of IC’s
etc.), its performance and any consequential damages, on the use of the Product in accordance with
(i) the terms of the License Agreement and the Sale and Purchase Agreement under which
agreements the Product has been delivered, (ii) the technical descriptions and (iii) all accompanying
written materials. In addition, to the maximum extent permitted by applicable law, Fujitsu
Microelectronics Europe GmbH disclaims all warranties and liabilities for the performance of the
Product and any consequential damages in cases of unauthorised decompiling and/or reverse
engineering and/or disassembling. Note, all these products are intended and must only be used
in an evaluation laboratory environment.
1. Fujitsu Microelectronics Europe GmbH warrants that the Product will perform substantially in
accordance with the accompanying written materials for a period of 90 days form the date of
receipt by the customer. Concerning the hardware components of the Product, Fujitsu
Microelectronics Europe GmbH warrants that the Product will be free from defects in material
and workmanship under use and service as specified in the accompanying written materials
for a duration of 1 year from the date of receipt by the customer.
2. Should a Product turn out to be defect, Fujitsu Microelectronics Europe GmbH´s entire liability
and the customer´s exclusive remedy shall be, at Fujitsu Microelectronics Europe GmbH´s
sole discretion, either return of the purchase price and the license fee, or replacement of the
Product or parts thereof, if the Product is returned to Fujitsu Microelectronics Europe GmbH in
original packing and without further defects resulting from the customer´s use or the transport.
However, this warranty is excluded if the defect has resulted from an accident not attributable
to Fujitsu Microelectronics Europe GmbH, or abuse or misapplication attributable to the
customer or any other third party not relating to Fujitsu Microelectronics Europe GmbH.
3. To the maximum extent permitted by applicable law Fujitsu Microelectronics Europe GmbH
disclaims all other warranties, whether expressed or implied, in particular, but not limited to,
warranties of merchantability and fitness for a particular purpose for which the Product is not
designated.
4. To the maximum extent permitted by applicable law, Fujitsu Microelectronics Europe GmbH´s
and its suppliers´ liability is restricted to intention and gross negligence.
NO LIABILITY FOR CONSEQUENTIAL DAMAGES
To the maximum extent permitted by applicable law, in no event shall Fujitsu
Microelectronics Europe GmbH and its suppliers be liable for any damages whatsoever
(including but without limitation, consequential and/or indirect damages for personal
injury, assets of substantial value, loss of profits, interruption of business operation,
loss of information, or any other monetary or pecuniary loss) arising from the use of
the Product.
Should one of the above stipulations be or become invalid and/or unenforceable, the remaining
stipulations shall stay in full effect
© Fujitsu Microelectronics Europe GmbH - 3 - MCU-AN-300021-E-V10

Start91460.asm
Contents
Contents
REVISION HISTORY.............................................................................................................. 2
WARRANTY AND DISCLAIMER........................................................................................... 3
CONTENTS ............................................................................................................................ 4
1INTRODUCTION................................................................................................................ 5
2SETTINGS OF THE START91460.ASM ........................................................................... 6
2.1 Controller Device (DEVICE)...................................................................................... 6
2.2 Boot / Flash Security (BOOT_FLASH_SEC) ............................................................ 6
2.3 Stack Type and Stack Size (STACKUSE, …)........................................................... 7
2.3.1 STACKUSE................................................................................................. 7
2.3.2 STACK_RESERVE, STACK_SYS_SIZE, STACK_USR_SIZE .................. 7
2.3.3 STACK_FILL, STACK_PATTERN .............................................................. 8
2.4 Copy code from Flash to I-RAM (I_RAM) ................................................................. 8
2.5 Low-Level Library Interface (CLIBINIT)..................................................................... 9
2.6 C++ startup (CPLUSPLUS)....................................................................................... 9
2.7 Clock Configuration................................................................................................. 10
2.7.1 Clock Selection (CLOCKSPEED) ............................................................. 10
2.7.2 Select Clock Modulator (CLOMO, CMPR)................................................ 11
2.8 External Bus Interface (EXTBUS)........................................................................... 13
3USER CLOCK SETTINGS (CLOCKSPEED == CLOCK_USER) ................................... 14
3.1 Clock source (CLOCKSOURCE, ENABLE_SUBCLOCK)...................................... 15
3.2 PLL ratio (PLLSPEED)............................................................................................ 16
3.3 PLL Auto Gear-Up and –Down (DIV_G, MUL_G)................................................... 18
3.4 Clock divider (CPUCLOCK, PERCLOCK, EXTBUSCLOCK).................................. 20
3.5 CAN clock (PSCLOCKSOURCE, PSDVC, CANCLOCK)....................................... 21
3.6 Voltage Regulator (REGULATORCTRL, REGULATORSEL)................................. 23
3.7 Memory Controller (FLASHCONTROL, FLASHREADT, FLASHMWT2)................ 25
4SECTION AND DATA DECLARATION .......................................................................... 28
4.1 Default Sections...................................................................................................... 28
4.2 Additional Sections.................................................................................................. 29
MCU-AN-300021-E-V10 - 4 - © Fujitsu Microelectronics Europe GmbH

Start91460.asm
Chapter 1 Introduction
1 Introduction
All C/C++-language applications need special startup code, which initializes all data areas
generated by the compiler and which performs a basic configuration of the microcontroller.
This document describes the startup file “start91460.asm” version 2.5 or later provided by
Fujitsu
Microelectronics Europe GmbH for the MB91460 series-microcontrollers.
Main Features of the Startup File “start91460.asm”:
- Configuration part for easy step by step set-up of the startup code
- Startup code for pre-setting of core and external bus registers
- Startup code for memory initialization according to FCC911-compiler sections
- Startup file is linkage order independent
© Fujitsu Microelectronics Europe GmbH - 5 - MCU-AN-300021-E-V10

Start91460.asm
Chapter 2 Settings of the Start91460.asm
2 Settings of the Start91460.asm
The startup file has to be configured for the target system (hardware) and the application
software. The startup file provides several prepared settings, which have to be checked and
which have possibly to be changed. The header of the startup file contains information how
to find the lines containing the options to be checked. All lines with the comment extension
“<<<” were pointing to available settings.
In the following paragraphs all available settings are described.
2.1 Controller Device (DEVICE)
Set the target device the application is running in. This setting is used by the startup file to
check the availability of registers and to check the plausibility of settings.
Available settings for DEVICE:
- MB91464A
- MB91467B
- MB91467C
- MB91467D
- MB91469G
- MB91465K
- MB91463N
- MB91461R
- MB91467R
- MB91465X
- others
Note: This list will be adapted, depending on new devices
Note: The setting “others” should only be used for the case that desired device of the
MB91460 Series is not listed.
Example:
The target controller is the MB91F467DA. This requires the setting.
#set DEVICE MB91467D ; <<< select device
2.2 Boot / Flash Security (BOOT_FLASH_SEC)
The most flash devices have two flash and two boot security vectors. It is important to set
the four vectors correctly. Valid boot security vectors means that the build-in bootrom can
not be entered anymore.
Available settings for BOOT_FLASH_SEC:
- OFF: The security feature is switched off. The section SECURITY_VECTORS is reserved
and the vectors are set to 0xFFFFFFFF.
- ON: The security vectors are not set. But the section SECURITY_VECTORS is reserved.
The security vectors have to be set in the user application.
Note: This feature is not available for all devices of the MB91460 Series. The datasheet of
the target device lists the available features.
Note: If the device MB91469G is selected, the section SECURITY_VECTORS is located
from 0x24:8000 – 0x24:800F.
Note: If the ROMless device MB91461R is selected no section SECURITY_VECTORS is
reserved.
MCU-AN-300021-E-V10 - 6 - © Fujitsu Microelectronics Europe GmbH

Start91460.asm
Chapter 2 Settings of the Start91460.asm
Note: For all other devices, including “others” the section SECURITY_VECTORS is located
from 0x14:8000 – 0x14:800F.
Example:
The security feature of target controller should be disabled.
#set BOOT
_
FLASH_SEC OFF ; <<< BOOT and Flash Security Vector
2.3 Stack Type and Stack Size (STACKUSE, …)
2.3.1 STACKUSE
The setting STACKUSE specifies the stack type that is configured, when the application
main()-function is called. The devices of MB91460 Series provide two different types of
stack: system stack and user stack. The application can use either system stack only or it
can use both system stack and user stack.
System stack is always used for interrupt function. It is automatically selected, if hardware
interrupts are executed or if software interrupts are called. All stack operation of interrupt
handlers will work with the system stack.
Outside of interrupt handlers the pre-selected stack type is used. This is either user stack
(option USRSTACK) or system stack (option SYSSTACK). If SYSSTACK is set, only the
system stack area has to be prepared. All operation will work on the same stack. The
necessary safety margin has to be reserved for one stack only. SYSSTACK should be used,
if the necessary RAM consumption for stack has to be low. If USRSTACK is set, both
system stack and user stack have to be prepared. The necessary safety margin has to be
provided twice. USRSTACK should be used, if separated stack areas are necessary for
management reasons. This might be the case with schedulers, operating systems or other
applications.
Available settings for STACKUSE:
- USRSTACK
- SYSSTACK
Example:
The user stack should be used outside of interrupt handlers. This requires the setting.
#set STACKUSE USRSTACK ; <<< set active stack
2.3.2 STACK_RESERVE, STACK_SYS_SIZE, STACK_USR_SIZE
These settings specify the amount of bytes to be reserved for stacks. This value has to cover
all:
- parameters passed over stack
- return addresses for function calls
- local variables (except static)
- temporary data due to compiler optimization
- interrupt context on stacks
- safety margin
For estimating necessary stack size the compiler offers the “-INF stack” option. With it the
compiler generates stack information files (extension “stk”), which list the number of bytes
necessary to execute each function. These stack information files are already available for
© Fujitsu Microelectronics Europe GmbH - 7 - MCU-AN-300021-E-V10

Start91460.asm
Chapter 2 Settings of the Start91460.asm
all library functions and can be found in the Lib\911\ subdirectory of the Softune Workbench
installation.
If the support tool “C-Analyzer” is installed, the additional tool “Musc” is able to collect these
data and to calculate the minimum stack size for the whole application.
Available settings for STACK_RESERVE:
- ON
- OFF
Note: If STACK_RESERVE is ON, the sections USTACK and SSTACK are reserved in this
module. Otherwise, they have to be reserved in other modules. If STACK_RESERVE
is OFF, the size definitions STACK_SYS_SIZE and STACK_USR_SIZE have no
meaning.
Example:
A system stack size of 0x200-4 bytes and a user stack size of 0x400-4 bytes should be
reserved.
#set STACK_RESERVE ON ; <<< reserve stack area in
; ; this module
#set STACK_SYS_SIZE 0x200-4 ; <<< byte size of System stack
#set STACK_USR_SIZE 0x400-4 ; <<< byte size of User stack
2.3.3 STACK_FILL, STACK_PATTERN
With theses settings the stacks can be filled with a specific pattern. Filling the stack with
pattern allows dynamically checking of the stack area, which had already been used.
Available settings for STACK_FILL:
- ON
- OFF
Note: If STACK_ STACK_FILL is OFF, the pattern definition STACK_PATTERN has no
meaning.
Example:
The stacks should be filled with the pattern 0x55AA6699.
#set STACK_FILL ON ; <<< fills the stack area with pattern
#set STACK_PATTERN 0x55AA6699 ; <<< the pattern to write to stack
2.4 Copy code from Flash to I-RAM (I_RAM)
If this option is activated code located in the section IRAM is copied during startup from the
ROM to the instruction RAM. The code is linked for the instruction RAM. This is for example
useful for flash routines, which must be executed in the instruction RAM or for routines,
which should be run in the instruction RAM to benefit from the shorter wait states of the
instruction RAM.
The segment CODE has to be renamed to IRAM for the code, which should be copied the
the instruction RAM during the startup. To rename the segment CODE to IRAM, the
following pragma instruction can be used.
MCU-AN-300021-E-V10 - 8 - © Fujitsu Microelectronics Europe GmbH

Start91460.asm
Chapter 2 Settings of the Start91460.asm
#pragma segment CODE = IRAM
Available settings for I_RAM:
- ON
- OFF
Example:
The code in the segment IRAM should be copied to the instruction RAM during startup.
#set I_RAM ON ; <<< select if code in section IRAM
; should be copied
2.5 Low-Level Library Interface (CLIBINIT)
The setting CLIBINI specifies whether the startup code has to call the stream initialization
function of the C-library.
The stream initialization is necessary only, if streamed IO-functions are used. These
functions (e.g. printf()) also require the definition of application specific low-level functions.
For more information refer to the compiler help.
Available settings for CLIBINIT:
- ON
- OFF
Example:
The stream initialization should not be done.
#set CLIBINIT OFF ; <<< select ext. libray usage
2.6 C++ startup (CPLUSPLUS)
In the C++ specifications, when external or static objects are used, a constructor must be
called followed by the main function. Because four-byte pointers to the main function are
stored in the EXT_CTOR_DTOR section, call a constructor sequentially from the lower
address of the four addresses in that section. If using C++ sources, activate this function to
create the section EXT_CTOR_DTOR.
Available settings for CPLUSPLUS:
- ON
- OFF
Example:
C++ is not used.
#set CPLUSPLUS OFF ; <<< activate if c++ files are used
© Fujitsu Microelectronics Europe GmbH - 9 - MCU-AN-300021-E-V10

Start91460.asm
Chapter 2 Settings of the Start91460.asm
2.7 Clock Configuration
2.7.1 Clock Selection (CLOCKSPEED)
There are different default configurations available, where all necessary settings for clocks
and the related registers are made. These configurations should not be changed. The
default settings include the settings for the flash access and the regulator configuration, too.
Beside these configurations, there is the possibility to define a user configuration.
Available settings for CLOCKSPEED:
- NO_CLOCK clock registers are not set by the startup file.
- SUB_32KHZ_CPU__32KHZ_PER_32KHZ_EXT_32KHZ_CAN__2MHZ means:
Main oscillation = 32 kHz, PLL is not active
CPU clock (CLKB) = 32 kHz
Peripheral clock (CLKP) = 32 kHz
Ext. bus clock (CLKT) = 32 kHz
CAN clock (CLKCAN) = 2 MHz, using main oszillation
- MAIN_4MHZ_CPU___2MHZ_PER__1MHZ_EXT__1MHZ_CAN__2MHZ means:
Main oscillation = 4 MHz, PLL is not activated
CPU clock (CLKB) = 2 MHZ
Peripheral clock (CLKP) = 1 MHZ
Ext. bus clock (CLKT) = 1 MHZ
CAN clock (CLKCAN) = 2 MHz, using main oszillation
- PLL_4MHZ__CPU__48MHZ_PER_16MHZ_EXT_24MHZ_CAN_16MHZ
Main oscillation = 4 MHz, PLL is activated
CPU clock (CLKB) = 48 MHZ
Peripheral clock (CLKP) = 16 MHZ
Ext. bus clock (CLKT) = 24 MHZ
CAN clock (CLKCAN) = 16 MHz, using PLLx
- PLL_4MHZ__CPU__64MHZ_PER_16MHZ_EXT_32MHZ_CAN_16MHZ means:
Main oscillation = 4 MHz, PLL is activated
CPU clock (CLKB) = 64 MHZ
Peripheral clock (CLKP) = 16 MHZ
Ext. bus clock (CLKT) = 32 MHZ
CAN clock (CLKCAN) = 16 MHz, using PLLx
- PLL_4MHZ__CPU__80MHZ_PER_20MHZ_EXT_27MHZ_CAN_20MHZ
Main oscillation = 4 MHz, PLL is activated
CPU clock (CLKB) = 80 MHZ
Peripheral clock (CLKP) = 20 MHZ
Ext. bus clock (CLKT) = 27 MHZ
CAN clock (CLKCAN) = 20 MHz, using PLLx
- PLL_4MHZ__CPU__80MHZ_PER_20MHZ_EXT_40MHZ_CAN_20MHZ
Main oscillation = 4 MHz, PLL is activated
CPU clock (CLKB) = 80 MHZ
Peripheral clock (CLKP) = 20 MHZ
Ext. bus clock (CLKT) = 40 MHZ
CAN clock (CLKCAN) = 20 MHz, using PLLx
MCU-AN-300021-E-V10 - 10 - © Fujitsu Microelectronics Europe GmbH