/[PAMELA software]/quicklook/dataToXML/Data/compilationInfo/src/FileManager/MMSUManager/FT_MMSUManager_p.c
ViewVC logotype

Contents of /quicklook/dataToXML/Data/compilationInfo/src/FileManager/MMSUManager/FT_MMSUManager_p.c

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.1.1.1 - (show annotations) (download) (vendor branch)
Tue Apr 25 09:00:20 2006 UTC (19 years, 2 months ago) by kusanagi
Branch: MAIN
CVS Tags: dataToXML1_02/01, dataToXML1_02/00, dataToXML1_03/00, dataToXML1_03/01, dataToXML1_00/00, firstRelease, dataToXML1_01/00, dataToXML1_03_02, HEAD
Changes since 1.1: +0 -0 lines
File MIME type: text/plain
These program extract in an XML format the info contained into the ROOT files generated by YODA from the PAMELA data. To visualize the XML files in a more human readable format a collection of XSL files are given in the Data subfolder.

1 /****************************************************************************
2 /* F i l e D a t a
3 /*
4 /* Module : FileManager
5 /* C.I. No. :
6 /* $Revision: 1.2 $
7 /* $Date: 2004/06/30 07:26:24 $
8 /* Belonging to :
9 /* :
10 /* $RCSfile: FT_MMSUManager_p.c,v $
11 /* Program Type :
12 /* Sub-modules :
13 /*
14 /****************************************************************************
15 /* S W D e v e l o p m e n t E n v i r o n m e n t
16 /*
17 /* Host system :
18 /* SW Compiler :
19 /* $Author: sebastiani $
20 /* :
21 /****************************************************************************
22 /* U p d a t i n g
23 /*
24 /* $Log: FT_MMSUManager_p.c,v $
25 /* Revision 1.2 2004/06/30 07:26:24 sebastiani
26 /* *** empty log message ***
27 /*
28 /* Revision 1.1.1.1 2003/08/04 09:40:21 sebastiani
29 /* Imported sources laben rel. 19.06.2003 integrated with pam2
30 /*
31 /* Revision 1.4 2002/05/09 08:16:34 zulia
32 /* * acceptance release
33 /*
34 /*
35 /*****************************************************************************/
36
37
38 /*============================= Include File ================================*/
39
40 #include <src/FileManager/MMSUManager/FT_MMSUManager_p.h>
41 #include <src/FileManager/MMSUManager/FT_MMSUManager_op.h>
42
43 /*****************************************************************************/
44
45 /*====== M M S U M a n a g e r P R O V I D E D I N T E R F A C E ======*/
46
47 /*****************************************************************************/
48 /* @Function: FT_piInitMMSUManager */
49 /* @Purpose : */
50 /* Provided Interface to initialize the MMSUManager object. */
51 /* */
52 /* @@ */
53 /* @Parameter Name @Mode @Description */
54 /* status_code OUT Return code */
55 /* @@ */
56 /*****************************************************************************/
57
58 status_code FT_piInitMMSUManager (void)
59 {
60 status_code status;
61
62 status =FT_opInitMMSUManager();
63 return (status);
64 }
65
66 /*****************************************************************************/
67 /* @Function: FT_piSndMsgMMSUManager */
68 /* @Purpose : */
69 /* Provided Interface to invoke a specific operation of the MMSUManager */
70 /* task. This is done by sending a message in the MMSUManager mailbox. */
71 /* The sent message has the following structure : */
72 /* Structure -MsgTsk- : */
73 /* Field -Code- Code of the task operation */
74 /* Field -Info- Buffer that contains the task operation parameters */
75 /* Filed -LlInfo- Parameters size. */
76 /* The operations code and the parameters type of the MMSUManager task are */
77 /* the following : */
78 /* */
79 /* Code operation Parameters (Type assigned to -Info- field) */
80 /* @@ */
81 /* @Parameter Name @Mode @Description */
82 /* SndMsg IN Pointer to task message */
83 /* status_code OUT Return code */
84 /* @@ */
85 /*****************************************************************************/
86
87 status_code FT_piSndMsgMMSUManager (MsgTsk* SndMsg)
88 {
89 status_code status;
90
91 status =FT_opSndMsgMMSUManager(SndMsg);
92 return (status);
93
94 }
95
96 status_code FT_piInitFileSystem() {
97 MsgTsk SndMsg;
98 SndMsg.Code = FT_INIT_FS;
99 return FT_opSndMsgMMSUManager(&SndMsg);
100 }
101
102 /*****************************************************************************/
103 /* @Function: FT_piMemBoardMod */
104 /* @Purpose : */
105 /* Provided Interface to handle the Memory Module interrupt raised by the */
106 /* DRAMMA device due to an internal failure. */
107 /* The -MemModule- parameter specify the MMSU and Memory Module where the <*/
108 /* failure is occured. */
109 /* */
110 /* @@ */
111 /* @Parameter Name @Mode @Description */
112 /* Box IN MMSU (MMSU_LOCAL,MMSU_REMOTE) */
113 /* MemModule IN Memory Module (FT_MEMORY_MODULE type) */
114 /* status_code OUT Return code */
115 /* @@ */
116 /*****************************************************************************/
117
118 status_code FT_piMemBoardMod (unsigned int MemModule)
119 {
120 status_code status;
121
122 status =FT_opMemBoardMod(MemModule);
123 return (status);
124 }
125
126
127
128 /*****************************************************************************/
129 /* @Function: FT_piMemModuleON */
130 /* @Purpose : */
131 /* Provided Interface to switch ON a Memory Module. */
132 /* The -MemModule- parameter specifies the Memory Module that must be */
133 /* switched ON. */
134 /* */
135 /* @@ */
136 /* @Parameter Name @Mode @Description */
137 /* MemModule IN Memory Module (FT_MEMORY_MODULE type) */
138 /* status_code OUT Return code */
139 /* @@ */
140 /*****************************************************************************/
141
142 status_code FT_piMemModuleON (unsigned int MemModule)
143 {
144 status_code status;
145
146 status =FT_opMemModuleON (MemModule);
147 return (status);
148 }
149
150
151
152 /*****************************************************************************/
153 /* @Function: FT_piMemModuleOFF */
154 /* @Purpose : */
155 /* Provided Interface to switch OFF a Memory Module. */
156 /* The -MemModule- parameter specifies the Memory Module that must be */
157 /* switched OFF. */
158 /* */
159 /* @@ */
160 /* @Parameter Name @Mode @Description */
161 /* MemModule IN Memory Module (FT_MEMORY_MODULE type) */
162 /* @@ */
163 /*****************************************************************************/
164
165 status_code FT_piMemModuleOFF (unsigned int MemModule)
166 {
167 status_code status;
168
169 status =FT_opMemModuleOFF (MemModule);
170 return (status);
171 }
172
173 /*****************************************************************************/
174 /* @Function: FT_piSavePage */
175 /* @Purpose : */
176 /* This function store the selected SRAM page into the memory module. If a */
177 /* previous storage is in progress than the store request is saved in the */
178 /* store request queue. */
179 /* @@ */
180 /* @Parameter Name @Mode @Description */
181 /* PageId IN ID of the SRAM page to be saved */
182 /* PageInfo IN DAQ write result for the SRAM page */
183 /* FileId IN Destination file */
184 /* FT_SAVE_RESULT OUT Return code */
185 /* @@ */
186 /*****************************************************************************/
187
188 FT_SAVE_RESULT FT_piSavePage(SM_PAGEID PageId, SD_DAQ_WRESULT PageInfo,
189 FS_FILEID FileId)
190 {
191 FT_SAVE_RESULT status;
192
193 status = FT_opSavePage(PageId, PageInfo, FileId);
194 return (status);
195 }
196
197 /*****************************************************************************/
198 /* @Function: FT_piGetCMDWErrorCounter */
199 /* @Purpose : */
200 /* This function returns the number of write errors towards the CMD I/F */
201 /* */
202 /* @@ */
203 /* @Parameter Name @Mode @Description */
204 /* @@ */
205 /*****************************************************************************/
206
207 status_code FT_piGetCMDWErrorCounter(UINT32* Counter)
208 {
209 status_code status = SUCCESSFUL;
210
211 FT_opGetCMDWErrorCounter(Counter);
212 return (status);
213 }
214
215 /*****************************************************************************/
216 /* @Function: FT_piWriteEOT */
217 /* @Purpose : */
218 /* This function is called by the WPBUS EOT interrupt and closes the store */
219 /* of a single SRAM page. If the save requests queue is not empty then the */
220 /* new SRAM page store is started */
221 /* @@ */
222 /* @Parameter Name @Mode @Description */
223 /* @@ */
224 /*****************************************************************************/
225
226 void FT_piWriteEOT(void)
227 {
228 FT_opWriteEOT();
229 }
230
231 /*****************************************************************************/
232 /* @Function: FT_piReadEOT */
233 /* @Purpose : */
234 /* This function is called by the RPBUS EOT interrupt and signals the end */
235 /* of a single sector transfer to the TAM I/F. If the there are some more */
236 /* sector left than a new transfer is started. */
237 /* @@ */
238 /* @Parameter Name @Mode @Description */
239 /* @@ */
240 /*****************************************************************************/
241
242 void FT_piReadEOT(void)
243 {
244 FT_opReadEOT();
245 }
246
247 /*****************************************************************************/
248 /* @Function: FT_piMemModuleStat */
249 /* @Purpose : */
250 /* This function return a 16 bit word containing the status of the memory */
251 /* modules as described in RTF Data Area Layout */
252 /* @@ */
253 /* @Parameter Name @Mode @Description */
254 /* status_code OUT status of the operation */
255 /* PtrModStat OUT modules status word */
256 /* @@ */
257 /*****************************************************************************/
258
259 status_code FT_piMemModuleStat(UINT16* PtrModStat)
260 {
261 status_code status = SUCCESSFUL;
262
263 FT_opMemModuleStat(PtrModStat);
264 return (status);
265 }
266
267 /*****************************************************************************/
268 /* @Function: FT_piChangeAcqMode */
269 /* @Purpose : */
270 /* This function is used to switch between the three possible acquisition */
271 /* modes. */
272 /* @@ */
273 /* @Parameter Name @Mode @Description */
274 /* FT_CHACQ_RESULT OUT Return code */
275 /* mode IN Acquisition mode */
276 /* @@ */
277 /*****************************************************************************/
278
279 FT_CHACQ_RESULT FT_piChangeAcqMode(SM_ACQMODE mode)
280 {
281 FT_CHACQ_RESULT status;
282
283 status = FT_opChangeAcqMode(mode);
284 return (status);
285 }
286
287 /*****************************************************************************/
288 /* @Function: FT_piChangeOpMode */
289 /* @Purpose : */
290 /* The function performs all the operations necessary to switch the system */
291 /* operational status */
292 /* */
293 /* @@ */
294 /* @Parameter Name @Mode @Description */
295 /* FT_CHMODE_RESULT OUT Return code */
296 /* @@ */
297 /*****************************************************************************/
298
299 FT_CHMODE_RESULT FT_piChangeOpMode(MC_STATE state)
300 {
301 FT_CHMODE_RESULT status;
302
303 status = FT_opChangeOpMode(state);
304 return (status);
305 }
306
307 /*****************************************************************************/
308 /* @Function: FT_piModuleTest */
309 /* @Purpose : */
310 /* The function sends a message to the MMSUManager task in order to start */
311 /* the memory module test */
312 /* */
313 /* @@ */
314 /* @Parameter Name @Mode @Description */
315 /* status_code OUT status of the operation */
316 /* @@ */
317 /*****************************************************************************/
318
319 status_code FT_piModuleTest(void)
320 {
321 status_code status = SUCCESSFUL;
322
323 FT_opModuleTest();
324 return (status);
325 }

  ViewVC Help
Powered by ViewVC 1.1.23