To the maximum extent permitted by applicable law, Fujitsu Microelectronics Europe GmbH restricts
its warranties and its liability for the SK-91F467-FLEXRAY and all its deliverables (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,
ujitsu Microelectronics Europe GmbH disclaims all warranties and liabilities for the performance of
F
the Product and any consequential damages in cases of unauthorised decompiling and/or reverse
engineering and/or disassembling. Note, the SK-91F467-FLEXRAY board and all its deliverables 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
The SK-91F467-FLEXRAY is a multifunctional development board for the FUJITSU FlexRay
communication controller MB88121 and the 32-bit Flash microcontroller MB91F467DA. It
can be used stand alone for software development and testing or together with monitordebugger software.
The board allows the designer immediately to start with the software and system
development, before his own final target system is available.
The SK-91F467-FLEXRAY supports the FUJITSU 32-bit Flash microcontroller MB91F467D
and the FUJITSU FlexRay stand alone communication controller MB88121.
The Starter Kit can be used as a stand-alone development platform, or if a MCU socket is
soldered instead of the Flash MCU MB91F467D, with the emulation system MB91V460
adapter board (MB2198-300) and 208 pin probe cable board (PB-91467D-NLS-208PFV).
This User Guide is describing PCB version V1.1. The PCB version is printed at the TOP side
of the starter kit close to MB91F467D MCU [U1].
The starter kit includes 32MBit (4MByte) SRAM memory on board. The SRAM can be used
with 5V, or with 3.3V external bus supply voltage.
1.3.2 MCU Clocks
The board is supplied with a 4MHz crystal as the main oscillation clock for the MCU. Using
the internal PLL of the MCU, internal clock rates up to 100MHz can be achieved. The MCU
sub clock is connected to a 32.768 kHz crystal.
1.3.3 MCU Operating Mode
The operating mode of the microcontroller can be selected with the Dip-switch S5.
1.3.4 FlexRay CC Clock
The FlexRay CC clock is operated by a 10MHz crystal mounted in a socket. By removing the
10MHz crystal it is also possible to use an external clock oscillator.
1.3.5 FlexRay CC-MCU Connection
The FlexRay CC (MB88121) is connected to the MCU via external bus. It is possible to use it
in 8 bit / 16 bit multiplexed, 8 bit / 16 bit non multiplexed or SPI communication-mode
(dependent from revision of MB88121). With jumper or switches the user can change
between the different modes.
1.3.6 External Bus interface Connectors
Via DIN 41612 VG96ABC and VG48ABC connectors (external bus interface of the MCU), it
is possible to connect the FlexRay FPGA Board to the Starter Kit and use the FPGA as
FlexRay communication controller. It is also possible to connect other devices e.g. user
applications or Fujitsu graphic device sub boards.
1.3.7 FlexRay Physical Layer
The connection to the physical layer of the FlexRay bus with 9-pin D-Sub connectors (X2
and X6) is realized with RS485 transceiver, or it is also possible to deselect the RS485
transceiver and use pluggable physical layer driver module from TZM (FT1080) instead.
1.3.8 CAN Bus
Three high-speed CAN-transceivers (PCA82C250) are available to connect all available onchip CAN-controllers to 9-pin D-Sub connectors (X9, X10 and X11). The transceivers
provides differential transmit and receive capability between CAN-controller and CAN-bus.
1.3.9 RS-232 and LIN
RS-232 and LIN signals are shared on the 9-pin D-Sub connectors (X1, X4 and X8). It can
be selected, if RS-232 or LIN will be used.
Three separate RS-232 transceivers and three separate LIN transceivers are available, to
connect the on-chip USARTs to the 9-pin D-Sub connectors.
The RS-232 transceivers generate the adequate RS-232 levels for receive (RXD) and
transmit (TXD) lines. The RTS signal can be shortcut to CTS using jumpers (some PC
software needs this connection, when a 1:1 cable is used).
Either the DTR line or the RTS line of X1, X4 or X8 connectors can be selected to generate
a system reset.
The LIN transceivers (TLE6259) generate the adequate levels to drive the bus line in LINsystems for automotive and industrial applications.
1.3.10 MCU Pins
All 208 pins of the microcontroller are connected to the edge connectors J1, J2, J3 and J4
and are directly available to the user.
1.3.11 User Buttons
There are four push buttons on board, which can be connected to input-ports of the
microcontroller. Some ports may support additional functions like external interrupts (INT0,
INT1 and INT2) and trigger for the Reload Timer or Input-Capture (TIN0 / ICU0). One
additional button is reserved as System-Reset-button to reset the MCU and the FLEXRAY
CC simultaneously, but it is possible to disconnect the RST-ports with JP52 or JP54.
It is possible to connect with Dip-switch S3 eight port input switches at S4 to the MCU port
P26_D0 – P26_D7. All eight ports can be switched separately to use e.g. only four ports as
input.
1.3.12 User LEDs and optional LCD
Sixteen user-LEDs are connected via two pull-down resistor networks to port P25_D0 P25_D7 and to port P16_D0 - P16_D7. Parallel to the LEDs on port P25, the connector J6
can be used to connect a standard alphanumeric display. The resistor networks RN2 and
RN3 can be removed, to free the ports.
1.3.13 Power Supply
The four on-board step-down switching regulators allow the user to connect an unregulated
DC input voltage between +9V to +12V (max. 2000mA) to the starter-kit. The switching
regulators provide the voltages of 5V (3A), 3.3V (3A), 2.5V (1,5A) and 1.8V (1,5A) on the
starter kit. These voltages give also the possibility, to connect an optional graphic-controller
starter kit to the board. The switching regulators are short circuit protected and provide a
thermal shutdown.
If the SK-91F467-FLEXRAY starter-kit is connected to the Fujitsu FlexRay FPGA-board it is
possible, that the power supply for the SK-91F467-FLEXRAY will be provided by the FPGAboard and a power supply connection to the SK-91F467-FLEXRAY is not needed. For that
case the pins 14B, 15B and 16B of DIN 41612 VG48ABC connector X14 are used as
voltage input behind the SK-91F467-FLEXRAY on-board power switch, so that the power
switch on the FPGA board switches the whole system.
Remove the board carefully from the shipping carton.
First check if there are any damages before power on the starter kit.
To supply the starter kit, use the delivered In-Plug AC-DC Adapter (UPA 2000). Select the
AC plug adapter suitable for your country power sockets
Figure 2-1: AC plug adapter
and insert this adapter into the connection terminal on the AC-DC adapter.
Figure 2-2: AC plug adapter selection
Check the selected output DC voltage of the AC-DC In-Plug adapter at the voltage selection
key. It should be 9V! Change the output voltage only in a powered-down condition!
Figure 2-3: DC voltage selection
Select the low voltage adapter suitable to the power connector X5 at the SK-91F467FLEXRAY and plug it to the connecting socket in the right orientation (+ connected to shield
and GND connected to centre pin).
Figure 2-4: Low voltage adapter selection
Now connect the DC low voltage adapter to the Starter kit and plug in the In-Plug Power
Supply to a power socket. The SK-91F467-FLEXRAY can be turned on with the on board
power switch S8 (or S9).
For the power supply of the SK-91F467-FLEXRAY a DC input voltage of 9V – 12V is
recommended. The positive voltage (+) must be connected to the shield, and ground
(GND) must be connected to the centre of the connector X5!
After power-on of the SK-91F467-FLEXRAY, the four red power-on LEDs D24 (5V), D30
(3.3V), D34 (2.5V) and D40 (1.8V) should be light. The reset LED D18 should be off.
Additionally the LED D2 and D4 should be on. The starter kit is delivered with programmed
Softune Workbench Monitor Debugger in internal Flash of MB91F467D series. The monitor
debugger is checking also the external SRAM access at CS1. In case of successful access
to external SRAM the LED D2 and D4 are ON. In case of failed access LED D1 and D4 are
set to ON.
The following table lists all jumpers including its default setting and location on the starter kit.
The default jumper setting is described for 16 bit non multiplexed bus communication
between MCU and FlexRay CC.
Fujitsu supplies a full working 32bit development environment with the “SK-91F467FLEXRAY” starter kit called Softune Workbench V6. The Softune Workbench also supports
a monitor debugger which is pre-programmed into the internal Flash memory of the “SK91F467-FLEXRAY”. To develop own software and to work with the Monitor Debugger of the
“SK-91F467-FLEXRAY” the Softune Workbench development environment must be installed
first. Follow the instructions for successful installation of the Softune Workbench.
1) Before starting the installation setup ensure that you are logged in with administrator
or power user permissions, otherwise the Softune installation will fail! Be aware that
Softune does not support multi-user support. Therefore install- and user login must
be the same.
2) Browse on the starter kit CD-ROM into the directory Software\SWBInstall and start
the setup.exe
You can also start the installation using a browser by opening the index.html of the
CD-ROM. Use the link “Software\Softune Workbench\” in the left side frame.
3) Follow the installation instructions
4) For the default installation path it is recommended to use c:\Softune32
5) After the installation is finished, Softune Workbench for FR can be started via the
Windows “Start” menu
Figure 2-7: Softune Workbench start menu location
6) When Softune Workbench is started the following window will be shown
This chapter describes all jumpers and switches that can be modified on the starter kit. The
default setting is shown with a grey shaded area.
3.1 MCU Operating-Mode (S5)
The DIP-switch S5 is used to set the operating mode of the MCU. Ensure that the mode pin
settings correspond to the operation-mode of the application. For more detailed information
please check the Hardware-Manual of the microcontroller.
DIP switch Setting Logical value
S5/1 (MD0)
ON (closed) 1 (high)
OFF (open) 0 (low)
S5/2 (MD1)
ON (closed) 1 (high)
OFF (open) 0 (low)
S5/3 (MD2)
ON (closed) 1 (high)
OFF (open) 0 (low)
S5/4 (Not used)
ON (closed) Not connected
OFF (open) Not connected
Default: grey
Table 3-1: MCU Operating Mode
By default, the “Single Chip Run-Mode” of MB91F467DA is selected.
The DIP-switch S2 is used to set the operating mode of the FlexRay communication
controller. Ensure that the mode pin settings correspond to the operation-mode of the
application. For more detailed information please check the Hardware-Manual of the
FlexRay CC.
DIP switch Setting Logical value
S2/1 (MD0)
ON (closed) 0 (low)
OFF (open) 1 (high)
S2/2 (MD1)
ON (closed) 0 (low)
OFF (open) 1 (high)
S2/3 (MD2)
ON (closed) 0 (low)
OFF (open) 1 (high)
S2/4 (MDE0)
ON (closed) 0 (low)
OFF (open) 1 (high)
S2/5 (MDE1)
ON (closed) 0 (low)
OFF (open) 1 (high)
S2/6 (MDE2)
ON (closed) 0 (low)
OFF (open) 1 (high)
Default: grey
Table 3-2: FlexRay CC Operating Mode
By default, the “16-bit non multiplexed mode” is selected.
The DIP-switch S1 is used to set the FlexRay CC SPI settings, if the FlexRay CC is selected
to communicate with the MCU over SPI. For more detailed information please check the
Hardware-Manual of the FlexRay CC.
Note:
he DIP-switch (S1) is connected to the FlexRay CC in case the
T
jumpers setting are set to SPI communication mode. Please refer
to chapter 3.5 MCU-FlexRay CC Connection.
There are four on-board switching regulators to provide the voltages 5V, 3.3V, 2.5V and
1.8V on the starter-kit. With the power ON/OFF-switch S8 or S9 (S9 is a soldering option to
use a different switch), the main input voltage from DC-connector X5 will be connected to the
VIN voltage of the board. The VIN voltage supplies the switching regulators and the VBat
voltage of the FlexRay physical layer driver modules from TZM (FT1080), if they are
connected to X3 and X7.
Switch Setting Description
S8 or S9
Default: grey
With JP91 the pins B14, B15 and B16 of the external bus interface connector X14 can be
connected to the VIN voltage, so that it is possible to supply the board from an external
connected board e.g. the Fujitsu FlexRay FPGA board.
ON (1-2) Power ON
OFF (2-3) Power OFF
Table 3-4: Power Switch
There is a triple supply monitor on-board, which monitors three of the four DC output
voltages and generates a system reset, in case with wrong levels of the on board voltages.
5V and 3.3V are always monitored and the third monitored voltage can be selected with the
solder jumpers JP42 and JP43.
With JP68 it is possible to select the whole board supply voltage Vcc to 5V or 3.3V
Jumper Setting Description
JP91
ON (closed) Vin connected to X14 pins B14, B15 and B16
OFF (open) Vin not connected to X14 pins B14, B15 and B16
P21 With this jumper it is possible to connect the MCU external bus interface supply
J
VDD35 to 3.3V. The MCU MB91460 series supports the function to supply the MCU
with 5V so that the normal I/O ports work with 5V and supply the external bus
interface with 3.3V.
JP23 This jumper is used to connect the HVDD5 supply to MCUVcc. The HVDD5 is the
MCU supply voltage for the high current ports.
JP25 This jumper is used to connect the VDD5R MCU supply pins to MCUVcc
JP26 This jumper is used to connect the Vcc voltage to MCUVcc.
JP27 This jumper is used to connect the VDD5 MCU supply pins to MCUVcc
JP28 This jumper is used to connect the HVSS5 MCU pins to GND. HVSS5 are the GND
pins for the high current ports.
Note:
JP23, JP25, JP26, JP27 and JP28 can be used for
measurements of power consumption of the MCU.
Jumper Setting Description
JP21
1-2 VDD35 connected to MCUVcc
2-3 VDD35 connected to 3.3V
JP23
ON (closed) HVDD5 connected to MCUVcc
OFF (open) HVDD5 not connected to MCUVcc
JP25
ON (closed) VDD5R connected to MCUVcc
OFF (open) VDD5R not connected to MCUVcc
JP26
ON (closed) MCUVcc connected to Vcc
OFF (open) MCUVcc not connected to Vcc
JP27
ON (closed) VDD5 connected to MCUVcc
OFF (open) VDD5 not connected to MCUVcc
JP28
ON (closed) HVSS5 connected to GND
OFF (open) HVSS5 not connected to GND
Default: grey
Table 3-7: MCU Power Supply SK-91F467-FLEXRAY
3.4.2 MCU Analogue Power Supply Voltage
The power supply as well as the reference voltage for the A/D-converter can be provided
internally or externally.
JP15 Connects power supply AVcc of the A/D converter to MCUVcc
JP16 Connects high reference voltage AVRH of the A/D converter to AVcc
3.5 MCU-FlexRay CC Connection at SK-91F467-FLEXRAY
The FlexRay communication controller MB88121 provides different communication modes to
a microcontroller. The MB88121 has different pin functions in its communication modes.
Therefore it is possible to connect the CC in different ways to the MCU, to evaluate the
different communication modes.
JP1 Connects MCU INT6 or MCU A10 to CC pin 35 (INT2 / A10)
JP2 Connects MCU INT7 or MCU A9 to CC pin 36 (INT3 / A9)
JP3 Connects MCU A5 or MCU SCK6 to CC pin 40 (SCK / A5)
JP4 Connects MCU A4 or MCU SOT6 to CC pin 41 (SDI / A4)
JP5 Connects MCU A3 or MCU SIN6 to CC pin 42 (SDO / A3)
JP7 Connects MCU A0 with CC A0
JP10 Connects MCU D26 or CC SPI-mode switch S1-3 (MDS2) to CC pin 53 (AD10 /
D10 / AD2 / D2 / MDS2)
JP11 Connects MCU D25 or CC SPI-mode switch S1-2 (MDS1) to CC pin 54 (AD9 /
D9 / AD1 / D1 / MDS1)
JP12 Connects MCU D24 or CC SPI-mode switch S1-1 (MDS0) to CC pin 55 (AD8 /
D8 / AD0 / D0 / MDS0)
JP14 Connects MCU D21 or MCU INT6 to CC pin 58 (AD5 / INT2)
JP17 Connects MCU D20 or MCU INT7 to CC pin 59 (AD4 / INT3)
JP19 Connects MCU CSX3 or MCU CSX6 to CC pin 19 (CS)
JP20 Connects MCU INT6 or MCU ASX to CC pin 22 (ALE / INT2)
Note:
For more information about the FlexRay CC modes and the
different pin functions, please refer to MB88121 documentation.
Jumper Setting Description
JP1
1-2 MCU INT6 connected to CC INT2
2-3 MCU A10 connected to CC A10
JP2
1-2 MCU INT7 connected to CC INT3
2-3 MCU A9 connected to CC A9
JP3
1-2 MCU A5 connected to CC A5
2-3 MCU SCK6 connected to CC SCK
JP4
1-2 MCU A4 connected to CC A4
2-3 MCU SOT6 connected to CC SDI
JP5
1-2 MCU A3 connected to CC A3
2-3 MCU SIN6 connected to CC SDO
1-2 MCU D25 connected to CC AD1 / AD9
2-3 CC SPI-mode switch S1-2 connected to CC MDS1
JP12
1-2 MCU D24 connected to CC AD0 / AD8
2-3 CC SPI-mode switch S1-1 connected to CC MDS0
JP14
1-2 MCU D21 connected to CC AD5
2-3 MCU INT6 connected to CC INT2
JP17
1-2 MCU D20 connected to CC AD4
2-3 MCU INT7 connected to CC INT3
JP19
1-2 MCU CSX3 connected to CC CS
2-3 MCU CSX6 connected to CC CS
JP20
1-2 MCU INT6 connected to CC INT2
2-3 MCU ASX connected to CC ALE
Default: grey
Table 3-10: MCU-FlexRay CC Connection
3.6 FlexRay Physical Layer
The SK-91F467-FLEXRAY provides different FlexRay physical layer communication. The
default setting is for RS-485 physical layer communication (on board). To test the original
FlexRay physical layer transceiver, it is possible to deselect the RS-485 transceiver and plug
in FlexRay physical layer driver module from TZM (FT1080). With the TZM (FT1080)
modules the user has the possibility to evaluate transceiver chips from different vendors
quite easy.
Note:
Disconnect the RS-485 physical layer transceiver signals before
plugging in the FT1080 modules to X3 and X7.
3.6.1 Channel A
JP35 Connects FlexRay channel A RxD to RS-485 transceiver (FT1080 must not be
plugged in X3!)
JP40Connects FlexRay channel A TxEN to RS-485 transceiver (FT1080 must not be
plugged in X3!)
JP45Connects FlexRay channel A TxD to RS-485 transceiver (FT1080 must not be
plugged in X3!)
JP38Connects FlexRay channel A RS-485 transceiver output B to Sub-D-9
connector (X2)
JP41Connects FlexRay channel A RS-485 transceiver output A to Sub-D-9
connector (X2)
JP34, JP36 Connects RS-485 termination network to signal lines at FlexRay channel A
JP48 Connects FT1080 module CH-A EN to configuration switch S6
The DIP switch S6 is used to set EN, WAKE and nSTB signals of the FlexRay physical layer
driver modules from TZM (FT1080). The control signals can also be connected with jumper
to the MCU to give the possibility to set them via user software. Both modules (FT1080) will
be set simultaneously, if JP48-JP50 and JP73-JP75 are closed.
DIP switch Setting Logical value
S6/1 (EN)
ON (closed) 0 (low)
OFF (open) 1 (high)
S6/2 (WAKE)
ON (closed) 0 (low)
OFF (open) 1 (high)
S6/3 (nSTB)
ON (closed) 0 (low)
OFF (open) 1 (high)
S6/4 (Not used)
ON (closed) Not connected
OFF (open) Not connected
Default: grey
Table 3-13: FT1080 Control Settings
Dip-Switch S6
(default setting)
ON
OFF
Figure 3-5: FT1080 Control Switch
JP31 Connects nSTB signal of FT1080 modules to MCU port 18_6
JP32 Connects WAKE signal of FT1080 modules to MCU port 18_5
JP33 Connects EN signal of FT1080 modules to MCU port 18_4
Three high-speed CAN-transceivers (PCA82C250) are on-board to connect all available onchip CAN to 9-pin D-Sub connectors (X9, X10 and X11).
JP82 Connects MCU RX0 to CAN transceiver U15
JP83 Connects MCU TX0 to CAN transceiver U15
JP87 Connects MCU RX1 to CAN transceiver U18
JP88 Connects MCU TX1 to CAN transceiver U18
JP89 Connects MCU RX2 to CAN transceiver U19
JP90 Connects MCU TX2 to CAN transceiver U19
Jumper Setting Description
JP82
JP83
JP87
JP88
JP89
JP90
Default: grey
ON (closed) CAN0 RxD connected to MCU
OFF (open) No connection to the microcontroller
ON (closed) CAN0 TxD connected to MCU
OFF (open) No connection to the microcontroller
ON (closed) CAN1 RxD connected to MCU
OFF (open) No connection to the microcontroller
ON (closed) CAN1 TxD connected to MCU
OFF (open) No connection to the microcontroller
ON (closed) CAN2 RxD connected to MCU
OFF (open) No connection to the microcontroller
ON (closed) CAN2 TxD connected to MCU
OFF (open) No connection to the microcontroller
Table 3-15: CAN-MCU connection
3.8 LIN / RS-232 UART
There are three UART connectors X1, X4 and X8 (9-pin D-Sub) on-board, which can be
used for RS-232 or LIN communication (to get information in detail about pin usage, please
refer to chapter 4.2 UART / LIN Connector (X1, X4, X8)). The LIN transceiver needs to be
configured as LIN-master or LIN-slave.
3.9 User Push Buttons INT0, INT1, INT2 and ICU0/TIN0
There are four user push buttons on the starter kit, which can be connected to the
microcontroller.
JP92 – JP95 Connects the user push buttons (SW2 – SW5) to the microcontroller
Jumper Setting Description
JP92 (SW2)
JP93 (SW3)
JP94 (SW4)
JP95 (SW5)
Default: grey
ON (closed) Button INT0 is connected to the microcontroller
OFF (open) No connection to the microcontroller
ON (closed) Button INT1 is connected to the microcontroller
OFF (open) No connection to the microcontroller
ON (closed) Button INT2 is connected to the microcontroller
OFF (open) No connection to the microcontroller
ON (closed) Button ICU0/TIN0 is connected to the microcontroller
OFF (open) No connection to the microcontroller
Table 3-19: User Push Buttons
3.10 User DIP Switch 8 Bit (S4)
There is an 8 bit user-DIP-switch on-board, which can be connected to one MCU port (P26),
Connecting High- or Low level to the pins. S3, also an 8 bit DIP-switch, dis-/connect the
eight channels of S4 to the MCU pins. In case of other usage of these pins, open S3 switch
accordingly.
DIP switch Setting Logical value
S4/1 - 8
Default: grey
Table 3-20: S4 Values
DIP switch Setting Description
S3/1 - 8
Default: grey
ON (closed) 0 (low)
OFF (open) 1 (high)
Note:
DIP-switch S3 is used to connect DIP-switch S4 to the MCU port
pins at port P26.
A system reset can be generated in different ways. The first possibility is to press the user
reset push button (SW1). Secondly the supply monitor will generate a reset if an unusual
voltage is detected and third a reset is raised if a UART that does a reset is selected.
If a system reset is done, it will be displayed by the red reset LED (D18).
The system reset will do a simultaneous reset of the microcontroller and the FlexRay
communication controller. The MCU and / or the FlexRay CC can be disconnected from the
system reset signal with two jumpers.
The Reset push button can be used in two modes:
•no delay of Reset
•press Reset button 2s
The selection is done by solder Jumper JP96.
JP52 Connects the FlexRay CC to the system reset signal (SK91F467-FLEXRAY)
JP54 Connects the MCU to the system reset signal
Jumper Setting Description
JP52
ON (closed) Reset is connected to FlexRay CC RST
OFF (open) No connection to the FlexRay CC
JP54
ON (closed) Reset is connected to MCU INITX
OFF (open) No connection to the MCU
JP96
1-2 Reset is generated when SW1 is pressed
2-3 Reset is generated after SW1 is pressed 2s
Default: grey
Table 3-22: Reset Connections
The triple supply monitor on-board has the possibility to watch 5V, 3.3V and the third voltage
is user configurable 2.5V or 1.8V. If any voltage has a failure, a system reset will be done.
JP42 Monitoring of 1.8V supply voltage
JP43 Monitoring of 2.5V supply voltage
Jumper Setting Description
JP42
ON (closed) Vcc1V8 connected to supply monitor
OFF (open) Vcc1V8 not connected to supply monitor
JP43
ON (closed) Vcc2V5 connected to supply monitor
OFF (open) Vcc2V5 not connected to supply monitor
Default: grey
Table 3-23: Supply Monitor Settings
By default 2.5V supply will be monitored.
The system reset also can be done via any UART. Therefore the user has the possibility to
select one of the three on-board UARTs.
The following figure shows the power connection jack of the starter kit. This connector is
used to connect an external unregulated DC power supply voltage (9V-12V DC
recommended 2000mA).
Shield is connected to positive voltage supply (+)
Centre is connected to ground (GND)
Table
Figure 4-1: Power Connector
4.2 UART / LIN Connector (X1, X4, X8)
Three 9-pin D-Sub female connectors are used for the serial interfaces LIN/UART2,
LIN/UART4 and LIN/UART5.
Take care, that the RS232 as well as the LIN signals are shared at the connectors and have
to be selected by jumpers (see chapter 3.8).
Figure 4-2: UART Connector
Pin Number Pin Signal Description
1+VBat Power from LIN bus
2
TXD RS-232 transmit output
LIN Bi-directional LIN-interface
3RXD RS-232 receive input
4DTR Connected to DSR (pin 6)
5GND Ground normally used for RS232 connection
6DSR Connected to DTR (pin 4)
7RTS Can be connected with CTS by jumper
8CTS Can be connected with RTS by jumper
9LGND Ground normally used for LIN connection
Three 9-pin D-Sub male connectors are used for the CAN interfaces CAN0, CAN1 and
CAN2.
Figure 4-3: CAN Connector
Pin Number Pin Signal Description
1NC Not used
2CANL LOW-level CAN voltage input/output
3GND Ground
4NC Not used
5NC Not used
6NC Not used
7CANH HIGH-level CAN voltage input/output
8NC Not used
9NC Not used
Shield GND Ground
Table 4-2: CAN Connector Signals
4.4 FlexRay Connector (X2, X6)
Two 9-pin D-Sub male connectors are used for the two FlexRay channels A and B. As
default RS-485 is used at SK-91F467-FLEXRAY.
Figure 4-4: FlexRay Connector
Pin Number Pin Signal Description
1NC Not used
2BM Bus line Minus
3GND Ground
4NC Not used
5User Connected to optional pin head (CH-A: J9; CH-B: J14)
6NC Not used
7BP Bus line Plus
8NC Not used
9NC Not used
Shield Shield Connected to shield of FT1080 modules
To use the FlexRay physical layer driver module from TZM (FT1080) there are two special
connectors on board of SK-91F467-FLEXRAY, both for FlexRay channels A and B, to insert
the modules. If the modules FT1080 should be used, it is necessary to disable the RS-485
driver modules (see chapter 3.6).
Figure 4-5: FlexRay Physical Layer Connector
Pin Number Pin Signal Description
1SGND Signal Ground
2Shield FlexRay bus shield (filtered)
3NC Not used
4BM Bus line Minus
5NC Not used
6BP Bus line Plus
7EN Mode control input
8NC Not used
9WAKE Local wakeup
10 NC Not used
11 nSTB Mode control input
12 NC Not used
13 BGE Bus guardian enable
14 NC Not used
15 No Pin Coded
16 No Pin Coded
17 TxD Transmission data input
18 Ubuffer Transmitter supply voltage buffering
19 TxEN Transmission data enable
20 GND Ground
21 RxD Receive data output
22 VIO I/O supply voltage
4.6 USER-LEDs and optional LC-Display (D1-D16, J6)
There are sixteen user LEDs on-board, D1-D8 connected to MCU port P25 and D9-D16
connected to MCU port P16. To disconnect the LEDs from the MCU, it is possible to remove
RN3 (D1-D8 at port P25) and RN2 (D9-D16 at port P16).
It is also possible to connect a standard LCD module with backlight to connector J6. With the
potentiometer RP1 the contrast of the LCD can be adjusted.
Pin 14 13 12 11 10 9 8 7 6 5 4 3 2 1 16 15
LCD
LED
Port
MCU
DB7 DB6 DB5 DB4 - - - - E R/W RS VO Vcc GND LED- LED+
There is a Flash-programming socket on the starter kit which makes it possible to program
the Flash MCU with a special programming adapter. Mode pins and reset signal is also
available at this connector.
Figure 4-7: In Circuit Programming Connector
Pin Number Pin Signal Description
1NC Not used
2NC Not used
3MD0 MCU mode-pin 0
4MD2 MCU mode-pin 2
5INITX MCU reset signal
6SIN4 UART4 receive data
7SOT4 UART4 transmit data
8SCK4 UART4 clock
9VCC Board supply voltage
10 GND Ground
Table 4-6: In-Circuit Programming Connector
4.8 MCU Pin Connectors (J1-J4)
All MCU pins are directly connected to the four pin header around the MCU. The last two
pins of the pin header J1, J2, J3 and J4 are unused (see PCB overprint).
Connector MCU Pins
J1 1-52
J2 53-104
J3 105-156
J4 157-208
Table 4-7: MCU Pin Connectors
On the PCB, the corresponding pin numbers of the MCU are written next to the connector
pins.
Make sure Softune Workbench for FR is installed on your PC and the “SK-91F467FLEXRAY” or “SK-91F467D-208PFV” is ready to use (power-on (X5), serial connection
(UART4) to COM port of the PC). Refer to Chapter 2 Installation for details on the hardware
and software installation.
5.1 Introduction to Softune Workbench
Start Softune Workbench. Select <File> <Open Workspace> to load the first example “SK91F467-FLEXRAY_test.wsp”. All examples can be found in the folder \software\examples on
the starter kit CD-ROM. It is recommended to copy this folder to the local hard-drive. In the
project tree on the left side, you can open the “source”-folder which contains the source-files
registered to this project. A double-click on one of the files will invoke the built-in editor,
which supports syntax-highlighting, tags and various other functions.
Figure 5-1: Softune Workbench main window
Note:
You may customize the editor by a right-click on the editor
window.
Whenever you modify the source-files, you have to re-compile and link the related files to
produce a valid load module (ABS-file). This is done using the MAKE-function. MAKE
invokes the assembler, C-compiler and linker for FR whenever necessary (only modified files
will be re-compiled).
If you wish to re-compile the entire project regardless of any changes, you can use the
BUILD-function. To check for syntax-errors on a specific source-file, use the
COMPILE/ASSEMBLE function.
These three functions are available on the button-bar or from the main menu (Project –
Compile / Make / Build / Abort).
Click on MAKE or BUILD. Messages from the individual language tools will be fed into the
output window at the bottom of the main screen. If the tool chain (C-compiler X Assembler X Linker) was completed successfully, the message “No Error” will appear.
If you get any errors during compilation, an appropriate message will be generated. Try this
with a simple syntax-error (e.g. delete a semicolon “;” from the end of a C-line) and click on
MAKE again. You will now see a message like this:
To locate the position in the source-file, where the error has occurred, double-click on the
message. The editor will open the appropriate source-file, indicating the error highlighted in
red, depending on the customise settings of the editor. Correct the error and re-compile the
project as explained above.
If more errors occurred, you can go through the error list step by step using the menu “Edit –
Top/Previous/Next/Bottom Error” or using the appropriate buttons which have the same
functions:
Note:
To get on-line help about a specific error, select the error
message and press F1. In many cases, you can get some useful
hints how to solve the problem. Of course, you can also use the
HELP-menu anytime during development or debugging.
In any case the settings done in the template must be checked and have to be
Getting Started
5.2 Project Start-up
In order to allow a quick and smooth project start-up Fujitsu Microelectronics Europe
supplies a template project as a reference. The easiest way to start a new project is to make
a copy of the template project and use this copy as a start-up. The template includes the
latest start91460.asm file, MCU header file, IRQ table, basic linker and C-Compiler settings.
Note:
adjusted to the specific needs and settings of the final application. The template is
providing an example for building up a new project.
THIS SAMPLE CODE IS PROVIDED AS IS AND IS SUBJECT TO ALTERATIONS. FUJITSU
MICROELECTRONICS ACCEPTS NO RESPONSIBILITY OR LIABILITY FOR ANY ERRORS
OR/ELIGIBILITY FOR ANY PURPOSES. (C) Fujitsu Microelectronics Europe GmbH
5.2.1 Create a New Project:
1. In order to start a new user-project use the “91460_template_91467d” project
2. Copy the folder 91460_template_91467d and rename the folder to e.g.
my_application
3. Enter the folder “my_application”
Rename “91460_template_91467d.prj” into “my_application.prj”
Rename “91460_template_91467d” into “my_application.wsp”
With this selection the project is linked to be used with the Softune Workbench monitor
debugger. Corresponding linker settings are done for the memory map in order to avoid
overwriting of the sections which are used by the monitor debugger. The code is linked in
this configuration for external SRAM, otherwise it is not possible to debug code with the
Softune Workbench monitor debugger. The monitor
7. Check MCU settings in the module start91460.asm. Be careful regarding any
modifications. If the peripheral clock speed is modified it can happen that the
communication between Softune Workbench and monitor debugger is lost. In the
module start91460.asm some basic MCU settings are done and some initial data
copy transfers are performed for specific data sections e.g. INIT. Check module
vectors.c if any interrupts are used for proper vector table set-up.
Note:
Always check the memory map of the linker settings and ensure
that this memory map is suitable for the application and target
system in use. Additionally the .mp1 file should be checked to
ensure correct settings.
8. Write application code in the module main.c or add any other module to the project.
9. Write and modify source code and settings corresponding to the needs of the
application. Finally use “Make”, or “Build” to compile and link the project. The
generated output files can be found in the sub-folder MONDEB_INTERNAL of the
project folder. The *.mhx file (Motorola S-Record) is located in the ABS sub-folder.
Note:
Always check the memory map of the linker settings and ensure
that this memory map is suitable for the application and target
system in use. Additionally the *.mp1 file should be checked to
ensure correct settings..
Figure 5-4: Open Softune Workbench Linker mapping file
Check linker mapping list in the*.mp1 file by right-click on “my_application.abs”,
Open List File, *.mp1.
10. After the project is built and debugged successfully switch to the active configuration
STANDALONE
5.2.3 Use Active configuration STANDALONE
11. With this selection the project is linked to work in internal flash memory. This
configuration will not work with the Softune Workbench monitor debugger. In this
configuration the code is linked to work in internal Flash memory, only.
12. Use “Make”, or “Build” to compile and link the project for internal Flash memory. The
generated output files can be found in the sub-folder STANDALONE of the project
folder. The *.mhx file (Motorola S-Record) is located in the ABS sub-folder.
Note:
Always check the memory map of the linker settings and ensure
that this memory map is suitable for the application and target
system in use. Additionally the *.mp1 file should be checked to
ensure correct settings.
13. Program the generated *.mhx file (Motorola S-Record) with the Flash programming
utility into the internal Flash. See Chapter 6.1 “Programming the internal Flash
Memory” for more details.
Note:
It is not possible to use the Softune Workbench monitor debugger
with this configuration because no code can be debugged which is
located in internal Flash. Also this configuration does not support
special debugger settings, which are disabled for this
onfiguration.
c
5.3 Softune Workbench Monitor Debugger
5.3.1 General Description
Whenever you have created a valid load module successfully, you can switch from the
development mode to the debugging mode of Softune Workbench.
Basically, there are 3 types of debugging systems supported :
1. The software simulator: This type of debugger is always present and does not
require any special hardware extensions. The simulator will cover the FR-core
features, but no peripheral functions. Therefore, you can use the simulator to
verify program flow, check for dynamic errors, look at the generated assembler
code , etc. .
2. The monitor debugger: This debugger type requires an evaluation board like the
“SK-91F467-FLEXRAY” connected to one of the COM-ports of your PC.
Therefore, make sure the evaluation board connected and powered-up as
described before. Explanations in this manual refer to the monitor debugger only.
3. The emulator debugger: The in-circuit-emulator (ICE) is a system, which allows a
connection to any target system using a probe-cable. The appropriate system for
the MB91F467DA series is the MB2198-01 system. More information about this
system can be found on Fujitsu's website.
Which debugger is used for the actual project can be configured in the project tree as shown
below or in the “Project – Setup Project – Debug” menu. The current selection is blue
marked (icon):
The default settings for the monitor debugger are: COM-Port 1, 57K6 baud, 8N1. If you wish
to change the COM-port, please right-click on the “Mondeb_57K6_com1.sup” entry and
select change.
Note:
If you change the baud rate or use a different crystal frequency,
you have to change the UART-settings in the debugging kernel
source project, re-compile and flash the new kernel to your “SK91F467-xxx” board first. The project can be found in
Software\SWBMonitorDebugger. All settings are done in the
module u_io.asm.
If these settings are correct, start your debugging session:
Make sure you have connected the “SK-91F467-xxx” starter kit and your monitor-kernel is
stored in the internal flash memory of the MB91F467DA series at the starter kit. Then power
up and reset the starter kit. Check the following configurations:
1) Correct CPU Mode selection (DIP-Switch S5)
After Power on the Monitor debugger indicates via the 8 user-LEDs the current
status. The following status indications exist. Ensure that the CPU is working in
normal RUN Mode (DIP-Switch S5 position all OFF)
DIP switch S5, default all OFF
Figure 5-7: MB91F467D and mode pin DIP switch
2) Correct start-up of the monitor debugger
Figure 5-8: Reset button and user LED
In case of any other status indication push the reset button or check chapter 6.6.1 for
detailed information.
Start the debugger by double clicking the “Mondeb_57K6_com1.sup” entry in the
project/debug tree - or by using “Debug – Start Debug” from the menu. You should see a
progress bar indicating the download process.
If no process is indicated an error message will occur (“e.g. Invalid communication status”).
Double-check the settings again as explained above. Also make sure the evaluation-board is
powered on, ready to use and the RS232-cable is connected properly. Also see the troubleshooting section in the appendix.
After starting the debugger, the source window will be opened which contains locate-arrows
for each (possible) source-line, the original source-code,
Figure 5-9: SWB debugging window
Breakpoint-indicators and the assembler code (in “mixed view”). The current program
position will be indicated by a yellow line. Use right-click in the source window to configure
the view (add/remove control characters, View Mixed source code, Breakpoint …)
Note:
You can choose “mixed view” from the context menu (right-click)
to display source and assembly code at the same time. The
command “go to current” will take you to the active code line!
GO: Executes the program continuously from the memory location pointed to by the
current program counter (PC) until a termination factor occurs.
STEP IN: Executes the program stepwise according to the listing in the source
window (steps in C- or ASM). Note that interrupts are disabled during step execution !
STEP OVER: Executes the program stepwise except call-instructions (which will be
executed until return). Interrupts are not disabled during a continuous CALL...RETURN
execution.
STEP OUT: Executes the program continuously to the parent function (until
RETURN). Interrupts are enabled. Note, that debug information is required for this function.
EXECUTE UNTIL CURSOR: Automatically sets a breakpoint at the actual cursor
position and executes continuously until this breakpoint, which will be deleted
afterwards.
Each valid code line in a debugger window automatically has a locator (blue arrow) and a
breakpoint-option (circle). Note that some C-lines may not be displayed with locators and
breakpoints, because the compiler has created “optimized” assembler-code. Select “mixed
view” in order to check the compiler output.
Instead of single-steps, you may also use the arrows to directly execute your program until a
certain line of your source-code :
BORT: Forcibly terminates execution. This button is not fully supported by the
A
monitor debugger and may cause malfunction if used to abort “continuous
operation” of the MCU.
This command button can only be used to abort single code line operations
Example: for(k=DELAY_CONSTANT; k>0; k--);
Use the button INT0 on the “SK-91F467-xxx” for ABORT function.
To ABORT continuous execution on the “SK-91F467-xxx” starter kit, you have to
use the INT0 button on the “SK-91F467-xxx” starter kit.
5.4 Advanced Monitor Debugger Features
TOGGLE BREAKPOINT: Sets or deletes breakpoint at the current source line:
To set or delete a breakpoint, click the circles at the beginning of a source-line.
Aindicates an active breakpoint. Hit “Run continuously” to execute code until
reaching this line. A list of all breakpoints can be found under the “Debug – Breakpoint”
menu. 255 Software-Breakpoints (using TRAP replacement) are possible.
Note:
To set breakpoints at positions which are currently not visible (e.g.
because the source window of that module is not open), you can
also enter a symbolic label directly in the “Breakpoint” menu.
Example: Enter “main” in the address-field and confirm. The new
breakpoint will automatically be assigned to the address of the
“main()”-function.
REGISTER WINDOW: Displays the CPU-register window. Updated registers appear
in red. Setup in context menu defines which Registers should be displayed.
WATCH WINDOW: Displays the current variables to „watch“. Double-click on any
variable in your code then specify watch in context menu to add to watch window. All listed
variables in a watch window can be displayed in any number format. Use Edit to directly
change the contents.
MEMORY WINDOW: Displays memory areas in various formats defined by Setup
(context menu). Changing of address/data is possible when debugger is not executing.
The memory window can be very helpful to check the registers or the frame memory of the
connected graphic controller !
DISASSEMBLER: Disassembles the content of the code memory beginning from
actual PC position and displays the result in a separate window. Individual
assembler-lines can be changed using the „inline assemble“-function.
DEBUG - STACK: Displays the current stack contents in terms of function calls.
Parameters, if any, are displayed in brackets.
DEBUG - VECTOR: Reads out and displays the actual interrupt-vector table. Use the „jump“
function to display any code areas pointed to by an interrupt vector (e.g. interrupt service
routines used in your program).
DEBUG - CALL: This function can be used to „call“ any routine defined in your code when
the debugger is on hold.
DEBUG – LOAD TARGET FILE: Starts a new download of the current load module (ABS
file). Usually this function will be executed automatically after starting the debugger (defined
in debug settings ; see „Project-Setup-Debug“). However, this function can be useful to reinitialize the debugger for the current debug session.
VIEW - SYMBOL: This function displays all (global) symbols of the current project.
Information about the type (char, integer etc.) and the location (address in RAM or register)
can be shown using „detail“.
VIEW - LOCAL: Similar to View-Symbol, but only local variables of the current function are
shown.
VIEW - COMMAND: From this window, the debugger can be controlled using a command
line input. All GUI functions are available as individual commands.
Example:
Run continuously
Step
Examine PDRG
Set break main
Dump/Halfword 0x2000000..0x20000FF
Shortcuts to complex commands can be defined (“alias”) and parameter strings can be
substituted by variables.
A set of commands can be combined to a “macro”. Aliases and macros can be defined
using the command window context menu.
Example: restart: set register PC=2000000
set break main
Run continuously
In order to document or save debugging details such as memory contents, all outputs fed to
the command console can be written to a file (“logging”).
A whole “program” of commands (incl. flow control) can be written to a PRC-file and
executed. Procedure-files are simple text-files with the extension “.PRC” and can be created
by the Softune Workbench editor or any other text editor. To execute a procedure-file, use
the command window menu or the “file-open” menu during debugging.
Note:
Procedure-files can be very helpful to configure the debugenvironment automatically, perform automated tests (e.g. when a
new C-module has to be tested) or to enhance basic emulator
functions such as breakpoints. Using a procedure file, breakpoints
can be defined dynamically depending on program conditions.
See the “Command Reference Manual” (on-line help) for detailed
information about the available command and parameter syntax.
Some procedure files exist already included in the example project
directory.
Valid load module files can only be achieved if the language tool configuration is appropriate.
The most convenient way to create owns a project is to copy the provided Template-Projects
from the example-directory and use it as “blank sheet”.
If the Softune Monitor debugger is being used the following memory areas are reserved by
the monitor debugger and must not be used by the application.
Memory Map of Softune Workbench Monitor debugger
91460_mondeb_uart4-v11
Memory Type Used for Area(s) Sections
Internal CPU Data
RAM
Internal Flash
Memory of
Stack, Data 0x28000 - 0x28FFF
0x000F:0000-
Debug Kernel
0x000F:FFFF
STACK, DATA
CODE, CONST
MB91F467DA series
Vector Table
0x0F:FC000x0F:FFFF
INTVECT
Note:
Be aware that the memory map may depend on the debugger version and any
modifications of the debugger made by the user.
Table 5-1: Memory map of Monitor debugger 91460_mondeb_uart4-v11
Note:
The following chip select areas are used by the Softune monitor
debugger and must not be used or overlap with other chip select
areas:
Always check the Linker Settings (“Project – Setup Project – Linker – Disposition”) to make
sure the following memory map is applied according to the project configuration:
Recommended linker settings for “SK-91F467-xxx” starter kits for debugging
Memory Type Used for Area(s) Sections
Data RAM, Variables, Stack 0x029000 -
DATA, INIT, STACK
0x02FFFF
External SRAM 1MB Code, Const,
IRQ Vector
0x00840000 0x0094FFFF
CODE, CONST
Table
Table 5-2: Linker Settings for MB91F467DA Monitor Debugger configuration
Note:
In any case all settings must be checked and corrected
corresponding to specific application requirements. Also check
settings in the start91467.asm initialisation file! Use the linker
mapping list (e.g. *.mp1 file) to check the final memory allocation.
The following chip select areas are used by the Softune monitor
debugger and must not be used or overlap with other chip select
areas:
•Use the correct linker settings as outlined above depending on your target
MCU and the target area (embedded flash or external RAM).
•Use the provided templates to make sure the sections are located correctly.
•Always check the *.mp1 file (use right mouse click on top *.abs file in the
project window of Softune Workbench and select “open list file”) to see the
used sections and address areas!
•The following Chip select areas are used by the Softune monitor debugger and
must not be used or overlap with other chip select areas:
CS1 – SRAM 0x0080.0000 - 0x009F.FFFF
Note:
Be aware that the Softune Workbench monitor debugger is only
able to debug code which is located in RAM! It is not possible to
debug code located in Flash memory!
As shown in the message window the Security address is not programmed in
Automatic programming process. This is done for security reason to avoid the
activation of the Security function by accident.
8) After successful programming assert Reset or Power-off / On the board in order to
start the programmed application.
Note 1:
The MB91F467DA series is checking the serial UART4 interface
for valid string to enter Flash programming mode. For details
about boot sequence refer to Hardware Manual of MB91460
series.
Note 2:
Be aware of Security Features of MB91F467DA series. Check
Documentation of MB91460 series for detailed information!
Starter kit does not power-on correctly.
Some or all of the power LEDs (D24, D30,
D34, and D40) do not lit up.
Starter kit stays in reset.
LED D18 (Reset indicator) lights up
permanently.
The communication from Softune
Workbench to the evaluation board fails
(Communication errors)
The windows of the debugger are empty. * This is due to wrong (maybe old) file path
When trying to program the application to
the embedded flash, the programmer
stops at first address with “loading error” !
Hardware units such as LEDs, user
buttons, UART are not working.
LCD at parallel LCD port does not work
Graphic sub-board does not work Check power supply 9-12V/1500mA. Reduce
Check voltage supply and jumpers :
The voltage on DC-Power plug should be in the
range of 9-12V. The plug should have + on shield
and – on the centre. The power supply should be
able to supply at least 500mA. To support both, the
“SK-91F467D-208PFV” and a graphic sub-board
the supply should be able to supply 1500mA.
* The LEDs should light up after switching on the
board. Use a multimeter to see whether 5V,3.3V,
2.5V and 1.8V are present on the Vcc/GND test
measurement points J21, J22, J23 and J24.
Check jumper positions according to chapter 2.1
Remove all user extensions of the starter kit
LED D18 (Reset) should flash. If D18 lights up
permanently, the voltage is too low - Increase the
voltage supply and check available supply current
to solve the problem.
Remove all user extensions on the board to avoid
any shortcuts or leakage current!
Make sure your COM-port number and the baud
rate settings are correct (see debugger
introduction). The default COM-port is 1 and the
default baud rate is 57K6Baud.
Make sure no other programs are using the same
COM-port on your PC. Close all other applications
(e.g. Flash programmer utilities, terminals etc.)
* Check if RTS/CTS is closed on the CPU module
(check jumper JP58, 60, 65 are closed).
* Use only a RS232 extension 1:1 cable
information. Closing all windows in the debugger
and re-open should fix the problem.
* You are probably trying to program a program to
the flash which is linked for the external RAM area.
Check for details the linker memory map and the
linker output mapping file *.mp1 file.
Make sure you have enabled these units on the
evaluation board using the appropriate jumpers.
See the provided examples and the hardware
manual for information on how to control the
peripherals.
Adjust the potentiometer RP1 to adjust contrast
of LCD. Remove resistor network RN3