LBIF RLB Test fixture software.pdf

RLB/LBI Test Fixture Software

1 Modes/Functions

1.1 Input/Output

1.1.1 Read PMF file

1.1.2 Load Byte Array to RLB

1.1.3 BIT Status Via Serial 15625 baud rate serial

1.1.4 PETIO (Output/Input message Support, via 15625 baud rate serial)

1.2 Initialization

1.3 Load RLB using Digital I/O board

1.4 Monitoring

1.4.1 BIT Simulation

1.4.2 Log File

1.4.3 CIU Monitoring (Option)

RLB/LBI Test Fixture Software

Clif notes

1 Modes/Functions References:

SDG634288

G634291 (TEST SET)

1.1 Input/Output

1.1.1 Read PMF file

Read PMF file to a Byte Array. Files must be tested for valid PMF format. The file format must be tested on read to ensure a correct program / data file. The following must be tested.

• Each line starts with “:”

• Verify checksum for each line

• Check for Valid Record Type

• Verify File Checksum

1.1.1.1 PMF File Format

The Paged Memory File format is Intel Hex with two additional record types. A file type record and a file checksum record has been added. Additionally the termination record type is not used. A data record with no data is used in place of the termination record.

HEX-RECORD CONTENT

Hex-Records are character strings made of several fields which specify the record type, record length, memory address, data, and checksum. Each byte of binary data is encoded as a 2-character hexadecimal number: the first ASCII character representing the high-order 4 bits, and the second the low-order 4 bits of the byte.

The 6 fields which comprise a Hex-record are defined as follows:

Field Characters Description 1 Start code 1 An ASCII colon, ":".

2 Byte count 2 The count of the character pairs in the data field.

3 Address 4 The 2-byte address at which the data field is to be loaded into memory.

4 Type 2 00, 01, or 02.

5 Data 0-2n From 0 to n bytes of executable code, or memory loadable data.

n is normally 20 hex (32 decimal) or less.

6 Checksum 2 The least significant byte of the two's complement sum of the values represented by all the pairs of characters in the record except the start code and checksum.

Each record may be terminated with a CR/LF/NULL. Accuracy of transmission is ensured by the byte count and checksum fields.

There are three types of Hex-records used in the PMF format.

HEX-RECORD TYPES

ID Description

0x00 A record containing data and the 2-byte address at which the data is to reside.

0x01 A termination record for a file of Hex-records. (not Used in PMF) May be supported as an option. STD Intel hex termination record is “00000001FF”

0x02 A segment base address record. This type of record is not Used in PMF.

0x88 A record containing the file type. This record contains 4 data bytes. Only the first data bytes is used. See the PMF File Types table for more details.

0xFF

File checksum record. This record contains a 32 bit checksum of all ASCII bytes in the file preceding the File checksum. This is the 2nd to last record in the file.

Included in this checksum is the sum of the ACSI bytes in the start of file checksum record “:040000FF”

PMF files use a termination record of type 00 (data) with no data. Ex: “:0000000000”

PMF File Types 0x03 Mid/High Band Matrix File 0x04 Low Band Palette File 0x24 Low Band Program Page 3 0x25 Low Band Program Page 4

PMF-RECORD EXAMPLE

Following is a typical Hex-record module consisting of four data records and a termination record.

:040000880300000071

:10010000214601360121470136007EFE09D2190140

:100110002146017EB7C20001FF5F16002148011988

:10012000194E79234623965778239EDA3F01B2CAA7

:100130003F0156702B5E712B722B732146013421C7

:040000FF000CBC4FE6

:0000000000

The file type record is explained as follows:

:040000880300000071

: Start code.

04 Hex 04 (decimal 04), indicating 4 data character pairs, 4 bytes of binary data, in this record.

0000 Four-character 2-byte address field: hex address 0000, 88 Record type indicating a file type record.

03 File type record data 03 = file type

The next 4 character pairs are the spare bytes of the file type data.

71 Checksum of the file type Hex-record.

The first data record is explained as follows:

:10010000214601360121470136007EFE09D2190140

: Start code.

10 Hex 10 (decimal 16), indicating 16 data character pairs, 16 bytes of binary data, in this record.

01 Four-character 2-byte address field: hex address 0100, 00 indicates location where the following data is to be loaded.

00 Record type indicating a data record.

The next 16 character pairs are the ASCII bytes of the actual program data.

40 Checksum of the first Hex-record.

The file checksum record is explained as follows:

:040000FF000CBC4FE6

: Start code.

04 Hex 04 (decimal 04), indicating 4 data character pairs, 4 bytes of binary data, in this record.

0000 Four-character 2-byte address field: hex address 0000, FF Record type indicating a file checksum record.

000CBC4F Four byte file checksum. This is a running sum of all ACII characters in the file up to the start of the file checksum data. The file checksum and its record checksum are not included in the sum.

E6 Checksum of the file checksum record.

The termination record is explained as follows:

: Start code.

00 Byte count is zero, no data in termination record.

00 Four-character 2-byte address field, zeros.

00 Record type 00 is data.

00 Checksum of termination record.

1.1.2 Load Byte Array to RLB

Simulate PSP to RLB load interface implemented in PSP Multiplex Buffer Enable register A0AC.

Multiplex Buffer Enable – A0AC B7 B6 B5 B4 B3 B2 B1 B0 49 24 25 58 29 18 48 19

Spare RLB_

DIN

RLB_

SYNC

RLB_

CCLK

RLB_

RESET-

AREN+ HDEN+ CWMXN+

B0 = Propeller Mux enable

1 = enable

0 = disable

B1 = Noise Mux enable 1 = enable 0 = disable B2 = Pulse Doppler Mux enable 1 = enable 0 = disable B3 = RLB_RESET- 1 = enable 0 = disable B4 = RLB_CCLK Indicate RLB LBPP or Mission B5 = RLB_SYNC Signal used to indicate 32 bit word to be sent to LBP B6 = RLB_DIN RLB discrete data line B7 = Spare

PSPP Code that implements load

Code from U_IO.Z8k / IOLBLD which included clock tick counts and summaries in comments on left side of page. Timing is determined by multiplying the number of clock ticks for each event by 0.25 uSec.

; PCR RLB

; CLOCK A SINGLE BIT TO THE LBP

OUTBIT: .MACRO LABEL1 ; TOTAL CLOCK CYCLES 53-57 AVERAGE=55

LD R0,#38h ; SET THE CCLK (CCLK+ SYNC+ DIN-) - 7 SLLB RL5,#1h ; SHIFT MSB INTO CARRY - 16

JR NC,LABEL1 ; IF NO CARRY LEAVE DATA 0 - 6

SET R0,#6h ; SET THE DATA BIT - 4

LABEL1:

OUT @R4,R0 ; OUTPUT DATA (CCLK +, SYNC +, DIN ?)-10

RES R0,#4h ; RESET CCLK - 4

OUT @R4,R0 ; OUTPUT DATA (CCLK-, SYNC+, DIN ?) - 10

SET R0,#4h ; RESET CCLK + 4

OUT @R4,R0 ; OUTPUT DATA (CCLK-, SYNC+, DIN ?) - 10

.ENDM

; MAIN LOOPS LOOPS THROUGH ALL THE 4 BYTE WORDS

;S D S C R P N P

;P I Y C E D O R SYNC IS ACTIVE LOW

;A N N L S I O ;R C K E S P ;E T E

IO99_6:

LDLP1:

LD R0,#18h ;0 0 0 1 1 0 0 0 SET SYNC - AND CCLK+ - 7

OUT @R4,R0 ; - 10

LD R0,#08h ;0 0 0 0 1 0 0 0 SET SYNC -, CCLK- - 7

OUT @R4,R0 ; - 10

LD R0,#18h ;0 0 0 1 1 0 0 0 SET SYNC-, CCLK + - 7

OUT @R4,R0 ; - 10

LD R0,#38h ;0 0 1 1 1 0 0 0 SET SYNC+ & CCLK+ - 7

OUT @R4,R0 ; - 10

LD R6,#4h ;SEND A WORD (4 BYTES) AT A TIME - 7

; TOTAL OVERHEAD PER WORD = 75

CLOCKS CYCLES

; INNER LOOP LOOPS THROUGH 4 BYTE PER WORDS

IO99_9:

LDLP2:

LDB RL5,@R1 ;GET FIRST DATA BYTE - 7

INC R1,#1h ;INCREMENT ADDRESS TO NEXT BYTE - 4

; TOTAL = 11

CLOCK CYCLES

OUTBIT LP1 ;CLOCK OUT 8 BITS AT A TIME

OUTBIT LP2

OUTBIT LP3

OUTBIT LP4

OUTBIT LP5

OUTBIT LP6

OUTBIT LP7

OUTBIT LP8

; TOTAL AVE = 416

CLOCK CYCLES

DJNZ R6,LDLP2 ;LOOP UNTIL WORD (4 BYTES) SENT - 11

IO99_C:

OUT CPUOKIOK,R15 ;RESET DEADMAN TIMER - 12

DJNZ R2,LDLP1 ;LOOP UNTIL ALL WORDS SENT - 11

There are four signals involved in loading the DSP:

RLB_RESET- is togged low at the start of the load, but remains high thereafter.

1) RLB_DATA

2) RLB_SYNC

3) RLB_CCLK

4) RLB_RESET-

The RLB_CCLK will continuously oscillate at a frequency of 300KHz minimum during the load. The RLB_ DATA is the serial output bit , clocked with the RLB_CCLK signal.

Once 32 bits have been transmitted the RLB_SYNC line will go low and then repeat the process above of sending another 32 bits. Shown below is a timing diagram for the DSP load process. DX/DR corresponds to the RLB_ DATA, FSR/FSX to RLB_SYNC and CLKX/R to RLB_CCLK signal.

1.1.3 BIT Status Via Serial 15625 baud rate serial

See RLBMessages_abridged.doc for details on message formats. Special baud rate may require alternate RS-232

1. Send 3 byte message – Request Low Band Status (msg 2)

2. Retrieve 9 byte message and display faults (msg 6)

1.1.4 PETIO (Output/Input message Support, via 15625 baud rate serial)

1. Provide GUI and or scripting to send messages. Can be command line based or similar to memory monitor in DTOS.

2. Request data from specified I/O location (msg 4)

3. Receive data from RLB (msg 7)

4. Send Message to output to a specified I/O location (msg 3)

5. Receive acknowledge from RLB (msg 7 or msg 6??)

1.2 Initialization

1. Initialize COM port, baud rate, parity, stop bits

2. Initialize DIO API

3. Configure DIO lines for output

1.3 Load RLB using Digital I/O board

1. Load LBPP via RLB_CLK, RLB_DATA, RLB_SYNC. This includes the entire contents of LBPP page 4 and LBPP page 5.

2. Load Palette via RLB_CLK, RLB_DATA, RLB_SYNC. This includes the entire contents of a compensated palette.

3. Load Active Low band Matrix RLB_DATA via RLB_CLK,RLB_DATA

RLB_SYNC. This is a subset of the matrix data. In BCIII the low band data starts at 0x1200 (from start of matrix) and contains 38 long words (152 bytes). This address and size information can be found in any OFP in u_datbas.z8k in data tables (GVSADT, and GWDCNT)

4. Requires decoding PMF format and extracting data bytes. Data is loaded 4 bytes at a time in the same order they occur in the PFM file.

5. When reading PMF files the file type and file checksum must be tested and verified OK before using the data.

6. The encoded hex data from the PMF files must be decoded into raw binary before sending to the LBPP via the RLB_CLK, RLB_DATA and RLB_RLB_SYC signals.

7. The User should be able to select the files to load and specify address ranges to load.

Data files to load (in expected order)

All files are classified CONFIDENTIAL Sample Filename

(may change) Description Start Address #Words (4 bytes) to send

1 LBP316_PMF LBPP program page 3 0 0x17A2 2 LBP416_PMF LBPP program page 4 0 0x1D2C

3 MDGPAL.PLF Compensated low band Palette file 0 0x0646

Data files to load (in expected order) All files are classified CONFIDENTIAL

Sample Filename (may change) Description Start Address #Words (4 bytes) to send

4 Matrix.mlf Mid/High Matrix data 0x1200 0x0026

1.4 Monitoring

1.4.1 BIT Simulation

At a default rate of 2 Hz send Low Band BIT Status request. Receive the Low Band BIT Status message, and display the low band BIT table. All faults are time stamped and recorded in the log file. See BIT Table Display

Figure 1-1 Sample RLB BIT Status display

The BIT Message rate should be selectable. The user should be able to turn off the

BIT monitoring. Any changes in update rate by the user shall be recorded in the log file.

The user shall be able to specify an expected BIT Status response. This feature will allow the user to specify that some faults/status conditions are expected. Only exceptions from the expected are logged as failures in the log file.

1.4.2 Log File

All detected faults, user directed outgoing messages, and incoming responses shall be time stamped and recorded to a text log file. The log file is not required to record all the automated BIT Status Request and BIT Status Message responses.

1.4.3 CIU Monitoring (Option)

Using I/O read messages the Low Band CIU signals shall be read and displayed.

The update rate shall be selectable and may be disabled by the user. Any change in CIU signal states shall be recorded to the log file. Any change in the update rate or disabling of this monitoring shall be recorded in the log file.