Wrong file format specified
The files you wish to download might be in a HEX format or they might be a raw, binary image. The
loaders need to be ‘told’ whether they are in HEX or BINARY format. If you are not sure about the file’s
format, “TYPE” it to the screen. If you see random printable, non-printable and graphics characters, it is
BINARY. If you see well formatted HEX characters, it is a HEX file. Intel HEX files start each line with a
“:”. Motorola ‘S’ files start each line with an “S”. Tektronix HEX files start with a “%” or a “/”. All of our
loaders automatically recognizes and converts 8 variations of these HEX formats. However, even HEX
files are a FORM of binary so you must tell the loaders whether to blindly load them as binary or assume
they are in HEX format.
Remember, your Resume’ will load and verify, but most likely will not execute properly!
Incorrect HEX conversion
If your source file is in HEX, you may need to specify an offset to get a proper conversion. If an offset is
required, it is usually the starting address of the EPROM. You can use the Quickloader editor to see where
the conversion placed the binary data within the device space.
Failed to split the file between emulators
If you want the command line loader to spilt the file between multiple emulators, you need to specify a /Ex
parameter to tell the loader how many emulators to split the file between. In Quickloader, you must specify
the ‘number of emulators’.
File loaded into the wrong emulator(s)
If you have 2 or more emulators daisy-chained, you may have loaded the file into the wrong unit(s). Watch
the STATUS LEDs to see which units where actually selected for the transfer. The loaders default to
emulator #1. To select a different emulator, specify a /Fx parameter. This tells the load the FIRST
emulator involved in the transfer.
Incorrect Byte Order
If you are loading into multiple emulators with automatic splitting, remember that the loader will load the
FIRST byte in the file into the lowest numbered emulator involved in the transfer. If the emulators are
plugged into the wrong target sockets, you can move them to the correct sockets or you can change the
order in which the emulators are daisy-chained.
Target Power noisy or Voltage too low.
Noise problems are very dynamic. It is possible that we could load and verify OK, but as soon as we release
reset and let the target start running, system noise increases and trashes the system. Low system voltage
could behave in a similar manner. It is possible that we could load and verify with a target voltage that is
well under spec, but the target will not execute properly. Econo ROM III draws more current than the
EPROM it is replacing. The target may be able to supply enough current during downloads, but may not be
able to hold the voltage up when it starts running, causing power fluctuations or noise.
Econo ROM III User’s Manual
16
Copyright ? 2000, TechTools