Inheritance diagram for IMemoryAccess:
The most important functionality that is supported by this interface is the UploadFirmware method. This method can be used to upload a new operating system and/or application into the reader.
The uploading process can never be canceled since that would leave an incomplete OS or Application in the reader, making the reader inaccesable!.
When performing the upload operation asynchronously, the status of the current upload process can be determined using the IsUploading property.
Another method of this object is the IsSystemAreaChecksumOk property which can check if the system area of this reader is valid. If it is not valid, this reader might be a potential source of errors.
Public Member Functions | |
HRESULT | Reader ([out, retval] IProximityReader **ppintfReader) |
Returns the reader this memoryaccess object belongs to. | |
HRESULT | UploadFirmware ([in] BSTR OSFilename,[in] BSTR ApplicationFilename,[in] EFlashArea eFlashArea,[in, defaultvalue(1)] VARIANT_BOOL UploadAsync,[in, defaultvalue(100)] long lMaxNumberOfSteps) |
This function loads new firmware into the Flash memory of this reader. | |
HRESULT | IsUploading ([out, retval] ECollectingStatus *peStatus) |
Returns the status of this reader's uploading process. | |
HRESULT | ReadMemory ([in] EMemoryType MemoryType,[in] long Address,[in] short NumberOfBytesToRead,[out, retval] VARIANT *pvtMemoryBlock) |
Read a block of memory from the EEPROM or Flash memory. | |
HRESULT | WriteMemory ([in] EMemoryType MemoryType,[in] long Address,[in] VARIANT *Data,[in, defaultvalue(0)] VARIANT_BOOL WriteAsync,[out, retval] VARIANT_BOOL *pfSucceeded) |
Write a block of memory to the EEPROM, Flash or Processor memory. | |
HRESULT | VerifyFlashMemory ([in] EFlashArea FlashArea,[out, retval] VARIANT_BOOL *pfAreaOk) |
Verify the flash memory. | |
HRESULT | IsSystemAreaChecksumOk ([out, retval] VARIANT_BOOL *pfSystemAreaOk) |
Returns true if the system area checksum is valid. |
|
Returns the reader this memoryaccess object belongs to.
|
|
This function loads new firmware into the Flash memory of this reader. Use this method to upload a new OS, or Application (or both) into this reader. Since the uploading of new firmware can only be done if the reader is currently in bootloader mode the UploadFirmware method will first make sure the reader is in bootloader mode by resetting it (if it is not already in bootloader mode). It will then start by erasing the flash area where the new firmware should be stored. The next step will be to upload the new firmware. When the uploading process has finished, the reader is reset to activate the new firmware using the IProximityReader::Reset method. This method is capable of uploading a separate OS and/or Application firmware but also capable of uploading a single firmware file (combined OS and application into a single file). When both OS and Application should be uploaded, the following steps are performed:
Steps 2 and 3 will be skipped if no OS needs to be flashed, 4 and 5 will be skipped if no Application needs to flashed. When uploading a single firmware file, first step 1 is performed, then both the OS and Application flash areas are erased, next the entire firmware file is uploaded at once. This method fires the default events of processtype ptUploadingFirmware. During this process a number of sub processes types are executed: /li Step 1 will generate the sptResetting sub process if the reader is in application mode, if the reader is already in bootloader mode, step 1 will be skipped. See IProximityReader::Reset for more information about the events fired during resetting. /li The erasing of the flash areas will generate sptErasingFirmware sub process events. Progress events are also generated during the erasing of the flash area. /li Uploading of the OS and/or the Application generates progress events. Note that both the OS and Application will generate progress events ranging from 0 to 100%. To determine what kind of image is being uploaded, an event sub process started is fired when the OS starts and stops uploading (sptUploadingOS) and one(sptUploadingCPA) when the Application starts and stops uploading. Note that this is only implemented to facility the uploading of old (separate OS and CPA) firmware. /li Uploading a single firmware file will generate only the normal progress events. After the upload process has finished, the reader should be reset to activate the new firmware. Use the IProximityReader::Reset method to do this. When executing the upload process asynchronously, the current state of the upload operation can be determined using the IsUploading property. The contents of the new firmware file must be conform the Intel Hexadecimal Object Format Specification.
|
|
Returns the status of this reader's uploading process.
|
|
Read a block of memory from the EEPROM or Flash memory.
|
|
Write a block of memory to the EEPROM, Flash or Processor memory. The default events of process type ptWritingMemory are generated by this method. This method however, will not fire progress events (since only small amounts of data will be generated, any delay will be neglegible small).
|
|
Verify the flash memory.
|
|
Returns true if the system area checksum is valid.
|