Home Random Page


CATEGORIES:

BiologyChemistryConstructionCultureEcologyEconomyElectronicsFinanceGeographyHistoryInformaticsLawMathematicsMechanicsMedicineOtherPedagogyPhilosophyPhysicsPolicyPsychologySociologySportTourism






Successful Reply Format

Byte 0 Value 14, indicating Rewrite NAND subcommand
Bytes 1 – 4 32-bit start page number
Bytes 5 – 8 32-bit final page number

Syntax Failed Reply Format

Byte 0 Value 14, indicating Rewrite NAND subcommand
Bytes 1 – 4 32-bit start page number
Bytes 5 – 8 32-bit final page number

 

Operation Failed Reply Format

Byte 0 Value 13, indicating NAND Read Disturbance Test subcommand
Bytes 1 – 4 32-bit start page number
Bytes 5 – 8 32-bit final page number
Bytes 9 – 12 32-bit page number of fault

 

READ FILE (0x07)

The Read File command returns four consecutive bytes of EDAC protected memory from the supervisor processor. The read process is atomic, so that consistent data is always returned. This command is intended for back-compatibility with other NSP devices with 32-bit floating-point file systems. There are two command formats available: short and long. These return corresponding short and long replies. These can be distinguished by their lengths.

Short Command Format



Byte 0 EDAC address divided by 4 (0 – 255)

Long Command Format

Bytes 0 - 1 EDAC address divided by 4 (0 – 65535)

Short Reply Format

Byte 0 EDAC address divided by 4 (0 – 255)
Bytes 1 - 4 EDAC data bytes read from memory

Long Reply Format

Bytes 0 – 1 EDAC address divided by 4 (0 – 65535)
Bytes 2 – 5 EDAC data bytes read from memory

WRITE FILE (0x08)

The Write File command writes four consecutive bytes to EDAC memory. The write process is atomic, so that consistent data is always stored. This command is intended for back-compatibility with other NSP devices with 32-bit floating-point file systems. There are two command formats available: short and long. These return corresponding short and long replies. These can be distinguished by their lengths.

Short Command Format



Bytes 0 EDAC address divided by 4 (0 – 255)
Bytes 1 - 4 Data bytes to write to EDAC memory

Long Command Format

Bytes 0 – 1 EDAC address divided by 4 (0 – 65535)
Bytes 2 – 5 Data bytes to write to EDAC memory

Short Reply Format

Bytes 0 EDAC address divided by 4 (0 – 255)
Bytes 1 - 4 Data bytes that were written to EDAC memory

Long Reply Format

Bytes 0 – 1 EDAC address divided by 4 (0 – 65535)
Bytes 2 – 5 Data bytes that were written to EDAC memory

READ EDAC (0x09)

The Read EDAC command returns bytes from EDAC memory. The read process is atomic. Long and short command formats are available.

Short Command Format



Bytes 0 – 1 EDAC address to start reading
Byte 2 Number of bytes to read. A value of 0 indicates that 256 bytes should be read.

Long Command Format

Bytes 0 – 1 EDAC address to start reading
Bytes 2 - 3 Number of bytes to read.

Reply Format

Bytes 0 – 1 EDAC address where reading started
Bytes 2 – N The data bytes read from EDAC memory

WRITE EDAC (0x0A)

The Write EDAC command writes bytes into EDAC memory. The write process is atomic.

Command Format

Bytes 0 – 1 EDAC address to start writing
Bytes 2 – N Data bytes to write to EDAC memory

Reply Format

Bytes 0 – 1 EDAC address where writing started
Bytes 2 – N The data bytes written to EDAC memory

GO (0x0B)

The Go Code command starts (or terminates) a star tracker sequence. The code is a bitfield, with the following contents:

Bit 0 (LSB) 0: Power off functional processor and detector immediately 1: Power on functional processor and detector immediately
Bit 1 0: Load functional processor software from supervisor flash 1: Load functional processor software from functional NAND flash
Bit 2 0: Power off functional processor and detector when functional processor indicates done, or after timeout 1: Do not turn off functional processor and detector when done
Bit 3 0: Do not send a command to the functional processor 1: Load the compact control structure into the functional processor
Bit 4 0: Do not execute a built-in-test 1: Execute a built-in-test.
Bit 5 0: Reboot the functional processor and then load software into it 1: Keep the functional processor running with whatever software is currently loaded. The timeout timer is reset.
Bits 6 – 7 (MSB) Reserved for future use. Write as zero.

If bit 1 is set the functional processor will load its bootloader from NAND flash (blocks 0, 1, 2 or 3). It will then immediately attempt to load and execute an Application Module image from block 0x8000, exactly as if it had received an INIT 0x00008000 command.

If bit 1 is clear the functional processor will load its bootloader from the supervisor flash. This will take several seconds, and when complete the star tracker will be in maintenance mode. Do not clear bit 1 when bit 3 or 4 is set.

Bit 5 is only valid when the sequence state is “running” or “completed”. If this is not the case, the bit will be considered cleared regardless of its commanded state.

If bit 2 is clear, the functional processor will be powered down after a timeout, completion, or an emergency terminate, whichever comes first.

If bit 2 is set but bit 5 is clear, the functional processor will be powered down by an emergency terminate only.

If bit 2 and bit 5 are set, the functional processor will be powered down if timeout occurs before completion. It will also be powered down by an emergency terminate. If it reaches completion before timeout it will remained powered.

Command Format

Bytes 0 Go code to execute

Reply Format

Bytes 0 Go code that is being executed

 

READ RESULT (0x0D)

The Read Result command is used to read the result structure from the supervisor memory. Short and long commands are available. If a single reply message would not be sufficient to contain the data requested then several messages will be sent back-to-back. The PF bit of the final message will be ‘1’, and all other messages have a PF bit of ‘0’.


Date: 2015-12-17; view: 595


<== previous page | next page ==>
NAND Read Disturbance Test | Short Command Format
doclecture.net - lectures - 2014-2024 year. Copyright infringement or personal data (0.008 sec.)