>>>>PARTNER-NB85E-TP<<<< Midas Lab. Inc. The supplementary explanation about PARTNER-NB85E-TP is described by this document. We ask you to surely read before use. Revision history ---------------- Version 3.31 - AS85EP2 was added to correspondence CPU. - There was a binary file that was not able to be read by the RD command. Version 3.30 - When RTE of LAN connection was used, the fault which may not operate normally was corrected. - The fault which cannot perform break point specification by a line number in a command window was corrected. - The TMCD register of the I/O definition file for NB85E was corrected. Version 3.20 - It corresponded to FLASH_MEM2 description of a CFG file. Please read the clause "about description of FLASH_MEM2". *Intel type(with write buffer) operation is unidentified. - Disassembling/assembling of a bit manipulation instruction(CLR1,SET1,NOT1,TST1) were corrected. Version 3.13 - The error was shown in the bit field display of the DWARF2 format file created with Green Hills compiler. It was corrected. - The sample program of GreenHills compiler was changed into DWARF2 format. - Specification of the channel number of RTE was added. Version 3.12 - V850E/ME2 was added to correspondence CPU. Version 3.11 - It corresponded to the Intel type Flash Memory Version 3.10 - Bus trace function was added. BTRC command and the Bus trace setting dialog box were added. Version 3.02 - NU85E was added to correspondence CPU. Version 3.01 - Since the file which cannot be read was in DWARF2 format file created with the compiler of GreenHills, it corrected. Version 3.00 - It corresponded to RTE-2000-TP. Please read the clause of "correspondence of RTE-2000-TP". - The problem which cannot display Static variable of an object(created with the compiler CA8xx(NEC) ) correctly was repaired. - It corresponded to the debugging information on DWARF2 form created with the compiler made from GreenHills. There is no special setup for this. - The internal processing method of debugging information was changed. The problem which cannot read the object with much debugging amount of information has been improved. The setting method of a debugging information area does not have change. Version 2.10 - When an input error occurred by FOR command, the fault which forces a program to terminate was repaired. - It repaired to process a maximum of 16 data elements correctly in F command. It was processing as a maximum of 16 bytes before. - /W option of G command repaired so that it might function during SYSCALL exe-cution. - In order to display the contents more than the arrangement element which carried out inspect of the arranged type variable to the object created with the compiler (CA8xx) by NEC Corp., and was defined as the case, it repaired so that an arrangement element might be displayed correctly. - In Load(L),WR, and RD command, since the deadlock state might be caused dur- ing reading or writing, it repaired. The % display method of a processing situation is changed. - About TIP function, execution / stop state was repaired so that a state might be controlled correctly. - The cancellation function under file processing was added to Load(L),WR,and RD command. * Cancellation is possible by the ESC key during reading or writing. Version 2.01 - Changed so that a user program can be executed, even if neither a trace unit nor an event unit was mounted in CPU. Version 2.00 - Added the following function by correspondence to RTE-1000-TP. Added the "5MHz-100kHz" to the JTAG-CLOCK control function (CPU Environment Setup). Added the external break function (CPU Environment Setup). Enabled a setup of data trace on the trigger conditions (Trace Aaddress Setup). Added the time tag indication to the history display (History window / command). Added the write function to Flash-ROM. Added the management command (ZF) of Flash-ROM, and also added the map form of Flash-ROM to CFG file. - Separated specification of the event point, the trace address, the address mask value of an access break setup, or data mask value. - Added the NROM/NROMD command. - Added the NSBP/NSBPD command. - Modified the bug from which a break point was changed when a break point is saved, in save/load function of a break point. - Modified the defective display about an icon indication of each child window. - Added the following notes to this document. About BPC register of peripheral I/O About the writes to Flash-ROM Version 1.20 - added "32M-256M" to ROM size of ROM command. - Modified the bug with the case where it becomes an error, even if it specified the effective cycle, by TD command. - Modified since TIP function was not processed correctly. - Changed so that the blank of the beginning of a sentence of CFG file might be skipped. Version 1.10 - Modified the bug of L command - Modified break processing (the path count and SYSCALL). - Expanded the internal area which stores the debugging information, and changed so that the file with much amount of information can also be read. Version 1.00 - First version About the version of "RTE for WIN32" to use ------------------------------------------- Please use V5.09.01 or latest versions. The latest version of "RTE for WIN32" can be downloaded from the following sites. http://www.midas.co.jp/products/download/program/rte4win_32.htm Correspondence CPU ------------------ PARTNER-NB85E-TP corresponds to the following CPU. Version 1.00-3.01 NB85E Version 3.01- NB85E, NU85E Version 3.12- NB85E, NU85E, V850E/ME2 Version 3.31- NB85E, NU85E, V850E/ME2, AS85EP2 About installation of the update version ---------------------------------------- The installation program of the update version deletes all the files in a SAMPLES folder before installation. When there is a file required in a Samples folder, please save before installation. About starting of the environment setup program RPTSETUP.EXE. ------------------------------------------------------------- When you start RPTSETUP.EXE, please be sure to specify the start option "/NB85E." The shortcut to RPTSETUP.EXE created when PARTNER was installed specifies this start option. Moreover, a project file (*. KPJ) can also be specified and started beforehand. In this case, please specify a project file by the path name as follows. Example: >RPTSETUP /NB85ET C:\PROJECT\TEST1\PRTNB85ET.KPJ About installation to WindowsNT/2000 ------------------------------------ When PARTNER-NB85E-TP is installed in Windows NT/2000, the shortcut to RPTSETUP.EXE is created to the program group for the personal, and is not created to the program group for the common. Therefore, when other users installed, the shortcut to RPTSETUP.EXE cannot see with the start menu. In such a case, RPTSETUP.EXE moves a current directory to the installed directory, specifies the start option "/NB85ET" as mentioned above, and starts RPTSETUP.EXE. Thus, when performing registration of a project after starting, the shortcut to RTESETUP.EXE is simultaneously created by the new program group by specifying the program group not existing to be a registration place. Moreover, when "OPEN" is executed by RPTSETUP.EXE, the directory of the project used last time usually turns into a current directory. However, when using RPTSETUP.EXE installed by other users, a current directory moves to the directory which surely started RPTSETUP.EXE. In such a case, it is convenient if you start from the shortcut which registered the shortcut of a project and registered PARTNER. When using the single mode 0 ---------------------------- When you use the single mode 0, please set the initial value of a program counter (PC) to PRTNB85ET.CFG as follows. INIT_PC 0x100000 In the initial state of CPU, the internal ROM domain is the write mode. If an internal ROM area is accessed when PARTNER starts, changes to the read mode. Therefore, it becomes impossible to execute a program correctly from the initial state of CPU. Therefore, it avoids that the access mode changes by setting addresses other than a internal ROM domain as the initial value of PC. In addition, immediately after starting PARTNER, or when INIT command was executed, this setting command is executed. About the history display (Real-time trace result display) ---------------------------------------------------------- 1) The Real-time trace is executed only by Run execution (G command). It is not executed, in Come execution, Trace execution, Step execution, and Return execution. 2) The Real-time trace traces branch (branch instruction) of an execution address. Therefore, complements the instruction executed between branch instructions and indicates. This complement processes a instruction of a maximum of 128. Therefore, the exceeded portion is not indicated, when the instruction executed between branch instructions exceeds 128 pieces. 3) In a history display, the cycle of the same address may be indicated continuously. This is because the status of a cycle differs. The actual instruction execution cycle is indicated on the back cycle. About the break point to ROM area --------------------------------- In ROM area, a break point can be set up to a maximum of two places. In the case of the combination about which the break point set up executes two instructions simultaneously, a break may not be taken. About the sample program ------------------------ The sample program is created so that it may operate by internal ROM and internal RAM. When the program suitable for the environment of a target board needs to be performed, please rebuild to the sample program suitable for environment. About the SYSCALL function (SYSC command) ----------------------------------------- There is an alternative input-and-output function which used the command window for realizing console input and output from a user program in PARTNER. However, this function is provisional correspondence. 1) SYSCALL function is enabled, and while a user program is running, operation except SYSCALL and the force break cannot be executed until a user program takes a break (the force break, or break by the break point). 2) If SYSCALL function is enabled, and the focus of an active window was changed while a user program is running, executes the force break to the user program. 3) When you use SYSCALL function, please move the focus of a window to the command window beforehand. 4) When a program is loaded, except for the case of 6) clause, SYSCALL function becomes invalid automatically. However, in the case of a re-load, a state is maintained. 5) When a label "midas_syscall" exists in the debugging information about the program to load, the value of a label is registered into an entry point and use of SYSCALL function is enabled. 6) The control and the status indication about SYSCALL function use SYSC command. About loading of a program (L command) -------------------------------------- When a program is loaded, clears all break points (including an access break point). However, in the case of a re-load, the break point set up is held. About the error message ----------------------- 1) "Can not execute monitor program" This message is displayed when the ready signal to CPU is not active. Usually, if the following operations are performed in an inaccurate address to a memory or I/O, this state will occur. - The window and command for operating a memory and I/O - When the item which displays the contents of a memory on a register window is specified - When an address inaccurate while displaying a history window exists in a trace result In order to avoid occurring of this error, please perform in the following ways. - Changes a condition setup of Real-time trace - Specify address within the limits which can be accessed certainly - Defines MAP form of the area which can access a composition file (RPTNB85ET.CFG) * In addition, please refer to a help of RPTSETUP, or the manual of PARTNER for the how to MAP form. However, even if it defines a map form as a composition file (RPTNB85ET.CFG), restriction of access about a history window cannot be executed. 2) "Can't execute this program" or "Can't execute this program, CPU is reset" This message is displayed when the break is not able to be correctly taken by step execution. It may occur, when the source program and the object program are not according. In such a case, although execution of a program is automatically stopped by the force break, PARTNER resets CPU, when not taking the break. About initialization of INIT command ------------------------------------ Since the contents set up by ENV command and ROM command are lost by execution of INIT command, please execute a setup again by those commands. About the message of a Real-time trace end ------------------------------------------ When trigger conditions are set up and execute the Real-time trace, a message displays, when trace is completed, while the user program executes. In order to display the trace result, executes the force break or waits for a break by the break point. About ASID value ---------------- ASID value of the parameter of a command or a dialog is the function for extension of the future. Please use it with initial value. About BPC register of peripheral I/O ------------------------------------ When the operation mode is the 64M mode and the programmable peripheral I/O area is effective, 12 or 13 bits (PA12, PA13) of BPC register are always set to 0. Therefore, after changing BPC register by I/O window or memory operation, even if it reads value from the register, 12 or 13 bits is always 0. About the writes to Flash Memory -------------------------------- When an error occurs by the writes to Flash-ROM, the management buffer of Flash-ROM is the Dirty state. In this state, if it writes to Flash-ROM by L command, F command etc., it may not operate correctly. In such a case, removes the obstacle of the error which occurred, or changes the management buffer of FlashROM into Clear state by ZF command. Correspondence of RTE-2000-TP ----------------------------- Changed the following function by correspondence to RTE-2000-TP. ROM command In using RTE-100/1000-TP, there is no change. When RTE-2000-TP was used, it was changed as follows. 1)In order to set up every EMEM board, it is called ROM1,ROM2,ROM3,and ROM4 command for every target board. An option is the same. The board to set up is specified by the dialog command. 2)The relation between ROM1/2/3/4 command and EMEM board is as follows. A setup which does not match this relation cannot be performed. | |Slot position|ROM command which ROM command|Bus size|of EMEM board|cannot be used -----------+--------+-------------+------------------ ROM1 | 8-bit |#3 | | 16-bit |#3 | | 32-bit |#3+#4 | ROM2 -----------+--------+-------------+------------------ ROM2 | 8-bit |#4 | | 16-bit |#4 | -----------+--------+-------------+------------------ ROM3 | 8-bit |#5 | | 16-bit |#5 | | 32-bit |#5+#6 | ROM4 -----------+--------+-------------+------------------ ROM4 | 8-bit |#6 | | 16-bit |#6 | NROM command In using RTE-100/1000-TP, there is no change. In RTE-2000-TP, the minimum unit of a specification area was changed. It corresponds to a bus size. 8/16-bitF128K-byte unit 32-bit F256K-byte unit ENV command The contents of a display, such as a kind of probe and the kind of an emulation ROM board, were changed and added. Bus trace When using Bustrace, an external Bus-trace board and the attachment of exclusive use are required. About the Intel type Flash Memory --------------------------------- In the definition parameter (TYPE) of a flash memory area, the following parameters have unidentified operation by the actual device. I32W_TOP Top boot block type(Intel type, with Write Buffer) I32W_BOTTOM Bottom boot block type(Intel type, with Write Buffer) I32W_NO Without boot block type(Intel type, with Write Buffer) When you use the device with WB, please specify usual IntelType and use it. The example of the target device is shown. HITACHI HMB32S4, HMT32S4 MITSUBISHI M***B33****, M***T33**** About V850E/ME2 --------------- When CPU is V850E/ME2, a setup in the cache-mode of "Set CPU environment" dialog command cannot be performed. And specification in the cache-mode of ENV command is invalid. About Channel number of RTE --------------------------- The channel number of RTE is specified by the environmental setting program (RTESETUP.EXE). Please choose 0, when you do not use the channel function of RTE. About description of FLASH_MEM2 ------------------------------- This description is used at the time of the device which is not supported with the form of FLASH_MEM. The following forms describe to a CFG file. Format: FLASH_MEM2 startaddr,type,size:count[,size:count[,size:count[,„„„]]],CPU_BUS[,FLASH_BUS] startaddr The start address of the flash memory is specified (Number of 16s). type Either of the following device types is specified. 0 AMD type 1 Intel type 1001 Intel type, with write buffer size:count The sector composition of a device is described. "size:count" is made into one set and it can specify to 128 sets. size The size of 1 sector is specofied(Number of 16s). count The continuous number of sectors is specified(Number of 10s). CPU_BUS Either of 8,16 or 32 is specified as CPU data bus width. FLASH_BUS Either of 8 or 16 is specified as device data bus width. An abbreviation is possible when the same as that of CPU_BUS. Example: FLASH_MEM2 0000000,0,2000:8,10000:126,2000:8,16,16 * WindowsNT, Windows2000, Windows95, Windows98, and MS-DOS are the trademarks of U.S. Microsoft Corp. * The names of the programs, systems, CPUs, and other products that appear in this document are usually trademarks of the manufacturer of the corresponding product.