Trouble Shooting - Fujitsu CREMSON MODULAR STARTERKIT User Manual

7.7 Trouble Shooting

Problem
Evaluationboard does not power-on
correctly. Some or all of the power
LEDs (D4,D7,D10,D13, D16) on the
CPU module do not light up.
Evaluationboard stays in reset.
LED D25 (Reset indicator) ligths up
permanently.
The communication from Softune
Workbench to the evaluation board
fails (Communication errors)
The program stops at the label
„uninitialized interrupt !"
The abort switch (USER0) does not
work correctly.
© Fujitsu Microelectronics Europe GmbH
Cremson Modular Starterkit
Chapter 7 . Appendix
Solution
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 center. The power supply
should be able to supply 1200mA to support
both, the CPU-module and the graphic
subboard.
* The LEDs should light up after switching on
the board. Use a multimeter to see whether
5V,3.3V and 2.5V are present on the Vcc/Gnd
terminals (JP2,3,4,5,6).
∗ Check jumper positions according to table 1
(Esp. : JP11 – JP15) !
∗ Remove all user extensions on the CPU
module and on the subboard
∗ LED D25 (Reset) should flash. If D25 lights
up permantantly, the voltage is too low (below
4.25V) - Increase the voltage to solve the
problem.
∗ Remove all user extensions on the board to
avoid shorts or leakage currents !
∗ Make sure your COM-port number and the
baudrate settings are correct (see debugger
introduction). The default COM-port is 1 and
the default baudrate is 57600Baud.
∗ 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 if pin 7-8 are connected).
* Use only an RS232 extension 1:1 cable
∗ Before downloading a new project to the
evaluation board, re-initialize your CPU-board
using the reset button. This will erase all valid
interrupt definitions from previous programs
executed on the starterkit.
* make sure you are using a debugging kernel
which is configured for using the USER0-
button as abort switch. See the description of
the monitor debugger project for more details
how to configure the kernel software.
* make sure not to mask the interrupts
- 35 -