| |
Technical
Support Knowledge Base
Error
Messages
Q: Error message "Device not ready
at address …”
A: It looks that your BDM
system reads or writes somewhere where it cannot. Perhaps there is no
device on that address in your target or the chip select signal is not
active. If you have checked-in "Generate Bus Error on 'device not
ready' " and BussError line (BDM connector) is connected in your
hardware error message should appear displaying the address where problem
exists.
Keywords(BDM,
Error,
CPU32, HC16)
Q: “Syntax Error” during download
A: Download file format doesn’t match
with the winIDEA’s syntax. First, try latest winIDEATM
version available. If you still get "Syntax error" message,
create the WSB file in the 'Help/Technical Support' menu and send it to
the iSYSTEM’s tech support with a short description.
Keywords(Syntax
Error)
Q: I get an error message “Error attaching
to HASYST” when I start winIDEA.
A: You probably installed
winIDEA on WIN95 environment. This message indicates that Winsock 2.0
is required. You can find the patch on the winIDEA v8.6 CD or winIDEA
v9.0 CD in the directory WINSOCK95.
Keywords(winIDEA
setup)
Q: I get an error message “OLE initialization
failed” when I start winIDEA.
A: You probably installed winIDEA on WIN95
environment. This message indicates that IE4.0 or higher is necessary.
You can install IE4.0 from directory IE40 on the winIDEA v8.6 CD/winIDEA
v9.0 CD or you can download it from Microsoft web site.
Keywords(winIDEA
setup)
Q: Error 3: Cannot initialize emulator
A: Probably, the emulator
is damaged, most possibly the emulation module.
Keywords(Error
3)
Q: Error 5: Cannot Initialize Emulator,
Cannot load FPGA on POD
A: Probably the POD or even
the in-circuit emulator is damaged.
Keywords(Error
5)
Q:
Error 7: Incorrect POD selected
A: First check if you selected the proper POD in the ‘Hardware/In-circuit
emulation/CPU’ tab. If you set the right POD and you still get the
error 7 message, generate the WSB file in the ‘Help/Technical Support’
menu and send it to the iSYSTEM’s tech support with a short description.
Prior to the WSB file generation the communication must be established.
Keywords(ICE,
Error
7)
Q: Error 21: Cannot start emulation. Check
RESET vector, Vcc and clock source…
A: Check if Vcc and clock source are set to internal and try
again. If you still have the same error run our sample project for your
POD without the target. If the sample project doesn’t work, the emulation
system might be damaged.
Keywords(Error
21, start)
Q: Error 44: BDM module not found
A: winIDEA cannot find the BDM module. Create the WSB file and send
it to the iSYSTEM’s tech support with a short description.
Keywords(Error
44)
Q: Error 54: Invalid emulation memory size
selected
A: Memory size of your in-circuit emulator doesn’t match with
the value set in the winIDEATM. Set proper value in the 'Hardware/Emulation
Options/Hardware' tab.
Keywords(Error
54)
Q: Error 63: Error during loading CPLD
A: It is possible that a hardware is damaged. If this happened after
you were already using the emulator it means that software works and your
hardware is damaged. If this error occurs after upgrading the software
or after you started new system for the first time, the problem may originate
from the winIDEATM. Contact iSYSTEM’s tech support in
such case to discard the software problem.
Keywords(Error
63)
Q: Error 73: Cannot initialize hardware.
Resource error
A: Contact iSYSTEM’s tech support. winIDEATM’s
resources don’t match.
Keywords(Error
73)
Q: Error 75: Programming FPGA
A: Probably, the emulator is damaged, most possibly the emulation
module.
Keywords(Error
75)
Q: Error 80: Cannot set oscillator
A: The BDM emulator is damaged or perhaps you have problems
with winIDEATM.
Contact iSYSTEM’s tech support.
Keywords(Error
80, BDM)
Q: Error 90: Memory areas 0xFF007B-0xFF007D
and 0xFFFFD0-0xFFFFE3 are reserved for emulator
A: These are locations of
TRAP vectors used for emulation only. You have to tell linker that no
code or vectors should be placed on these addresses. See link file in
our sample project for 80C 251 (on winIDEA CD) where you can see the command
for excluding this areas from download file. Of course be aware that it
is example for Keil compiler.
Keywords(Error
90, 251 family)
Q:
Error 97: Cannot start emulation! Check clock, Vcc and reset vector
1FFE0000h
A: Check your system with
our sample project and without the target connected. If it doesn’t
work, probably the POD is damaged or even the in-circuit emulator.
Keywords(Error
97, 68LC302, 68302)
Q: Error 105: Cannot init Hardware. Error
loading FPGA at BDMSDI module
A: This message can occur
if you use the IC2000 in-circuit emulator and the BDM module is inserted
in the BaseUnit+ or in the Remulator. The BDM module Rev. F or higher
solves this problem.
Keywords(Error
105, BDM)
Q: Error 128: Incorrect PEAR register. Valid
setting mask is xx10x1xx
A: When using the HC12A4_B
POD in Expanded Narrow Mode, the PEAR register must be set to a value
xx10x1xx, when using Expanded Wide mode, the PEAR register must be set
to a value xx1011xx. Pre-set bits defines some port E signals as control
signal since they are necessary for emulation, other bits can be defined
by user.
Keywords(Error
128, HC12A4, PEAR register)
Q: Error 131: Incorrect Trace module type
selected
A: Check if you chose proper trace module type
in the ‘Hardware/Analyzer Setup/Operation tab. If you select proper
one and you still get the same error message, generate the WSB file send
it to iSYSTEM’s tech support with short description of your problem.
Keywords(Error
131, trace)
|
SiteMap