Rockwell Automation 6182 SDK - Manual (Page 67)

RAC6182-Specific Extensions to the CE API 4–27
Publication 6182-UM002B-EN-P
return(0);
}
NKDbgPrintfW(TEXT(“card said mem %08x IO %08x\n”),
*(ULONG *)MemSpace,
*(ULONG *)IOSpace);
// done processing interrupt, reenable and wait again
InterruptDone(interrupt);
} else {
NKDbgPrintfW(TEXT(“waitforsingleobject failed\n”));
return(-1);
}
}
}
The functions prototyped in osupdateapi.h are intended for use by system
developers only. Rockwell Automation recommends against and does
not support use of these functions in applications and device drivers.
Methods for updating the RAC6182 operating system software are
discussed in the RAC6182 User’s Manual.
osu_UpdateOSFromFile
Rockwell Automation recommends against and does not support use of
this function.
osu_RemoteUpdateOSFromRAM
Rockwell Automation recommends against and does not support use of
this function.
A RAC6182 has a Windows CE registry which is stored in the RAM of
the device. Since RAM data are valid only while the RAC6182 is
powered on, a persistent backup of the registry is maintained on the
Disk-On-Chip
The Windows CE operating system does not automatically flush the
registry in RAM to persistent storage, therefore if registry settings are
changed by an application, the application should invoke a FlushRegistry
operation to ensure that the settings will persist from one operating
session to another.
Note: Because of the relatively large amount of time required to
flush the registry to flash, it is highly recommended that
applications adding or changing registry information
complete a set of changes before issuing a flush rather than
attempting to flush after every single update.
Functions for OS Update
Function for Registry
Flush