HOME >> FAQ
arrow GO TO FAQ TOP
   
FAQ

Q9.Can we define the function key of screen debugger?
Q8.How long does it take to download the program data?
Q7.At the screen debugger start up, a message [Check the device definition file] appears. The debugger can not start. [for K0, K4]
Q6.After execution with redraw and without break by the screen debugger, the damp indication scrolling brings that the event data is updated.
Q5.SFR value of the screen debugger appears wrong value.
Q4.Why is the screen debugger locked when *****. LINK file is loaded? (Key entry can not be accepted.)
Q3.For the screen debugger start up, a message [A bus timeout error has occurred] displayed at RUN execution when the screen debugger is activated with Y chosen in response to the inquiry [Do you use a Target? (y/n)]?
Q2.How much is required size to start up the screen debugger?
Q1.The screen debugger can not operate normally.

Q9. Can we define the function key of screen debugger?
A9. By customize function for function key, key assignment is able to be changed. (Please try to execute NSKEY.EXE)

[Note]
New addition can not be possible.
Q8. How long does it take to download the program data?
A8. As an example, a case of 32byte object file is as below. [for K0]

Host machine: PC-9821Ap2
486DX2 66MHz PC-9821Ae
486DX2 25MHz
Baud rate
9600bps 1min. 47sec. 1min. 47sec.
384000bps 28sec. 29sec.
Q7. At the screen debugger start up, a message [Check the device definition file] appears. The debugger can not start. [for K0, K4]
A7. For the debugger start up, the device definition file of NEC is required. Install the related device definition file for device series to be emulated in the installation directory of the screen debugger.

[Note]
For the name of CPU, input the series name of CPU as an emulation subject. For the internal ROM size, the internal RAM size, extended internal RAM size, etc. set them to the same values as a CPU emulation subject at the initial value setting screen.

DF780XX.DF1
DF780XX.SFR Device definition file for 78K0 (for In circuit emulator)
D4XXX. Device definition file for 78K, 78K4
DF780XX. Device definition file for 78K, 78K0. (for compiler, not used for In circuit emulator.)
Q6. After execution with redraw and without break by the screen debugger, the damp indication scrolling brings that the event data is updated.
A6. By the damp indication scrolling, new data is read successively. Therefore, the data at the event can not be displayed. Don’t scroll the damp, if you want to see the data.
Q5. SFR value of the screen debugger appears wrong value.
A5. For the specification of CPU, a read-only SFR is also read-only on In circuit emulator.
Therefore, data can not be written.

For the specification of CPU, a write-only SFR is also write-only on In circuit emulator.
Therefore, data can not be read.
(If no error message appears when data is written, SFR is set normally.)

When In circuit emulator breaks, SFR value obtained before RUN execution is actually displayed. (SFR (SPR) stage update: OFF) The SFR (SPR) value after break is displayed when the Redraw key is pressed.
Q4. Why is the screen debugger locked when *****. LINK file is loaded? (Key entry can not be accepted.)
A4. The size of the temporary file is too small to load the information of *****. LINK file.
The size of temporary file depends on the size, the numbers of symbol, and other factors by the loaded file.
Q3. For the screen debugger start up, a message [A bus timeout error has occurred] displayed at RUN execution when the screen debugger is activated with Y chosen in response to the inquiry [Do you use a Target? (y/n)]?
A3. User target voltage may be too low.
Please confirm that the power supply voltage of Target Board is within the operating range of ASMIS.
Q2. How much is required size to start up the screen debugger?
A2. The required size of main memory is as blow.
NS-78K4……….500kbytes or greater
NS-78K0……….444kbytes or greater
NS-75X0……….395kbytes or greater
NS-75X3……….395kbytes or greater
(For both of PC-98 and IBM PC/AT)

[Note]
To obtain a practical processing speed, you are recommended to use EMS memory.

[About the device driver for EMS]
For EMS memory, use LIM4.0 or later.
For EMS page, it should be four continuing pages at least.
EMS memory that reserves a page frame for graphic VRAM is not supported.
Set the EMS driver to reserve the page frame within the range from 0C000H to 0DFFFH.

We have checked the following EMS drivers operation.

[Attached to NEC’s MS-DOS 3.30C]
EMM.SYS
EMM386.SYS
[MELWARE]
MELEMM.SYS
MELEMM.386
[IOS-10STD]
EMM4J.SYS
VMM386.SYS
[MEMORY PRO 386]
VEMS.SYS
Q1. The screen debugger can not operate normally.
A1. Please confirm the following items.

The version of MS-DOS should be 3.30C or later.

FILES=20 or greater.

Use the hard disk.
(To prepare the temporary file, spare the space at least 2Mbytes is required.)

The debugger is not operates on Windows.
(Even through DOS-window of Windows, the debugger can not be operated.)

For main memory of the personal computer, sufficient space is spared to operate the debugger.
NS-78K4……….500kbytes or greater
NS-78K0……….444kbytes or greater
NS-75X0……….395kbytes or greater
NS-75X3……….395kbytes or greater
(For both of PC-98 and IBM PC/AT)

The screen debugger type matches the host machine.

RS-232C cable has the straight structure.

Not in HI TEXT mode.
▲Back to top