34
34
34
34
•
run the following command:
flashtool -cfg Config\FlashTool\FujitsuDevKit16\PEdebugKernel_IR.ftc
for the internal RAM variant or
flashtool -cfg Config\FlashTool\FujitsuDevKit16\PEdebugKernel_ER.ftc
for the external RAM variant.
Note
: From the Flashtool 1.1 (or higher) version, you can use the
PEDBG_IR.BAT batch file to burn the debug kernel with internal RAM
variables and PEDBG_ER.BAT file to burn the external RAM version.
These batch files are in the installation directory of the PE. You can also
download the latest FLASHTOOL.ZIP package from the PE web site,
which includes also these batch files.
H O W T O B U R N T H E C P U F L A S H W I T H O U T D E V K I T 1 6
The Flashtool also allows burning the CPU internal FLASH without the need for
using the Devkit16 Mainboard. This is important in the moment when you have
an application board of your own and you want to verify if the application you
have written is working well on your board.
The application board must have a serial RS-232 interface connected to the CPU
UART interface dedicated to the communication in the serial asynchronous
mode. Refer to the following table to find out, which CPU uses which UART
for this purpose:
CPU type
UART used
MB90F497
UART1
MB90F543
UART1
MB90F549
UART1
MB90F553
UART0
MB90F562
UART1
MB90F574
UART0
MB90F583
UART0
MB90F591
UART0
MB90F594
UART0
MB90F598
UART1
Note: In the Flashtool 1.2, only the F543 and F497 CPUs are supported
The user application board also must have a mode logic, which would allow to
set the state of MD0–2 and P00, P01 CPU pins.
For burning the CPU internal FLASH, you should do the following steps:
•
connect your application board RS-232 serial interface to the PC
•
set the asynchronous serial programming mode (MD0–2 = „011“ and
P00–01 = „00“)