Cyclone Automated Control Package
16
3.6 Typical Usage
Figure 3-1: Typical programming procedure flow chart
Figure 3-1 describes the most common sequence of calls to the DLL after
successfully connecting to the Cyclone unit.
Step 1
:
Initiate programming operations.
“START_execute_all_commands”
carries out the programming operations defined in the stand-alone image stored
on the Cyclone unit. “START_dynamic_program_bytes” allows the user to
manually specify the data as well as the memory address of the programming.
Step 2
: Wait for programming completion. Note that no error checking is
provided by the “check_STARTED_cyclonepromax_status” call. A result of 0 will
be returned even if an error has occurred or if communication with the Cyclone is
lost.
Step 3
: Retrieve the error code from the Cyclone unit to determine if the
programming was successful.