To the maximum extent permitted by applicable law, Fujitsu Microelectronics Europe GmbH restricts
its warranties and its liability for CREMSON MODULAR STARTERKIT 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,
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, the CREMSON MODULAR STARTERKIT 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 Fujitsu Cremson Modular Starterkit is a stand-alone application board that makes it easy
to evaluate and demonstrate almost all features of a particular graphic system (MCU +
Graphic Controller). The board is a combination of a CPU-main board and a graphic
subboard.
Fujitsu has a number of graphic controllers for embedded systems organized in different
device families. All graphic controllers from one particular family are software-compatible.
Therefore, this evaluation system has different software packages, manuals etc. depending
on the device family. To control the graphic device, Fujitsu offers 2 CPU modules with 32-bit
MCUs MB91F362 and MB91F369. The MB91F369 CPU board has a debugging option to
allow high-level source code debugging.
The board can be programmed and used as a stand-alone evaluation unit. When using the
system with the MB91F369 CPU-board, a full-features monitor debugger is available in
addition to allow high-level debugging using Softune Workbench.
All peripheral functions are available on external pin-headers in order to design and test user
applications cost- and time-effectively. For some resource functions, additional hardware is
already present on the board (e.g. CAN- and UART-transceivers, LEDs, Buttons, etc).
The included Windows-based Software “Softune Workbench” is an integrated front-end for
development and debugging. It allows fast development of “ANSI C”-based applications for
the evaluationboard. To get started quickly, a number of example projects and templates are
available.
Related documents such as hardware manuals, software API descriptions etc. are available
and should always be used in addition to this manual (see appendix).
Be sure to have the latest information available – check our websites for updates and last
minute informations :
Insert the provided CD-ROM, browse to the installation page for the “Modular Starterkit” and
select the Installation option for Softune Workbench. Follow the instructions in the
“Installation Guide” to unpack and install Softune Workbench for FR, as well as some
example projects and additional tools. It is recommended to use the default installation path
C:\Softune. Please use the available registration form to receive the installation password.
After the installation, you will find all language tools, the IDE and other system files within the
directory Softune\Bin. Samples for the Starterkit can be found in the Softune\sample
directory. The tools directory contains additional software tools (flashloader etc.).
Execute “FR Family Softune Workbench” from your Start-Menu.
If any errors occur during installation, remove any previous versions of Softune Workbench
from your PC and retry. Make sure you have enough disk space available and you have a
supported Windows OS installed. For more information see the provided installation
information and last-minute information.
Refer to the getting started session (next chapter) for more details on how to use Softune
Workbench for developing and debugging.
2.3 Download the debugging kernel (CPU-board F369 only)
You have to make sure that the debugging kernel is loaded to the internal flash ROM of the
MB91F369 MCU before you can use the monitor debugging features of the MB91F369 CPU
module. To do so, please follow these steps :
1. Locate the monitor debugger project in your sample-directory “MonDebADA91369”. In this
project you will find the load module “mondeb\Debug\ABS\MonDeb-ADA-91369.mhx” which
you have to program to the embedded flash. If this load module should not be present, you
have to open this workspace in Softune Workbench and re-build the project to have the mhxfile available for download.
2. To download the debugger kernel, open the provided MB91360 flash programmer
(contained in your tools-directory).
3. Select device type “MB91F365,6,7,8,9Gx”
4. Use browse to specify the above mhx file in the “file to program” field.
5. Select your COM-port (default is COM1) and any desired baudrate (default is 38400).
6. Make sure the CPU-module is switched off or in permanent reset. Now click on Automatic
Mode and immediately switch on the starterkit (or release the reset) to start the flash
programming. The flash programming sequence will be executed automatically.
CAUTION : DO NOT INTERRUPT THE FLASH PROGRAMMING OR CUT OFF THE
POWER DURING PROGRAMMING !
7. Wait until the programming sequence is finished. Reset the CPU-module after having
programmed the kernel successfully. Now your board is ready to be used with the Softune
workbench monitor debugger.
See the flashprogramming chapter for more details on how to program the embedded flash
of the MB91F369 MCU.
Make sure you have Softune Workbench for FR and the additional tools (e.g. the
flashprogrammer) installed on your PC and the evaluation board is ready to use. Refer to
Chapter 2 for details on the hardware and software installation.
3.1 Using the MB91F362 CPU-module
If you have a system with the MB91F362 CPU module, you can not use the monitor
debugger. Instead, you have to program the application to the embedded flash. Therefore,
the provided examples are already linked for the embedded flash area of the MB91F362
(08:0000…0F:FFFF).
Creating applications for this board configuration could look like this :
1. Modify an existing project for the F362 CPU board and the GDC subboard
2. Compile&Link (Build) the project to create a valid loadmodule for the embedded flash
3. Use the MB91360 flash programmer tool to program the embedded flash
4. Test the application in stand-alone mode and continue at step 1.
3.2 Using the MB91F369 CPU-module
If you have a system with the MB91F369 CPU module, you are able to use the monitor
debugger of Softune workbench. Hence, the examples are linked for the additional
debugging RAM of the F369 CPU-module (80:0000…8F:FFFF). Your application will be
downloaded to the debugging RAM automatically by starting the debugger.
Alternatively, you can also program the application to the embedded flash of the MB91F369
to create a stand-alone application which starts immediately after a reset. To do so, you
have to re-link the application to the internal flash area (08:0000..0F:FFFF).
Creating applications for this board configuration could look like this :
1. Modify an existing project for the F369 CPU board and the GDC subboard
2. Compile&Link (Build) the project to create a valid loadmodule for the ext. RAM
3. Start the debugger to download the application to the ext RAM
4. Test and debug the application in the debugger
5. Return to the development area of Softune Workbench to make changes
6. Continue at step 2 until your project has reached a stable stage
7. Change the linker settings for internal flash (see Appendix)
5. Use the MB91360 flash programmer tool to program the embedded flash
6. Test the application stand-alone
7. Change the linker-settings and continue at step 1. if necessary
L Make sure to not overwrite the “security vector” (0x0FFEF4) – see hardware manual
L Use the provided templates to make sure the sections are located correctly