10LC Wiki

Here we start with the statements that are used for configuring the unit and the compile environment.

The SetupPod statement configures both the 9010A and the compile environment, and sets the default values for some of the other Setup* statements like SetupBusTestAddress, SetupRunUUTAddress and the names of Forcing Lines. This is equivalent to the POD setup parameter in 9LC.

Unlike with 9LC, information on the standard Pods is stored within the compiler and no additional external files are needed. If you use the SetupPod statement, it must be the first statement in a source file.

The following Pods are supported directly by 10LC:

The syntax of the statement is as follows: SetupPod <PodName>;

SetupPod Z80

If you need to create your own Pod configuration/environment, you can use the Setup* statements directly.

This statement enables or disables traps associated with UUT errors. This statement can be specified multiple times, and you can specify multiple traps within a single statement. This is equivalent to the TRAP setup parameter in 9LC.

The following Trap names are available:

The syntax of the statement is as follows: SetupTraps <TrapName> [<TrapName>…] Yes|No;

SetupTraps DataError No;
SetupTraps ActiveInterrupt DataError No;
SetupTraps BadPowerSupply ActiveInterrupt ActiveForceLine Yes;

This statement enables or disables Pod-specific forcing lines associated with a CPU. You can specify forcing lines but their bit value, or by their string identifiers. Like with the SetupTraps statement, this statement can be specified multiple times, and you can specify multiple forcing lines within a single statement. Forcing Lines are numbered 0-7 for a total of 8 possible lines. This is equivalent to the ENABLE statement in 9LC.

The following Forcing Line names are supported directly by 10LC (but may not apply to the currently configured Pod! )

The syntax of the statement is as follows: SetupEnableFL <FLName|FLNumber> [<FLName|FLNumber>…] Yes|No;

SetupEnableFL 1 Yes;
SetupEnableFL 2 No;
SetupEnableFL  BrAck  Ready Yes;

If you have a Pod configured, the Forcing Line name or number will be checked against the configured Pod, and if that Pod does not have a Forcing Line for a given name/number, an compile error will be thrown.

If you do not have a Pod configured, you can use just the Forcing Line number, and with no Pod configured, the number will not be checked. The names/numbers of forcing lines are shown on the front of the Pod. Note that the names may differ slightly, (e.g. br/ack on the Pod is brack in 10LC) so you will have to find the corresponding name in the list above.

This statement sets whether the 9010A unit emits a beep on an error transition. This is equivalent to the BEEP setup parameter in 9LC.

SetupBeep Yes;

This statement sets whether the 9010A pauses execution, displays an error message, and asks the user if they want to loop the last operation whenever an error is encountered. This is equivalent to the EXERCISE ERRORS setup parameter in 9LC.

SetupInteractiveErrors Yes;

This statement configures the default address used when a Bus Test is performed. This value defaults to 0x0000 but may be changed when a Pod is specified via the SetupPod statement. This is equivalent to the BUS TEST setup parameter in 9LC.

SetupBusTestAddress 0xFFF0;

This statement configures the default address used when the Run UUT operation is performed. This value defaults to 0x0000 but may be changed when a Pod is specified via the SetupPod statement. This is equivalent to the RUN UUT setup parameter in 9LC.

SetupRunUUTAddress 0xFFFE;

This statement configures the serial XOn character used to pause transmission of serial data. This is equivalent to the STALL setup parameter in 9LC and it defaults to <CONTROL+S> (0x13).

SetupXon 0x70;

This statement configures the serial XOff character used to resume transmission of paused serial data. This is equivalent to the UNSTALL setup parameter in 9LC and it defaults to <CONTROL+Q> (0x11).

SetupXOff 0x72;

This configures the serial line length used when transmitting serial data. This is an important setting when sending/receiving hex data from the 9010A unit as longer lines lessen the effectiveness of the per-line checksum.

The 10LC compiler also uses this setting to determine the length of hex lines when it generates its output hex file. It has a range of 10-255. If not specified, the default value is 79. This is equivalent to the LINESIZE setup parameter in 9LC.

SetupLinesize 70;

This configures the amount of time the 9010A should wait for a connected Pod to respond to a requested operation. As of right now, there is no description for how long a single “count” of this value is.

It has a range of 6-60000. If not specified, the default value is 200. This is equivalent to the TIMEOUT setup parameter in 9LC.

SetupPodtimeout 100;

This configures both the character combination used to represent newlines on the serial interface as well as a configurable delay time between successive lines being transmitted. The value used with this statement is a 32-bit hexadecimal value.

The first single-character parameter represents a delay count between transmitting successive lines. Each count is ~6ms per count on firmware version 2C or later, or ~2.4ms per count on versions earlier than 2C. The second six-character parameter is the hexadecimal character combination that should be sent to indicate a newline. A zero value indicates no character is to be sent. If not specified, the default value is 0x00, 0x000D0A (0x00000D0A). This is equivalent to the NEWLINE setup parameter in 9LC.

SetupNewline Delay 0x20 Chars 0x000D0A;

This setting is not directly exposed by 9LC and configures the bitmask of Forcing Lines that may be referred to by the SetupEnableFL statement. Normally, the values for these lines come from loaded Pod information (see SetupPod) but can be specified manually for situations where a support Pod entry does not yet exist.

The are up to 8 supported Forcing Lines but most pods generally only use a few of the available bits. The specified mask indicates which Forcing Lines are supported by the connected Pod and thus are valid to be enabled or disabled by the SetupEnableFL statement.

SetupMaskFLMayBeEnabled 0x07    // Enable Forcing Lines 1, 2 and 3.

This is another setting that is not directly exposed by 9LC and configures the names of Forcing Lines that may be referred to by the SetupEnableFL statement. Normally, the names for these lines come from loaded Pod information (see SetupPod) but can be specified manually for situations where a support Pod entry does not yet exist.

The are up to 8 supported Forcing Lines but most pods generally only use a few of the available bits. The 8 names correspond, in order, to the 8 supported Forcing Lines. Each Forcing Line name has a limit of 6 characters.

SetupForcingLineNames "" "" "" "" "BusReq" "Wait" "" ""    // Set Names For Enable Forcing Lines 4 and 5.

This statement allows you do configure the expected memory map of the UUT that is going to be used with your code. There are three kinds of entries that can be specified for the memory map: RAM, ROM and IO. The ROM and IO versions of the statement require an additional parameter that specifies the expected ROM signature or the bits used in the I/O.

This is equivalent to the ADDRESS SPACE setup area and its descriptors in 9LC.

SetupMemMap RAM From 0x0000 To 0x0FFF; 
SetupMemMap ROM From 0x1000 To 0x18FF SIG  0xAA55; 
SetupMemMap ROM From 0x1900 To 0x1FFF SIG  0x1234; 
SetupMemMap IO  From 0x2000 To 0x2001 MASK 0x000000FF; 
SetupMemMap IO  From 0x2002 To 0x2003 MASK 0x7F;