Skip to end of banner
Go to start of banner

1. Getting Started with FP/GP-ARM DLL

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

There were errors rendering macro:

  • An unknown error occurred.

When the FPA index is 0 (ALL-FPAs) then almost all functions are executed simultaneously. Less critical functions are executed sequentially from FPA-1 up to FPA-64 but this distinction cannot be seen from the application software. The longest running programming functions, Encapsulated Functions i.e. F_AutoProgram, are all executed fully in parallel. When different configurations are used for each FPA (i.e. if FPA-1 programs 10kB of data and FPA-2 programs 20kB of data) then the Multi API-DLL function call will return when all API-DLL function calls have finished.

When an inactive FPA index is selected (FPA not initialized), then the return value from selected function is FPA_INVALID_NO (-2 or 0xFFFFFFFE). When all FPA has been selected (FPA index == 0) then only active FPAs will be called. For example if only one FPA is active and FPA index == 0, then only one FPA will be used.

All API-DLL instances used by the Multi API-DLL are fully independent with respect to each other. Data transferred to one FPA does not have to be the same as the data transferred to other FPAs. For example, code data programmed using FPA-1 will use the buffers from API-DLL 1, and code data programmed using FPA-2 will use buffers from API-DLL 2. Once the different code buffers are setup, programming can be done simultaneously using FPA index 0 and the function F_AutoProgram. To configure the data buffers shown in Figure 1.8 use Data Buffer Functions

The major features supported by the API-DLL are:

  • Initialize and terminate communication with FPA and target device,

  • Configure settings from file or using functions,

  • Program code data from file or modify code buffer using functions,

  • Return string report message generated for most actions,

  • Reset target device,

  • Program target device ( erase, blank check, program, verify, lock, and unlock ),

    • Erase all or selected part of memory,

    • Blank check all or selected part of memory,

    • Write code file contents,

    • Verify code file contents,

    • Read all or selected part of memory,

    • Lock memory protection bits and debug access (if supported on device),

    • Unlock device to return memory to factory settings (if supported on device).

  • No labels