GLAST/LAT >
DAQ and FSW >
FSW >
Doxygen Index >
FBS / V0-0-0
Constituent: fbs_rtos     Tag: linux-gcc
Interface Data Structures File List Data Fields Globals
FBS_load.c.ux-xxx-xxx File Reference
Universal file loader for FSW files (unix implementation). More...
#include "FBS/FBS_msgs.h"
#include "MDB/MDB_pubdefs.h"
Include dependency graph for FBS_load.c.ux-xxx-xxx:
This graph shows which files directly or indirectly include this file:
|
Functions |
unsigned int | FILE_loadModuleByID (unsigned int id, int sym) |
| Load a FSW code module by file ID.
|
unsigned int | FILE_loadModuleByName (const char *nam, int sym) |
| Load a FSW code module by file name.
|
unsigned int | FILE_loadModuleSecondary (unsigned int id, int sym, unsigned int *dat) |
| Load a FSW code module by file ID (special for secondary boot).
|
Detailed Description
Universal file loader for FSW files (unix implementation).
CVS $Id: FBS_load.c.ux-xxx-xxx,v 1.1.1.1 2005/11/04 04:10:57 apw Exp $
- Author:
- A.P.Waite
Function Documentation
unsigned int FILE_loadModuleByID |
( |
unsigned int |
id, |
|
|
int |
sym |
|
) |
|
|
|
Load a FSW code module by file ID.
- Parameters:
-
| id | (in) File ID |
| sym | (in) Symbol loading flag (conventional VxWorks definition) |
- Warning:
- I can find no rationale for providing this functionality in the unix world, so the unix implementation simply (reports) and returns an error.
- Return values:
-
| FPTH_CSBODY | Body checksum mismatch |
| FPTH_IMEMALOC | Cannot allocate memory to read module |
| FPTH_LOADFAIL | Load module failed |
| FPTH_MEMDVCRE | Memory device create failed |
| FPTH_MEMDVOPN | Memory device open failed |
| FPTH_NOOPEN | Cannot open module |
| FPTH_NOTIMPL | Function not implemented (unix only) |
| FPTH_OMEMALOC | Cannot allocate memory to inflate module |
| FPTH_SLURP | File length mismatch |
| FPTH_SUCCESS | Success |
| FPTH_ZLIBFAIL | Inflation failed |
| FPTH_ZLIBINIT | Inflation initialization failed |
|
unsigned int FILE_loadModuleByName |
( |
const char * |
nam, |
|
|
int |
sym |
|
) |
|
|
|
Load a FSW code module by file name.
- Parameters:
-
| nam | (in) File name |
| sym | (in) Symbol loading flag (conventional VxWorks definition) |
- Warning:
- I can find no rationale for providing this functionality in the unix world, so the unix implementation simply (reports) and returns an error.
- Return values:
-
| FPTH_CSBODY | Body checksum mismatch |
| FPTH_IMEMALOC | Cannot allocate memory to read module |
| FPTH_LOADFAIL | Load module failed |
| FPTH_MEMDVCRE | Memory device create failed |
| FPTH_MEMDVOPN | Memory device open failed |
| FPTH_NAMENULL | Module name is NULL |
| FPTH_NOOPEN | Cannot open module |
| FPTH_NOTIMPL | Function not implemented (unix only) |
| FPTH_OMEMALOC | Cannot allocate memory to inflate module |
| FPTH_SLURP | File length mismatch |
| FPTH_SUCCESS | Success |
| FPTH_ZLIBFAIL | Inflation failed |
| FPTH_ZLIBINIT | Inflation initialization failed |
|
unsigned int FILE_loadModuleSecondary |
( |
unsigned int |
id, |
|
|
int |
sym, |
|
|
unsigned int * |
dat |
|
) |
|
|
|
Load a FSW code module by file ID (special for secondary boot).
- Parameters:
-
| id | (in) File ID |
| sym | (in) Symbol loading flag (conventional VxWorks definition) |
| dat | (in/out) Return extra information if error |
- Warning:
- I can find no rationale for providing this functionality in the unix world, so the unix implementation simply (reports) and returns an error.
- Return values:
-
| FPTH_CSBODY | Body checksum mismatch |
| FPTH_IMEMALOC | Cannot allocate memory to read module |
| FPTH_LOADFAIL | Load module failed |
| FPTH_MEMDVCRE | Memory device create failed |
| FPTH_MEMDVOPN | Memory device open failed |
| FPTH_NOOPEN | Cannot open module |
| FPTH_NOTIMPL | Function not implemented (unix only) |
| FPTH_OMEMALOC | Cannot allocate memory to inflate module |
| FPTH_SLURP | File length mismatch |
| FPTH_SUCCESS | Success |
| FPTH_ZLIBFAIL | Inflation failed |
| FPTH_ZLIBINIT | Inflation initialization failed |
FILE_loadModuleSecondary() is a courtesy entry point for use during a fully automated secondary boot. During this period, errors cannot be reported through standard communications channels (because they haven't been brought up yet), so errors are recorded in the boot diagnostics area for later retrieval by primary boot. To refine the error reporting the boot diagnostics allow an extra parameter to be saved. That is what is brought out through this interface. |
Generated on Fri Nov 4 21:09:30 2005 by
1.4.4