| BEP memory read commands |
In the event of a BEP anomaly, the following BEP memory read / memory dump commands could be of diagnostic use. Consult the MIT ACIS software team (Peter, Jim) as to which areas of memory are of interest and which specific commands should be run. They could be run as part of a CAP, which could also include other existing SOPs, as needed, such as coldboot, warmboot_hkp, etc.
Memory dump commanding is discussed in detail in the ACIS Science Instrument Software User's Guide, Section 3.6
If the only memory dump requested is the BEP EEPROM, there is already an existing SOP, 1.10_V2.2 ACIS Flight Software Dump (MIT, HEAD).
Useful BEP memory dump commands are listed in the table below:
| packetID | Description | cmdSeqNo | CLD filename | CLD checksum | Dump Size | No. of Packets |
|---|---|---|---|---|---|---|
RBROMDUMP1 | Dump EEPROM contents | 00306 | 1A_RB000_196 | 40E372D | 1 MB | 259 |
RB_D_CACHE | Dump BEP D-cache | 02022 | 1A_RBDCA_201 | 80A4095 | 256 kB | 65 |
RB_I_CACHE | Dump BEP I-cache | 02025 | 1A_RBICA_202 | B0A4216 | 512 kB | 130 |
RB_BEPBULK | Dump BEP bulk memory | 04441 | 1A_RB002_189 | B0C352F | 1 MB | 259 |
RBFATALBUF | Dump "FatalBuffer"* | 19518 | 1R_RBFATALBUF | NA | 256 Bytes | 1 |
RB_CTLREGS | Dump BEP & Actel Control Registers | 19792 | 1R_RB_CTLREGS | NA | 48 bytes | 1 |
RB_MONREGS | Dump Mongoose Registers | 19795 | 1R_RB_MONREGS | NA | 64 bytes | 1 |
*RBFATALBUF is a special case command, which dumps a small portion of
BEP bulk memory. The standard patch mostfatal, added in FSW HJK
v60 and uplinked 9/19/23, writes diagnostic information into BEP
bulk memory after a bus crash. RBFATALBUF retrieves that information.
These commands are all in the ACIS tables and the CLD files should be available to the OC/CC on console in the Wayside Control Center.
It is important that each dump command is allowed to run to completion before moving on. If a new memory operation is commanded while an old one is still in progress, the old one will be terminated prematurely and the new one started; the "result" field in the commandEcho packet reporting the new command will containt the value 14 (CMDRESULT_CLOBBERED) to indicate that the previous operation had been clobbered.
The time required to complete each memory dump command depends on the size
of the dump and whether the dump is occurring alongside science
telemetry or not. (Running a large memory dump command in any telemetry
format besides 2 is not recommended.) In the case of the EEPROM dump command,
RBROMDUMP1, the 1 megabyte dump takes 259
bepReadReply packets and about 6 minutes in FMT2 in the absence of science telemetry. Completion of the dump can be verified by
counting bepReadReply packets, waiting until bepReadReply packets stop arriving,
and/or waiting for psci to write out the dump file.
If the science load is still running, confirm that there are no memory dump commands in the time period planned for these BEP diagnostic memory dumps. That includes the dumpSysConfig and dumpHuffman commands that appear as part of the setup commanding of every SI mode.
Related procedures that might be done in conjunction with the BEP memory dumps:
Last updated: 19 Mar 2024 by C. Grant