Filter
Top Products
145
CHAPTER2 Dependence Functions
■ Memory access during logging
During program execution, the emulator debugger (MB2198) reads/writes memory after causing MCU
break once to access, and then reexecuting the program. Therefore, when the emulator debugger accesses
memory, it cannot get a log at the time of the memory access correctly.
To prevent this, during logging, do not perform operation involving memory access (such as SET
MEMORY/SHOW MEMORY command operation and memory window operation).
Note:
During logging, MCU running states of the Stop mode and the Sleep mode, etc. cannot be displayed
in the status bar.
■ Log file
The following restriction is placed on the creatable log file size due to the file system to which the log file
is stored:
FAT: Up to 2GB
FAT32: Up to 4GB
NTFS: No restriction
Others: No restriction
When the file system is FAT or FAT32 and if the file size exceeds its limitation, the file name is changed
and logging continues.
Note:
When the log file exists already at this point, the log file is overwritten.
Operation example
If the file size exceeds its limitation, the log file is made as
filename.srl → filename#1.srl
If the file size exceeds its limitation again, the log file is made as
filename#1.srl → filename#2.srl
•
•
filename#N-1.srl → filename#N.srl
Notes:
1. Only internal HDD is supported for the log file storage destination. Network, external HDD and
external disk (such as CD, DVD and MO) are not supported for the log file storage destination.
2. Storing the log file of the RAM Checker requires free disk space of 500MB or greater. When free
disk space is less than 500MB, logging stops.