G E N E R A L   U S P   Q U E S T I O N S

and problems

A N S W E R S

and solutions

You can copy the debugger distribution files from the CD to 1.44 MB diskettes and install the software from the diskettes. On the CD, switch to the appropriate product directory and copy each of the Disk1, Disk2 etc. folders to a separate diskette.  Run the setup program from the diskette containing the Disk1 folder.

Yes, you can. The processor on the POD can execute program code from either the emulator's (internal) and/or target's (external) memory, depending on the memory mapping scheme. For details, please refer to the Memory Mapping section in the User's Manual. If the whole program memory is mapped to emulator (command: 'map p all i'), the processor will execute the code from the emulator's memory, and the target's program memory will not be accessed. The target's memory image—usually a hex file—or a testing routine can be loaded to the emulator's memory. The target's memory can be physically removed.

1. Please verify that the parallel port of your ICE was activated. You can do this by referring to the copy of the purchase order or contacting Signum Technical Support.
2. Make sure that the ICE is connected to the PC through either a parallel or serial cable. Run a terminal program, such as Windows Hyperterminal (if you are using the serial port) or the parallel port terminal emulator 'pptty.exe' (if you are using the parallel port). The 'pptty.exe' program can be found in the Firmware directory on the Signum Systems CD-ROM. Switch off and on the ICE. If you cannot see the ICE's identification message in the terminal window, contact Signum Technical Support.
3. Try to run the debugger on a different computer.
4. Make sure that the selected communication port is not used by the mouse, printer, modem or FAX driver, or captured by another application.

Yes, you can:

1. Connect the POD to the ICE unit and run the debugger.
2. Set Power and Clock to "Internal" by executing the commands: "power i" and "clock i". The processor on the POD will be powered by the ICE power supply and the clock signal will be supplied by the oscillator on the POD (please note the oscillator frequency).
3. Map program and data memory (where appropriate) to ICE by executing the commands:   "map p all i" and "map d all i".
4. Load the program and run it.

You cannot set a breakpoint at a C source line that does not have its assembly representation. This is obvious in the case of comments, but also concerns an optimized code. For example, you may try to set a breakpoint at line #744 of a program:

  744> Exposed = (Exposed) / 16;
  745> P1_3 = 1;

In response, the debugger sets a breakpoint (denoted by the '*' character) at line 745 rather than 744:

   744> Exposed = (Exposed) / 16;
  * 745> P1_3 = 1;

This occurs because line 744 is not explicitly represented in the assembly code, and line 745 happens to be the closest source code line represented by assembly statements. You can verify it by switching to the mixed mode, where line 740 is immediately followed by line 745:

  740> delay(100);
  0:33CE: 053B INC 3B
  0:33D0: E53B MOV A,3B
  0:33D2: 7002 JNZ 33D6
  0:33D4: 053A INC index
  0:33D6: E53B MOV A,3B
  0:33D8: 249C ADD A,#9C
  0:33DA: E53A MOV A,index
  0:33DC: 34FF ADDC A,#FF
  0:33DE: 50ED JNC 33CD
  * 745> P1_3 = 1; /* see Reference Element */
  0:33E0: 753900 MOV Count,#00

When debugging your program, it is strongly recommended that you switch occasionally to the mixed mode to see what code your processor is in fact executing. The source mode might be misleading particularly when dealing with an optimized code.

Cf. WEMUXX Help File:
Note. If breakpoint (or passpoint) is set at any statement which is not an executable statement, for example a comment line, the breakpoint (or passpoint) will be toggled at the next executable program statement.