3 Gordon Drive, P.O.Box 1347 Rockland, Maine 04841 U.S.A.
Find Tools for Your Chip


Subscribe to our Newsletter

© 2004 Avocet Systems, Inc.
Call Us Today at 207-596-0080
Avocet Systems, Inc. : The Complete Solution for Embedded Systems Development Tools

Sign-On (Startup) FAQs

What is an "INTERNAL XVT ERROR 33008-2401399"?

This error was created by a bug in Version 3.0.0 release of SourceGate. This condition is caused when the emulator sends an error message to SouceGate (SG) before SG is finished initializing. It normally happens when the clock source is set to "Target" but the emulator is not plugged into the target system or the target clock is not available for other reasons. The emulator then sends a "No Clock" error message to SG before it has a chance to set up its initialization.

There are four solutions to this problem:

  1. Get a release of SourceGate later than 3.0.0. This could be any beta or official release.
  2. Power up the emulator and press the reset button on the emulator five (5) times. This SHOULD set the emulator back to factory default which is emulator clock. Note that this solution is the quickest way to get back up and running but doesn't always work and the cause of the problem is not resolved and will happen again if the target clock is lost. This will also trash your configuration.
  3. Use a terminal emulation program (hyperterminal, etc.) to sign on to the emulator. Once signed on type "MEM" at the dash prompt. Change the clock to "emulator" in the configuration window. You can also issue a "CONFIG" command from the dash prompt. Either of these should clear up the problem and allow you to sign on SG again. Note: The cause of the problem is not resolved and will happen again if the target clock is lost.
  4. Edit the v3.0.0 INI file and insert the following:
[Message Window]
EmuMsgDestinations=5

Then invoke SG2 again.

When I try to start SourceGate, I get the message "Open comm error ...". What is wrong?

This message is from the host computer's operating system. The communications port that you specified in the SourceGate startup command is either invalid, or is in use by another device such as a mouse. See the next question for information about changing SourceGate's communication parameters.

How do I change SourceGate's communications parameters?

The COM port and baud rate are specified as options to SourceGate's startup command. For example, to run SourceGate on COM2 at a baud rate of 115,200, the startup command is
c:\pathname\SG2 -COM2 -115200.

To change SourceGate's startup command in Windows 3.1, single-click on the SGII icon, click on "File" in the Windows menu bar, click on "Properties", and edit the "Command" field.

To change SourceGate's startup command in Windows 95, right-click on the SGII icon, click on "Properties", click on the "Shortcut" tab, and edit the "Target" field. If you do not have the SGII icon on your desktop, click on the "My Computer" icon, select the appropriate drive (C:, D: etc.), click on the "Windows" folder, click on the "Start Menu" folder, click on the "Programs" folder, click on the "HMI" folder, right-click on the SGII icon, click on "Properties", click on the "Shortcut" tab, and edit the "Target" field.

When I try to sign on to the emulator using the RS-232 serial communications link, SourceGate displays the message:

"The communications software has failed to receive a response from the emulator.
Please check the communications link, or try resetting the emulator."

What could be wrong? (for BMD sign on problems see further down this page or go to the bmd faq page at BMD FAQ.)

This indicates that there is no communication between the host computer and the emulator.
  1. Check the connections between the host computer, the RS-232 cable, and the emulator.
  2. Check to make sure that the emulator has power. Is the green "POWER" LED on? Can you hear the emulator's fan running?
  3. Make sure that you specify the correct COM port in SourceGate's startup command. This is a common problem as many computers do not have their COM ports labeled. See "How do I change the SourceGate's communications parameters?" for more information.
  4. If the emulator is connected to a target system, then disconnect the emulator from the target and proceed to the next step. If not, go to the next step.
  5. Press the emulator's RESET button five times in order to restore the emulator to the factory settings for stand-alone operation. You should wait about 1 second between each reset.
  6. If the emulator still will not communicate, then try to determine if the problem is with the emulator or with the host computer by either running a different RS-232 device on the computer, or by running the emulator on different computer.
  7. Try running at a different baud rate. It is rare, but we have seen a few cases where the a computer would not be able to communicate with the emulator at a specific baud rate. The allowable rates are 9600,19200,38400, 57600, and 115200.
  8. Contact HMI Technical Support.


Miscellaneous Notes:

  1. The standard Windows 3.1 communications drivers does not support HMI's hardware handshaking scheme, and is not reliable at high, or even moderate, baud rates. If you are running SourceGateII under Windows 3.1, we highly recommend that you install our communications driver, HMICOMM.DRV, or a high performance third party driver such a HYPERCOM.DRV. We have not seen any problems with Windows 95's communications driver.
  2. Many older computers came equipped with 8250 UARTs, and we have repeatedly seen these to cause communication problems when running under Microsoft Window 3.1 or Windows 95. We highly recommend the use of 16550 (or equivalent) UARTs.
  3. In general, the SourceGate should be able so establish communications with the emulator even if there is a problem between the emulator and the target system. The 68306 and 68307 emulators are an exception to this rule. On these emulators, if a problem between the emulator and the target system prevents the processor in the emulator's pod (circuit board which connects to the target) from running, then the emulator may have communications problems. If you are using one of these emulators, especially with a clip-over type adapter, and you can not get the emulator to communicate when it is connected to the target, make sure you have a good connection at the adapter, and that your circuit is designed such that the emulator can place the target processor into tri-state mode.

When I try to sign on to the BMD, SourceGate displays the message "Fatal Error from CFSC. BMD not responding"

What could be wrong?

The BMD is not responding to SourceGate. The following is a list of what might cause this.

  1. The BMD is simply a communications device which takes advantage of debug capability designed into the target system's processor. In order for the BMD to work, it MUST be connected to a target system which has a working processor installed.
  2. The BMD draws its power from the target system. The BMD draws approximately 250mA during normal operation, but may temporarily draw as much as 1A when power is first applied. Many target systems designers place a current-limiting resistor in the Vdd path, which can prevent the BMD from being able to draw enough current to operate properly. In many cases, the easiest solution is to bypass this resistor; however, if you do not wish to do this, HMI includes an adapter with the BMD which allows you to provide an external power source.
  3. Check the connections between the host computer, the RS-232 cable, and the BMD.
  4. Make sure that you specify the correct COM port in SourceGate's startup command. This is a common problem as many computers do not have their COM ports labeled. See "How do I change the SourceGate's communications parameters?" for more information.
  5. Try running at a different baud rate. It is rare, but we have seen a few cases where the a computer would not be able to communicate with the emulator at a specific baud rate. The allowable rates are 9600,19200,38400, 57600, and 115200.
  6. If you still can not establish communications with the BMD, contact HMI Technical Support.

For other BMD questions and issues look at BMD FAQ.