R„V1.0‚00K‚05‚06¤‚07Á‚08ï‚09‚*9V‚0A‚*A4‚0Cå‚0D_‚0E“ƒ014Ôƒ015ƒ0162ƒ*16Yƒ017ƒ*17Ã018@ƒ028ƒ029ă*29߃02Alƒ02B¨ƒ02Cƒ02Døƒ02E$ƒ02F?ƒ030oƒ031—ƒ033¼ƒ*33áƒ034sƒ035–ƒ036²ƒ040΃041 ƒ042 ƒ*42L ƒ043 ƒ045Í ƒ046é ƒ047 ƒ04A— ƒ04B¯ ƒ04CÈ ƒ04Dó ƒ*4D+ ƒ04F ƒ050$ ƒ051B ƒ052_ ƒ*52Š ƒ053† ƒ054œ ƒ*54ä ƒ056ñƒ0583ƒ05Azƒ05B™ƒ05C³ƒ05Eðƒ05F4ƒ*5FNƒ060êƒ0622ƒ063cƒ*63¨ƒ064£ƒ065åƒ066(ƒ067Gƒ06Aƒ*6A°ƒ06Cuƒ*6C¯ƒ06D`ƒ073ƒ077·ƒ*77ïƒ088^ƒ089ƒ08A­ƒ090˃0A0èƒ0A1ƒ0A2"ƒ0A3=ƒ0A5eƒ0A6¡ƒ0A7àƒ0A8 ƒ0A9]ƒ0AA™ƒ0AB܃0ADƒ*ADDƒ0AE|ƒ0B0·ƒ0B1 ƒ0B2=ƒ0B3aƒ0B5‰ƒ0B6ñƒ0B7 ƒ0C9;ƒ*C9Nƒ0F8œƒ0F9¿ƒ0FAüƒ*FA9„010AÇ„0111á„*111„0115Ê„*115è„011F_„0161‚„0164•„0165¿„0167ö„0169 „016Ah„016B«„016CÉ„*16Cê„016EF „0170t „0172Á „*172æ „0173Ò!„0174"„017C#"„*17C\"„017D#„017EE#„017F{#„*17F¬#„0181$„0185Ò$„*185%„0186¿%„0187&„0188F&„*188i&„0189'„01905'„*190_'„0194(„*194¹(„0195})„*195¤)„0196Ñ)„*196*„0197B*„*197i*„0198’*„*198­*„0199+„0202A+„0210j+„0212¢+„0223¾+„*223í+IThis is a dummy error used to display the version - it is never called. 4Type definition record with unrecognizable format. !Address of module is not known. Unknown module specified. ,No line information was loaded for module. .No symbol information was loaded for module. 5Cannot determine module for specified location. [*] ¬Could not find specified location in any known module. The specified location is either outside of the program or in a module for which there is no symbol information. .Cannot determine current default module. [*] ¯Could not find current location in any known module. The current execution point is either outside of the program or in a module for which there is no symbol information. xSymbol not known in current context. Symbol is either not known, or is not local to the current module or procedure. 2No symbol information is loaded for the program. ?Attempt to reference a program symbol of an unsupported type. 0Specified line is not an executable statement. *Specified line does not exist in module. %Cannot evaluate line reference. [*] 2No symbol information was loaded for the module. 4Specified type is incompatible with directory. [*] {Specified type cannot be used with the specified (or default) directory. For example, DIR PUBLICS LINE is contradictory. ?Cannot perform symbol table request. No user program loaded. ATried to REMOVE debug object declared locally in DO..END block. Workspace exceeded. [*] ‹Out of workspace. Delete any unnecessary debug objects (e.g., PROCs, LITERALLYs). This could also be caused by deeply recursive PROCs. :The name is either undefined or not of the correct type. The name is undefined. 4The name is already defined with a different type. *Parameter is outside the body of a PROC. The name is not a PROC. .Illegal type specified in DIR DEBUG command. &The named object is not a LITERALLY. #Illegal assignment to a register. #Error in debug symbol lookup. [*] May be caused by removing a global object referenced in a local context (e.g., a PROC), and then executing that reference (calling the PROC). !Type illegal for PUT or APPEND. Type illegal for DEFINE. Type illegal for REMOVE. 0Attempt to PUT or APPEND a local debug object. I/O error on PUT file. 0This command is not currently implemented. [*] BConsult the ICE-5100 Product Release Notes for more information. ;This command is not allowed inside of a compound command. Invalid type conversion. $String longer than 254 characters. †String too long for numeric conversion. In order to convert character strings to unsigned numbers, they must be of length 0 or 1. WRITE list too long. WRITE data too large. )Invalid format string in WRITE command. 6Address or partition does not exist in . [*] ÖThe address or partition must be entirely within the specified memory space. For example, the partition 60K LENGTH 5K is an invalid reference to the CODE because program memory contains only 64K bytes. Invalid expression for MTYPE. Invalid Boolean operation. Invalid string operation. )Memory space conflict in operation. [*] úThis could be caused by performing a Boolean operation on two program symbols which exist in different s. The expression (.var1 < .var2) comparing the addresses of var1 and var2 would be illegal if var1 is in XDATA and var2 is in IDATA. Invalid operation. FAttempt to assign a value to a symbolic location in CODE memory. [*] An attempt was made to assign an expression to a location associated with CODE memory (e.g., :main.proc1 = 5, where proc1 is a procedure in module main). Straight assignments can only be made to variables or data located in data memory (e.g., byte xdata 80 = 5). @Cannot use editor if ICE-5100 was invoked with SUBMIT control. EICE-5100 stack overflow - probably due to deep recursion of a PROC. LITERALLY nesting too deep. Invalid bit operation. ;Help for last error message cannot specify a unit number. BThe number # specified in HELP E must be a decimal number. Invalid partition. [*] šA memory partition was specified in which the first address is greater than the second address. For example, ASM 200H TO 100H is an invalid partition. FToo many source items were specified within a memory modify command. /Command cannot be performed during emulation. CThe specified break conditions exceed break memory resources. [*] ùThe break hardware will support a maximum of four individual breakpoints. A range breakpoint or an OUTSIDE breakpoint is equivalent to three individual breakpoints and any number of page breakpoints are equivalent to one individual breakpoint. @An invalid baud rate value was specified with the BAUD option. AAn invalid channel value was specified with the CHANNEL option. FIFO is not in freeze mode. 6Cannot write to CODE memory which is mapped to USER. /Load file contains relocatable symbol(s). [*] ÃPossibly because the object file was not generated by RL51 and, therefore, contains non-absolute symbol definitions. The records containing non-absolute symbols are ignored during the load. 8Load file contains invalid absolute OMF record(s). [*] ¯Possibly because the object file was not generated by RL51 and, therefore, contains non-absolute OMF or fixup records. These types of records are ignored during the load. .Load file is not a valid MCS-51 object file. %Bad object record in the load file. 6Memory segment request failure during operation. [*] mMore memory is needed to perform operation. Deletion of debug objects will not increase available memory. -Divide by zero (operation yields 0 result). Invalid type for arithmetic. Invalid integer operation. Illegal numeric constant. Attempt to INCLUDE :CI:. I/O error on INCLUDE file. I/O error on LIST file. &I/O error while loading object file. :Error while attempting to open the Virtual Symbol Table. =Error while attempting to seek in the Virtual Symbol Table. >Error while attempting to write to the Virtual Symbol Table. ;Error while attempting to close the Virtual Symbol Table. :Error while attempting to read the Virtual Symbol Table. ANumber to be converted to a string occupies more than 50 bytes. 3Too much text was specified for the write buffer. 1Format used in WRITE command was incorrect. [*] 6See HELP WRITE for information on the WRITE command. 9The type of an element in an output list was incorrect. PA quoted string within a WRITE format is not terminated (e.g., USING ('"hi')). 2Invalid number for the currently specified base. "Illegal use of the up-arrow (^). &Invalid string to number conversion. fIllegal base value. BASE will only accept assignments to values equivalent to 2, 10, or 16 decimal. Unable to create file. .An error occurred while writing to the file. Load error. [*] LData in the Virtual Symbol Table was corrupted during or following a load. !Illegal syntax in the CRT file. ;Insufficient memory for the Virtual Symbol Table buffers. ;Error occurred while trying to load a system overlay. [*] ŒThis probably occurred because the disk from which the system software was loaded is not in the same drive as it was when it was invoked. Fatal disk file error. Probe software load error. [*] ÅAn error occurred while attempting to load the probe software. This could have been because the probe software file could not be found or there was a checksum error in the probe software file. Probe interface error. [*] uSerial communication failed between the host and probe. Issue a RESET ICE command to restore serial communication. !No break registers are defined. Illegal number. (Illegal single line assembler operand. 5Illegal length (null) string specified as ASM text. (Too few operands for this instruction. FThe types of the operand(s) do not match the mnemonic or each other. AOne byte relative jump is out of range. Range is -128 to +127. Invalid immediate operand. Invalid indirect operand. [*] ZOnly R0, R1, DPTR, A+DPTR, and A+PC may appear after an @ sign for indirect addressing. ,Unrecognized mnemonic used in instruction. KInvalid address used in instruction requiring reference to a bit address. #Invalid use of the slash (/). [*] êA slash (/) followed by a bit address can only be used as the second operand in the following instructions: MOV C,/bit-address ANL C,/bit-address ORL C,/bit-address 0Invalid destination address for ACALL or AJMP. Operand value is too large. 7Invalid specified for the current CPU. [*] ²A special function register name was specified which does not exist for the CPU type. For example, TH2 would be an invalid if the CPU being emulated was an 80C51. 3Cannot repeat instructions, code block too large. 4Incomplete repetition of specified instruction(s). /Symbolic reference is not in CODE memory. [*] áCaused by specifying a program address with a symbol which is not defined in program memory. For example, if VAR1 is a program variable, the command GO TIL .VAR1 is invalid because .VAR1 does not refer to a CODE address. ASymbolic references in the ASM command must be fully qualified. >Instruction step size was changed to match the hardware. [*] «The specified expression for ISTEP was greater than the maximum step size of 255 (0FFH). The expression was changed to the maximum step size prior to ISTEP execution. ^Probe hardware malfunction. Current program counter and newest trace frame may be invalid. %Processor module is not responding. !Probe hardware malfunction. [*] •Processor may be in an unknown state, and the current program counter and newest trace frame may be invalid. A RESET CHIP command is recommended. 3Probe hardware malfunction. Processor was reset. (Memory verify error while writing. [*] .Read after write check found the value read did not match the value written. Possible causes: - Attempted write to ROM or nonexistent memory - Bad RAM The error message can be overridden by setting the VERIFY pseudo-variable to FALSE, however, the write error will still exist. (Bond-out device is not responding. [*] ÂPossible causes: - Probe is not receiving power - Bond-out clock not present - Bond-out is in Power Down mode - Bond-out malfunction %Invalid specified. [*] +Only s 0 through 7 are valid. 0Specified register is not bit-addressable. [*] =See HELP REGS for information on bit-addressable registers. %Invalid register bank selected. [*] 'Valid register banks are 0 through 3. Probe is not ready. [*] YPossible causes: - Probe software load error - Bond-out malfunction 7ISTEP or LSTEP not allowed when SYNCSTART is enabled. 'A return type of Boolean is expected. 6Recursion in the register definition is not allowed. BRKREG/TRCREG undefined. -Probe or serial port is not responding. [*] KCheck probe power and serial connections, then issue a RESET ICE command.